01Understand
Start with the real state.
Define the request, scope, constraints, and evidence available before an agent prepares an action.
requestscopeconstraint
A11 / controlled intelligence infrastructure
Build at the frontier.Operate on evidence.
A11 gives agents room to move quickly while keeping consequential work reviewable, versioned, and controlled.
Owner-controlled
Evidence-led
Fail-closed by design
Release gate / example record
Evidence before promotion.
06moves
Repository stateSource and revision are identified.
Verified
Runtime stateRemote configuration is not assumed.
Pending
Release decisionPromotion waits for the next gate.
Blocked
01 The system shows what is known, what is missing, and who decides next.
A11 / 01Capability and certainty are different things.
01Observe
Separate the current state from the proposed state.
02Protect
Keep identity, authority, secrets, and data inside clear boundaries.
03Verify
Use direct evidence before promoting an outcome.
04Handoff
Make the next owner decision visible and accountable.
The operating model
One system.
Six controlled moves.
A11 turns agent capability into an inspectable operating loop. Each move has a purpose, a boundary, and a handoff condition.
02Protect
Bound the action.
Limit permissions, secrets, and irreversible operations to an explicit trust zone.
Trust zone / explicit03Execute
Do only what is authorised.
Use identity, version checks, and idempotency to keep execution accountable.
04Verify
Test the result.
Match the outcome to a defined condition before calling it ready.
✓
05Record
Leave a trace.
Capture a redacted evidence event that another owner can inspect.
06Handoff
Keep control moving.
Make the next decision, owner, and release boundary explicit.
View release gates ↗Public surfaces
A clear front door
for agent reality.
Explore the public architecture, the builder perspective, the reusable skills, and the evidence surface without confusing a concept with a deployment.
01 / frontier
Agent Frontiers
Reasoning, tools, memory, and human authority as one governed system.
↗ 02 / build BuildersPatterns for secure bridges, typed events, transactions, and audit records.
↗ 03 / practice SkillsReusable operating knowledge for turning a proposal into verified work.
↗ 04 / inspect Evidence RoomRepository facts, validation results, decision records, and release boundaries.
↘Evidence Room
Know what happened.
Prove what is ready.
The Evidence Room keeps verified records distinguishable from proposals and keeps unknown runtime state labelled as unknown until it is directly established.
Inspect the evidence model ↘Evidence ledgerOwner-controlled
01
Verified recordsRemain tied to a source, test, or decision.
clear02
Pending boundariesStay visible until the next gate is satisfied.
open03
Unknown stateIs never presented as live or deployed.
held04
Next handoffNames the decision that keeps the system moving.
namedA11 / 02Operating standard
Proposed is not executed.
Configured is not deployed.
A11 can prepare, explain, validate, and record. Consequential execution remains bounded by identity, authority, version validity, idempotency, and explicit handoff.
A11 / next surface