v74.0.0

# Release Notes

## v74.0.0
Release date: 2026-04-30

`v74.0.0` is the Receiz Key, identity artwork, and profile media release. In this offline verifier repository, the release work is publication of canonical `v74.0.0` artifacts and outward version-surface alignment only.

Canonical full release note: [docs/releases/v74.0.0.md](docs/releases/v74.0.0.md)
Product-truth freeze: [docs/releases/v74.0.0-product-truth.md](docs/releases/v74.0.0-product-truth.md)
Release checklist: [docs/releases/v74.0.0-checklist.md](docs/releases/v74.0.0-checklist.md)
Release process: [docs/releases/v74.0.0-process.md](docs/releases/v74.0.0-process.md)
Prior v73 archive: [docs/releases/v73.0.0.md](docs/releases/v73.0.0.md)

## Highlights
- Receiz Key restore is locked as a sovereign key-file recovery path proven by fresh key signatures and active key registration; PBI may attest new key export but is not required for already-held keys.
- Account now owns Receiz Key controls for private Identity Record PNG export, optional file-password protection, Identity Record PNG or legacy key JSON import, active/revoked key listing, refresh, and two-step revocation.
- Offline Receiz Key projection preserves verified portable state and admitted local identity proof even when the server misses later.
- Profile identity artwork derives deterministically from account creation Kai truth, with KaiSigil glyph geometry and size math kept canonical.
- PBI-signed identity seal and identity record artifacts append verified authorship state without replacing the base profile shell.
- Long-form profile originals preserve full text, title, hash, word count, and a compact Read affordance; attached Receiz URLs preserve exact href values.
- Profile video originals may use playback derivatives and range-aware proxying while original proof downloads stay canonical.
- Sold share positions remain local truth across market snapshots and route hydration, and portable state import preserves profile media/state fields with visible integrity failures.
- Release-governed version surfaces now move together to `v74.0.0` across package metadata, public verifier artifacts, shipped release badges, README pointers, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v74.0.0`.
- Repository release/docs surfaces now align to `v74.0.0`.
- Root package metadata now resolves cleanly at `v74.0.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Operational notes
- The broader release brief records tag `v73.0.0` at commit `fb2d82142` as the baseline and 44 commits plus release-candidate working-tree updates in scope.
- Published release surfaces now include the canonical `v74.0.0` release note, product-truth freeze, checklist, process, and updated docs indexes.
- The `v70.0.0` public alpha law, `v70.0.0` invariant register, `v73.0.0` ownership/vault continuity baseline, and `v64.0.0` value-loop invariants remain in force.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.

## Migration checklist
- No new database migrations are introduced by this documentation cut.
- Confirm Receiz Key restore, registration, export/import, active/revoked key listing, refresh, and two-step revocation gates.
- Confirm offline Receiz Key projection keeps admitted local identity proof when later server fetches miss.
- Confirm deterministic profile identity artwork, KaiSigil geometry, PBI-signed identity artifacts, and stable profile creation timestamps.
- Confirm long-form profile originals, attached-link preservation, and profile video derivative playback preserve canonical original proof.
- Confirm sold-position continuity and portable profile state import keep local truth and visible integrity failures.
- Update outward release/docs references to `v74.0.0`.
- Deploy updated `site/` artifacts.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v73.0.0
Release date: 2026-04-29

`v73.0.0` is the ownership, vault, and continuity release. In this offline verifier repository, the release work is publication of the `v72.0.0` archive, canonical `v73.0.0` artifacts, and outward version-surface alignment only.

Canonical full release note: [docs/releases/v73.0.0.md](docs/releases/v73.0.0.md)
Product-truth freeze: [docs/releases/v73.0.0-product-truth.md](docs/releases/v73.0.0-product-truth.md)
Release checklist: [docs/releases/v73.0.0-checklist.md](docs/releases/v73.0.0-checklist.md)
Release process: [docs/releases/v73.0.0-process.md](docs/releases/v73.0.0-process.md)
Included v72 archive: [docs/releases/v72.0.0.md](docs/releases/v72.0.0.md)

## Highlights
- Business account entity ownership and certificates now have first-class API, server, and contract coverage.
- Receipt ownership provenance and transfer flows now carry stronger proof bundles and route-level continuity.
- Vault and original-download paths preserve portable verified records instead of treating recovered artifact state as disposable UI state.
- Account brain selections expose compact proof-bundle data in a dismissible mobile-friendly popover, with Open shown only for nodes that have a real route target.
- Account authority navigation names the offline surface as Offline Verifier and consolidates Privacy/Terms into Legal while keeping Security one tap away.
- Account, profile, composer, chat, discovery, and world twin surfaces keep post-v72 UI improvements under explicit continuity and fit contracts.
- Release-governed version surfaces now move together to `v73.0.0` across package metadata, public verifier artifacts, shipped release badges, README pointers, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v73.0.0`.
- Repository release/docs surfaces now align to `v73.0.0`.
- Root package metadata now resolves cleanly at `v73.0.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Operational notes
- The broader release brief records `61ae0ef2b` as the `v72.0.0` baseline, but this offline verifier checkout does not contain that commit object or a `v72.0.0` tag locally.
- Published release surfaces now include the canonical `v72.0.0` archive and the `v73.0.0` release note, product-truth freeze, checklist, process, and updated docs indexes.
- The `v70.0.0` public alpha law, `v70.0.0` invariant register, `v72.0.0` stable continuity locks, and `v64.0.0` value-loop invariants remain in force.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.

## Migration checklist
- No new database migrations are introduced by this documentation cut.
- Confirm business ownership APIs, certificate generation, and holdings reads have contract coverage.
- Confirm receipt provenance and transfer proof do not rewrite artifact identity or canonical receipt truth.
- Confirm vault decode, verifier, and original-download state preserve portable verified record truth.
- Confirm account brain selected-node proof data and route-target-only Open actions.
- Confirm account authority navigation names Offline Verifier, consolidates Privacy/Terms into Legal, and keeps Security one tap away.
- Confirm world twin face authority and photoreal shell fit remain bounded by contracts.
- Update outward release/docs references to `v73.0.0`.
- Deploy updated `site/` artifacts.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v72.0.0
Release date: 2026-04-28

