Build on the governed-execution OS.

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.

StableContract locked; changes are versioned. DraftDocumented; may change before 1.0. RoadmapPlanned; not yet designed or built.

The execution chain

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.

  1. 1 Contracts

    Machine-readable interface definitions bound what a module may propose.

    Execution Chain, Stage 1 — Contracts Stable

  2. 2 Tenant boundary

    Organization → workspace → environment scoping, enforced at the storage layer.

    Execution Chain, Stage 2 — Tenant boundary Stable

  3. 3 Verified identity

    Every action is bound to a known actor: human, service, or agent.

    Execution Chain, Stage 3 — Verified identity Stable

  4. 4 Deterministic policy

    Pure, ordered rule evaluation produces allow / deny / require-approval.

    Execution Chain, Stage 4 — Deterministic policy Stable · Deep-dive: Policy Model Stable

  5. 5 Governed action

    Controlled execution inside a transaction — only what policy allowed.

    Execution Chain, Stage 5 — Governed action Stable

  6. 6 Evidence

    A verifiable, hash-chained receipt is recorded for every action.

    Execution Chain, Stage 6 — Evidence Stable · Deep-dive: Evidence Model Stable

Specification Layer

Implementation & Runtime Layer

Documentation index

Stable

Execution-chain spec

Contracts → tenant boundary → verified identity → deterministic policy → governed action → evidence. Purpose, inputs/outputs, and invariants for each stage.

Stable

Deterministic policy model

How policies are expressed, evaluated, and versioned. Deny-by-default, pure evaluation, ordered rules.

Stable

Evidence model

What is recorded per action, the receipt format, and how receipts are verified.

Draft

API reference

Resource model, authentication, error envelope, and pagination conventions. Endpoints are roadmap — none are live.

Draft

JavaScript SDK

Installation, authentication, and a "first governed action" walkthrough.

Draft

Python SDK

Installation, authentication, and a "first governed action" walkthrough.

Draft

Quickstart

From zero to your first verified action, running entirely on your own machine.

Draft

Module build guide

Module structure, the contracts a module must satisfy, and testing expectations.

Quickstart path

  1. Read the execution chain — understand the six stages every action passes through. Execution-chain spec

  2. Run the quickstart — propose, authorize, execute, and verify your first action locally. Quickstart guide

  3. Learn the policy model — express allow/deny/require-approval rules deterministically. Policy model

  4. Build a module — satisfy the module contract and test against deterministic fixtures. Build guide

Where this site fits

ametios.com
The AmetiOS manifesto — the vision and the why.
ametios.dev (this site)
The build surface — contracts, specs, SDKs, reference code.
masterengine.dev
MasterEngine — the governed mission platform; AmetiOS is the OS it runs on.