Foundation 07 · Ordered reality
Kai, Chronos, and causality
Chronos locates events in conventional time. Kai identifies harmonic position and causal structure. Causality orders what produced what. Correction appends the verified relation without rewriting the past.
What this enables
The solved state
You can preserve distinct time domains, reconstruct causal history, add correction without erasure, and keep rollover, Settlement, exit, and consent legible across time.
- 01Event receives temporal coordinates
- 02Cause binds to effect
- 03Verifier admits the append
- 04Correction extends history
- 05Rollover preserves governed continuity
Governing statement
Kai and Chronos remain distinct
Chronos records conventional temporal location. Kai carries harmonic temporal position. Causal order records dependency. No one coordinate replaces the others.
Clock time answers when an observer placed the event. Kai answers its structured harmonic position. Causality answers which event produced the next result.
- What was broken
- A single wall-clock timestamp cannot fully establish causal order, cross-domain timing, or the structured relation between events.
- What is established
- Temporal polyphony preserves multiple exact time domains while causal history binds dependencies explicitly.
- What you can do now
- You can sort, replay, and inspect events without pretending that clock order alone proves causation.
- Why it matters
- Distributed, offline, and cross-domain events retain their actual relationship instead of being flattened into one inherited clock.
Two events may have Chronos timestamps while their Kai coordinates and causal parent establish the order required for deterministic replay.
docs/chronos-causality-kai-time-kernel.mddocs/temporal-polyphony-kernel.mdpackages/receiz-sdk/src/causalHistory.ts
Governing statement
Correction extends the record
A correction is a verified causal append. Perpetual rollover preserves continuity, Settlement, exit, and consent without erasing the states that made the correction necessary.
When later proof establishes a better result, history keeps the earlier event and adds the verified correction that now governs the current projection.
- What was broken
- Mutable systems repair errors by overwriting the old state, removing the evidence required to explain the correction.
- What is established
- Causality correction and rollover preserve the prior proof while appending the governed next state.
- What you can do now
- You can audit what changed, why it changed, which proof authorized it, and which state now governs.
- Why it matters
- Correction becomes accountable progress rather than invisible revision.
A verified correction event names its causal parent, joins append-only history, and changes the present projection without deleting the earlier record.
docs/causality-correction-kernel.mddocs/perpetual-rollover-kernel.mdpackages/receiz-sdk/src/causalReplay.ts