Skip to content

R3: establish primitive-boundary topology #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Riverbraid wants to merge 1 commit into
base: main
Choose a base branch
from
Open

R3: establish primitive-boundary topology #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 14 additions & 32 deletions .github/workflows/verify.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,44 +1,26 @@
name: Riverbraid Verification Suite
name: Riverbraid Core Mechanical Boundary

on:
push:
branches:
- main
branches: [main]
pull_request:
branches:
- main
branches: [main]
workflow_dispatch:

permissions:
contents: read

jobs:
verify-core:
verify-mechanical-boundary:
runs-on: ubuntu-24.04
steps:
- name: Checkout Riverbraid-Core
uses: actions/checkout@v4
- name: Checkout exact Core subject
uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262

- name: Setup Node.js
uses: actions/setup-node@v4
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020
with:
node-version: '20.11.0'
- name: Clone Ring 0 sibling repositories
shell: bash
run: |
set -euo pipefail
cd ..
for repo in \
Riverbraid-Golds \
Riverbraid-Governance \
Riverbraid-Integrity-Floors \
Riverbraid-Types
do
echo "Cloning $repo"
git clone --depth 1 "https://github.com/Riverbraid/${repo}.git" "$repo"
done
echo "RING0_SIBLINGS_CLONED"
- name: Run compatibility audit
shell: bash
run: |
set -euo pipefail
node audit_final.js
node constellation-audit.mjs --ring 0
- name: Final status
run: echo "RIVERBRAID_CORE_RING0_CI_OK"

- name: Run scoped mechanical verifier
run: node mechanical-verify.mjs
33 changes: 14 additions & 19 deletions AUTHORITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,14 @@
# Riverbraid-Core Authority
Ring: 0
Role: Proposed Phase 15 trust anchor
Status: CLASSIFIED
## Claim Boundary
This repository participates in the proposed Phase 15 Ring 0 trust anchor layer.
This file does not claim full constellation verification.
This repository may only claim VERIFIED after its local verifier produces verify-output.json with status VERIFIED.
## Refused Claims
This repository does not claim:
- production readiness
- legal compliance
- universal safety
- absolute truth
- full constellation verification
- downstream ring verification
## Mechanical Honesty Rule
File presence is not verification.
Verification requires a real verifier output.
# Riverbraid-Core authority boundary

**Lifecycle:** ACTIVE_ARCHITECTURAL_SURFACE
**Role:** MECHANICAL_PROTOCOL
**Protocol authority:** MECHANICAL_GRAMMAR_ONLY
**Project authority:** NONE

Riverbraid-Core controls only Riverbraid's mechanical interoperability grammar: how records and attributed assertions are identified, serialized, referenced, preserved, structurally validated, and transported.

Its authority terminates before truth, trust, evidentiary weight, interpretation, legitimacy, meaning, moral priority, risk ranking, readiness, certification, adoption judgment, or the correct resolution of disagreement.

A Riverbraid project decision may select a Core version for the Riverbraid project. That does not make an external interpretation true or universally authoritative.

Historical Ring/constellation and trust-anchor material is preserved under `historical/phase15/` and is not current Core authority.
27 changes: 27 additions & 0 deletions PROTOCOL-BOUNDARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Riverbraid Core Protocol Boundary

## Controlling boundary

Core is the controlling specification for Riverbraid's mechanical interoperability grammar.

Its authority terminates before trust, truth, evidentiary weight, interpretation, legitimacy, meaning, moral priority, risk ranking, readiness, certification, or adoption judgment.

## Primitive-boundary rule

For every Core field, enum, predicate, status, registry-membership rule, validator rule, default, and lifecycle label, determine whether it records a demonstrable mechanical fact or imports an interpretation.

An interpretive item must be attributed to a declared profile/authority, made namespaced and extensible, moved outside Core, or removed.

## Relationship rule

Core may define an assertion envelope and stable references. It does not define universal meanings for relationship predicates.

A mapping between vocabularies is another attributed and scoped assertion with its own evidence and challenge path. It is never an automatic Riverbraid equivalence.

## Extension rule

Unknown namespaced predicates, types, and extension members must be preservable without network dereferencing, renaming, dropping, or coercion during structural processing.

## Build-control separation

Riverbraid's F0–F4 gates, authorization records, custody receipts, hash ledgers, and implementation stop conditions are project/build controls. They do not become protocol primitives merely because they are used to build Riverbraid.
58 changes: 9 additions & 49 deletions PUBLIC_EVIDENCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,57 +1,17 @@
# Riverbraid Public Evidence Manifest
# Riverbraid-Core public evidence boundary

This document records the current public evidence surface for Riverbraid.
It is intended for external review of the repository system's structural and workflow evidence. It does not claim third party certification, absolute security, absence of bugs, or universal correctness.
The current Core evidence surface is intentionally narrow.

