docs: establish TruthBounty V2 governance baseline - #1
Merged
Conversation
dDevAhmed
marked this pull request as ready for review
August 25, 2026 15:39
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Establishes a reviewable TruthBounty V2 governance baseline before implementation remediation begins.
Changes
TruthBountyWeighted.solas transitional/reference andTruthBountyClaims.solas deprecated for V2 settlement;repos.md;SC-036, absentFE-###backlog, and duplicateStellar Wave/stellar-wavelabels.Why this comes first
The current canonical README still describes V1 backend-owned claims, lifecycle, aggregation, and frontend data authority. Implementation work cannot be reconciled safely while contributors are governed by contradictory documentation.
Review gates
TruthBountyWeighted.solremains reference/transitional.TruthBountyClaims.solis excluded from production deployment.PROTOCOL_V2_SPEC.md, the engineering blueprint, master backlog, and dependency graph.Verification
All four branch files were fetched from GitHub after writing and compared byte-for-byte with the reviewed drafts.
Out of scope
This PR does not modify Solidity, backend, frontend, deployments, issue states, labels, or milestones. Those actions remain blocked until the ADR and reconciliation baseline are reviewed.