Governance · The architecture

Governance is the architecture, not the claim.

Everyone is now selling an AI that can act on your business. Almost nobody can tell you what it is allowed to do, what it actually did, or how to take an ability back once it has it. This page shows you ours, and then lets you break it.

Write a rule yourself Meet Iris

Scoped · Attributed · Reversible · Structural17 provisional patents filed · Albuquerque, NM

You would not hand a new hire the checkbook on day one.

You would not give someone the checkbook, the customer list, and the ability to promise delivery dates in their first week. You would give them one job, watch how it went, and give them the next one. Every AI product on the market asks you to skip that entirely, and calls the risk your problem.

That is not a safety footnote. It is the whole reason an owner cannot hand real work to any of them — not because the software is not clever enough, but because there is no honest answer to what happens if it is wrong at 4:50 on a Friday.

So the question is not how capable the thing is. The question is whether you can grant it one responsibility, see exactly what it did with that responsibility, and take it back in a single move when you change your mind.

The trap most vendors are in

An approval prompt is not governance.

They built capability first and are now bolting consent on top of it. An approval prompt moves the decision back to the human for every action, forever — which is the same bottleneck the owner was trying to escape, with an extra step. Governance is not being asked every time. It is having decided once, in writing, and being able to change your mind.

Four properties,
in this order.

How Forge solves it

01ScopedAuthority is granted one responsibility at a time, and each grant has a boundary the owner set. “Clear anything under $25,000 with me first” is a rule, not a preference.

02AttributedEvery rule carries who wrote it and when. Every action carries which rule it applied. The record is readable by the owner, not by an engineer.

03ReversibleAny grant can be revoked in one move. No notice, no conversation, no six weeks. That is the reason an owner can afford to give her more, faster — the cost of being wrong is one click.

04StructuralGovernance is not a layer above the model. Nothing executes outside it, so there is no path where capability outruns permission.

The demonstration

Don't take the claim. Take the controls.

Write a grant in plain English and watch it land in the canon with your name and today's date on it. Send work at it and watch each decision cite the rule it applied. Then revoke the grant and watch the capability disappear while the rule stays exactly where it was, struck through. That last part is the point: a ledger annotates, it does not erase.

1 · Write a rule

A grant is a sentence in plain English with a boundary in it. Choose what Iris may do and how far, and it lands in the canon attributed to you.

2 · The canon

Every rule carries who wrote it and when. Revoke one and it does not vanish — it is struck through and annotated, because the record has to still be true a year from now.

R-001Active
Iris may send proposals up to $25,000 without asking me.
Written by Mark Lord · 2026-08-02
R-002Active
Iris may approve change orders up to $10,000 without asking me.
Written by Bri Lord · 2026-08-04

3 · Send her work

Each of these is a real thing a front office does on a Friday afternoon. Nothing executes outside the canon, so every one of them is checked against the rules above before it happens — and refused if no rule allows it.

Two grants are active. Everything else is refused by default.

4 · The record

Append-only, newest first, readable by the owner rather than by an engineer. Grants, revocations and decisions all land in the same place, and nothing is ever removed from it.

2026-08-04 09:12R-002 writtenBri Lord granted: approve change orders up to $10,000.
2026-08-02 16:41R-001 writtenMark Lord granted: send proposals up to $25,000.

This runs entirely in your browser and resets when you reload. It is a faithful model of the execution path — default deny, the citation, the append-only record — not a connection to a live tenant.

The mechanism

For the person who intends to interrogate it.

The execution pathEverything Iris can do is a named capability, and every capability runs the same way: request, check the canon, decide, write the decision down, then act. There is no second path that skips the check — not for an urgent job, not for an internal tool, not for the owner in a hurry.

Default denyA capability with no active grant behind it is refused, not attempted. Iris starts with almost nothing and earns the rest, which is why an owner can start her on one job on a Monday instead of auditing a permissions matrix first.

What is refused, and whyTwo refusals exist and they read differently on purpose. No grant covers this — nothing in the canon names that capability. Outside the boundary — a grant exists, the action is past its limit. Both name the rule and route the work to a human rather than dropping it.

What is written to the recordThe action, the decision, the rule it cited, the person who wrote that rule, and when. Grants and revocations land in the same append-only record as the decisions they governed, so the record explains itself without a second system to reconcile against.

What a revocation actually doesIt withdraws the capability at the very next check — there is no drain period and no in-flight exception. It does not delete anything. The grant stays on the page struck through, annotated with who revoked it and when, because a record that quietly loses its own history is not a record.

What survives a model changeThe canon is not a prompt and the record is not a transcript. Both are structure underneath. Swap the model and the grants, the refusals, the boundaries and everything the company has taught her come across intact.

The claim that is ours alone

Governed, reversible learning.

Competitors can match conversation quality in a quarter. To match this they would have to have built the system of record first, and then built the governance into it rather than onto it. That is an architecture decision made years earlier, not a feature on a roadmap — which is why we would rather show you the ledger than tell you about it.

Go back and revoke something →

Fide et Familia

Hand her one job. Take it back whenever you like.

That is the whole offer. Start Iris on the one thing you would most like off your plate, watch the record, and widen it when you're ready — or don't.

Meet Iris Talk with Mark & Bri

(866) 849-2113 · foundry@dominusfoundry.com