"Different parts of the system run on different clocks. This protocol identifies the mismatches."
Verification clocks (real-time), accounting clocks (T+2), regulatory clocks (quarterly), narrative clocks (annual reporting). When event timing crosses these clocks, mismatches occur (e.g. dispute raised after quarter-close). This protocol catalogues mismatches and rules for handling them.
Sealed: 14 October 2025·Owner: Tech Lead · Sovereign Architect·Weight: Operational · Medium
4
Clocks
~12
Mismatches/yr
0
Unresolved
Signature Diagram · FLOW
📝 Real Example · Numbers · Names
In the field
04 April 2026 case: dispute raised on Q1 dPRN that had cleared. Real-time → settled. Quarterly close → already booked. Resolution per Protocol 047: synchronise via reversal entry, document mismatch, no claw-back of Covenant.
▸ Triggers · When This Fires
Cross-clock event detected
Quarter-close event with open issues
Annual narrative + ledger reconciliation
⚠ Consequence · If Broken
Untracked mismatches breed accounting disputes and regulator confusion. The catalogue + ruleset = predictable handling = trust.