`v72.0.0` is the stable continuity release. In this offline verifier repository, the release work is publication of the canonical `v72.0.0` artifacts and release-governed version-surface expectations only.

Canonical full release note: [docs/releases/v72.0.0.md](docs/releases/v72.0.0.md)
Product-truth freeze: [docs/releases/v72.0.0-product-truth.md](docs/releases/v72.0.0-product-truth.md)
Release checklist: [docs/releases/v72.0.0-checklist.md](docs/releases/v72.0.0-checklist.md)
Release process: [docs/releases/v72.0.0-process.md](docs/releases/v72.0.0-process.md)

## Highlights
- Account switching clears actor-scoped route warmth and refuses to preserve market/private wallet state unless the viewer user id matches.
- Compact mobile Live Twin rendered-portrait overlays apply a bounded lower-left face-lock correction so eyes and mouth stay on the person's face without restoring the old oversized mobile downshift.
- `/<username>` remains canonical profile truth; `?manage=1` remains owner permissions only.
- Owner/private enrichment must not make signed-in profile first paint slower than public profile truth.
- Useful hydration repairs stay: stale app-open state can refresh in the background without replacing a settled visible shell.
- Release-governed version surfaces moved together to `v72.0.0` at the stable continuity cut.

## Verifier impact
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Operational notes
- The `v70.0.0` public alpha law remains intact.
- The `v64.0.0` value-loop invariants remain in force.
- In this offline verifier repository, `v72.0.0` is now retained as historical release truth while current-release pointers move to `v73.0.0`.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v70.0.0
Release date: 2026-04-24

`v70.0.0` is the first public alpha release cut of Receiz as an end-to-end product system. In this offline verifier repository, the release work is publication of the canonical `v70.0.0` artifacts, product-truth reference documents, growth record, invariant register, and outward version-surface alignment only.

Canonical full release note: [docs/releases/v70.0.0.md](docs/releases/v70.0.0.md)
Product-truth freeze: [docs/releases/v70.0.0-product-truth.md](docs/releases/v70.0.0-product-truth.md)
Release checklist: [docs/releases/v70.0.0-checklist.md](docs/releases/v70.0.0-checklist.md)
Release process: [docs/releases/v70.0.0-process.md](docs/releases/v70.0.0-process.md)
Growth from v60: [docs/releases/v70.0.0-growth-from-v60.md](docs/releases/v70.0.0-growth-from-v60.md)
Invariant register: [docs/releases/v70.0.0-invariant-register.md](docs/releases/v70.0.0-invariant-register.md)
Docs manifest: [docs/releases/v70.0.0-docs-manifest.md](docs/releases/v70.0.0-docs-manifest.md)
Literal product law: [docs/literal-product-law.md](docs/literal-product-law.md)
PBI recovery and Receiz ID binding: [docs/pbi-recovery-receiz-id-binding.md](docs/pbi-recovery-receiz-id-binding.md)

## Highlights
- Receiz ID is the primary everyday login rail; `/signin` is a pass-through route.
- Existing local Receiz ID accounts go directly to the managed profile, and cold devices create a local Receiz ID before continuing to the new managed profile.
- `/<username>` is canonical profile truth; `/<username>?manage=1` is the same profile with owner powers layered on top.
- Settlement remains proof-native value, Reserve remains funded external-conversion value, and notes stay Reserve-only.
- Certificates and shares bridge live proof-native value into buyer-funded Reserve.
- Market sells preserve funded/unfunded causality and patch visible truth from the known trade result.
- Receiz ID, PBI/keyfile proof, route snapshots, wallet graphs, market positions, twin state, and proof bundles are real local truth.
- Stale runtime, stale service-worker, and stale session states recover through local proof or server resync and return to the route the user was on.
- Live twins cannot fall back to a profile picture as an identity substitute.
- Mind trail ZIP downloads package every file with Receiz proof material so the downloaded bundle verifies as a proof bundle.
- Release-governed version surfaces now move together to `v70.0.0` across package metadata, public verifier artifacts, shipped release badges, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v70.0.0`.
- Repository release/docs surfaces now align to `v70.0.0`.
- Root package metadata now resolves cleanly at `v70.0.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Preserved verifier contract
- Trusted-signature success still requires verified `signatureV4`.
- Trusted-signature failure semantics remain fail-closed:
  - invalid present `signatureV4` -> `Trusted signature invalid`
  - unavailable present `signatureV4` -> `Trusted signature unavailable`
  - missing `signatureV4` -> `Trusted signature missing. Expected signatureV4.`
- Effective anchor context remains required (explicit or derivable).
- Groth16 fields remain required and only real `g16:` proof payloads are accepted.
- Carrier extraction/normalization for PNG, PDF, SVG, JSON, trailer, and `.receizbundle`.
- Package ZIP/folder manifest verification paths.
- Canonical identity derivation and artifact-binding checks.
- Fail-closed verification semantics.

## Operational notes
- Published release surfaces now include the canonical `v70.0.0` release note, product-truth freeze, checklist, process, growth record, invariant register, docs manifest, literal product law, PBI recovery binding reference, and updated docs indexes.
- The `v64.0.0` value-loop invariants remain in force.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.
- No verifier proof-format or producer payload migration is implied by these repository release/documentation updates alone.

## Migration checklist
- No new database migrations are introduced by this documentation cut.
- Confirm Receiz ID is the everyday login rail and `/signin` is pass-through only.
- Confirm PBI/keyfile recovery binds back to local Receiz ID truth.
- Confirm `/<username>` and `/<username>?manage=1` share canonical profile truth.
- Confirm Settlement/Reserve causality, Reserve-only notes, certificate funding, and market funded/unfunded sale splits.
- Confirm local proof and deterministic local truth outrank weaker stale network/session payloads.
- Confirm route-preserving stale-runtime and service-worker recovery.
- Confirm live twin identity image locking and proof-sealed mind trail ZIP downloads.
- Update outward release/docs references to `v70.0.0`.
- Deploy updated `site/` artifacts.
- Publish the `v70.0.0` release note, product-truth freeze, checklist, process, growth record, invariant register, docs manifest, product-truth reference docs, and updated docs indexes.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v66.0.0
Release date: 2026-04-21

