Skip to content

v64.0.0-process.md

Latest commit

 

History

History
107 lines (76 loc) · 4.34 KB

v64.0.0-process.md

File metadata and controls

107 lines (76 loc) · 4.34 KB

Receiz v64.0.0 Release Process

Release date: April 21, 2026 Status: Release prep

Purpose

This process document defines how the v64.0.0 release is prepared, validated, and tagged. It is scoped to the complete value-loop release and the repository version-surface alignment that publishes that truth.

Inputs

  • docs/value-loop-invariants.md
  • docs/releases/v64.0.0-product-truth.md
  • docs/releases/v64.0.0-checklist.md
  • docs/releases/v64.0.0.md
  • wallet, market, certificate, and value-state contract test evidence from the broader platform workspace

Release Framing

Title: Receiz v64.0.0 - The Complete Value Loop

v64.0.0 is the release where Receiz becomes one complete value system instead of separate advanced primitives.

The product now has a closed causal 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.

Preparation Steps

  1. Freeze product language.

    • Use Settlement for proof-native liquid value.
    • Use Reserve or funded Reserve for funded external-conversion value.
    • Use wire transfer for the Reserve-funded wire path.
    • Use buyer-funded certificate where certificate funding is the causal source.
    • Keep provider names out of user-facing liquidity language.

  2. Publish canonical release artifacts.

    • Add or update docs/value-loop-invariants.md.
    • Add docs/releases/v64.0.0.md.
    • Add docs/releases/v64.0.0-product-truth.md.
    • Add docs/releases/v64.0.0-checklist.md.
    • Add docs/releases/v64.0.0-process.md.

  3. Align repository release surfaces.

    • Update package.json to 64.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 the value-loop gates.

    • Settlement remains primary and proof-native.
    • Reserve funds notes, sends, positions, and wire transfers.
    • Sends and buys deploy Reserve first, then Settlement covers the remainder.
    • Market sells split funded Reserve and unfunded Settlement.
    • Certificate issue locks value and funded certificate sale credits the seller.
    • Notes remain Reserve-only.
    • Wire transfer remains Reserve-funded.
    • Account-lane charts use account truth and account quote math.

  5. Validate release-surface lockstep.

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

Focused Verification Matrix

Broader platform release validation should include:

  • TypeScript compile: pnpm exec tsc --noEmit --pretty false
  • Value-loop guard: pnpm test:value-loop-guard
  • Golden-path release flow: pnpm test:release-golden-path
  • Release freeze: pnpm test:release-freeze
  • Release lock: pnpm release:lock

The behavioral contract coverage must include wallet, market, certificate, note, wire-transfer, and value-state metadata preservation gates listed in docs/releases/v64.0.0-checklist.md.

Documentation Cut

The changed files for this documentation cut are:

  • docs/value-loop-invariants.md
  • docs/releases/v64.0.0-product-truth.md
  • docs/releases/v64.0.0-checklist.md
  • docs/releases/v64.0.0-process.md
  • docs/releases/v64.0.0.md

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

Tag Criteria

Do not tag v64.0.0 until:

  • all required release artifacts exist
  • version surfaces are aligned to v64.0.0
  • value-loop contract evidence has passed in the broader platform workspace
  • no user-facing language replaces Settlement or Reserve with provider implementation detail
  • no new flow moves value without preserving Reserve/Settlement metadata

Release Principle

Future wire improvements must preserve funded causality.

Future value surfaces must keep Settlement primary and proof-native.

If a future change moves value without preserving Reserve/Settlement metadata, it is not finished.