Foundation 05 · Immediate continuity
Verified local truth
Verified local truth is durable accepted proof. It is not cache, and it does not become stale because a network is absent.
What this enables
The solved state
You can use already verified truth immediately, preserve a settled first paint, and accept later verified additions without rediscovering what is already known.
Governing statement
Verified local truth is durable proof
Once truth is verified and stored locally, it remains accepted truth. Later truth may extend it only through a separately verified successor or verified register addition bound to the exact accepted predecessor or head.
Verification has already happened. The device can use that accepted result now instead of asking a weaker service to rediscover it.
- What was broken
- Traditional cache logic treats local state as disposable and waits for a server before showing what the person already proved.
- What is established
- Verified local truth retains its authority after storage and remains available for immediate projection.
- What you can do now
- You can open a known proof object and see settled truth immediately, including when the network is unavailable.
- Why it matters
- A service delay cannot turn known proof into uncertainty or loading theater.
An admitted artifact can paint from durable local truth while background synchronization searches only for verified additions.
AGENTS.mddocs/offline-verified-register.mdpackages/receiz-sdk/src/browserAdmissionStore.ts
Governing statement
New truth requires verified succession
A later state extends known truth only when it is a separately verified successor or verified register addition bound to the exact accepted predecessor or head; it does not rewrite the evidence that established the earlier state.
History grows forward. Correction and enrichment preserve the earlier proof and add the verified next fact.
- What was broken
- Mutable records can silently replace yesterday's state and destroy the evidence needed to understand how the present result formed.
- What is established
- Append-only history preserves accepted states and records each verified successor against its exact predecessor or register head.
- What you can do now
- You can reconstruct the object's history and identify exactly which separately verified successor changed its current projection.
- Why it matters
- Continuity, correction, ownership, and causality remain auditable instead of becoming overwritten snapshots.
A later provenance event extends the artifact history while the earlier sealed event remains inspectable.
docs/verified-history-first-principles.mdpackages/receiz-sdk/src/causalHistory.tsapp/components/pwa/__tests__/offlineAppendProjectionContract.test.ts