`v66.0.0` is the local proof continuity release. In this offline verifier repository, the release work is publication of the canonical `v66.0.0` artifacts, local-proof reference documents, and outward version-surface alignment only.

Canonical full release note: [docs/releases/v66.0.0.md](docs/releases/v66.0.0.md)
Product-truth freeze: [docs/releases/v66.0.0-product-truth.md](docs/releases/v66.0.0-product-truth.md)
Release checklist: [docs/releases/v66.0.0-checklist.md](docs/releases/v66.0.0-checklist.md)
Release process: [docs/releases/v66.0.0-process.md](docs/releases/v66.0.0-process.md)
Experience-first engineering: [docs/experience-first-engineering.md](docs/experience-first-engineering.md)
Verified history first principles: [docs/verified-history-first-principles.md](docs/verified-history-first-principles.md)
Offline verified register: [docs/offline-verified-register.md](docs/offline-verified-register.md)

## Highlights
- Local proof is now frozen as the default authority when the node already holds stronger verified truth.
- Verified-register-backed proof outranks weaker legacy offline evidence.
- Account surfaces preserve valid local identity roots when the session API is unavailable, anonymous, or weaker.
- Public Twin projection can come from the local twin mind register and local model rail before online streaming is needed.
- Twin mind PNG import requires portable public-key verification instead of server-secret HMAC authority for canonical import.
- World, Explore, Wallet, Market, and tracked-position surfaces preserve known deterministic state unless a transport payload proves a stronger state.
- Service-worker offline persistence is explicit through `x-receiz-offline-persist` response headers for verified snapshots.
- No new database migration is required by the release docs themselves.
- Release-governed version surfaces now move together to `v66.0.0` across package metadata, public verifier artifacts, shipped release badges, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v66.0.0`.
- Repository release/docs surfaces now align to `v66.0.0`.
- Root package metadata now resolves cleanly at `v66.0.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Preserved verifier contract
- Trusted-signature success still requires verified `signatureV4`.
- Trusted-signature failure semantics remain fail-closed:
  - invalid present `signatureV4` -> `Trusted signature invalid`
  - unavailable present `signatureV4` -> `Trusted signature unavailable`
  - missing `signatureV4` -> `Trusted signature missing. Expected signatureV4.`
- Effective anchor context remains required (explicit or derivable).
- Groth16 fields remain required and only real `g16:` proof payloads are accepted.
- Carrier extraction/normalization for PNG, PDF, SVG, JSON, trailer, and `.receizbundle`.
- Package ZIP/folder manifest verification paths.
- Canonical identity derivation and artifact-binding checks.
- Fail-closed verification semantics.

## Operational notes
- Broader platform validation for `v66.0.0` is captured in the canonical release note, process, and checklist, including local proof authority classification, verified-register precedence, offline identity continuity, deterministic ledger proof bundles, local twin register projection, twin mind public-key import, verified-snapshot persistence, and market/tracked-position local truth preservation.
- Published release surfaces now include the canonical `v66.0.0` release note, the `v66.0.0` product-truth freeze, the `v66.0.0` checklist, the `v66.0.0` process document, and the local-proof reference docs.
- The `v64.0.0` value-loop invariants remain in force.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.
- No verifier proof-format or producer payload migration is implied by these repository release/documentation updates alone.

## Migration checklist
- No new database migrations are introduced by this documentation cut.
- Confirm local verified-register proof outranks weaker offline or legacy evidence.
- Confirm wallet transaction receipts verify deterministic ledger proof bundles before treating ledger claims as truth.
- Confirm anonymous or missing network session payloads do not erase locally held identity proof.
- Confirm local twin register projection wins for the visible reply when present.
- Confirm twin mind portable import/export production keys are configured.
- Confirm deterministic public snapshots and private account snapshots opt into explicit offline persistence.
- Confirm wallet, market, tracked-position, World, and Explore surfaces preserve known state until stronger state is proven.
- Update outward release/docs references to `v66.0.0`.
- Deploy updated `site/` artifacts.
- Publish the `v66.0.0` release note, product-truth freeze, checklist, process, local-proof reference docs, and updated docs indexes.
- No producer payload or proof-format migration is implied by these verifier-repo documentation updates alone.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v64.0.0
Release date: 2026-04-21

`v64.0.0` is the complete value-loop release. In this offline verifier repository, the release work is publication of the canonical `v64.0.0` artifacts plus outward version-surface alignment only.

Canonical full release note: [docs/releases/v64.0.0.md](docs/releases/v64.0.0.md)
Product-truth freeze: [docs/releases/v64.0.0-product-truth.md](docs/releases/v64.0.0-product-truth.md)
Release checklist: [docs/releases/v64.0.0-checklist.md](docs/releases/v64.0.0-checklist.md)
Release process: [docs/releases/v64.0.0-process.md](docs/releases/v64.0.0-process.md)
Value-loop invariants: [docs/value-loop-invariants.md](docs/value-loop-invariants.md)

## Highlights
- Receiz now documents one closed value loop: create value, hold Settlement, send proof-native value, use Reserve for notes and wire transfers, issue shares into certificates, let buyers fund certificates, and credit sellers only when value is actually funded.
- Settlement is the primary proof-native liquid value lane.
- Reserve is the funded external-conversion lane for notes, sends, positions, and wire transfers.
- Sends and buys deploy funded Reserve first, then Settlement covers the remainder.
- Market sells split into funded Reserve and unfunded Settlement.
- Settlement shares and certificates bridge Settlement to buyer-funded Reserve.
- Certificate issue locks value, and funded certificate sale credits the seller.
- No new value state or database migration is added by this documentation cut.
- Release-governed version surfaces now move together to `v64.0.0` across package metadata, public verifier artifacts, shipped release badges, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v64.0.0`.
- Repository release/docs surfaces now align to `v64.0.0`.
- Root package metadata now resolves cleanly at `v64.0.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Preserved verifier contract
- Trusted-signature success still requires verified `signatureV4`.
- Trusted-signature failure semantics remain fail-closed:
  - invalid present `signatureV4` -> `Trusted signature invalid`
  - unavailable present `signatureV4` -> `Trusted signature unavailable`
  - missing `signatureV4` -> `Trusted signature missing. Expected signatureV4.`
