What is governance before execution?

Governance before execution means authorization, policy validation, and scope enforcement are preconditions for an autonomous agent to act, rather than runtime suggestions or retrospective audits. If an agent cannot satisfy the permit, it does not run.

What is the Builder's Permit?

The Builder's Permit is a deterministic authorization model that treats autonomous systems the way regulated construction is treated. No execution without a named issuing party, a defined scope, an expiry, an inspection gate in the execution path, and a durable record.

Why does local-first execution matter for AI governance?

A record held by a third party is a record a third party can edit, delay, or lose. Local-first execution keeps the authorization evidence with the operator, which matters for regulated industry, defense adjacency, and any sovereignty requirement.

Governance Before Execution | AI Agent Authorization Framework

field: the invariant

Separate the thinking from the doing

A model is probabilistic by design and that is exactly what makes it useful. Execution cannot be. The architecture puts a deterministic boundary between the two, so that inference proposes and a governed layer disposes. That boundary is not advisory and it is not circumventable by the model that sits behind it.

PRECONDITION

Authorization is checked first

Before an action reaches anything real, the layer resolves who issued the authority, what scope it covers, and whether it is still valid. A failed check is a refusal, not a warning written to a log somebody reads next quarter.

DETERMINISM

Same inputs, same decision

Reproducibility is not a performance target here. It is the precondition for holding anyone accountable, because a decision you cannot reproduce is a decision nobody can be held to.

ARTIFACT

Evidence written before the act

Every material action produces a cryptographically verifiable, replayable record, written ahead of execution rather than reconstructed after it. The artifact does not depend on model internals or on any vendor's infrastructure to be read.

LOCALITY

The operator holds the record

Execution is local-first with no cloud dependency. A record held by somebody else is a record somebody else can edit, delay, or lose. For regulated industry and anything with a sovereignty requirement, that is the whole procurement conversation.

field: standards

The four that do not move

Authorization

No agent acts without an issued permit naming an owner, a scope, and an expiry. Permissions are granted rather than inherited, and they do not accumulate quietly over time.

Determinism

Same inputs, same decision, every time. Nondeterminism is confined to inference and never reaches the execution path.

Evidence

Every material action leaves a durable, timestamped record that outlives the session that produced it. If it was not recorded, it did not happen.

Revocation

Authority granted has to be authority withdrawable, immediately, without a redeploy. A permission you cannot pull back is not a permission. It is a transfer of control.

field: what it produces

An artifact somebody else can verify

The output is the point. When an incident happens, the difference between an afternoon and a week is whether the authorization record already exists or has to be assembled backward out of whatever logs happened to survive.

Issuing party. A named human owner, resolvable at the time of action rather than inferred afterward.
Granted scope. What was permitted, written before execution, with everything outside it refused at the boundary.
Decision trace. The inputs, the policy evaluated, and the result, replayable to the same outcome.
Cryptographic digest. Integrity that a third party can check without trusting the party that produced it.
Expiry and revocation state. When the authority ended and whether it was withdrawn before it did.
Independence. Readable without access to model weights, vendor tooling, or a proprietary console.

field: provenance

The date is the claim

Over the next ninety days nearly every vendor in this category will announce a governance layer and some will describe theirs as the first. Authorship is settled by dates and records. It is not settled by announcements.

Development Record

FiledTwo USPTO provisional patent applications covering the architecture and the governance model.

CompletedGovernance layer finished November 2025. Unchanged since.

PublishedGovernance Before Execution: A Deterministic Reference Architecture for Auditable Autonomous Systems.

MethodCryptographic digests and third-party timestamps on every material revision, kept from the beginning.

OriginCharlotte, North Carolina. Independent. No institutional funding.

A governance layer announced after the failure it would have prevented is a marketing decision. One specified before it is an invention. The entire difference sits in the dates, and dates are the one artifact that cannot be back-filled.

Governancebefore execution.