Documented release
v96.0.0
SDK A+ Release Evidence Lock
Release date 2026-06-29
Outcome
Outcome
The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
Changes
What changed
@receiz/sdk@96.0.0 ships the receiz CLI
@receiz/sdk@96.0.0 ships the receiz CLI.
Technical and authority boundary
@receiz/sdk@96.0.0 ships the receiz CLI.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- @receiz/sdk@96.0.0 ships the receiz CLI.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
receiz conformance validates packaged proof fixtures locally and reports zero…
receiz conformance validates packaged proof fixtures locally and reports zero network calls and zero DB calls.
Technical and authority boundary
receiz conformance validates packaged proof fixtures locally and reports zero network calls and zero DB calls.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- receiz conformance validates packaged proof fixtures locally and reports zero network calls and zero DB calls.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
receiz inspect <file projects a proof payload and prints its known Kai/proof head
receiz inspect <file projects a proof payload and prints its known Kai/proof head.
Technical and authority boundary
receiz inspect <file projects a proof payload and prints its known Kai/proof head.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- receiz inspect <file projects a proof payload and prints its known Kai/proof head.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
receiz init <dir writes a local-first durable proof memory starter
receiz init <dir writes a local-first durable proof memory starter.
Technical and authority boundary
receiz init <dir writes a local-first durable proof memory starter.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- receiz init <dir writes a local-first durable proof memory starter.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
SDK proof memory exposes passive ReceizSdkObservation events through onObservation
SDK proof memory exposes passive ReceizSdkObservation events through onObservation.
Technical and authority boundary
SDK proof memory exposes passive ReceizSdkObservation events through onObservation.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- SDK proof memory exposes passive ReceizSdkObservation events through onObservation.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
Copy-paste developer integrations now cover React proof memory, browser proof…
Copy-paste developer integrations now cover React proof memory, browser proof admission, append-sync routes, webhook receivers, and Sports card renderers.
Technical and authority boundary
Copy-paste developer integrations now cover React proof memory, browser proof admission, append-sync routes, webhook receivers, and Sports card renderers.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- Copy-paste developer integrations now cover React proof memory, browser proof admission, append-sync routes, webhook receivers, and Sports card renderers.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
test
test:sdk-release-contracts is wired into test:release-freeze.
Technical and authority boundary
test:sdk-release-contracts is wired into test:release-freeze.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- test:sdk-release-contracts is wired into test:release-freeze.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
@receiz/sdk stays locked to the same release version as the app
@receiz/sdk stays locked to the same release version as the app.
Technical and authority boundary
@receiz/sdk stays locked to the same release version as the app.
- Why
- The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
- Capability enabled
- @receiz/sdk stays locked to the same release version as the app.
- Compatibility
- The v96.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v96.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
The core change is that @receiz/sdk is no longer only a typed client and documentation package. It now ships a receiz CLI that can inspect proof payloads, run local fixture conformance, and generate a local-first proof memory starter. The CLI uses existing SDK validators, projections, and durable proof memory. It does not create a new conformance authority, a new issuer, a new verifier, a new server confirmation layer, or a new database authority.
Available outcomes
Capabilities now available
@receiz/sdk@96.0.0 ships the receiz CLI
@receiz/sdk@96.0.0 ships the receiz CLI.
receiz conformance validates packaged proof fixtures locally and reports zero…
receiz conformance validates packaged proof fixtures locally and reports zero network calls and zero DB calls.
receiz inspect <file projects a proof payload and prints its known Kai/proof head
receiz inspect <file projects a proof payload and prints its known Kai/proof head.
receiz init <dir writes a local-first durable proof memory starter
receiz init <dir writes a local-first durable proof memory starter.
SDK proof memory exposes passive ReceizSdkObservation events through onObservation
SDK proof memory exposes passive ReceizSdkObservation events through onObservation.
Copy-paste developer integrations now cover React proof memory, browser proof…
Copy-paste developer integrations now cover React proof memory, browser proof admission, append-sync routes, webhook receivers, and Sports card renderers.
test
test:sdk-release-contracts is wired into test:release-freeze.
@receiz/sdk stays locked to the same release version as the app
@receiz/sdk stays locked to the same release version as the app.
Primitive boundary
Primitives affected
- proof
- identity
- provenance
- verification
- public-witness
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 · provenance · verification · public-witness
- 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 04869531fb49ccb6596d628372f9f1bdb594c73de2ea8aab18fe0b3527a505d0. Source-family inventory: complete.
SHA-256 4a9cb2db42362af54fd68cf2544000932b4cd47b365637ec6e672c5088c12ea3SHA-256 82231acde5ade80aaad1f1b1c3928a2aed1b87c72886cea37299176eba4af82aSHA-256 820caa89047ddcf3da3864eb842673b6ced6417f404ce27e89a21a12caa49928SHA-256 9241fdd9a2c7ef3751811367c99732cdcbffa7b18702b8f81275aa1867f99914SHA-256 7a650e0352331b8801606b1027c3169bd24257f96016ee0aff50a214e882af1eSHA-256 78a7d21b50a11e80b9eacb1192cfe626a46eb7ebc792f2bb83e28676cff521e8SHA-256 007d4a0643d6dc9ea8a17482c21faa2c0e0fe07d771b0d02579e1b88ed5f9e34