Foundation 06 · Verification without permission
Offline operation
Offline verification is the primitive. A server may later synchronize verified additions; it is not required to make a valid sealed artifact true.
What this enables
The solved state
You can record, seal, preserve, inspect, and verify supported proof objects without surrendering the truth boundary to network availability.
Governing statement
Verification travels with the artifact
Offline verification validates the sealed artifact from its carried proof material. Network and server state may append later; they do not grant the artifact its existing truth.
The artifact brings the evidence needed for verification. A connection can help discover more verified history, but the connection is not the original authority.
- What was broken
- Server-dependent records become unusable or unverifiable when an account, service, or network is unavailable.
- What is established
- The sealed artifact and verifier establish the proof boundary locally.
- What you can do now
- You can inspect and verify supported artifacts directly from their bytes without waiting for a service response.
- Why it matters
- Evidence remains available to the person who holds it instead of becoming permission rented from an online system.
The offline verifier reads a sealed artifact, recomputes integrity, and reports the verification result without requiring a signed-in session.
docs/offline-verified-register.mdapp/lib/documentSeal/offlineSeal.tspackages/receiz-sdk/src/artifactVerification.ts
Governing statement
Offline work joins history through verified append
Offline authorship creates a causally identified event. Later synchronization verifies and appends that event without rewriting stronger known truth.
Work can happen without a connection. When connection returns, the event joins shared history only after its proof passes.
- What was broken
- Offline work is often treated as an inferior temporary copy that can be discarded or overwritten during reconnection.
- What is established
- Deterministic identity, causality, verification, and append-only admission preserve the offline event as proof.
- What you can do now
- You can continue recording and preserving supported truth offline, then synchronize verified additions later.
- Why it matters
- Connectivity changes delivery time, not whether the accepted proof object exists.
An offline-sealed record is admitted locally, then a later verified append extends the register when synchronization becomes available.
docs/offline-record-seal-frozen-invariants.mdpackages/receiz-sdk/src/artifactAdmission.tsapp/components/pwa/__tests__/offlineAppendProjectionContract.test.ts