## Verification Summary
`mechanical-verify.mjs` evaluates only the declared R3 mechanical boundary in `mechanical-profile.json`. A scoped PASS means that the named checks satisfied that named mechanical profile for the exact checked-out Core commit.

| Evidence Layer | Status | Result |
|---|---:|---:|
| Registry size | Verified | 30 repositories |
| Phase 20 stationarity | Pass | 30 stationary, 0 failed or incomplete |
| Phase 21 workflows | Pass | 30 remote passing, 0 failed |
| Third party certification | Not asserted | Pending external process |
It does not establish truth, trustworthiness, evidentiary weight, safety, compliance, readiness, maturity, certification, adoption, external audit, or downstream AI behavior.

## Evidence Anchors
## Historical evidence

| Artifact | Status |
|---|---|
| phase20-cross-repo-anchor-registry.json | present |
| phase20-cluster-verification.json | present |
| phase21-final-workflow-audit.json | present |
| phase22-evidence-inventory.json | anchored |
Earlier 30-repository, Ring, constellation, stationarity, and workflow evidence remains preserved as historical Riverbraid evidence. It is not rewritten as proof of the lean R3 topology.

## Core Anchors
Exact Phase 15 machine/prose surfaces detached by R3 are preserved under `historical/phase15/`.

- Phase 21 workflow evidence commit: e207787873fb1a7351d1320f56eec6605a9c58ec
- Phase 22 evidence inventory commit: fadcb1c14affcaeafe12ecc3a50eded3987c9a9d
- Core repository: https://github.com/Riverbraid/Riverbraid-Core
## Public reproduction

## Verified Scope

Riverbraid currently verifies:

1. The registry contains exactly 30 repositories.
2. Phase 20 recorded the registry as stationary.
3. Phase 21 recorded all 30 repositories as having completed successful GitHub Actions runs on their current remote heads.
4. The evidence inventory explicitly does not assert third party certification.

## Not Claimed

Riverbraid does not claim:

1. Third party certification.
2. Absolute security.
3. Absence of defects.
4. Legal, compliance, SOC 2, ISO, or formal audit approval.
5. That workflow success proves all future behavior.

## External Reproduction

The intended reproduction path is:

git clone https://github.com/Riverbraid/Riverbraid-Core.git
cd Riverbraid-Core
node cluster-verify.mjs

The verifier requires sibling local checkouts of the 30 registry repositories and GitHub CLI access through gh.
The current cross-repository mechanical reproduction owner is `Riverbraid-Evaluation-Kit`. It records exact evaluator, profile, subject commit, environment, check outcomes, evidence references, and nonclaims.
127 changes: 26 additions & 101 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,116 +1,41 @@
# Riverbraid-Core

> Status: CORE_AUDIT_SURFACE
> Ring Role: Core / normative protocol authority
> Claim Boundary: deterministic integrity floor, byte audit, and ring governance only
> Lifecycle: ACTIVE_ARCHITECTURAL_SURFACE
> Role: MECHANICAL_PROTOCOL
> Protocol authority: MECHANICAL_GRAMMAR_ONLY
> Project authority: NONE
> Current reproduction profile role: MECHANICAL_SUBJECT

Riverbraid-Core is a deterministic integrity floor for the Riverbraid architecture.
Riverbraid-Core is the controlling specification for Riverbraid's **mechanical interoperability grammar**.

It defines the minimum governance substrate used to make structure, authority, and drift visible before trust is granted. It does not claim to implement the full experimental Riverbraid research surface. Outer repositories may extend, visualize, adapt, or experiment, but Riverbraid-Core remains the canonical reference for protocol authority and audit behavior.
It defines only the shared mechanics necessary to identify, serialize, preserve, reference, validate, and transport Riverbraid records and attributed assertions. Its authority terminates before interpretation.

## Role in Riverbraid
Riverbraid does not decide truth, trust, evidentiary weight, legitimacy, risk, readiness, certification, moral priority, or the correct interpretation of evidence.

Riverbraid-Core is a canonical protocol authority surface within Riverbraid.
## Mechanical boundary

## Public verification boundary
Core may standardize:

This repository is part of the current Evaluation Kit canonical verification registry and defines core protocol authority and audit behavior for Riverbraid.
- record and assertion identity;
- deterministic serialization and digest contracts once separately adopted;
- references to subjects, sources, agents, scopes, conditions, evidence, profiles, and challenges;
- structural validator behavior and scoped result transport;
- preservation of unknown namespaced types, predicates, and extensions;
- recording of lifecycle and supersession events without rewriting history.

## Evidence boundary
Core must not standardize:

This repository does not claim certification, legal approval, production readiness, absolute security, external audit, complete AI safety, adoption, registry freshness, or absence of defects.
- which assertion or interpretation is correct;
- universal meanings for relationship predicates;
- a root of trust or universal trust score;
- evidentiary weight, relevance, legitimacy, causality, safety, compliance, readiness, maturity, certification, or adoption judgment.