- Effective anchor context remains required (explicit or derivable).
- Groth16 fields remain required and only real `g16:` proof payloads are accepted.
- Carrier extraction/normalization for PNG, PDF, SVG, JSON, trailer, and `.receizbundle`.
- Package ZIP/folder manifest verification paths.
- Canonical identity derivation and artifact-binding checks.
- Fail-closed verification semantics.

## Operational notes
- Broader platform validation for `v64.0.0` is captured in the canonical release note, process, and checklist, including wallet account-lane truth, account quote math, Reserve-first send/buy execution, market funded/unfunded sale splits, certificate funding causality, Reserve-only note issuance, Reserve-funded wire transfer, and value-state metadata preservation.
- Published release surfaces now include the canonical `v64.0.0` release note, the `v64.0.0` product-truth freeze, the `v64.0.0` checklist, the `v64.0.0` process document, and the canonical value-loop invariants.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.
- No verifier proof-format or producer payload migration is implied by these repository release/documentation updates alone.
- The broader product baseline referenced by this release is the `v63.2.0` value-state release; this repository advances its public release surface from `v61.0.0` to `v64.0.0`.

## Migration checklist
- No new database migrations are introduced by this documentation cut.
- No new value state is added by `v64.0.0`.
- Confirm wallet leads with Settlement balance, USD first, with phi equivalent underneath where phi context is shown.
- Confirm Reserve appears beneath Settlement as the funded external-conversion lane.
- Confirm Settlement and Reserve popover charts use account-lane truth and account quote math.
- Confirm Market wallet panel and portfolio chart use real phi conversion math through the wallet account quote.
- Confirm notes stay Reserve-only.
- Confirm wire transfer draws from Reserve.
- Confirm sends and buys deploy Reserve before Settlement remainder.
- Confirm market sells split funded Reserve and unfunded Settlement.
- Confirm certificate issue locks value and funded certificate sale credits the seller only when funded.
- Update outward release/docs references to `v64.0.0`.
- Deploy updated `site/` artifacts.
- Publish the `v64.0.0` release note, product-truth freeze, checklist, process, invariants, and updated docs indexes.
- No producer payload or proof-format migration is implied by these verifier-repo documentation updates alone.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v61.0.0
Release date: 2026-04-19

`v61.0.0` is the governed historical-continuity and runtime-discipline release on top of `v60.0.0`. In this offline verifier repository, the release work is publication of the canonical `v61.0.0` artifacts plus outward version-surface alignment only.

Canonical full release note: [docs/releases/v61.0.0.md](docs/releases/v61.0.0.md)
Product-truth freeze: [docs/releases/v61.0.0-product-truth.md](docs/releases/v61.0.0-product-truth.md)
Release checklist: [docs/releases/v61.0.0-checklist.md](docs/releases/v61.0.0-checklist.md)

## Highlights
- Pre-v4 receiz now sits under governed historical continuity: frozen cohort membership, sealed governance artifact support, explicit `Historical` trust presentation, and historical package delivery that preserves original bytes.
- Holder-aware public market witness truth from `v60.1.0` remains the floor, and market exits now stay on deterministic internal routes through the shared stable client-navigation path.
- Settled home and profile twin shells keep hidden warming hidden and defer richer runtime promotion until explicit activation, including on compact touch devices.
- The release line now publishes its operating standards around experience-first engineering, expensive truth, fast entry, and governed historical continuity as part of repository truth.
- No new database migrations are added beyond the `v60.0.0` baseline.
- Release-governed version surfaces now move together to `v61.0.0` across package metadata, public verifier artifacts, shipped release badges, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v61.0.0`.
- Repository release/docs surfaces now align to `v61.0.0`.
- Root package metadata now resolves cleanly at `v61.0.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Preserved verifier contract
- Trusted-signature success still requires verified `signatureV4`.
- Trusted-signature failure semantics remain fail-closed:
  - invalid present `signatureV4` -> `Trusted signature invalid`
  - unavailable present `signatureV4` -> `Trusted signature unavailable`
  - missing `signatureV4` -> `Trusted signature missing. Expected signatureV4.`
- Effective anchor context remains required (explicit or derivable).
- Groth16 fields remain required and only real `g16:` proof payloads are accepted.
- Carrier extraction/normalization for PNG, PDF, SVG, JSON, trailer, and `.receizbundle`.
- Package ZIP/folder manifest verification paths.
- Canonical identity derivation and artifact-binding checks.
- Fail-closed verification semantics.

## Operational notes
- Broader platform validation for `v61.0.0` is captured in the canonical release note and checklist, including historical cohort governance, deterministic market exit continuity, settled-shell runtime discipline, compact verified-player control tightening, and release-surface lockstep.
- Published release surfaces now include the canonical `v61.0.0` release note, the `v61.0.0` product-truth freeze, and the `v61.0.0` checklist.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.
- No verifier proof-format or producer payload migration is implied by these repository release/documentation updates alone.
- `v60.1.0` has a dedicated release note in the repository, but there is no dedicated `v60.2.0` through `v60.4.x` public release note or matching repository tag, so the canonical `v61.0.0` note records the full post-`v60.0.0` product delta in one governed release record.

## Migration checklist
- No new database migrations beyond the `v60.0.0` baseline.
- Confirm public market witness timing and holder count still derive from real holder activity, and deterministic market exits stay on the stable client-navigation path for Receiz routes.
- Confirm home and profile twin shells do not visually remount or upgrade after settlement, compact touch devices keep full twin hydration on-demand, and the home dock only promotes the full runtime after explicit interaction.
- Confirm the verified-player audio control glass stays compact and legible on small layouts.
- Confirm historical pre-v4 records render as `Historical` rather than being silently treated as current `Verified` or generic warnings.
- Confirm historical downloads preserve raw bytes and include the sealed governance bundle instead of rewriting the original artifact identity.
- Confirm the pinned historical cohort artifact and payload stay byte-stable, and no public/private cohort boundary drift has occurred.
- Update outward release/docs references to `v61.0.0`.
- Deploy updated `site/` artifacts.
- Publish the `v61.0.0` release note, product-truth freeze, checklist, and updated docs indexes.
- No producer payload or proof-format migration is implied by these verifier-repo documentation updates alone.

