Repository navigation
Allow reading upstream source during development - #2
Merged
Merged
Conversation
Amends the reference-material policy: the triage-only restriction on references/ is lifted, reading clvm, clvm_rs, and chia_rs source is now allowed at any time. Recorded decision by Evan, 2026-07-26. Rationale: for the operator intersection, correctness is defined by the deployed consensus binary, and the diff harness compares against that binary, so reading source cannot silently corrupt the evidence. Three guardrails preserve what the old rule was protecting: no code is copied into the tree, spec statements are still established by evidence against the binary rather than by resemblance to upstream source, and commits disclose when upstream source informed a choice.
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
1 participant
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.
What changed
The reference-material policy in CLAUDE.md previously allowed opening
references/ only in divergence-triage sessions. This lifts that
restriction: upstream source (clvm, clvm_rs, chia_rs) may be read at
any time, including while implementing. Recorded as your decision,
2026-07-26.
Three guardrails replace the blanket rule:
established by evidence against the consensus binary (probes,
cross-checked vectors), never by "matches upstream source". The
spec stays complete enough that a reader never needs upstream
source to predict a vector.
choice.
Review guide
the property you care about (the spec is the deliverable and the
vector evidence stays anchored to the deployed binary) now that
reading is unrestricted?
workflow section from PR Adopt feature-branch workflow with reviewed PRs #1. The two PRs touch different sections
and merge cleanly in either order.