Documented release
v66.0.0
Local Proof Continuity
Release date 2026-04-21
Outcome
Outcome
The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
Changes
What changed
Receipt rendering now classifies proof authority instead of treating all…
Receipt rendering now classifies proof authority instead of treating all evidence as equal.
Technical and authority boundary
Receipt rendering now classifies proof authority instead of treating all evidence as equal.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Receipt rendering now classifies proof authority instead of treating all evidence as equal.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Verified-register-backed proof outranks legacy offline evidence
Verified-register-backed proof outranks legacy offline evidence.
Technical and authority boundary
Verified-register-backed proof outranks legacy offline evidence.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Verified-register-backed proof outranks legacy offline evidence.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Receipt details and proof popovers expose stronger local authority without…
Receipt details and proof popovers expose stronger local authority without letting older payloads reframe it.
Technical and authority boundary
Receipt details and proof popovers expose stronger local authority without letting older payloads reframe it.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Receipt details and proof popovers expose stronger local authority without letting older payloads reframe it.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Wallet transaction receipts now verify deterministic ledger proof bundles before…
Wallet transaction receipts now verify deterministic ledger proof bundles before treating ledger claims as truth. Offline identity and account continuity moved forward
Technical and authority boundary
Wallet transaction receipts now verify deterministic ledger proof bundles before treating ledger claims as truth. Offline identity and account continuity moved forward
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Wallet transaction receipts now verify deterministic ledger proof bundles before treating ledger claims as truth. Offline identity and account continuity moved forward
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Account surfaces preserve a valid bootstrap/keyfile/PBI-backed local identity when the…
Account surfaces preserve a valid bootstrap/keyfile/PBI-backed local identity when the session API is unavailable or weaker.
Technical and authority boundary
Account surfaces preserve a valid bootstrap/keyfile/PBI-backed local identity when the session API is unavailable or weaker.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Account surfaces preserve a valid bootstrap/keyfile/PBI-backed local identity when the session API is unavailable or weaker.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Anonymous or missing network session payloads no longer erase locally…
Anonymous or missing network session payloads no longer erase locally held identity proof.
Technical and authority boundary
Anonymous or missing network session payloads no longer erase locally held identity proof.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Anonymous or missing network session payloads no longer erase locally held identity proof.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
The account route now treats network session as enrichment over…
The account route now treats network session as enrichment over a local identity root, not permission to exist.
Technical and authority boundary
The account route now treats network session as enrichment over a local identity root, not permission to exist.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- The account route now treats network session as enrichment over a local identity root, not permission to exist.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Brand-new local Receiz ID creation writes a local PBI enrollment…
Brand-new local Receiz ID creation writes a local PBI enrollment block, projects the signed-in shell and profile seed immediately, and then publishes/binds to the global register as a best-effort verified append when online. Public twin gained a real local rail
Technical and authority boundary
Brand-new local Receiz ID creation writes a local PBI enrollment block, projects the signed-in shell and profile seed immediately, and then publishes/binds to the global register as a best-effort verified append when online. Public twin gained a real local rail
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Brand-new local Receiz ID creation writes a local PBI enrollment block, projects the signed-in shell and profile seed immediately, and then publishes/binds to the global register as a best-effort verified append when online. Public twin gained a real local rail
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
The public twin can project from the local twin mind…
The public twin can project from the local twin mind register and local model path before the network stream is needed.
Technical and authority boundary
The public twin can project from the local twin mind register and local model path before the network stream is needed.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- The public twin can project from the local twin mind register and local model path before the network stream is needed.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Local twin register projection now wins for the visible reply
Local twin register projection now wins for the visible reply. The online stream path remains available when no local register projection exists, but it no longer silently replaces a settled local projection.
Technical and authority boundary
Local twin register projection now wins for the visible reply. The online stream path remains available when no local register projection exists, but it no longer silently replaces a settled local projection.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Local twin register projection now wins for the visible reply. The online stream path remains available when no local register projection exists, but it no longer silently replaces a settled local projection.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Browser local model support is integrated through the WebLLM rail…
Browser local model support is integrated through the WebLLM rail with deterministic fallback when the model is unavailable.
Technical and authority boundary
Browser local model support is integrated through the WebLLM rail with deterministic fallback when the model is unavailable.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Browser local model support is integrated through the WebLLM rail with deterministic fallback when the model is unavailable.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Twin mind PNG import now requires portable public-key verification instead…
Twin mind PNG import now requires portable public-key verification instead of server-secret HMAC authority for canonical import. World, Explore, Wallet, and Market honor known state more strictly
Technical and authority boundary
Twin mind PNG import now requires portable public-key verification instead of server-secret HMAC authority for canonical import. World, Explore, Wallet, and Market honor known state more strictly
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Twin mind PNG import now requires portable public-key verification instead of server-secret HMAC authority for canonical import. World, Explore, Wallet, and Market honor known state more strictly
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
World profile/public/me API snapshots opt into service-worker offline persistence for…
World profile/public/me API snapshots opt into service-worker offline persistence for deterministic or private route truth.
Technical and authority boundary
World profile/public/me API snapshots opt into service-worker offline persistence for deterministic or private route truth.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- World profile/public/me API snapshots opt into service-worker offline persistence for deterministic or private route truth.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Explore route snapshots are durable verified local truth and reconcile…
Explore route snapshots are durable verified local truth and reconcile into the visible view without replacing useful already-visible content.
Technical and authority boundary
Explore route snapshots are durable verified local truth and reconcile into the visible view without replacing useful already-visible content.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Explore route snapshots are durable verified local truth and reconcile into the visible view without replacing useful already-visible content.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Wallet now projects the durable wallet graph during first render…
Wallet now projects the durable wallet graph during first render instead of applying it in a later effect.
Technical and authority boundary
Wallet now projects the durable wallet graph during first render instead of applying it in a later effect.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Wallet now projects the durable wallet graph during first render instead of applying it in a later effect.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Market snapshot continuity preserves known local positions and refuses lagging…
Market snapshot continuity preserves known local positions and refuses lagging payloads that temporarily drop a buy or sell already known locally.
Technical and authority boundary
Market snapshot continuity preserves known local positions and refuses lagging payloads that temporarily drop a buy or sell already known locally.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Market snapshot continuity preserves known local positions and refuses lagging payloads that temporarily drop a buy or sell already known locally.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Tracked positions now follow the same rule
Tracked positions now follow the same rule: a transport payload must prove a stronger state before it can remove visible local position truth.
Technical and authority boundary
Tracked positions now follow the same rule: a transport payload must prove a stronger state before it can remove visible local position truth.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Tracked positions now follow the same rule: a transport payload must prove a stronger state before it can remove visible local position truth.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Signed-in Market first paint now carries active share and prediction…
Signed-in Market first paint now carries active share and prediction positions in the entry transport; ownership is not delayed until the background market snapshot. The service worker became a verified-snapshot carrier
Technical and authority boundary
Signed-in Market first paint now carries active share and prediction positions in the entry transport; ownership is not delayed until the background market snapshot. The service worker became a verified-snapshot carrier
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Signed-in Market first paint now carries active share and prediction positions in the entry transport; ownership is not delayed until the background market snapshot. The service worker became a verified-snapshot carrier
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Offline persistence is explicit through x-receiz-offline-persist response headers
Offline persistence is explicit through x-receiz-offline-persist response headers.
Technical and authority boundary
Offline persistence is explicit through x-receiz-offline-persist response headers.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Offline persistence is explicit through x-receiz-offline-persist response headers.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Deterministic public snapshots and private account snapshots are stored as…
Deterministic public snapshots and private account snapshots are stored as local truth carriers, not generic cache guesses.
Technical and authority boundary
Deterministic public snapshots and private account snapshots are stored as local truth carriers, not generic cache guesses.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Deterministic public snapshots and private account snapshots are stored as local truth carriers, not generic cache guesses.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
The app-shell fallback remains a resilience path
The app-shell fallback remains a resilience path; route truth is still carried by verified snapshots and deterministic payloads. Product language and release surfaces moved together
Technical and authority boundary
The app-shell fallback remains a resilience path; route truth is still carried by verified snapshots and deterministic payloads. Product language and release surfaces moved together
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- The app-shell fallback remains a resilience path; route truth is still carried by verified snapshots and deterministic payloads. Product language and release surfaces moved together
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Public version labels, offline verifier artifacts, package metadata, and service-worker…
Public version labels, offline verifier artifacts, package metadata, and service-worker defaults now move together to v66.0.0.
Technical and authority boundary
Public version labels, offline verifier artifacts, package metadata, and service-worker defaults now move together to v66.0.0.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- Public version labels, offline verifier artifacts, package metadata, and service-worker defaults now move together to v66.0.0.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
The release docs now freeze the offline primitive as release…
The release docs now freeze the offline primitive as release truth, not just as engineering preference.
Technical and authority boundary
The release docs now freeze the offline primitive as release truth, not just as engineering preference.
- Why
- The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
- Capability enabled
- The release docs now freeze the offline primitive as release truth, not just as engineering preference.
- Compatibility
- The v66.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v66.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
The server, database, and network remain important for discovery, publication, global propagation, appends, and online enrichment. They are no longer allowed to delay or downgrade stronger verified truth already held by the node.
Available outcomes
Capabilities now available
Receipt rendering now classifies proof authority instead of treating all…
Receipt rendering now classifies proof authority instead of treating all evidence as equal.
Verified-register-backed proof outranks legacy offline evidence
Verified-register-backed proof outranks legacy offline evidence.
Receipt details and proof popovers expose stronger local authority without…
Receipt details and proof popovers expose stronger local authority without letting older payloads reframe it.
Wallet transaction receipts now verify deterministic ledger proof bundles before…
Wallet transaction receipts now verify deterministic ledger proof bundles before treating ledger claims as truth. Offline identity and account continuity moved forward
Account surfaces preserve a valid bootstrap/keyfile/PBI-backed local identity when the…
Account surfaces preserve a valid bootstrap/keyfile/PBI-backed local identity when the session API is unavailable or weaker.
Anonymous or missing network session payloads no longer erase locally…
Anonymous or missing network session payloads no longer erase locally held identity proof.
The account route now treats network session as enrichment over…
The account route now treats network session as enrichment over a local identity root, not permission to exist.
Brand-new local Receiz ID creation writes a local PBI enrollment…
Brand-new local Receiz ID creation writes a local PBI enrollment block, projects the signed-in shell and profile seed immediately, and then publishes/binds to the global register as a best-effort verified append when online. Public twin gained a real local rail
The public twin can project from the local twin mind…
The public twin can project from the local twin mind register and local model path before the network stream is needed.
Local twin register projection now wins for the visible reply
Local twin register projection now wins for the visible reply. The online stream path remains available when no local register projection exists, but it no longer silently replaces a settled local projection.
Browser local model support is integrated through the WebLLM rail…
Browser local model support is integrated through the WebLLM rail with deterministic fallback when the model is unavailable.
Twin mind PNG import now requires portable public-key verification instead…
Twin mind PNG import now requires portable public-key verification instead of server-secret HMAC authority for canonical import. World, Explore, Wallet, and Market honor known state more strictly
World profile/public/me API snapshots opt into service-worker offline persistence for…
World profile/public/me API snapshots opt into service-worker offline persistence for deterministic or private route truth.
Explore route snapshots are durable verified local truth and reconcile…
Explore route snapshots are durable verified local truth and reconcile into the visible view without replacing useful already-visible content.
Wallet now projects the durable wallet graph during first render…
Wallet now projects the durable wallet graph during first render instead of applying it in a later effect.
Market snapshot continuity preserves known local positions and refuses lagging…
Market snapshot continuity preserves known local positions and refuses lagging payloads that temporarily drop a buy or sell already known locally.
Tracked positions now follow the same rule
Tracked positions now follow the same rule: a transport payload must prove a stronger state before it can remove visible local position truth.
Signed-in Market first paint now carries active share and prediction…
Signed-in Market first paint now carries active share and prediction positions in the entry transport; ownership is not delayed until the background market snapshot. The service worker became a verified-snapshot carrier
Offline persistence is explicit through x-receiz-offline-persist response headers
Offline persistence is explicit through x-receiz-offline-persist response headers.
Deterministic public snapshots and private account snapshots are stored as…
Deterministic public snapshots and private account snapshots are stored as local truth carriers, not generic cache guesses.
The app-shell fallback remains a resilience path
The app-shell fallback remains a resilience path; route truth is still carried by verified snapshots and deterministic payloads. Product language and release surfaces moved together
Public version labels, offline verifier artifacts, package metadata, and service-worker…
Public version labels, offline verifier artifacts, package metadata, and service-worker defaults now move together to v66.0.0.
The release docs now freeze the offline primitive as release…
The release docs now freeze the offline primitive as release truth, not just as engineering preference.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- verification
- public-witness
- local-truth
- continuity
- market
Compatibility
Compatibility
Archive compatibility evidence boundary
No dedicated compatibility record is bound to this projection.
Treat compatibility as unknown; version or date proximity is not evidence.
Migration
Migration
Required: unknown
No explicit migration source is bound; no migration is inferred from dates.
Qualification
Conformance
No immutable conformance evidence is assigned in this projection.
Control boundary
Governance
- Verification
- Unknown
- Declared change class
- No separate classification record
- Release approval
- No separate approval record
- Risk owner
- No separate assignment recorded
Publication, deployment, production smoke, and attestation remain independent evidence dimensions unless exact sources establish them.
Registry boundary
Registry
No registry is bound where the canonical release family does not carry one.
Archive projection
Audience, domain, and change-kind facets
- Audiences
- developers · businesses · creators · institutions · people
- Domains
- proof · identity · ownership · settlement · provenance · verification · public-witness · local-truth · continuity · market
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Unknown
- Deployment
- Unknown
- Production smoke
- Unknown
- Signed attestation
- Unknown
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 2e111b188fe6e862212e5dd114522791a2072681c84b41dffddc326f11c07501. Source-family inventory: complete.
SHA-256 b3ab10a646d18043b82f544e66d2fa6708f732cdd1f9df65413bc95e4130daa4SHA-256 108385d0d1e460ec7c3088334c38c69e8f539f42c684a08e66c841000ed21b3fSHA-256 3e09826f7a83f7b906a0b5b3c14b06414e8db61353118144634403ef728f2097SHA-256 181dc261fd8b0be700daa27c4f298028754f8853bf1cca9c3aa3f5e8cfcf5dc1SHA-256 2e8a1c938e7d030b1ba560cc311772f539fb2bb43e84219796ab0616522d03be