## Security posture
Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.

## v60.1.0
Release date: 2026-04-18

`v60.1.0` is the continuity-and-market-proof release on top of `v60.0.0`. In this offline verifier repository, the release work is publication of the canonical `v60.1.0` artifacts plus outward version-surface alignment only.

Canonical full release note: [docs/releases/v60.1.0.md](docs/releases/v60.1.0.md)
Product-truth freeze: [docs/releases/v60.1.0-product-truth.md](docs/releases/v60.1.0-product-truth.md)
Release checklist: [docs/releases/v60.1.0-checklist.md](docs/releases/v60.1.0-checklist.md)

## Highlights
- Public profile asset markets now derive holder count and latest witness timing from live public positions and buy activity.
- The market desk, chart dock, and public market metadata surfaces are tighter and more legible on compact devices, especially in public and signed-out flows.
- Home and profile twin shells keep background preload hidden until explicit open intent, preventing late visible promotion after settlement.
- Public profile route assembly is lighter, and `MarketValuePill` sigils now use deterministic surface-scoped IDs to avoid hydration drift.
- No new database migrations are added beyond the `v60.0.0` baseline.
- Release-governed version surfaces now move together to `v60.1.0` across package metadata, public verifier artifacts, shipped release badges, and current-release documentation.

## Verifier impact
- Current shipped verifier, studio, and settlement entrypoints are marked `v60.1.0`.
- Repository release/docs surfaces now align to `v60.1.0`.
- Root package metadata now resolves cleanly at `v60.1.0`.
- No verifier proof-format or producer payload migration is implied by this release update.
- Verifier trust semantics remain unchanged relative to `v60.0.0`.

## Preserved verifier contract
- Trusted-signature success still requires verified `signatureV4`.
- Trusted-signature failure semantics remain fail-closed:
  - invalid present `signatureV4` -> `Trusted signature invalid`
  - unavailable present `signatureV4` -> `Trusted signature unavailable`
  - missing `signatureV4` -> `Trusted signature missing. Expected signatureV4.`
- Effective anchor context remains required (explicit or derivable).
- Groth16 fields remain required and only real `g16:` proof payloads are accepted.
- Carrier extraction/normalization for PNG, PDF, SVG, JSON, trailer, and `.receizbundle`.
- Package ZIP/folder manifest verification paths.
- Canonical identity derivation and artifact-binding checks.
- Fail-closed verification semantics.

## Operational notes
- Broader platform validation for `v60.1.0` is captured in the canonical release note and checklist, including holder-aware public market witness truth, compact market-desk polish, hidden-only twin preload, profile-route continuity, deterministic sigil hydration, and release-surface lockstep.
- Published release surfaces now include the canonical `v60.1.0` release note, the `v60.1.0` product-truth freeze, and the `v60.1.0` checklist.
- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.
- No verifier proof-format or producer payload migration is implied by these repository release/documentation updates alone.
- There is no dedicated `v60.0.1` release note or tag in the repository, so the canonical `v60.1.0` note records the full post-`v60.0.0` product delta in one governed release record.

## Migration checklist
- No new database migrations beyond the `v60.0.0` baseline.
- Confirm public profile asset markets show holder count and latest witness timing from real public holder activity.
- Confirm market buy continuation still survives passkey and funding fallback, and sell stays hidden when the viewer has no position.
- Confirm home and profile twin shells do not visually remount or upgrade after the page has already settled.
- Confirm opening the twin explicitly still promotes the full twin module cleanly.
- Confirm profile, player, artifact, and home market pills render without hydration ID drift.
- Update outward release/docs references to `v60.1.0`.
- Deploy updated `site/` artifacts.
- Publish the `v60.1.0` release note, product-truth freeze, checklist, and updated docs indexes.
- No producer payload or proof-format migration is implied by these verifier-repo documentation updates alone.

Author: kojibai

CHANGELOG.md

@@ -2,6 +2,32 @@
 
 All notable changes to this project will be documented in this file.
 
+## [v74.0.0] - 2026-04-30
+
+### Changed
+- Advanced the current release/documentation surface from `v73.0.0` to `v74.0.0`.
+- Updated canonical root package metadata and set `package.json` to `v74.0.0`.
+- Published the canonical `v74.0.0` Receiz Key, identity artwork, and profile media release artifacts:
+  - `docs/releases/v74.0.0.md`
+  - `docs/releases/v74.0.0-product-truth.md`
+  - `docs/releases/v74.0.0-checklist.md`
+  - `docs/releases/v74.0.0-process.md`
+- Updated current-release references in repository docs and verifier-contract docs to point at `v74.0.0`.
+- Aligned public release framing around sovereign Receiz Key restore, account key controls, deterministic profile identity artwork, PBI-signed identity artifacts, stable profile creation timestamps, long-form profile originals, attached-link preservation, video playback derivatives, sold-position continuity, and portable profile state import.
+- No new database migration is introduced by this documentation cut.
+- Updated shipped version markers in published verifier, studio, and settlement entrypoints to `v74.0.0`.
+
+### Kept
+- File-first verification remains authoritative and deterministic.
+- Trusted-signature gating remains `signatureV4`-required for verified outcomes.
+- Effective anchor context remains required for verified outcomes.
+- Groth16 fields remain required and only real `g16:` proof payloads are accepted.
+- Carrier extraction and normalization rules for PNG, PDF, SVG, JSON, trailer, and `.receizbundle`.
+- Package ZIP/folder manifest verification paths.
+- Canonical field validation and artifact binding checks.
+- Fail-closed verification model.
+- The `v70.0.0` public alpha law, `v73.0.0` ownership/vault continuity baseline, and `v64.0.0` value-loop invariants remain in force.
+
 ## [v73.0.0] - 2026-04-29
 
 ### Changed

README.md

@@ -2,20 +2,19 @@
 
 Verify a file offline. Proof is in the file.
 
