Seven days. Twenty pieces. One control mechanism running underneath nearly all of them: ownership — who holds the file, the signing key, the exit clause. This desk reads consent flows for fun. This week the whole wire read like one.

←TODAY: In 2026 the format tax, the vendor cloud, and the procurement default are the three quietest line items in every AEC budget. →3012: By the Zurich-3012 horizon, a building that cannot prove what it claims — or reopen its own files — is condemned, not upgraded. Fulcrum: Lock-in is invisible on entry and total on exit; the only leverage you keep is the clause you wrote before you signed.

Top stories:

Zoning as Code (score 95) was the week’s strongest move, and the most political. Treat the envelope as Layer Zero — a named parametric solid carrying setback, height, FAR, solar access — and the ordinance becomes a function you re-run. The control mechanism it exposes: when the rule is a default you can recompute, daylight and street life stop being externalities you regret and become parameters you priced. Read it, then model your hardest parcel.

Second, BIMnopoly named the tax out loud. AECmag’s piece and the Admares + ABB factory story are the same argument from two ends: physical-AI fabrication may erode the schema lock-in that BIM vendors have monetised for two decades — but only for offices whose IFC actually carries machine-readable semantics. The robot reads your model directly, so a sloppy property set stops being a coordination note and becomes a production fault. Harden the handover contract in the BEP now: which objects are machine-readable, at what LOIN, who owns each property.

Third, My BMS Wants an LLM drew the boundary I would deploy tomorrow. An LLM that writes building-control code is only safe if every command passes a per-operation, content-bound token, verified against simulation and hard device bounds before it reaches a relay — and the signing key stays local. That is not a feature. That is the difference between a 25-year-old facilities tech who can override the machine and a vendor cloud that goes dark with your plant behind it.

Fourth, PAZ-BOX made the payback legible: CHF 574/year Premium, CHF 974/year Business, eight Archicad Add-Ons on one floating licence. The point is not the sticker. It is the query you should run before any renewal — cost over hours-saved-times-rate — and demand a number under 1.0.

Fifth, CORTEX closed the governance loop: a trustworthy AI verdict must carry its evidence chain, replayable, so a human can overrule it on the merits. A building that cannot cite the sensor readings behind its own alarm is a building you cannot safely automate.

Signal vs. noise: The genuine signal was one phrase repeated across unrelated desks — draw your dependency graph. Graphene in the mixer, CLT from forest to press, AionDB folding three databases into one Rust process: each carries real leverage and a matching single point of failure. The noise was Klaus, your five-minute AI employee. It does exactly what it promises, which is the problem — convenience that hides topology. “We handle it” is a dependency you no longer control. Map it before you wire it into your inbox.

Hidden gem: Seaborn (score 33) deserved more attention than its number suggests. It is the cheapest integrity tool in the stack — a declarative layer that couples a figure to the statistic it claims to show. In a week about auditability, the quietest lesson was the most prosecutorial: plot the distribution, not the mean, and let the spread carry the argument. The library is a governance instrument in disguise.

Hack: Score every tool renewal on one number before the sales call. Run the payback ratio in SQL against your own billing — a licence only earns its place if it clears 1.0.

SELECT tool,
       annual_cost / (hours_saved_per_year * billing_rate) AS payback_ratio
FROM   tool_licences
WHERE  active
ORDER  BY payback_ratio DESC;   -- anything > 1.0 is renting, not earning

Any row above 1.0 is a default you are paying to keep. That is the whole audit.

Looking ahead: Watch the AI-fabrication handover contracts — Admares + ABB will force the LOIN question that competition models have dodged for years. Watch whether local-fallback stacks (own the weights, hold the file) move from hobby to policy. And bring the payback query to the PAZ-BOX session; let the suite earn its number to your face.

Sources & Further Reading

• Primary: arXiv — content-bound tokens for LLM building control
• Reinforcing: AECmag — BIMnopoly: the format tax