-
Notifications
You must be signed in to change notification settings - Fork 0
R3: establish primitive-boundary topology #7
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.
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
main
Choose a base branch
from
r3/public-routing-boundary
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,24 @@ | ||
| # Riverbraid: A Deterministic Integrity Floor for AI Governance | ||
| # Riverbraid public navigation | ||
|
|
||
| Riverbraid is an open source verification floor for making structure, authority, and drift visible before trust is granted. | ||
| > Lifecycle: ACTIVE_ARCHITECTURAL_SURFACE | ||
| > Role: PUBLIC_ROUTING_AND_COMMUNITY_HEALTH | ||
| > Protocol authority: NONE | ||
| > Project authority: ROUTING_ONLY | ||
| > Runtime membership: EXCLUDED_AS_RUNTIME_COMPONENT | ||
|
|
||
| Riverbraid is an open-source evidence fabric for preserving inspectable claims, evidence references, attributed relationship assertions, uncertainty, and legitimate interpretive divergence. | ||
|
|
||
| Riverbraid does not decide truth, trust, evidentiary weight, legitimacy, risk, readiness, certification, moral priority, or the correct interpretation of evidence. | ||
|
|
||
| ## Start here | ||
|
|
||
| | Path | Repository | Purpose | | ||
| |---|---|---| | ||
| | 🚀 Start Here | [Riverbraid-Evaluation-Kit](https://github.com/Riverbraid/Riverbraid-Evaluation-Kit) | Run the public proof path. | | ||
| | 📖 Read More | [Riverbraid-Documentation](https://github.com/Riverbraid/Riverbraid-Documentation) | Understand concepts, boundaries, and the system map. | | ||
| | ⚖️ Protocol Source | [Riverbraid-Core](https://github.com/Riverbraid/Riverbraid-Core) | Inspect the normative protocol source. | | ||
| | 🧭 Registry | [Riverbraid-Golds](https://github.com/Riverbraid/Riverbraid-Golds) | See the coordinated repository surface. | | ||
| | 🛡️ Safety Example | [Riverbraid-Safety-Gold](https://github.com/Riverbraid/Riverbraid-Safety-Gold) | Review a bounded safety verification surface. | | ||
| | ✨ Visual Demo | [Riverbraid-Gold-V2](https://github.com/Riverbraid/Riverbraid-Gold-V2) | See the integrity concept visually. | | ||
| - **Run the currently declared mechanical reproduction profile:** [Riverbraid-Evaluation-Kit](https://github.com/Riverbraid/Riverbraid-Evaluation-Kit) | ||
| - **Understand the system and current public map:** [Riverbraid-Documentation](https://github.com/Riverbraid/Riverbraid-Documentation) | ||
| - **Inspect the mechanical interoperability grammar:** [Riverbraid-Core](https://github.com/Riverbraid/Riverbraid-Core) | ||
| - **Inspect Riverbraid project decisions and lifecycle authority:** [Riverbraid-Governance](https://github.com/Riverbraid/Riverbraid-Governance) | ||
|
|
||
| > [!IMPORTANT] | ||
| > Riverbraid does not claim certification, legal approval, production readiness, external audit, complete AI safety, absolute security, or absence of defects. | ||
| Five research repositories remain active but experimental and noncontrolling: Cognition, Gold-V2, Liminal-Monitoring, Wasm-Bridge, and Weave-Gold. They are excluded from the current mechanical reproduction profile. | ||
|
|
||
| ## Public route | ||
| Forty-two older repositories are preserved as historical Riverbraid surfaces pending archive. Historical status is a project lifecycle statement, not a claim that their ideas are false or unimportant. | ||
|
|
||
| Profile → Evaluation Kit → Documentation → Core or domain repository as needed. | ||
| This `.github` repository provides community-health and routing material. The Riverbraid owner is currently a GitHub User account, so this file is not relied on as the sole account-level public entrance. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When consumers compare this public routing page with the repository's machine-readable state, the new
ACTIVE_ARCHITECTURAL_SURFACElabel contradictsrepo.role.json, which still declaresstatus: "parked"andactive_behavior_claimed: false;verify-parked.cjsalso explicitly enforces the parked status. This leaves the public and automated lifecycle classifications mutually inconsistent, so either the metadata and verifier must be updated as part of this transition or the profile must retain a parked lifecycle label.Useful? React with 👍 / 👎.