Docs · Learn
Concepts
The mental model behind Aarmos. Short pages you can deep-link from an "Explain" popover or paste into a review. For task-based troubleshooting, see the FAQ.
The execution chain
Authority, invocation, actor, decision, effective policy, verdict, evidence — the spine every other concept is a detailed view of.
Invocation, actors and admission
How a trigger is admitted, how actors inside one invocation are attributed, how participants contribute facts, and why evidence is committed before an action runs.
The agent lifecycle
How Build and Run sit on a governance substrate that produces proof by construction — not a four-stage checklist.
AVAR receipts
Portable, hash-chained, Ed25519-signed evidence for every action. Verifies without Aarmos running.
The policy gate
Microsecond-scale allow / ask / deny decision for every tool call — the enforcement point that produces every receipt.
Effective policy
Many sources — org, workspace, decision, actor, operator — resolve into one artifact with one digest. The merge only ever narrows.
Coverage and status
Is it governed right now? Four honest answers, why a live runtime is not a governed one, freshness windows, and retiring runtimes you no longer run.
Policy lifecycle
From observed traffic to a policy that governs: draft, simulate against real history, review, sign, activate — and why a draft can never activate itself.
Local-first storage
Vault, chats, connectors, and ledger stay on the device. AES-GCM at rest; prompts, keys, and receipts stay on-device.
Delegation
Durable, revocable grants rather than authority asserted at call time. Attenuation, chains, and what a decision relied upon.
Organizational governance
Scopes, membership, identity links, segregation of duties, and bounded break-glass — and why stale organizational state refuses authority without stopping evidence.
Governance continuity
Recovery Points name the governance state you can resume from — and contain none of it. Trust Recovery returns a state, never a score.
Authority succession & forks
When a team splits or an operator leaves: fork points, holds that replicate, and why a shared prefix is never shared history.
Decision governance
Declare the smallest business action worth governing: schema contract, typed inputs, bound participants, a verdict with a window — recorded as evidence.
Information governance
Classification, declared purpose, and disclosure lineage — governing sensitive information without inspecting payloads.
Operational Intelligence
Readings derived from recorded evidence — contribution, stability, counterfactuals, overlapping execution — with coverage always disclosed.
Change Sets
Governing changes to governance itself: draft, simulate against real history, approve, activate, roll back — every step recorded as evidence.
Kill switch & bundle grace
How the panic stop behaves, what bundle grace means, and why signature failures never get a grace window.
Playbooks, signing & packs
Headless runs, Ed25519 signatures, signed packs, destructive-verb defaults, and attestation bundles.
The CLI bridge
Optional localhost pairing that lets the agent read files, watch git, and propose edits with approval.