AMSA coordinates and audits multi-agent AI systems on top of a deterministic, cryptographically verifiable substrate. Every identity, state change, memory entry, and ownership transfer beneath AMSA is hash-linked and independently re-derivable — so agent behavior stays auditable after the fact, not just observable in the moment.
AMSA orchestrates agents on top of the DIS substrate — these invariants aren't marketing properties of AMSA alone, they're enforced in the underlying DIS/SDS code and checked by the test suite on every build.
No uuid, no os.urandom, no wall-clock timestamps inside any hash input. Identity comes from a LogicalClock tick and canonical JSON — same inputs always produce the same chain.
Every record embeds hash_chain(prev_hash, payload). Change one byte in history and every record after it fails verify() — not eventually, immediately.
Asset and permission transfers fold into a binary Merkle tree. You can prove any single transfer is valid without replaying the entire ledger.
Every execution record carries the exact state-hash and memory-hash active at that tick — so a result is provably traceable to what the agent actually knew, not what it claims to have known.
Canonical JSON plus content addressing means re-compressing the same state twice produces the same archive hash, every time, on any machine.
Model sampling is still sampling. DIS doesn't fight that — it cryptographically records what a non-deterministic model did, so the record is verifiable even when the output wasn't predictable.
AMSA is the orchestration layer. Each module beneath it ships standalone with its own test suite, then composes into the full substrate AMSA runs on.
Every number below comes from the test suite and demo shipped in the source, not a deck.
def hash_chain(prev_hash: str, payload: Any) -> str: # No timestamps, no randomness — # identical inputs always yield this hash. blob = canonical_json({ "prev": prev_hash, "payload": payload, }) return sha256(blob).hexdigest()
Ran 871 tests in 4.218s OK $ python demo.py [25/25] Mesh diff (two checkpoints) ... PASS All 25 sections completed. 0 assertions failed.
We're sharing the reviewer package — full source, specs, and the limitations we haven't solved yet — with engineers evaluating this for integration, licensing, or acquisition.