Twenty pieces crossed this desk in the past seven days, and a single spine runs through them: build the tool, own the evidence, know the age of the file in your hands. Read from Bern, that is not a productivity slogan — it is a sovereignty posture.

←TODAY: In August 2026 the sharpest Swiss engineers are prototyping their own calculations in Grasshopper Python rather than waiting for a vendor roadmap. →3012: By the Zurich-3012 horizon the offices that survived are the ones whose workflows opened in any browser long after the .rvt went dark. Fulcrum: A tool you built is a tool you can still audit, migrate, and answer for — which is the whole game.

Top stories:

The week’s centre of gravity is the build-your-own-tools thread, converging on BSS Title Edition XIV (opens 1 September 2026). Sebastian Lieb’s “place of truth in Grasshopper” wires Archicad, Rhino/Grasshopper, RFEM and Excel so one design change propagates instead of costing a week of re-entry — a workflow you build, not buy. Days later, Camilla Seidler and Peter Steiner of Pirmin Jung showed the same instinct at structural scale: form-found timber loads and in-house façade analysis written because Swiss software never shipped them. Two independent desks arriving at the same conclusion in one week is not coincidence — it is a market signal.

Terafab put the ceiling on that ambition. A building sized for 1 TW of compute is really a cooling machine wearing a factory, where the heat load — not the floor area — decides whether a site is even physical. The practical lesson lands squarely on procurement: size the heat rejection before the square metres, and insist on open protocols (BACnet, Brick, Haystack) with a local fallback, so your building can still feel itself when the vendor cloud goes dark. That clause is the data-residency argument in HVAC clothing.

Graphisoft’s open collaboration layer — previewed at AIA San Diego, built on IFC, BCF, PDF, DWG and RVT — promises a synchronised common source of truth. For a 14-person studio the real test is verification, not the demo: run one deliberate IFC round-trip and diff the element counts by class before you route a live project through anything new. Meanwhile the Betuwe story from the Twente team quietly rewrote the geotech budget: 170 Sentinel-1 scenes plus a national LiDAR pass mapped millimetre-scale settlement across 975 m of live freight corridor without dispatching a survey train. Free, standing, European data — pull the Copernicus archive for your own footprint before you fix the foundation transition detail.

Signal vs. noise: Genuinely new this week was the commons reframing — Betuwe’s InSAR archive and Japan’s 80,000-hour robot-data bet both asking the same openBIM question the AEC world already argues over: is the dataset you hoard a competitive asset, or a commons you’d be stronger pooling? The noise was greener. Barnabas Calder’s Rotterdam Rocks! critique (via Dezeen) is the necessary cold water: greenery on a €240 million, aviation-dependent new-build is a communication about sustainability, not a measure of it. Price the null option — the tCO₂e avoided by retrofitting the nearest viable building — and make the client sign next to it.

Hidden gem: Pigeon, the deliberately slow messaging app, deserved more than its novelty framing. Its real lesson is provenance: your model was never a live feed — it is mail with a postmark. Print the IFC export timestamp on every sheet that reaches site and read IfcOwnerHistory before you trust a file. In a week obsessed with synchronised truth, the quietest app made the sharpest accountability point.

Hack: Own the evidence of what a sync dropped — count IFC elements by class yourself, before and after any round-trip, so the diff is yours and not the vendor’s demo. IfcOpenShell reads it in four honest lines:

import ifcopenshell
from collections import Counter
f = ifcopenshell.open("round_tripped.ifc")
print(Counter(e.is_a() for e in f))

Run it on the export and the re-import, subtract the two Counters, and read only the classes that changed. That table is the evidence you own — the same posture Lieb, Seidler and Steiner are teaching at the tool level, applied to the file you actually ship.

Looking ahead: All eyes on 1 September, when BSS Title Edition XIV opens and both the Lieb and Seidler/Steiner sessions land. Watch whether Graphisoft’s collaboration layer moves from AIA preview to a version small studios can actually verify, and keep an eye on Copernicus — the free-satellite-baseline pattern that carried Betuwe will not stay a rail story.