v1.5.0-genesis

This reflect the transition from "vibration" to "stationarity" and the establishment of the Absolute Path Containment invariant.Riverbraid Gold Cluster v1.5.0-GenesisRelease Date: 2026-03-30Release Status: SEALED | STATIONARY | BOUNDEDOverviewThis release establishes the Stationary State Baseline for the entire Riverbraid Gold cluster. It resolves structural instability caused by boundary leakage and inconsistent file hygiene (LF normalization) that prevented consistent cryptographic verification.Key Architectural InvariantsAbsolute Path Containment: The run-vectors.cjs verifier is now physically "jailed" to its local repository root using path.resolve and a strict startsWith(ROOT) gate. This prevents "bleeding" where one repository verifier could erroneously hash metadata from a sibling repository.Stationary Measurement: Measurement artifacts (constitution.snapshot.json) are explicitly excluded from the hash surface. This decouples the act of observation from the state itself, ensuring that Snapshot(Hash) === Verify(Hash).Canonical Hygiene: A global 0x0a (LF) enforcement protocol was applied to all governed .json, .cjs, and .md files. The verifier now treats any non-compliant line ending as a terminal failure.Environmental Isolation: Active exclusion of .codespaces, .git, and node_modules ensures the Merkle Root is derived solely from the constitutional substrate, immune to environmental noise.Mechanical Audit ManifestThe following repositories are officially anchored to the v1.5.0-genesis tag:Repository SubstrateVerification MetricStateCore & GoldsAbsolute Path ContainmentVerifiedTemporal & ActionTemporal Drift ShieldedVerifiedCrypto & JudicialLogical IsolationVerifiedMemory & IntegrationSurface AlignmentVerifiedVision, Audio, CognitionHigh-Entropy HygieneVerifiedRefusal & HarnessBoundary SealedVerifiedLite & .githubSymmetry AlignmentVerifiedFinal Governance NoteThe Merkle Root (de2062) and GPG Fingerprint (D9475D6B717D0E6C8EC84F6D8F86D9F4F2B083A4) are now permanently bound to this stationary floor. Any future mutation must originate from this baseline.

Riverbraid Gold Cluster v1.2.0

Riverbraid Gold Cluster v1.2.0

Release Date: 2026-02-28
Status: STATIONARY
Braid: CLOSED-LOOP
Merkle Root: de2062
Fingerprint: D9475D6B717D0E6C8EC84F6D8F86D9F4F2B083A4

---

What Changed

Language Unification — Full Python Standard

The Gold Cluster is now unified in a single language: Python ≥ 3.10.

Prior to this release, the cluster operated with a split stack — Riverbraid-Core in Python and all Gold petals in JavaScript/Node.js. This release eliminates that split. Every module in the cluster now speaks the same language as the governance-locked root it wraps.

This is not a functional change. The logic, invariants, signals, and fail-closed behavior of every petal are identical to v1.1.0. The change is structural: one language, one runtime, no translation layer between the Core and the cluster.

Replaced in every Gold petal:

• All index.js files → named Python modules (anchor.py, judicial.py, refusal.py, etc.)
• All verify.mjs files → verify.py with identical fail-closed behavior
• All package.json / package-lock.json files → removed; Python standard library covers all requirements
• TypeScript types/ directories → removed; not applicable in Python

Added in every Gold petal:

• __init__.py — clean public API surface per petal
• Named module files with full docstrings and explicit function signatures

Unchanged in every Gold petal:

• All protocol.steps files
• All policy.rules, refusal.codes, memory.state files
• All .json contract and configuration files
• All .md documentation files
• All .sh shell bootstrap and sync scripts
• All .github/workflows/ files (update runner commands from node/npm to python)
• All LICENSE, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT files

---

Riverbraid-Golds Orchestrator

The cluster orchestrator (Riverbraid-Golds) has been rewritten in Python to match.

• manifest.js → manifest.py — full Absolute V2 Pipeline implementation
• run-vectors.cjs → merged into manifest.py
• main (build entry) → build.py
• braid_sync.py added as Python equivalent of braid-sync.sh
• Shell scripts (bootstrap_golds_v1_5.sh, braid-sync.sh) remain — environment-level tooling is correctly shell

New pipeline usage:

# Run the full Absolute V2 Pipeline
python build.py

# Verify local stationary state
python braid_sync.py

# Verify a single petal
cd Riverbraid-Crypto-Gold && python verify.py

---

Documentation — Unified README Standard

All nine repositories now have uniform, fully rewritten READMEs following a consistent structure:

• What It Is — single clear statement of purpose
• What It Is Not — explicit boundary declarations
• How It Works — mechanics documented plainly
• Usage — copy-paste ready examples
• Files table — every file accounted for, data files noted as data not code
• Design Properties — the invariants that apply to that specific petal
• Gold Cluster navigation table — every repo links to every other with signal and purpose

The .github organization profile README has also been rewritten to serve as a clear front door to the project.

---

Petal Status

Petal	Signal	Status
Riverbraid-Core	Root	FROZEN — unchanged, governance-locked
Riverbraid-Golds	—	UPDATED — Python orchestrator
Riverbraid-Crypto-Gold	MECHANICAL_HONESTY	UPDATED — Python
Riverbraid-Judicial-Gold	LEAST_ENTROPY	UPDATED — Python
Riverbraid-Refusal-Gold	BOUNDARY_LOGIC	UPDATED — Python
Riverbraid-Memory-Gold	MEANING_CENTRIC	UPDATED — Python
Riverbraid-Integration-Gold	SEMANTIC_BRIDGE	UPDATED — Python
Riverbraid-Harness-Gold	STATIONARY_STATE_ACTIVE	UPDATED — Python

---

Breaking Changes

None to external behavior or invariants.

The language change is structural. Any existing wrapper that called Gold petal logic via Node.js will need to update its calls to use Python. The underlying logic, thresholds, signals, and protocol definitions are identical.

Riverbraid-Core is unchanged. Its API, formulas, and governance spec are frozen per spec/governance-1.0.0.json.

---

Upgrade from v1.1.0

1. Pull the latest changes for each petal
2. Remove Node.js dependencies (node_modules/, package.json, package-lock.json)
3. Confirm Python ≥ 3.10 is available in your environment
4. Run python verify.py in each petal directory to seal anchors
5. Run python build.py from Riverbraid-Golds to confirm cluster is STATIONARY

---

Invariant Contract

No invariants were modified in this release. The Absolute V2 (Refined) Standard is intact. All petal signals, protocol definitions, and governance rules are unchanged from v1.1.0.

The cluster remains stationary.