[EPIC] Runtime v1 — architecture complete: the ten conditions

[ucguy4u]

What this tracks

The point at which Airo Mind stops being an evolving architecture and becomes a stable platform.

Contracts C1–C7 are defined in docs/superpowers/specs/2026-07-28-airo-mind-runtime-contracts.md and versioned as part of the runtime ABI. This issue tracks the ten conditions that mark them complete.

The ten conditions

• 1. The runtime boots with only the Supervisor
• 2. Every capability runs through the Supervisor
• 3. No capability owns durable persistence
• 4. Every durable object is reachable from the operation log
• 5. Every projection can be deleted and rebuilt
• 6. A Recovery Package restore reproduces identical state
• 7. Two devices converge by exchanging operations only
• 8. DestroyContent removes every reachable representation of user content, except immutable structural metadata intentionally retained by design
• 9. Every runtime contract has automated conformance tests
• 10. Every performance contract has benchmark gates in CI

9 and 10 are what make 1–8 real

Per I5 — an invariant is not complete until it can fail — and I8 — cost is part of correctness — a condition with no failing form is not met, it is merely claimed.

That distinction is not theoretical here. Four consecutive council reviews found properties recorded as applied and absent from the code: the header AAD, the revocation-subject rewrite, error variants declared and never constructed, and I7 adopted against a format that violates it by construction.

Conditions 1–8 without 9–10 would be the same failure at architecture scale.

Known distance from each condition, today

#	Status
1, 2	Supervisor does not exist — #1302
3	Four known violations: DriftMeetingRepository, features/coins/, features/money/, settings AI-storage dashboard — #1293. Plus relational_store — #1297
4	Operation log does not exist — #1194
5	Projection engine does not exist — #1195
6	Vault redesign in flight — #1305
7	Sync does not exist — #1200
8	Purge is convention, not mechanism; steps 4–8 unenforced — #1217
9	No conformance suite exists
10	No benchmark gates exist — #1287, #1294

Why the exception cost is stated

Every accepted exception before this point is a permanent maintenance cost, because the runtime is intended to underpin every future capability. An exception granted to one capability becomes the precedent the next one cites.

After this point

Engineering effort shifts to building capabilities rather than changing the substrate beneath them. Milestones 20 and 21 — the Capability Platform and the Ecosystem — assume this is done.

Blocked by

Effectively all of milestone 19. This is the milestone's exit criterion, not a task.