Meridian / Documentation
Chronicle Audit Model
SOURCE · docs/standards/chronicle-audit-model.md · synced from the engineering repo
Chronicle Audit Model
Status: draft
Version: 0.1.0
Purpose
Define the canonical control-repo language for Meridian Chronicle historical reconstruction, sequence-bounded replay, drift comparison, and audit-ready views over Meridian Index and Meridian Proof.
Chronicle model
- aggregate Chronicle views expose an ordered timeline, reconstructed state, current projected state, and a drift verdict for one replayable aggregate
- instrument Chronicle views widen the history scope to include instrument lifecycle, policy, and settlement activity that references one instrument id
- audit Chronicle views pair replay and drift data with related evidence ids and bundle readiness from Meridian Proof
- replayable Chronicle state reconstructs from existing stored events and does not append new Chronicle events in this runtime
Core records
- aggregate Chronicle view
- instrument Chronicle view
- audit Chronicle view
- drift verdict
- requested sequence boundary
Required Chronicle references
- aggregate id
- instrument id
- sequence
- timeline event
- reconstructed state
- current state
- evidence id
- bundle id
Current runtime boundary
- Meridian Chronicle is read-only in the current reference runtime
- Meridian Gateway currently exposes aggregate, instrument, and audit Chronicle routes only
- cryptographic consistency proofs, anomaly detection, GraphQL exposure, and regulator export generation remain outside this Phase M surface