GLOBAL ARCHITECTURE DISCOVERYAn independent architecture index

GAD / DESIGN READING

Building-Diffusion: ask what the graph keeps fixed

A board covered with different building forms can suggest a broad design search. The more revealing question is which relationships were allowed to change. A change in visible form does not by itself explain which computational constraints were…

GAD Editorial · Published · · English study · Chinese summary · Study dated 2026-10-05

A board covered with different building forms can suggest a broad design search. The more revealing question is which relationships were allowed to change. A change in visible form does not by itself explain which computational constraints were retained or which spatial relationships have changed.

Building-Diffusion makes that distinction unusually explicit. Published in the June 2026 CVPR workshop proceedings, the research describes a conditional discrete diffusion method for node attributes in building-layout graphs. It encodes a programme graph and generates voxel labels while keeping graph structure fixed. The authors evaluate the method on the Building-GAN dataset. This is published research, not evidence of a released architectural product. The proceedings entry says code and pretrained models will be released; their current availability has not been independently established here. Official paper record

Separate the diagram from the variation

A fixed computational graph and the adjacency of the final occupied spaces are different levels of description. The former should not be taken as proof that every spatial relationship is identical across outputs.

For a hypothetical mixed-programme concept, GAD proposes two short lists before reviewing generated options. The first records inherited assumptions: the relationships represented by the input, the available categories and the spatial resolution used. The second records what the generation may vary. Do not assume that an appealing output has reconsidered a relationship held constant by the representation.

Translate the lists into architectural questions. Is the team testing how an agreed arrangement can be expressed, or deciding whether that arrangement is appropriate? The former can benefit from variations inside a fixed framework. The latter needs a comparison between frameworks as well as their generated alternatives.

This separation also improves a workshop. Present the input diagram beside every option group. A reviewer can then ask whether a proposed service relationship is encoded in the brief, produced through labels or left to later design work. Check the representation before claiming that this relationship was held fixed.

Count meaningful alternatives

Compare candidates using the decisions the project actually faces. A different allocation or shape matters when it changes a relevant relationship, usable volume or opportunity for further development. Avoid treating every new image as an equally distinct design idea.

Preserve failed and repetitive candidates in the evaluation record. They reveal where the representation constrains the search and where the generation adds useful variety. If a designer changes the generation conditions, begin a new comparison group so the contribution of that decision remains visible.

The next design stage requires its own tests. A graph relationship cannot establish a workable doorway, sufficient circulation, a structural system or compliance with project requirements. Develop a shortlisted arrangement through conventional dimensional and specialist review rather than enlarging a diagram directly into a building promise.

Make the boundary useful

GAD has not executed the research implementation. Its immediate value for practice is a more precise vocabulary for evaluating generative tools. Ask what is generated, what is inherited and what remains outside the model. A productive concept exercise makes those boundaries understandable enough that the designer can deliberately change the right one.

Continue exploring