Subject
The documentation gap.
Enterprise AI systems operating without governance record.
Aug 2026 — four months
EU AI Act enforcement.
Nobody knows what their AI is allowed to do.
An architecture design workbench where the diagram you draw is also the governance record — no separate documentation pass, no PDF that goes stale the day it's exported.
Position
Governance should be a property of the design, not a layer bolted on afterward.
The design is the deliverable.
Every architecture team already has diagrams — in Lucidchart, Miro, draw.io. They get exported to PDF once, attached to a compliance document, and left there. Six months later the system has changed twice and the diagram hasn't.
What a regulator actually asks for is more specific than a picture: which models are deployed where, what authority each component holds, where a human has to sign off, and what data classification moves across each connection. Those are questions about the system itself, not about a drawing of it.
Treating the design as the record means every component you place declares its authority, the data it touches, and when a human needs to be involved — not just its shape. Once that's true, the diagram and the documentation stop being two separate things.
In the field
Most enterprises keep their AI architecture in three different places — a diagramming tool, a Confluence page, a risk register — and none of them talk to each other.
What this is not
Lucidchart, Visio, and LeanIX all produce documents about your system. ModelAIr produces a record of it.
Status
Beta · Invite only
Capacity limited
For architects under governance pressure.
Built for architects, not curious observers.
If you're under pressure to produce AI system documentation that doesn't exist yet — for the EU AI Act, an internal audit, or a board that wants answers — get in touch.