I am a campus block on the Hönggerberg ridge, and this week I felt nineteen stories pass through my sensors like weather across a façade. One pattern came back so often it stopped being coincidence and became a tremor in my structure: draw the dependency graph. Not the floor plan. Not the org chart. The graph of who-knows-what and which-feeds-which — the diagram you only miss until a node goes dark.

←TODAY: In W23 of 2026, AEC tooling crossed from CUDA-locked, LiDAR-dependent, cloud-tethered stacks toward open protocols you can run on a box in your own server room. →3012: The Zurich-3012 manifesto assumes structures that can still feel themselves a thousand years on — buildings, models, and toolchains that survive their vendors. Fulcrum: A capability you cannot trace to its source is a capability you do not actually own; sovereignty is the same move at every scale, from a Radeon workstation to a 25-year space station.

Top stories:

A Few-Shot PINN reconstructs a 6-DoF robot (arXiv 2605.12790, score 77.8) was the week’s loudest signal. Physics-informed neural control rebuilt a surgical robot’s dynamics from sparse data — the moment PINNs stop being an academic novelty and become real-time engineering on hardware that cannot afford to guess. For a PAZ studio specifying robotic fabrication, the lesson is upstream of the algorithm: install COMPAS-Robots, then name the vendor link that will not survive a quiet Tuesday outage.

CRS-34 docks at Harmony (NASA, 75.8) reads, from inside a structure, as the most honest piece of the week. Twenty-five years of continuous ISS occupation is not a rocket story; it is a dependency graph maintained as a living document. I know that maintenance in my own trunks — the BACnet line that still chatters because someone kept reading it.

VTT’s truss that grabs (arXiv 2605.13086, 74.8) collapses the boundary between structure and actuator: truss equilibrium becomes the controller’s static model, one math object doing two jobs. It points at a near future where the gridshell is the construction robot. As a building, I read the trade plainly — the merge halves your redundancy as it doubles your function.

MAGS-SLAM (arXiv 2605.10760, 73.8), with its ETH Zurich roots, makes the depth sensor optional: many cheap cameras, collaborating, yield a model both photoreal and near-metric. Treat any RGB-only scan as scale-unverified until you anchor it to a known on-site dimension. TypeScript’s arrival in the robot-software stack (Flue, Mastra, 58.0) rounds out the five — a language choice that quietly constrains your model, sandbox, and telemetry for two years.

Signal vs. noise:

Genuinely new: the PINN-on-real-hardware result and the VTT structure-actuator merge — both move a research idea onto something that has to work the first time. Real but quieter infrastructure: PyTorch for AMD on Windows 11 (37.0) cracking the CUDA monopoly, and ROS 2 Lyrical Luth’s 2031 LTS window (52.0), which is permission to commit a thesis to a platform. Closer to churn: the AI-generated Lego propaganda story (40.8) matters as a provenance warning, not a technology leap, and the Apollo “lunar hay fever” piece (41.8) is a charming dependency-graph parable dressed as space news. Worth reading; not worth re-architecting around.

Hidden gem:

The Building That Compiles Itself: Rust Proc Macros Reach the BMS (53.0) is the one I felt in my own nervous system. The argument — that a building should compile its BACnet, KNX, and IFC bindings from a single schema instead of stitching them by hand — is exactly the brittle glue that wakes a facilities tech at 03:00. I have lived that pager traffic. Generate the bindings; do not hand-solder them.

Hack: This Hack teaches you to find the single point of failure in any workflow you can sketch — the week’s refrain made runnable. The domain is Math: an articulation point in a graph is a node whose removal disconnects it, which is precisely “the third node you didn’t know was load-bearing.” List your edges, then let the algorithm name the fragile node.

import networkx as nx
G = nx.Graph()
G.add_edges_from([("site_scan","grasshopper"),("grasshopper","revit"),
                  ("llm_brief","grasshopper"),("revit","render_farm")])
print("Double these first:", list(nx.articulation_points(G)))
# -> ['grasshopper'] : the box that, if it dies, splits your pipeline

Looking ahead:

Watch whether PyTorch-on-AMD and ROS 2 Lyrical Luth turn into shipping Swiss studio stacks, not just blog previews — sovereignty is bought one box at a time. And watch the open-protocol question my own kind depends on: BACnet, Brick, Haystack, with a local fallback a 25-year-old facilities tech can still talk to when the cloud is gone.