Skip to content

v66.0.0-process.md

Latest commit

 

History

History
118 lines (87 loc) · 5.49 KB

v66.0.0-process.md

File metadata and controls

118 lines (87 loc) · 5.49 KB

Receiz v66.0.0 Release Process

Release date: April 21, 2026 Status: Release prep

Purpose

This process document defines how the v66.0.0 release is prepared, validated, and tagged. It is scoped to the local proof continuity release and the repository version-surface alignment that publishes that truth.

Inputs

  • docs/experience-first-engineering.md
  • docs/deterministic-surfaces.md
  • docs/verified-history-first-principles.md
  • docs/offline-verified-register.md
  • docs/value-loop-invariants.md
  • docs/releases/v66.0.0-product-truth.md
  • docs/releases/v66.0.0-checklist.md
  • docs/releases/v66.0.0.md
  • local proof, account continuity, twin register, wallet, market, service-worker, and release-lock evidence from the broader platform workspace

Release Framing

Title: Receiz v66.0.0 - Local Proof Continuity

v66.0.0 is the release that moves the post-v64.0.0 system from value-loop completeness into fuller obedience to Receiz's actual authority model:

Identity is local. Proof is local. State is deterministic. History is append-only. Memory is compact. Sync is propagation.

Known local truth should move immediately. Everything else must justify its existence.

Preparation Steps

  1. Freeze authority language.

    • Use local proof as the default authority when the node already holds stronger verified truth.
    • Use network/session/server language as enrichment, publication, propagation, discovery, or append support.
    • Keep deterministic state, append-only history, compact memory, and sync-as-propagation explicit.

  2. Publish canonical release artifacts.

    • Add or update docs/experience-first-engineering.md.
    • Add or update docs/verified-history-first-principles.md.
    • Add or update docs/offline-verified-register.md.
    • Add docs/releases/v66.0.0.md.
    • Add docs/releases/v66.0.0-product-truth.md.
    • Add docs/releases/v66.0.0-checklist.md.
    • Add docs/releases/v66.0.0-process.md.
    • Keep docs/deterministic-surfaces.md and docs/value-loop-invariants.md in the product-truth reference set.

  3. Align repository release surfaces.

    • Update package.json to 66.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 local-proof gates.

    • Verified-register-backed proof outranks weaker offline evidence.
    • Receipt and proof surfaces expose proof authority without weakening stronger local proof.
    • Wallet transaction receipts verify deterministic ledger proof bundles.
    • Local identity roots survive unavailable, anonymous, or weaker network session payloads.
    • Local twin register projection wins the visible reply when present.
    • Twin mind PNG import uses portable public-key verification.

  5. Validate known-state and snapshot gates.

    • World and private account snapshots opt into explicit offline persistence where route truth must survive offline.
    • Explore snapshots reconcile into visible state without replacing useful already-visible content.
    • Wallet projects the durable wallet graph during first render.
    • Market and tracked positions preserve locally known positions until a stronger state is proven.
    • Service-worker persistence treats verified snapshots as truth carriers, not generic cache guesses.

  6. Validate release-surface lockstep.

    • Search for stale current-release v64.0.0 references in public release surfaces.
    • Confirm new v66 docs are linked from public indexes.
    • Confirm shipped HTML version markers display v66.0.0.
    • Confirm package metadata resolves to 66.0.0.

Focused Verification Matrix

Broader platform release validation should include:

  • 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
  • Local proof, identity, twin, service-worker, wallet, market, and tracked-position contract suites that cover the product gates in docs/releases/v66.0.0-checklist.md

Documentation Cut

The changed release documents for this documentation cut are:

  • docs/experience-first-engineering.md
  • docs/verified-history-first-principles.md
  • docs/offline-verified-register.md
  • docs/releases/v66.0.0-product-truth.md
  • docs/releases/v66.0.0-checklist.md
  • docs/releases/v66.0.0-process.md
  • docs/releases/v66.0.0.md

Repository release-surface files are also updated so the public docs and shipped static entrypoints agree on v66.0.0.

Tag Criteria

Do not tag v66.0.0 until:

  • all required release artifacts exist
  • version surfaces are aligned to v66.0.0
  • local-proof and known-state contract evidence has passed in the broader platform workspace
  • twin mind public-key signing environment is present for production import/export
  • no flow asks the network to reconfirm a proof the node already holds before moving known local truth
  • no settled screen visibly reloads from background hydration

Release Principle

Known local truth should move immediately.

Everything else must justify its existence.

If a future change asks the network to reconfirm a proof the node already holds, replaces a stronger local block with a weaker remote payload, or makes a settled screen visibly reload from background hydration, it is a regression against v66.0.0.