A paper landed on arXiv in late August that most offices will never read, and it explains the deal most offices should be reading about. In “Generation of High-Level Concepts in 3D Scene Graphs via Autoregressive Diffusion” (arXiv 2608.28733, 28 August 2026), Jose Andres Millan-Romera and co-authors at the University of Luxembourg take the rawest thing a scanner produces — observed vertical planes, walls without names — and generate, in a single diffusion pass, the hierarchy above them: this plane belongs to that room, that room to this floor, this floor to that building. No hand-written rules, no separate model for structure and one for position. And it works on real architectural floor plans, not just synthetic scenes and robot logs.

Read that carefully, because it names the asset. The point cloud is a measurement. The scene graph — rooms, adjacencies, the semantic hierarchy — is an interpretation. Interpretations are what a practice sells. The frontier just showed that the interpretation can be manufactured from the geometry automatically, which means the geometry alone is no longer the valuable part.

←TODAY: On 30 July 2026 Procore agreed to buy DroneDeploy for ~$845m cash — and with it ~20 trillion sq ft of visual data, tens of millions of annotations, and 100,000+ documented safety issues. →3012: By the Zurich-3012 horizon the record of a site is a living graph, and the office that can’t export its own copy is a tenant on its own project. Fulcrum: The moment capture becomes native to a platform, the question stops being “should we scan” and becomes “where does the record live, and what comes back out.”

Here is the honest half first, because the piece is worthless if it pretends otherwise: the platform version does the job better than any 14-person studio does it alone. One login instead of five, one support contract, capture that lands in the model instead of on a hard disk in a drawer. Ajei Gopal of Procore frames the purchase as “digital coworkers”; DroneDeploy’s Mike Winn calls it making reality capture “a native part of how construction teams work, not an add-on tool,” as Construction Management reported. Both are true. The 100,000 documented safety issues are the tell — somebody’s site engineers wrote those, and that human judgement is now training substrate.

So the awkward question for our side of the desk is narrow: what leaves the studio in someone else’s account, and what does the export actually produce? A squad that keeps its own playbook survives a change of manager; the one renting the manager’s tactics doesn’t. Same for a practice and its site record.

Atelier: Switzerland already has the contract instrument for this, and most offices haven’t re-read it. Merkblatt SIA 2051 was withdrawn at the end of 2024 in favour of the SN EN ISO 19650 series — so if your BEP template still cites 2051, it points at a dead document. SIA 1001/11:2018, the BIM-Vertragszusatz, is where data access rights, backup obligations and Datenschutz get written down. Your one Monday move: open your current BEP and check which standard it references — if it says SIA 2051, that is this week’s fix, before any tool decision.

Hack: Run the export, don’t read the docs about it. Take one finished project, export the capture and annotations to IFC, and open it with nothing but the software you own — then count what survived. Point IfcOpenShell at the file:

import ifcopenshell
m = ifcopenshell.open("site_export.ifc")
spaces, annots = m.by_type("IfcSpace"), m.by_type("IfcAnnotation")
print(len(spaces), "rooms", len(annots), "annotations")
print([s.Name for s in spaces[:5]])

If the rooms come back unnamed and the annotations come back empty, the graph didn’t survive the round-trip — you exported the measurement, not the interpretation. That afternoon is the whole audit. If you want the same check to live inside your model rather than in a script, PAZGPT and the native PAZ Archicad add-ons let you interrogate room stamps and GDL objects without leaving Archicad automation you already run.

PAZ Takeaway: Own at least one capability that matters and maintain it yourself — a documented export-and-archive routine that runs at every project close, or the studio’s own annotated detail library. PAZ’s home ground here is exactly that seam: a maintained Grasshopper↔Archicad Library and Graphisoft-native tooling that keep your site record readable in software you control, so the interpretation stays yours whoever owns the platform.

This quarter, do three things: name the account holder on every live project (whose subscription holds the record — client, Generalplaner, contractor, or you), write the exit clause into SIA 1001/11 before the next entry, and run the IFC export above on one closed job. Know on paper which of your capabilities you own and which you rent.

Source: Construction Management + arXiv 2608.28733