-Current release: `v73.0.0`
-
-## What changed in v73.0.0
-- Current release/docs surfaces are aligned to `v73.0.0`.
-- Added the `v72.0.0` stable continuity release archive at [docs/releases/v72.0.0.md](docs/releases/v72.0.0.md).
-- Published the canonical `v73.0.0` ownership, vault, and continuity release note at [docs/releases/v73.0.0.md](docs/releases/v73.0.0.md).
-- Published the release-scoped product-truth freeze at [docs/releases/v73.0.0-product-truth.md](docs/releases/v73.0.0-product-truth.md).
-- Published the release checklist at [docs/releases/v73.0.0-checklist.md](docs/releases/v73.0.0-checklist.md).
-- Published the release process at [docs/releases/v73.0.0-process.md](docs/releases/v73.0.0-process.md).
-- `v73.0.0` carries forward the `v70.0.0` public alpha law and the `v72.0.0` stable continuity locks while adding business account ownership, receipt provenance, vault portability, account brain proof detail, Offline Verifier authority navigation, and bounded world twin fit contracts.
+Current release: `v74.0.0`
+
+## What changed in v74.0.0
+- Current release/docs surfaces are aligned to `v74.0.0`.
+- Published the canonical `v74.0.0` Receiz Key, identity artwork, and profile media release note at [docs/releases/v74.0.0.md](docs/releases/v74.0.0.md).
+- Published the release-scoped product-truth freeze at [docs/releases/v74.0.0-product-truth.md](docs/releases/v74.0.0-product-truth.md).
+- Published the release checklist at [docs/releases/v74.0.0-checklist.md](docs/releases/v74.0.0-checklist.md).
+- Published the release process at [docs/releases/v74.0.0-process.md](docs/releases/v74.0.0-process.md).
+- `v74.0.0` carries forward the `v70.0.0` public alpha law and the `v73.0.0` ownership/vault continuity baseline while adding Receiz Key restore and revocation, deterministic profile identity artwork, PBI-signed identity artifacts, stable profile creation truth, long-form profile originals, exact attached-link preservation, video playback derivatives, sold-position continuity, and portable profile state import.
 - The `v64.0.0` value-loop invariants remain in force.
 - No new database migration is required by this documentation cut.
-- Current shipped verifier, studio, and settlement entrypoints now display `v73.0.0`.
-- Root package metadata now resolves cleanly to `v73.0.0`.
+- Current shipped verifier, studio, and settlement entrypoints now display `v74.0.0`.
+- Root package metadata now resolves cleanly to `v74.0.0`.
 - Verifier semantics remain unchanged relative to `v60.0.0`.
 - Core verifier outcomes remain file-authoritative, deterministic, and fail-closed.
 
@@ -33,9 +32,9 @@ Current release: `v73.0.0`
   </tr>
 </table>
 
-The repo-local conformance hub at [docs/conformance/README.md](docs/conformance/README.md) tracks the latest vendored conformance snapshot in this repository. It includes live badge surfaces, current imported results, and suite-by-suite requirement coverage docs for the currently imported suites; the broader `v73.0.0` release is documented in the release note and can be vendored here on the next snapshot refresh.
+The repo-local conformance hub at [docs/conformance/README.md](docs/conformance/README.md) tracks the latest vendored conformance snapshot in this repository. It includes live badge surfaces, current imported results, and suite-by-suite requirement coverage docs for the currently imported suites; the broader `v74.0.0` release is documented in the release note and can be vendored here on the next snapshot refresh.
 
-## Release train highlights (v14 -> v73)
+## Release train highlights (v14 -> v74)
 - `v14.0.0`: UI release marker advanced to `v14.0.0`; app entrypoint rename started (`receiz-offline-verifier.html` -> `offline-verifier.html`).
 - `v15.0.0` / `v15.5.0`: runtime/doc route references aligned to `/offline-verifier.html`; release markers advanced.
 - `v16.0.0`: wording shifted from "original/sealed artifact" language to consistent "file/sealed file" language.
@@ -84,6 +83,7 @@ The repo-local conformance hub at [docs/conformance/README.md](docs/conformance/
 - `v70.0.0`: release/docs alignment for the public alpha cut, including one-click Receiz ID entry, canonical `/<username>` profile truth, complete Settlement/Reserve value-loop causality, local-first/server-always recovery, route-preserving stale-runtime recovery, live twin identity locking, proof-sealed world trail bundles, and the `v70.0.0` invariant register; verifier semantics remain unchanged from `v60.0.0`.
 - `v72.0.0`: release/docs archive for the stable continuity cut, including actor-scoped route warmth clearing on account switch and compact mobile Live Twin face-lock overlay fit; verifier semantics remain unchanged from `v60.0.0`.
 - `v73.0.0`: release/docs alignment for the ownership, vault, and continuity cut, including business account ownership, receipt provenance, vault portability, account brain proof detail, Offline Verifier authority navigation, and bounded world twin fit contracts; verifier semantics remain unchanged from `v60.0.0`.
+- `v74.0.0`: release/docs alignment for the Receiz Key, identity artwork, and profile media cut, including sovereign Receiz Key restore, deterministic profile identity artwork, PBI-signed identity artifacts, stable profile creation truth, long-form originals, attached-link preservation, video derivatives, sold-position continuity, and portable profile state import; verifier semantics remain unchanged from `v60.0.0`.
 
 ## Supported artifact inputs (v60)
 1. PNG artifact containing exactly one `receiz.proof_bundle` text chunk.
@@ -149,21 +149,25 @@ Machine-readable schemas are provided in [docs/schemas](docs/schemas):
 - [receiz-bundle-envelope.schema.json](docs/schemas/receiz-bundle-envelope.schema.json)
 
 ## Repository layout
-- [docs/README.md](docs/README.md): documentation map for `v73.0.0`.
+- [docs/README.md](docs/README.md): documentation map for `v74.0.0`.
 - [site/index.html](site/index.html): published verifier entrypoint.
 - [apps/offline-verifier.html](apps/offline-verifier.html): mirrored app entrypoint.
 - [apps/offline-record-seal.html](apps/offline-record-seal.html): offline record, seal, and verify studio surface.
 - [apps/offline-settlement.html](apps/offline-settlement.html): offline settlement bundle builder.
-- [docs/releases/v73.0.0.md](docs/releases/v73.0.0.md): canonical `v73.0.0` ownership, vault, and continuity release note.
+- [docs/releases/v74.0.0.md](docs/releases/v74.0.0.md): canonical `v74.0.0` Receiz Key, identity artwork, and profile media release note.
+- [docs/releases/v74.0.0-product-truth.md](docs/releases/v74.0.0-product-truth.md): `v74.0.0` product-truth freeze document.
+- [docs/releases/v74.0.0-checklist.md](docs/releases/v74.0.0-checklist.md): release-prep checklist and additional gates for `v74.0.0`.
+- [docs/releases/v74.0.0-process.md](docs/releases/v74.0.0-process.md): release-prep process for `v74.0.0`.
+- [docs/releases/v73.0.0.md](docs/releases/v73.0.0.md): canonical `v73.0.0` ownership, vault, and continuity release archive.
 - [docs/releases/v73.0.0-product-truth.md](docs/releases/v73.0.0-product-truth.md): `v73.0.0` product-truth freeze document.
 - [docs/releases/v73.0.0-checklist.md](docs/releases/v73.0.0-checklist.md): release-prep checklist and additional gates for `v73.0.0`.
 - [docs/releases/v73.0.0-process.md](docs/releases/v73.0.0-process.md): release-prep process for `v73.0.0`.
 - [docs/releases/v72.0.0.md](docs/releases/v72.0.0.md): canonical `v72.0.0` stable continuity release archive.
 - [docs/releases/v72.0.0-product-truth.md](docs/releases/v72.0.0-product-truth.md): `v72.0.0` product-truth freeze document.
 - [docs/releases/v72.0.0-checklist.md](docs/releases/v72.0.0-checklist.md): release-prep checklist and additional gates for `v72.0.0`.
 - [docs/releases/v72.0.0-process.md](docs/releases/v72.0.0-process.md): release-prep process for `v72.0.0`.
-- [docs/releases/v70.0.0-invariant-register.md](docs/releases/v70.0.0-invariant-register.md): public alpha invariant register carried forward by `v73.0.0`.
-- [docs/literal-product-law.md](docs/literal-product-law.md): literal product law carried forward for `v73.0.0`.
+- [docs/releases/v70.0.0-invariant-register.md](docs/releases/v70.0.0-invariant-register.md): public alpha invariant register carried forward by `v74.0.0`.
+- [docs/literal-product-law.md](docs/literal-product-law.md): literal product law carried forward for `v74.0.0`.
 - [docs/experience-first-engineering.md](docs/experience-first-engineering.md): experience-first rules for local proof and deterministic state.
 - [docs/verified-history-first-principles.md](docs/verified-history-first-principles.md): append-only history and stronger-known-truth principles.
 - [docs/offline-verified-register.md](docs/offline-verified-register.md): local register semantics for verified offline truth.

RELEASE_NOTES.md

@@ -1,5 +1,53 @@
 # Release Notes
 
+## v74.0.0
+Release date: 2026-04-30
+
+`v74.0.0` is the Receiz Key, identity artwork, and profile media release. In this offline verifier repository, the release work is publication of canonical `v74.0.0` artifacts and outward version-surface alignment only.
+
+Canonical full release note: [docs/releases/v74.0.0.md](docs/releases/v74.0.0.md)
+Product-truth freeze: [docs/releases/v74.0.0-product-truth.md](docs/releases/v74.0.0-product-truth.md)
+Release checklist: [docs/releases/v74.0.0-checklist.md](docs/releases/v74.0.0-checklist.md)
+Release process: [docs/releases/v74.0.0-process.md](docs/releases/v74.0.0-process.md)
+Prior v73 archive: [docs/releases/v73.0.0.md](docs/releases/v73.0.0.md)
+
+## Highlights
+- Receiz Key restore is locked as a sovereign key-file recovery path proven by fresh key signatures and active key registration; PBI may attest new key export but is not required for already-held keys.
+- Account now owns Receiz Key controls for private Identity Record PNG export, optional file-password protection, Identity Record PNG or legacy key JSON import, active/revoked key listing, refresh, and two-step revocation.
+- Offline Receiz Key projection preserves verified portable state and admitted local identity proof even when the server misses later.
+- Profile identity artwork derives deterministically from account creation Kai truth, with KaiSigil glyph geometry and size math kept canonical.
+- PBI-signed identity seal and identity record artifacts append verified authorship state without replacing the base profile shell.
+- Long-form profile originals preserve full text, title, hash, word count, and a compact Read affordance; attached Receiz URLs preserve exact href values.
+- Profile video originals may use playback derivatives and range-aware proxying while original proof downloads stay canonical.
+- Sold share positions remain local truth across market snapshots and route hydration, and portable state import preserves profile media/state fields with visible integrity failures.
+- Release-governed version surfaces now move together to `v74.0.0` across package metadata, public verifier artifacts, shipped release badges, README pointers, and current-release documentation.
+
+## Verifier impact
+- Current shipped verifier, studio, and settlement entrypoints are marked `v74.0.0`.
+- Repository release/docs surfaces now align to `v74.0.0`.
+- Root package metadata now resolves cleanly at `v74.0.0`.
+- No verifier proof-format or producer payload migration is implied by this release update.
+- Verifier trust semantics remain unchanged relative to `v60.0.0`.
+
+## Operational notes
+- The broader release brief records tag `v73.0.0` at commit `fb2d82142` as the baseline and 44 commits plus release-candidate working-tree updates in scope.
+- Published release surfaces now include the canonical `v74.0.0` release note, product-truth freeze, checklist, process, and updated docs indexes.
+- The `v70.0.0` public alpha law, `v70.0.0` invariant register, `v73.0.0` ownership/vault continuity baseline, and `v64.0.0` value-loop invariants remain in force.
+- In this offline verifier repository, the release work is documentation, visible version-surface alignment, and package-metadata normalization only.
+
+## Migration checklist
+- No new database migrations are introduced by this documentation cut.
+- Confirm Receiz Key restore, registration, export/import, active/revoked key listing, refresh, and two-step revocation gates.
+- Confirm offline Receiz Key projection keeps admitted local identity proof when later server fetches miss.
+- Confirm deterministic profile identity artwork, KaiSigil geometry, PBI-signed identity artifacts, and stable profile creation timestamps.
+- Confirm long-form profile originals, attached-link preservation, and profile video derivative playback preserve canonical original proof.
+- Confirm sold-position continuity and portable profile state import keep local truth and visible integrity failures.
+- Update outward release/docs references to `v74.0.0`.
+- Deploy updated `site/` artifacts.
+
+## Security posture
+Security posture remains fail-closed: verification still requires byte-level integrity, trusted signature evidence, anchor context, and real Groth16 proof validation.
+
 ## v73.0.0
 Release date: 2026-04-29
 

apps/offline-record-seal.html

@@ -701,7 +701,7 @@ <h2>Verify File</h2>
 
     <p class="footer">
       <span>Receiz Offline Studio · record, seal, and verify from artifact bytes.</span>
-      <span class="footer-version">v73.0.0</span>
+      <span class="footer-version">v74.0.0</span>
     </p>
 
     <section class="offline-tools" aria-label="Offline HTML downloads">

apps/offline-settlement.html

@@ -528,7 +528,7 @@ <h2>2. Export Claim Ledger Bundle</h2>
       <p class="status-note" id="statusNote">Add offline settlement note artifacts to assemble an offline-settlement claim bundle.</p>
     </section>
 
-    <p class="release-meta">Receiz Offline Settlement · v73.0.0</p>
+    <p class="release-meta">Receiz Offline Settlement · v74.0.0</p>
   </main>
 
   <script>

apps/offline-verifier.html

@@ -618,7 +618,7 @@ <h2 id="result-title">2) Verification result</h2>
     </section>
 
     <p class="foot" style="text-align:center;">
-      <a href="https://github.com/kojibai/receiz_offline_verifier" target="_blank" rel="noopener noreferrer">v73.0.0</a>
+      <a href="https://github.com/kojibai/receiz_offline_verifier" target="_blank" rel="noopener noreferrer">v74.0.0</a>
     </p>
   </main>
 

docs/FORMAT.md

@@ -1,6 +1,6 @@
 # Artifact format (verifier-visible)
 
-This document defines the verifier-visible data contract for `v73.0.0`.
+This document defines the verifier-visible data contract for `v74.0.0`.
 
 ## Supported artifact carriers
 - PNG with text chunks.

docs/README.md

@@ -1,18 +1,22 @@
 # Receiz Docs
 
-This directory is the public documentation set for Receiz `v73.0.0`.
+This directory is the public documentation set for Receiz `v74.0.0`.
 
 ## Start Here
 
-- [releases/v73.0.0.md](releases/v73.0.0.md): canonical ownership, vault, and continuity release note for `v73.0.0`.
+- [releases/v74.0.0.md](releases/v74.0.0.md): canonical Receiz Key, identity artwork, and profile media release note for `v74.0.0`.
+- [releases/v74.0.0-product-truth.md](releases/v74.0.0-product-truth.md): release-scoped product-truth freeze for `v74.0.0`.
+- [releases/v74.0.0-checklist.md](releases/v74.0.0-checklist.md): release-prep checklist and additional gates for `v74.0.0`.
+- [releases/v74.0.0-process.md](releases/v74.0.0-process.md): release-prep process for `v74.0.0`.
+- [releases/v73.0.0.md](releases/v73.0.0.md): ownership, vault, and continuity release archive for `v73.0.0`.
 - [releases/v73.0.0-product-truth.md](releases/v73.0.0-product-truth.md): release-scoped product-truth freeze for `v73.0.0`.
 - [releases/v73.0.0-checklist.md](releases/v73.0.0-checklist.md): release-prep checklist and additional gates for `v73.0.0`.
 - [releases/v73.0.0-process.md](releases/v73.0.0-process.md): release-prep process for `v73.0.0`.
 - [releases/v72.0.0.md](releases/v72.0.0.md): stable continuity release archive for `v72.0.0`.
 - [releases/v72.0.0-product-truth.md](releases/v72.0.0-product-truth.md): release-scoped product-truth freeze for `v72.0.0`.
 - [releases/v72.0.0-checklist.md](releases/v72.0.0-checklist.md): release-prep checklist and additional gates for `v72.0.0`.
 - [releases/v72.0.0-process.md](releases/v72.0.0-process.md): release-prep process for `v72.0.0`.
-- [releases/v70.0.0-invariant-register.md](releases/v70.0.0-invariant-register.md): invariant register for the public alpha release boundary carried forward by `v73.0.0`.
+- [releases/v70.0.0-invariant-register.md](releases/v70.0.0-invariant-register.md): invariant register for the public alpha release boundary carried forward by `v74.0.0`.
 - [releases/v70.0.0.md](releases/v70.0.0.md): canonical public alpha release note for `v70.0.0`.
 - [literal-product-law.md](literal-product-law.md): literal product law for local identity, file proof, append-only truth, canonical profiles, funded causality, and network propagation.
 - [experience-first-engineering.md](experience-first-engineering.md): experience-first rules for local proof, deterministic state, and hidden runtime work.

docs/deterministic-surfaces.md

@@ -1,6 +1,6 @@
 # Deterministic Surface Contract
 
-Status: Canonical reference from `v70.0.0`; carried forward for `v73.0.0`
+Status: Canonical reference from `v70.0.0`; carried forward for `v74.0.0`
 
 Receiz trust surfaces must never use fake loaders.
 
@@ -52,7 +52,7 @@ Snapshots are allowed because they are deterministic route state, not fake UI.
 - Snapshots must never become the only source of truth.
 - Cold loads, pasted links, reloads, and new tabs must still resolve correctly from the route itself.
 
-For `v70.0.0` and carried forward through `v73.0.0`, deterministic public snapshots and private account snapshots may also be explicit offline truth carriers when the response opts into persistence with `x-receiz-offline-persist`.
+For `v70.0.0` and carried forward through `v74.0.0`, deterministic public snapshots and private account snapshots may also be explicit offline truth carriers when the response opts into persistence with `x-receiz-offline-persist`.
 
 - Offline persisted snapshots must represent verified or deterministic route truth.
 - Offline persisted snapshots must not be treated as generic cache guesses.