Execution-chain spec
Contracts → tenant boundary → verified identity → deterministic policy → governed action → evidence. Purpose, inputs/outputs, and invariants for each stage.
AmetiOS is a governed business-mission execution operating system: every action a machine takes runs through contracts, a tenant boundary, verified identity, deterministic policy, and evidence. This hub is the engineering surface — exact interface contracts, specs, SDK documentation, and working reference code. For the vision behind the platform, read the AmetiOS manifesto.
Six stages, in order. Each stage carries the invariant its contract holds; the chips belong to the documents that specify the stage, never to the stage itself.
Machine-readable interface definitions bound what a module may propose.
Organization → workspace → environment scoping, enforced at the storage layer.
Every action is bound to a known actor: human, service, or agent.
Pure, ordered rule evaluation produces allow / deny / require-approval.
Execution Chain, Stage 4 — Deterministic policy Stable · Deep-dive: Policy Model Stable
Controlled execution inside a transaction — only what policy allowed.
A verifiable, hash-chained receipt is recorded for every action.
Execution Chain, Stage 6 — Evidence Stable · Deep-dive: Evidence Model Stable
Contracts → tenant boundary → verified identity → deterministic policy → governed action → evidence. Purpose, inputs/outputs, and invariants for each stage.
How policies are expressed, evaluated, and versioned. Deny-by-default, pure evaluation, ordered rules.
What is recorded per action, the receipt format, and how receipts are verified.
Resource model, authentication, error envelope, and pagination conventions. Endpoints are roadmap — none are live.
Installation, authentication, and a "first governed action" walkthrough.
Installation, authentication, and a "first governed action" walkthrough.
From zero to your first verified action, running entirely on your own machine.
Module structure, the contracts a module must satisfy, and testing expectations.
Annotated, runnable reference code: governed webhook, approval inbox, evidence receipt.
Read the execution chain — understand the six stages every action passes through. Execution-chain spec
Run the quickstart — propose, authorize, execute, and verify your first action locally. Quickstart guide
Learn the policy model — express allow/deny/require-approval rules deterministically. Policy model
Build a module — satisfy the module contract and test against deterministic fixtures. Build guide