Documented release
v97.1.0
SDK App Runtime And Commerce Cloud Rails Release
Release date 2026-06-30
Outcome
Outcome
v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
Changes
What changed
@receiz/sdk@97.1.0 exposes receiz.appState.publish(), publishRecord(), resolve(), byUrl(), byHost(), byCreator(), byNamespace(), byId()…
@receiz/sdk@97.1.0 exposes receiz.appState.publish(), publishRecord(), resolve(), byUrl(), byHost(), byCreator(), byNamespace(), byId(), restoreByUrl(), restoreByHost(), restoreById(), and zero-network projection extraction helpers.
Technical and authority boundary
@receiz/sdk@97.1.0 exposes receiz.appState.publish(), publishRecord(), resolve(), byUrl(), byHost(), byCreator(), byNamespace(), byId(), restoreByUrl(), restoreByHost(), restoreById(), and zero-network projection extraction helpers.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- @receiz/sdk@97.1.0 exposes receiz.appState.publish(), publishRecord(), resolve(), byUrl(), byHost(), byCreator(), byNamespace(), byId(), restoreByUrl(), restoreByHost(), restoreById(), and zero-network projection extraction helpers.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
receiz.doctor() and receiz.capabilities() give developers self-debugging capability reports for identity…
receiz.doctor() and receiz.capabilities() give developers self-debugging capability reports for identity, wallet, payments, proof store, media, domains, Twin, commerce, rewards, events, search, permissions, and jobs.
Technical and authority boundary
receiz.doctor() and receiz.capabilities() give developers self-debugging capability reports for identity, wallet, payments, proof store, media, domains, Twin, commerce, rewards, events, search, permissions, and jobs.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- receiz.doctor() and receiz.capabilities() give developers self-debugging capability reports for identity, wallet, payments, proof store, media, domains, Twin, commerce, rewards, events, search, permissions, and jobs.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
receiz.commerce.oneClickCheckout() composes delegated wallet summary reads and embedded checkout creation…
receiz.commerce.oneClickCheckout() composes delegated wallet summary reads and embedded checkout creation so wallet-first/card-delta flows are one typed call.
Technical and authority boundary
receiz.commerce.oneClickCheckout() composes delegated wallet summary reads and embedded checkout creation so wallet-first/card-delta flows are one typed call.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- receiz.commerce.oneClickCheckout() composes delegated wallet summary reads and embedded checkout creation so wallet-first/card-delta flows are one typed call.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
receiz.media.upload(), receiz.domains., receiz.events.subscribe(), receiz.proof.query(), and receiz.jobs.enqueue() give apps typed rails…
receiz.media.upload(), receiz.domains., receiz.events.subscribe(), receiz.proof.query(), and receiz.jobs.enqueue() give apps typed rails for the common Commerce Cloud substrate without hand-rolled route glue.
Technical and authority boundary
receiz.media.upload(), receiz.domains., receiz.events.subscribe(), receiz.proof.query(), and receiz.jobs.enqueue() give apps typed rails for the common Commerce Cloud substrate without hand-rolled route glue.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- receiz.media.upload(), receiz.domains., receiz.events.subscribe(), receiz.proof.query(), and receiz.jobs.enqueue() give apps typed rails for the common Commerce Cloud substrate without hand-rolled route glue.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
receiz.sandbox
receiz.sandbox. and CLI commands receiz doctor, receiz dev, receiz deploy-check, receiz seed-store, and receiz simulate-checkout make local development deterministic.
Technical and authority boundary
receiz.sandbox. and CLI commands receiz doctor, receiz dev, receiz deploy-check, receiz seed-store, and receiz simulate-checkout make local development deterministic.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- receiz.sandbox. and CLI commands receiz doctor, receiz dev, receiz deploy-check, receiz seed-store, and receiz simulate-checkout make local development deterministic.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed
The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed.
Technical and authority boundary
The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
Public app-state reads resolve through URL, host/domain, creator, namespace, and…
Public app-state reads resolve through URL, host/domain, creator, namespace, and object id read paths.
Technical and authority boundary
Public app-state reads resolve through URL, host/domain, creator, namespace, and object id read paths.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- Public app-state reads resolve through URL, host/domain, creator, namespace, and object id read paths.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
App-state projections are URL-normalized so https
App-state projections are URL-normalized so https://example.app and https://example.app/ resolve to the same public projection.
Technical and authority boundary
App-state projections are URL-normalized so https://example.app and https://example.app/ resolve to the same public projection.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- App-state projections are URL-normalized so https://example.app and https://example.app/ resolve to the same public projection.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
The SDK ships typed constants and helpers for canonical app-state…
The SDK ships typed constants and helpers for canonical app-state envelopes so developers and AI agents can publish public app state without hand-assembling feed boilerplate, then recover typed projection data without reimplementing response unwrapping.
Technical and authority boundary
The SDK ships typed constants and helpers for canonical app-state envelopes so developers and AI agents can publish public app state without hand-assembling feed boilerplate, then recover typed projection data without reimplementing response unwrapping.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- The SDK ships typed constants and helpers for canonical app-state envelopes so developers and AI agents can publish public app state without hand-assembling feed boilerplate, then recover typed projection data without reimplementing response unwrapping.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations
receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations.
Technical and authority boundary
receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
OIDC Connect consent uses correct browser redirect semantics and button readability
OIDC Connect consent uses correct browser redirect semantics and button readability.
Technical and authority boundary
OIDC Connect consent uses correct browser redirect semantics and button readability.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- OIDC Connect consent uses correct browser redirect semantics and button readability.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
Public Receiz record projection responses use the canonical absolute verification…
Public Receiz record projection responses use the canonical absolute verification URL and preserve owner-scoped behavior.
Technical and authority boundary
Public Receiz record projection responses use the canonical absolute verification URL and preserve owner-scoped behavior.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- Public Receiz record projection responses use the canonical absolute verification URL and preserve owner-scoped behavior.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
Admin performance analytics now measures the user-visible app experience instead…
Admin performance analytics now measures the user-visible app experience instead of misleading internal/admin surfaces.
Technical and authority boundary
Admin performance analytics now measures the user-visible app experience instead of misleading internal/admin surfaces.
- Why
- v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
- Capability enabled
- Admin performance analytics now measures the user-visible app experience instead of misleading internal/admin surfaces.
- Compatibility
- The v97.1.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.1.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
v97.1.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk: storefronts, marketplaces, rewards, blogs, directories, customer portals, access systems, and Commerce Cloud style products.
Available outcomes
Capabilities now available
@receiz/sdk@97.1.0 exposes receiz.appState.publish(), publishRecord(), resolve(), byUrl(), byHost(), byCreator(), byNamespace(), byId()…
@receiz/sdk@97.1.0 exposes receiz.appState.publish(), publishRecord(), resolve(), byUrl(), byHost(), byCreator(), byNamespace(), byId(), restoreByUrl(), restoreByHost(), restoreById(), and zero-network projection extraction helpers.
receiz.doctor() and receiz.capabilities() give developers self-debugging capability reports for identity…
receiz.doctor() and receiz.capabilities() give developers self-debugging capability reports for identity, wallet, payments, proof store, media, domains, Twin, commerce, rewards, events, search, permissions, and jobs.
receiz.commerce.oneClickCheckout() composes delegated wallet summary reads and embedded checkout creation…
receiz.commerce.oneClickCheckout() composes delegated wallet summary reads and embedded checkout creation so wallet-first/card-delta flows are one typed call.
receiz.media.upload(), receiz.domains., receiz.events.subscribe(), receiz.proof.query(), and receiz.jobs.enqueue() give apps typed rails…
receiz.media.upload(), receiz.domains., receiz.events.subscribe(), receiz.proof.query(), and receiz.jobs.enqueue() give apps typed rails for the common Commerce Cloud substrate without hand-rolled route glue.
receiz.sandbox
receiz.sandbox. and CLI commands receiz doctor, receiz dev, receiz deploy-check, receiz seed-store, and receiz simulate-checkout make local development deterministic.
The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed
The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed.
Public app-state reads resolve through URL, host/domain, creator, namespace, and…
Public app-state reads resolve through URL, host/domain, creator, namespace, and object id read paths.
App-state projections are URL-normalized so https
App-state projections are URL-normalized so https://example.app and https://example.app/ resolve to the same public projection.
The SDK ships typed constants and helpers for canonical app-state…
The SDK ships typed constants and helpers for canonical app-state envelopes so developers and AI agents can publish public app state without hand-assembling feed boilerplate, then recover typed projection data without reimplementing response unwrapping.
receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations
receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations.
OIDC Connect consent uses correct browser redirect semantics and button readability
OIDC Connect consent uses correct browser redirect semantics and button readability.
Public Receiz record projection responses use the canonical absolute verification…
Public Receiz record projection responses use the canonical absolute verification URL and preserve owner-scoped behavior.
Admin performance analytics now measures the user-visible app experience instead…
Admin performance analytics now measures the user-visible app experience instead of misleading internal/admin surfaces.
Primitive boundary
Primitives affected
- proof
- identity
- ownership
- settlement
- provenance
- media
- 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 · ownership · settlement · provenance · media · verification · public-witness
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Absent
- Package publication
- Unknown
- Deployment
- Not Performed
- Production smoke
- Unknown
- Signed attestation
- Unknown
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 d856ed4ac8ff9694bee3c65e125dc9d2a52bb1b28f3bc8e71649104ca1e28fc7. Source-family inventory: complete.
SHA-256 988485c4399212c16b4366f4ca1bea4b43532bd1d24a2cefe93af297871f6ef4SHA-256 1705b0c851cc1a4d2e48dc05032297809f8374ba61c02e94a1739b0b6aed86a8SHA-256 90cea1f3d9d2387c514a66ec8fdd0fee909d7a843e51c3ba82f703012a68a9d6SHA-256 8d2baaaad22a46a057ce479f87d6d4fedfd73ab29d0979411b434eead07405eaSHA-256 abc03a4b2fe9cf716bc831f466652301840d0eebb0dad2876bf781367bdb9741SHA-256 ed0bfa7dbb386f5c6f43b580c3bfd50a120e90a0e9a43b572483049da0066266