Synthetic replay
The planned fixed replay will follow one decision through every authority boundary.
Inspect replay anatomyControl plane + system of record for regulated enterprise agents
Consequential agent decisions, governed end to end.
Ontogony puts an explicit authority boundary between what an agent produces and what an organization treats as an official decision.
Ontogony records what the agent knew, what it did, which models it called, which semantic or policy authority judged the result, what was promoted, and what can be replayed or verified offline.
- Replay
- Fixed synthetic
- Evidence
- Pre-generated
- Customer data
- None
- Execution
- Not a live production system
Proof framing
One decision. Every authority boundary.
The planned replay reserves a place for one fixed synthetic record. Until publication approval, the mechanism is visible and the record is not.
Publication control
Publication gate: closed
The publication set has not been published. Architecture and method remain visible; records, digests, artifacts, and verification outcomes do not.
Governed loop
Advisory output does not promote itself.
Follow the ordered transfer from source intake to dossier evidence. The labeled review-return edge keeps advisory review distinct from named promotion authority.
Static system map
The governed decision loop
Responsibility moves through seven named stages, then closes through replay and offline verification. Supporting lanes cross the sequence without replacing it.
- 01Source intake and lineageComponent · MetaboleCurrent
Lineage-bearing source material
- 02Temporal context and reconstructionComponent · AisthesisCurrent
Reconstructed decision context
- 03Governed runComponent · AllagmaCurrent
Governed operation and event evidence
- 04Controlled model accessComponent · ConexusCurrent
Bounded model result and call record
- 05Semantic and policy judgmentComponent · KanonCurrent
Judgment with cited authority
- 06Promotion and officializationComponent · ARGCurrent
Promoted, denied, or held decision
- 07Dossier and verificationComponent · ALLCurrent
Inspectable dossier boundary
- 08Replay and offline verificationMethod · Offline verificationCurrent
Current · Deterministic test range — a supporting lane outside the core decision sequence.
Required handoffAdvisory resultEvidence attachmentAdvisory review returnSupporting laneProhibited ownership
Structured fallback
Topology text equivalent
The same eight-stage sequence shown in the diagram, in reading and keyboard order.
| Stage | Responsibility | Component | Handoff | Relationship |
|---|---|---|---|---|
| 1Current | Source intake and lineage | Metabole | Lineage-bearing source material | Required handoff |
| 2Current | Temporal context and reconstruction | Aisthesis | Reconstructed decision context | Required handoff |
| 3Current | Governed run | Allagma | Governed operation and event evidence | Required handoff |
| 4Current | Controlled model access | Conexus | Bounded model result and call record | Advisory result |
| 5Current | Semantic and policy judgment | Kanon | Judgment with cited authority | Required handoff |
| 6Current | Promotion and officialization | ARG | Promoted, denied, or held decision | Evidence attachment |
| 7Current | Dossier and verification | ALL | Inspectable dossier boundary | Evidence attachment |
| 8Current | Replay and offline verification | Loop closure | Review findings returned to the loop | Advisory review return |
Cross-cutting and supporting lanes
- Shared mechanics — Ontogony.Platform
- Cross-cutting mechanics used by the governed loop.
- Evidence canonization — Flock
- A supporting lane for multi-agent evidence handling.
- Redacted evidence intake — Vendor adapters
- A boundary lane for vendor and runtime evidence.
- Deterministic test range — Synthetic Estate
- A controlled test lane outside the core decision sequence.
- Operator and buyer projection — Workbench
- A projection surface, not a source of truth.
Illustrative walkthrough
Watch one synthetic decision cross every boundary.
See what each stage receives, may decide, must not decide, and hands on. The example teaches the loop without presenting a record, evidence, or replay.
Inspection path
Proof, bounded outcomes, and domain context
Move from a public proof surface to the responsibility outcome it explains, then inspect where a planned or research domain supplies context. None of these projections is an availability claim.
01 · Proof
Inspect what may be published
Public status
The future ledger will separate implementation, evidence, availability, and readiness claims.
View system statusContract registry
The future registry will describe guarantees and exclusions at responsibility transfers.
Review the contract methodOffline verification
The standalone verifier checks an approved unpacked bundle without calling private Ontogony services. No approved bundle is currently published.
Review offline verification02 · Outcomes
Follow responsibilities by intended outcome
Problem → outcome
Governed execution
Problem: External runtimes can perform work without making their authority boundaries or consequential actions inspectable.
Outcome: A run can be explained as an ordered set of bounded operations, gates, and evidence-producing handoffs.
Follow the capability pathProblem → outcome
Semantic and policy judgment
Problem: Model output alone cannot determine which facts, policies, or interpretations are authoritative.
Outcome: A decision record can distinguish advisory output from the authority that judged it.
Follow the capability pathProblem → outcome
Dossier and offline verification
Problem: Reviewers need a durable record and a way to detect whether published files differ from their manifest.
Outcome: The decision loop ends at an inspectable dossier and an independent checksum-verification boundary.
Follow the capability path03 · Domains
Place the loop in a bounded decision context
Responsible gaming
The fixed launch demonstration is designed around a synthetic withdrawal-risk decision moving through the full governed loop.
Boundary: Technical decision assurance is not a legal or regulatory determination.
Read the domain boundaryOrigins
From the problem of becoming to the problem of authority
How can a machine-produced decision become authoritative without becoming opaque?
Ontogony began with a philosophical question about identity, authority, and persistence. The governed loop translates it into an inspectable operational boundary.