Skip to content

v70.0.0-process.md

Latest commit

 

History

History
113 lines (88 loc) · 5.37 KB

v70.0.0-process.md

File metadata and controls

113 lines (88 loc) · 5.37 KB

Receiz v70.0.0 Release Process

Release date: April 24, 2026 Status: Release prep

Purpose

This process document defines how the v70.0.0 public alpha release is prepared, validated, and tagged. It is scoped to the public release documentation cut and the repository version-surface alignment that publishes that truth.

Inputs

  • docs/literal-product-law.md
  • docs/experience-first-engineering.md
  • docs/deterministic-surfaces.md
  • docs/verified-history-first-principles.md
  • docs/offline-verified-register.md
  • docs/pbi-recovery-receiz-id-binding.md
  • docs/value-loop-invariants.md
  • docs/releases/v70.0.0-invariant-register.md
  • docs/releases/v70.0.0-product-truth.md
  • docs/releases/v70.0.0-growth-from-v60.md
  • docs/releases/v70.0.0-docs-manifest.md
  • docs/releases/v70.0.0-checklist.md
  • docs/releases/v70.0.0.md

Release Framing

Title: Receiz v70.0.0 - Public Alpha Release

v70.0.0 is the first public alpha release cut of Receiz as an end-to-end product system. It packages the work from v60.0.0 through the final v69.9.x stabilization line into one governed public release.

Preparation Steps

  1. Freeze literal product law.

    • Keep local identity, file-backed proof, append-only verified history, canonical profile truth, funded value causality, and network-as-propagation explicit.
    • Do not soften the release into generic platform language.

  2. Publish canonical release artifacts.

    • Add docs/literal-product-law.md.
    • Add docs/pbi-recovery-receiz-id-binding.md.
    • Add docs/releases/v70.0.0.md.
    • Add docs/releases/v70.0.0-product-truth.md.
    • Add docs/releases/v70.0.0-checklist.md.
    • Add docs/releases/v70.0.0-process.md.
    • Add docs/releases/v70.0.0-growth-from-v60.md.
    • Add docs/releases/v70.0.0-invariant-register.md.
    • Add docs/releases/v70.0.0-docs-manifest.md.
    • Confirm the extra public docs surface is accounted for, including verifier format, architecture, compatibility, hardening, threat model, deployment, copy guidance, conformance, schemas, governance, PresenceBound, and the public Receiz standard.

  3. Align repository release surfaces.

    • Update package.json to 70.0.0.
    • Update root README current-release references.
    • Update RELEASE_NOTES.md and CHANGELOG.md.
    • Update docs/README.md, docs/governance/README.md, and docs/FORMAT.md.
    • Update shipped version markers in site/index.html, apps/offline-verifier.html, apps/offline-record-seal.html, and apps/offline-settlement.html.

  4. Validate identity and profile gates.

    • Receiz ID is the primary everyday rail.
    • /signin is pass-through only.
    • Cold devices can create a local Receiz ID and continue to the managed profile.
    • PBI/keyfile recovery binds back to local Receiz ID truth.
    • /<username> and /<username>?manage=1 share the same profile truth.

  5. Validate value-loop and local-truth gates.

    • Settlement and Reserve preserve funded causality.
    • Notes remain Reserve-only.
    • Market sells preserve funded/unfunded splits.
    • Local Receiz ID, PBI/keyfile proof, snapshots, wallet graphs, market positions, twin state, and proof bundles remain real local truth.
    • Weaker network/session payloads do not downgrade stronger device-held proof.

  6. Validate runtime, offline, and twin gates.

    • Stale runtime and service-worker states recover through local proof or server resync.
    • Hard runtime recovery returns to the original route.
    • Live twin identity never falls back to a profile picture.
    • Mind trail ZIP downloads verify as proof bundles.
    • Standalone PWA corrections stay scoped to standalone PWA display.

  7. Validate release-surface lockstep.

    • Confirm package metadata resolves to 70.0.0.
    • Confirm shipped HTML version markers display v70.0.0.
    • Confirm current release docs and indexes point to v70.0.0 artifacts.
    • Confirm no current-release surface still advertises v66.0.0; historical v66.0.0 release archive docs may retain their original version truth.

Focused Verification Matrix

Broader platform release validation should include the gates named in docs/releases/v70.0.0-checklist.md, including:

  • TypeScript compile: pnpm exec tsc --noEmit --pretty false
  • Deterministic surfaces: pnpm test:deterministic-surfaces
  • Release freeze: pnpm test:release-freeze
  • Release lock: pnpm release:lock
  • Receiz ID login and cold-device creation suites
  • PBI/keyfile recovery binding suites
  • canonical profile and owner-mode profile-law suites
  • Settlement/Reserve causality suites
  • stale runtime and service-worker recovery suites
  • live twin identity and mind trail proof-bundle suites

This offline verifier repository does not contain those broader platform test suites. Its local release gates are version-surface, documentation, package metadata, and shipped static-entrypoint checks.

Tag Criteria

Do not tag v70.0.0 until:

  • all required release artifacts exist
  • version surfaces are aligned to v70.0.0
  • the release gates in docs/releases/v70.0.0-checklist.md pass from the exact release candidate
  • governed surfaces all show v70.0.0
  • broader platform identity, profile, value-loop, runtime, offline, and twin gates have passed against the release candidate

Release Rule

Do not ship v70.0.0 unless the release gates in docs/releases/v70.0.0-checklist.md pass from the exact release candidate and the governed surfaces all show v70.0.0.