Documented release
v97.6.0
Signed Merchant Public-Store, Live Proof Graph, MCP, SDK, and Service Worker Law Release
Release date 2026-07-01
Outcome
Outcome
This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
Changes
What changed
@receiz/sdk now exposes the no-env-token signed merchant public-store rail
@receiz/sdk now exposes the no-env-token signed merchant public-store rail:
Technical and authority boundary
@receiz/sdk now exposes the no-env-token signed merchant public-store rail:
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- @receiz/sdk now exposes the no-env-token signed merchant public-store rail:
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
publicStore.publishWithIdentityProof(...)
publicStore.publishWithIdentityProof(...)
Technical and authority boundary
publicStore.publishWithIdentityProof(...)
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- publicStore.publishWithIdentityProof(...)
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
publicStore.assertSignedPublishContract(...)
publicStore.assertSignedPublishContract(...)
Technical and authority boundary
publicStore.assertSignedPublishContract(...)
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- publicStore.assertSignedPublishContract(...)
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
Signed merchant public-store publish uses the merchant's Identity Seal /…
Signed merchant public-store publish uses the merchant's Identity Seal / Receiz Key proof object as the authority. It does not require RECEIZACCESSTOKEN, and the SDK suppresses configured bearer tokens for that lane.
Technical and authority boundary
Signed merchant public-store publish uses the merchant's Identity Seal / Receiz Key proof object as the authority. It does not require RECEIZACCESSTOKEN, and the SDK suppresses configured bearer tokens for that lane.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- Signed merchant public-store publish uses the merchant's Identity Seal / Receiz Key proof object as the authority. It does not require RECEIZACCESSTOKEN, and the SDK suppresses configured bearer tokens for that lane.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
POST /api/public-proof/registry/feed accepts signed public-store envelopes, verifies feed digest, challenge…
POST /api/public-proof/registry/feed accepts signed public-store envelopes, verifies feed digest, challenge digest, tenant host, merchant Receiz ID, public key identity, and signature, then appends the public projection beneath Receiz proof rails.
Technical and authority boundary
POST /api/public-proof/registry/feed accepts signed public-store envelopes, verifies feed digest, challenge digest, tenant host, merchant Receiz ID, public key identity, and signature, then appends the public projection beneath Receiz proof rails.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- POST /api/public-proof/registry/feed accepts signed public-store envelopes, verifies feed digest, challenge digest, tenant host, merchant Receiz ID, public key identity, and signature, then appends the public projection beneath Receiz proof rails.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
The signed publish result returns the append coordinate
The signed publish result returns the append coordinate:
Technical and authority boundary
The signed publish result returns the append coordinate:
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- The signed publish result returns the append coordinate:
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
/proof-graph became a public one-viewport proof graph organism
/proof-graph became a public one-viewport proof graph organism: live ☤KAI pulse, proof/economy/flow/asset/agent views, mobile-first graph navigation, and in-page public proof network inspection.
Technical and authority boundary
/proof-graph became a public one-viewport proof graph organism: live ☤KAI pulse, proof/economy/flow/asset/agent views, mobile-first graph navigation, and in-page public proof network inspection.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- /proof-graph became a public one-viewport proof graph organism: live ☤KAI pulse, proof/economy/flow/asset/agent views, mobile-first graph navigation, and in-page public proof network inspection.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
/exchange now exposes the proof graph from the file footer proof rail
/exchange now exposes the proof graph from the file footer proof rail.
Technical and authority boundary
/exchange now exposes the proof graph from the file footer proof rail.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- /exchange now exposes the proof graph from the file footer proof rail.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
@receiz/mcp-server remains the official agent wrapper over the SDK
@receiz/mcp-server remains the official agent wrapper over the SDK. Documentation now separates delegated agent/server writes from merchant proof-owned public-store publishing.
Technical and authority boundary
@receiz/mcp-server remains the official agent wrapper over the SDK. Documentation now separates delegated agent/server writes from merchant proof-owned public-store publishing.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- @receiz/mcp-server remains the official agent wrapper over the SDK. Documentation now separates delegated agent/server writes from merchant proof-owned public-store publishing.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
Service worker and offline verifier release identity moved to 97.6.0…
Service worker and offline verifier release identity moved to 97.6.0 so runtime continuity, offline proof verification, and app release identity remain aligned.
Technical and authority boundary
Service worker and offline verifier release identity moved to 97.6.0 so runtime continuity, offline proof verification, and app release identity remain aligned.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- Service worker and offline verifier release identity moved to 97.6.0 so runtime continuity, offline proof verification, and app release identity remain aligned.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
Sports saved-card export now renders base cards as BASE 1
Sports saved-card export now renders base cards as BASE 1:1 / Base issue 1:1. Rare and premium cards keep ODDS and rarity odds language.
Technical and authority boundary
Sports saved-card export now renders base cards as BASE 1:1 / Base issue 1:1. Rare and premium cards keep ODDS and rarity odds language.
- Why
- This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
- Capability enabled
- Sports saved-card export now renders base cards as BASE 1:1 / Base issue 1:1. Rare and premium cards keep ODDS and rarity odds language.
- Compatibility
- The v97.6.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.6.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
This release preserves the authority hierarchy. The SDK, MCP, server, service worker, database, and public projection rail are convenience, sync, indexing, and inspection layers beneath proof objects, verified local truth, Kai/Klok state, ownership appends, settlement primitives, and public proof surfaces.
Available outcomes
Capabilities now available
@receiz/sdk now exposes the no-env-token signed merchant public-store rail
@receiz/sdk now exposes the no-env-token signed merchant public-store rail:
publicStore.publishWithIdentityProof(...)
publicStore.publishWithIdentityProof(...)
publicStore.assertSignedPublishContract(...)
publicStore.assertSignedPublishContract(...)
Signed merchant public-store publish uses the merchant's Identity Seal /…
Signed merchant public-store publish uses the merchant's Identity Seal / Receiz Key proof object as the authority. It does not require RECEIZACCESSTOKEN, and the SDK suppresses configured bearer tokens for that lane.
POST /api/public-proof/registry/feed accepts signed public-store envelopes, verifies feed digest, challenge…
POST /api/public-proof/registry/feed accepts signed public-store envelopes, verifies feed digest, challenge digest, tenant host, merchant Receiz ID, public key identity, and signature, then appends the public projection beneath Receiz proof rails.
The signed publish result returns the append coordinate
The signed publish result returns the append coordinate:
/proof-graph became a public one-viewport proof graph organism
/proof-graph became a public one-viewport proof graph organism: live ☤KAI pulse, proof/economy/flow/asset/agent views, mobile-first graph navigation, and in-page public proof network inspection.
/exchange now exposes the proof graph from the file footer proof rail
/exchange now exposes the proof graph from the file footer proof rail.
@receiz/mcp-server remains the official agent wrapper over the SDK
@receiz/mcp-server remains the official agent wrapper over the SDK. Documentation now separates delegated agent/server writes from merchant proof-owned public-store publishing.
Service worker and offline verifier release identity moved to 97.6.0…
Service worker and offline verifier release identity moved to 97.6.0 so runtime continuity, offline proof verification, and app release identity remain aligned.
Sports saved-card export now renders base cards as BASE 1
Sports saved-card export now renders base cards as BASE 1:1 / Base issue 1:1. Rare and premium cards keep ODDS and rarity odds language.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- verification
- public-witness
- local-truth
- continuity
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
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Unknown
- Deployment
- Not Performed
- Production smoke
- Unknown
- Signed attestation
- Absent
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 1a1769e3444725de85a435aa258f7e685cdc46e810624c7020dbb01b30c562ea. Source-family inventory: complete.
SHA-256 cebd43031dbe12c5dda0b6fa3cfafbc5beed845aa4770b3a8a0ec69a2a36f069SHA-256 57e868f680977f899058efc7b44a39500ecda77076aff8d4f0dfc5864ae7ad83SHA-256 97a43514d34b81b625c40ea279f9e83af50a50c6c0c80c5af43c4ed05100de9aSHA-256 3e92f46670ddfce3f17987bbcaee01fc0c6fd79546e30158523d42db04b62b18SHA-256 3508e970b13f27ed45f4c427e035b0e24e7586c9f3bf8dd4c64c6d5153f6d542SHA-256 22f656678a58e71076ecc7d49fa2e533e7c2e8f72c30a9c88e58dd1ccc634c8cSHA-256 48cd6456d9b10abf1c5c6a1149acf8d9abf58a2c5580e1c20ad6d2ba69bcb6c7