Documented release
v97.0.0
Public App-State Projection Rail And SDK Ecosystem Release
Release date 2026-06-30
Outcome
Outcome
v97.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
Changes
What changed
@receiz/sdk@97.0.0 exposes receiz.appState.publish(), publishRecord(), byUrl(), byHost(), byCreator(), byNamespace(), and byId()
@receiz/sdk@97.0.0 exposes receiz.appState.publish(), publishRecord(), byUrl(), byHost(), byCreator(), byNamespace(), and byId().
Technical and authority boundary
@receiz/sdk@97.0.0 exposes receiz.appState.publish(), publishRecord(), byUrl(), byHost(), byCreator(), byNamespace(), and byId().
- Why
- v97.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- @receiz/sdk@97.0.0 exposes receiz.appState.publish(), publishRecord(), byUrl(), byHost(), byCreator(), byNamespace(), and byId().
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- The backend exposes delegated public app-state publishing through POST /api/public-proof/registry/feed.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- Public app-state reads resolve through URL, host/domain, creator, namespace, and object id read paths.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- 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.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.
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.
- Why
- v97.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- 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.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- receiz.publicProof.registryFeed(feed) remains supported as an alias for existing integrations.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- OIDC Connect consent uses correct browser redirect semantics and button readability.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- Public Receiz record projection responses use the canonical absolute verification URL and preserve owner-scoped behavior.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.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.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
- Capability enabled
- Admin performance analytics now measures the user-visible app experience instead of misleading internal/admin surfaces.
- Compatibility
- The v97.0.0 compatibility record remains the exact boundary for this outcome.
- Migration
- The v97.0.0 migration record remains the exact adoption boundary for this outcome.
Purpose
Why it matters
v97.0.0 is the release that makes Receiz a practical substrate for developers building advanced public apps with @receiz/sdk.
Available outcomes
Capabilities now available
@receiz/sdk@97.0.0 exposes receiz.appState.publish(), publishRecord(), byUrl(), byHost(), byCreator(), byNamespace(), and byId()
@receiz/sdk@97.0.0 exposes receiz.appState.publish(), publishRecord(), byUrl(), byHost(), byCreator(), byNamespace(), and byId().
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.
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
- 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
- Normal
- Release approval
- v97.0.0-public-app-state-sdk-release
- Risk owner
- bjklock
Dated signed attestations apply only to their exact commit, tree, and build; package publication, deployment, and production smoke remain independent evidence dimensions.
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
- Change kinds
- capability
Independent dimensions
Release boundary status
- Repository release
- Documented
- Git tag
- Present
- Package publication
- Unknown
- Deployment
- Unknown
- Production smoke
- Unknown
- Signed attestation
- Present
Exact source bytes
Provenance
This Academy record is a projection beneath its sources. Record SHA-256 b4afcd105141cec178211164300fc1d8f48862f60a42f9b717478820c66a9bb3. Source-family inventory: complete.
SHA-256 8a94cdd4013c762f1a0750287e1eaada072596abee36c7793ffb04da2de92a71SHA-256 27efe51cd2b0d2b2b09bf6a991b19c4e359a626691960937ba2b18169f20b742SHA-256 92f636db2cb5f50096c9e26a79e382ffb3739c216f73742a48cfb04b51c52268SHA-256 ba474dae6002a7efab757e06000984ff55db696ca42b23d5905d07480d50a996SHA-256 69ee08fd9acc2bec9ddd51bdaace36414a30faff60f2d79484e177e1a5ea8c55SHA-256 1f662fcd10bda07a5478e3216835627585cf57560d96b9338e719fe3756ba1f5SHA-256 75f7cc885fcff69f2f19f21ec01d71932759cb0a03555ad18e3786fecd2e60a5SHA-256 3c59eb2a417e890ac607fd02074c9120d3768f7d539b93dbe166e4fe057bbc8dSHA-256 31faebd1f43632981e172198c000c6beb812e7d84d3d45bd337a50634478fc93