Skip to content

Releases: Riverbraid/Riverbraid-Core

Riverbraid Gold Cluster v1.2.0

25 Feb 01:14
71d37c4

Choose a tag to compare

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.jsmanifest.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.

Riverbraid Standard v1.0.0

02 Jan 02:42

Choose a tag to compare

Riverbraid Standard v1.0.0

Overview

Riverbraid Standard v1.0.0 is a deterministic, auditable capacity gate and reflection ledger intended as a reference implementation for AI integrity boundaries.

This release defines a floor, not a product.

What This Release Is

  • A frozen mathematical core with explicit governance thresholds
  • A strict separation of concerns across three layers:
    • Frozen Core (deterministic math only)
    • Anchor Sentinel (time + identity normalization)
    • Reflection Ledger (cryptographic persistence)
  • A fail-closed HMAC-SHA256 chained ledger
  • A mandatory secret policy (RIVERBRAID_SECRET)
  • A complete audit path from signal → decision → record → verification

What This Release Is Not

  • Not a framework
  • Not an agent
  • Not adaptive or self-modifying
  • Not a product or service
  • Not a claim of authority over AI systems

Governance Locks

  • Composite formula:
    0.4s + 0.3p + 0.2v + 0.1(1-c)
  • Thresholds:
    • > 0.45 → SOFTEN
    • > 0.75 → REST
    • c < 0.25 → REST (hard override)
  • Determinism required for all core outputs
  • Recursive canonical serialization for all cryptographic operations

Integrity Guarantees

  • No IO, time, randomness, or environment access in the core
  • Full ledger chain audit on startup
  • Fail-closed on any corruption
  • SHA256SUMS provided for release artifacts

Intended Use

This repository exists to be pointed at.

It demonstrates the minimum structure required to:

  • Preserve determinism
  • Prevent silent drift
  • Make integrity inspectable

Release Artifacts

  • Compiled dist/ output
  • SHA256SUMS for verification
  • Git tag: v1.0.0

This release is complete and sealed.