Clarify reconstruction target and evidence boundary#167
Merged
bingran-you merged 1 commit intomainfrom Apr 14, 2026
Merged
Conversation
The tree now separates leaked-source snapshot evidence from later released-binary observations so parity work does not silently blend version-sensitive behavior from incompatible build lines. Constraint: Source snapshot and released binaries describe different evidence lines Rejected: Treat released CLI behavior as the implicit default target | would mix public drift with snapshot-only internal contracts Confidence: high Scope-risk: narrow Reversibility: clean Directive: Future parity assets should name their target line and evidence family before claiming Claude Code equivalence Tested: npx -p first-tree first-tree verify Not-tested: No source-repo runtime changes
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
Testing