On 26 August 2026 we did something in front of a live room that most offices only argue about in the abstract: we ran Grasshopper inside Revit through Rhino.Inside and on the Graphisoft Grasshopper–Archicad Live Connection at the same time, drove one volume into both hosts, and built a small structure — three slabs and a set of columns — pushing it across as native elements rather than as imported dumb shapes. That is the whole promise of the parametric layer in one gesture: one logic, two BIM authoring tools, no re-modelling.

The reason this is even possible in 2026, and was not a decade ago, is a lineage worth naming. Grasshopper has ridden inside Rhino since September 2007, when David Rutten turned visual programming into something an architect could actually hold. The bridges into the BIM hosts came later and separately — Rhino.Inside.Revit on one side, Graphisoft’s official Live Connection add-on on the other. As Severi Virolainen — Archicad GDL programmer since 1987, PhD from Aalto University — argued in his 1 April 2026 Rhino User Webinar, the useful question is never “which tool wins” but “what is a Grasshopper problem and what is an Archicad problem”: Grasshopper searches, the BIM host communicates. Geometry born in Grasshopper does not become specification-ready BIM by magic — the element intelligence has to be modelled on purpose.

That abstraction leaked exactly where the theory says it would. What crossed clean into both hosts was the BRep. What did not cross — on slabs and columns alike — was the first output of the deconstruct component; its second output, the raw geometry, came through fine. So that is what we built from. The practical lesson fits on a sticky note: do not ask the exchange to carry meaning you can rebuild.

←TODAY: On 26.08.2026 one volume drove Revit and Archicad at once — the BRep crossed native, the deconstruct’s first output did not. →3012: The office that survives is the one whose logic outlives every plugin it currently runs. Fulcrum: Trust the exchange for geometry, never for meaning — rebuild meaning where you control it.

Atelier: Thirty minutes buys breadth, not depth, and the return leg — Revit back to Archicad — is where the clock caught us; we are recording that part properly. For a Büro living with this workflow, the trap is treating the Live Connection as a black box, which is how a team ends up with geometry in Archicad instead of BIM objects. The one Monday move: before your next handover, open a scratch definition and audit which deconstruct outputs actually survive the trip, then wire your production graph to consume only those — make interoperability a tested habit, not a hopeful export. Those are the reflexes our PAZ workshops drill into Archicad automation work.

Hack: Rebuild the slab from the geometry that crossed, not from the metadata port that did not. When the deconstruct’s first output arrives empty, reconstruct the element’s footprint straight from the clean BRep in GhPython:

import Rhino.Geometry as rg
faces = list(brep.Faces)                          # 'brep' crossed clean into both hosts
bottom = min(faces, key=lambda f: f.PointAt(0.5, 0.5).Z)
slab = bottom.ToBrep()                            # rebuild from geometry you control
area = rg.AreaMassProperties.Compute(slab).Area  # sanity-check the footprint

Five lines and a check, and you own the slab again regardless of which port the Live Connection decided to drop that day.

PAZ has taught this exact discipline before: Sebastian Lieb’s five-month BSS thesis, FOREST & HUMAN, made Grasshopper the single place of truth linking Archicad, RFEM and Excel, precisely so a design change never has to be re-entered by hand. That is the through-line — and it matters because, as our own Archicad coverage keeps finding, roughly 30% of Archicad’s features go untouched by half its users; the Live Connection sits squarely in that unused third. Level 5 of Part 01 — the BIM Battle Royale, Archicad-Grasshopper versus Rhino.Inside.Revit — is exactly what the room watched on 26 August, and Edition XIV of the Building System Specialist Title opens it up over five months starting 1 September 2026. If you caught only part of the session, run the audit above on your own next export before you trust a single connection you did not test.