## Canonical One-Liner
Relationship predicate meanings belong to declared, namespaced vocabularies or profiles. A vocabulary mapping is an attributed assertion; it is not a hidden Riverbraid equivalence.

Riverbraid is an open-source deterministic integrity floor for AI governance: a fail-closed, byte-auditable architecture that makes structure, authority, and drift visible. Its broader research directions, including mathematical physics of cognition, memory-flow-truth braiding, and intent-aware compute, remain experimental surfaces built on top of this bounded floor.
## Historical machine surfaces

## Core Function
Earlier ring/constellation and “Trust Anchors” machinery is preserved as Riverbraid history and is not inherited as current Core semantics. The R3 migration must preserve its exact historical bytes while detaching it from the active mechanical verifier.

Riverbraid-Core provides:
* Ring classification and constellation audit
* Required file surface verification
* Byte-level audit of tracked repository files
* BOM detection for text surfaces
* Dirty worktree detection
* Verification output validation
* Audit manifest generation
* Append-only audit trail recording
## Reproduction

## Authority Boundary

Riverbraid-Core is normative for Riverbraid protocol governance.

It defines the audit substrate and verification rules. It does not implement domain-specific behavior for runtime forks, UI layers, signing tools, embedded ports, language surfaces, or experimental cognition layers.

Any repository outside Core must not redefine Riverbraid protocol semantics. It may only declare its role, expose its verification surface, and pass the applicable ring gates.

## Coupling Test

Any change to these files requires a full Ring 2 verification pass before being treated as valid:
* constellation-audit.mjs
* byte-audit.mjs
* cluster-manifest-v2.json
* verify-output.json
* audit-output.json
* AUDIT-MANIFEST.sha256
* AUDIT-TRAIL.ndjson

Required checks:

```bash
node constellation-audit.mjs --ring 2
node byte-audit.mjs --ring 2
```

Expected verified states:
* RING_GATE_PASS_VERIFIED
* BYTE_GATE_PASS_VERIFIED

## Scale Separation Gate

Core owns protocol authority and audit rules.

Outer rings own implementation surfaces, runtime experiments, bridges, tools, visualization, and communication layers.

Core must remain small enough to audit directly. New experimental behavior belongs outside Core unless it is required for the integrity floor itself.

## Linear vs Nonlinear Boundary

The Core audit path is linear:
1. Declare manifest
2. Check required files
3. Read verifier outputs
4. Hash tracked bytes
5. Reject BOM
6. Reject dirty worktrees
7. Emit audit manifest
8. Record audit trail

The broader Riverbraid research surface may remain nonlinear, experimental, expressive, or exploratory. That layer does not override Core verification.

## Stationary State Invariant

Riverbraid-Core is stationary when all of the following are true:
* Local worktree is clean
* Required files are present
* Verifier outputs parse successfully
* Ring 2 returns RING_GATE_PASS_VERIFIED
* Ring 2 returns BYTE_GATE_PASS_VERIFIED
* Audit manifest exists
* Audit trail records the verification event
* No UTF-8 BOM is present in tracked text files

## Verification

Run:

```bash
node constellation-audit.mjs --ring 2
node byte-audit.mjs --ring 2
```

## Claim Hygiene

Riverbraid-Core supports the bounded claim that Riverbraid has a working open-source deterministic integrity floor and governance artifact.

The broader claims around True AI, mathematical physics of cognition, memory-flow-truth braiding, resonance, and intent-aware compute remain active experimental directions unless implemented, tested, and verified in dedicated repositories.
The current public reproduction owner is [Riverbraid-Evaluation-Kit](https://github.com/Riverbraid/Riverbraid-Evaluation-Kit). A result is meaningful only with its exact subject, profile/check contract, evaluator, environment, evidence, and nonclaims.
27 changes: 9 additions & 18 deletions RING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,9 @@
# Riverbraid-Core Ring Declaration
repo: Riverbraid-Core
ring: 0
ring_name: Trust Anchors
phase: Phase 15
promotion_state: CLASSIFIED
## Membership Basis
Ring membership is assigned by Riverbraid-Core/cluster-manifest-v2.json.
Ring membership does not mean verification.
Ring membership does not mean custodian signature.
Ring membership does not mean the gate has been evaluated.
## Promotion States
UNAUDITED
CLASSIFIED
FILES_PRESENT_UNVERIFIED
VERIFIED
## Claim Boundary
This repository remains within declared conditions only.
# Historical Ring ontology notice

The prior Riverbraid Ring / constellation ontology is **historical** and is not a current Core classification system.

The exact prior `RING.md` bytes are preserved at:

`historical/phase15/RING.md`

Current Riverbraid-Core does not assign a trust-anchor ring, promotion rank, or semantic authority through this file. See `PROTOCOL-BOUNDARY.md` and `mechanical-profile.json` for the current mechanical boundary.
Loading
Loading