Skip to content

Clarify reconstruction target and evidence boundary#167

Merged
bingran-you merged 1 commit intomainfrom
codex/target-evidence-boundary
Apr 14, 2026
Merged

Clarify reconstruction target and evidence boundary#167
bingran-you merged 1 commit intomainfrom
codex/target-evidence-boundary

Conversation

@bingran-you
Copy link
Copy Markdown
Collaborator

Summary

  • add a reconstruction-target guardrail for versioned parity claims
  • separate source-snapshot authority from released-binary authority
  • index the new guardrail from the verification-and-native-test-oracles node

Testing

  • npx -p first-tree first-tree verify

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
@bingran-you bingran-you merged commit efa7926 into main Apr 14, 2026
1 check passed
@bingran-you bingran-you deleted the codex/target-evidence-boundary branch April 14, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant