Release date: April 30, 2026 Status: Release prep
- Current documented release anchor in this repository before this cut:
v73.0.0 - Broader product baseline referenced by this release: tag
v73.0.0at commitfb2d82142, as supplied by the broader release brief. - Broader release scope: 44 commits plus release-candidate working-tree updates, 90 changed files, 7,661 insertions, 679 deletions, as supplied by the broader release brief.
- This offline verifier checkout records the broader product diff as release-brief evidence while updating documentation, package metadata, and static version markers locally.
- This checklist governs the
v74.0.0Receiz Key, identity artwork, and profile media documentation cut and outward version-surface alignment.
docs/literal-product-law.mddocs/experience-first-engineering.mddocs/deterministic-surfaces.mddocs/verified-history-first-principles.mddocs/offline-verified-register.mddocs/pbi-recovery-receiz-id-binding.mddocs/value-loop-invariants.mddocs/releases/v70.0.0-invariant-register.mddocs/releases/v73.0.0.mddocs/releases/v73.0.0-product-truth.mddocs/releases/v73.0.0-checklist.mddocs/releases/v73.0.0-process.mddocs/releases/v74.0.0.mddocs/releases/v74.0.0-product-truth.mddocs/releases/v74.0.0-checklist.mddocs/releases/v74.0.0-process.md- current-release pointers updated in
README.md,docs/README.md,RELEASE_NOTES.md,CHANGELOG.md,docs/governance/README.md, anddocs/FORMAT.md - root package metadata updated in
package.json - shipped version markers updated in
site/index.html,apps/offline-verifier.html,apps/offline-record-seal.html, andapps/offline-settlement.html
- no new database migration is required by this offline verifier repository documentation cut
- existing production schema requirements from prior identity, business ownership, certificate, receipt, vault, profile, value-loop, world, wallet, market, and recovery releases still apply in the broader platform workspace
- Receiz Key restore is a sovereign key-file recovery path.
- Fresh key signatures and active key registration prove restore.
- PBI may attest new key export but is not required to restore from an already-held key.
- Account exposes Receiz Key control where account protection lives.
- Private Identity Record PNG export embeds the Receiz Key payload.
- Optional file-password protection is available for Identity Record export.
- Identity Record PNG and legacy key JSON import paths remain supported.
- Active and revoked keys can be listed, refreshed, and revoked.
- Key revocation requires a two-step owner action.
- First-time offline Receiz Key projection requires verified portable state.
- Later offline login may reuse an admitted local identity block.
- A server miss does not erase admitted local identity proof.
- Profile identity artwork derives deterministically from account creation Kai truth.
- Runtime randomness, storage upload timing, and profile remount timing do not affect identity artwork.
- Receiz card chrome may frame the seal without styling KaiSigil glyph geometry or size math.
- PBI-signed identity seal and identity record artifacts append verified authorship state without replacing the base profile shell or inventing a separate showcase coordinate.
- PBI-signed identity surfaces seed premium material from both the receipt hash and PBI signing Kai moment.
- Signed witness emphasis uses trust-blue chrome rather than gold.
- Profile creation timestamps are stable local truth and cannot move forward across route hydration, workspace hydration, or remounts.
- Long-form profile originals preserve full text, title, hash, word count, and a compact Read affordance.
- URL, read, and value pills are not squeezed into one row.
- Attached Receiz URLs preserve the exact href while front-card labels show only the domain.
- Composer and anchor transport do not silently cap valid long links at 280 characters.
- Profile video originals may use storage-backed playback derivatives and range-aware proxying for fast playback.
- Original proof downloads remain canonical.
- Sold share positions remain local truth across market snapshots and route hydration.
- Closed positions cannot resurrect as live ownership.
- Portable state import preserves profile media/state fields.
- Valid partial ledger entries are admitted only under explicit partial-import handling.
- Integrity failures remain visible.
- Package metadata, service-worker defaults, public version badges, verifier surfaces, README release pointer, and release docs move together to
v74.0.0.
Release-prep commands expected in the broader platform workspace:
pnpm exec tsc --noEmit --pretty falsepnpm test:deterministic-surfacespnpm test:release-freezepnpm release:lock
Focused suites expected in the broader platform workspace:
- Receiz Key restore, registration, active-key listing, refresh, and revocation tests
- Identity Record PNG export/import and legacy key JSON import tests
- offline Receiz Key projection and admitted-local-identity tests
- deterministic profile identity artwork and KaiSigil geometry tests
- PBI-signed identity seal and identity record publishing tests
- profile creation timestamp stability tests
- long-form profile original payload and Read affordance tests
- attached URL preservation and long-link transport tests
- profile video derivative playback and canonical original-download tests
- sold-position continuity and closed-position resurrection tests
- portable state import, partial ledger handling, and integrity-failure visibility tests
- business/custom-domain hardening suites touched by the release candidate
- root package metadata resolves to
v74.0.0 - current shipped verifier, studio, and settlement entrypoints display
v74.0.0 - current release docs and indexes point to the
v74.0.0release artifacts - product-truth reference docs are linked from the public docs map
- broader platform validation for
v74.0.0is captured in the canonical release note, product-truth document, process document, and checklist - verifier trust semantics remain unchanged relative to
v60.0.0 - no verifier proof-format or producer payload migration is implied by these repository release/documentation updates alone
Do not ship v74.0.0 unless the release gates in this checklist pass from the exact release candidate and the governed surfaces all show v74.0.0.