delegation-and-review §3: a read-only survey reports leads, not facts - #78
Merged
Merged
Conversation
Fan-out finders scanning for dedup targets, dead code, or duplication over-claim in the scope-inflating direction — substring counts, false 'byte-identical', dissolving dedups, 'dead' code with live registrations. §3 already covers the empty-input synthesizer (confabulates from nothing) and the settled-tree re-read; this is the distinct third case: the survey ran, returned non-empty, and every finding was a confidently-wrong lead. Re-verify each in source before speccing, and re-check whenever a finding reverses scope, because the plan built on the survey is now stale. Class-distilled from a mining pass over the owner's own sessions (no code taken). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
firaen22
force-pushed
the
mine-survey-reports-leads
branch
from
July 25, 2026 00:11
d525a7b to
3272a11
Compare
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
2 participants
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
New §3 bullet: fan-out finders scanning for dedup targets, dead code, or duplication systematically over-claim in the scope-inflating direction. Treat each finding as a hypothesis — open the cited files and confirm before it enters the plan, and re-check whenever a finding reverses scope, because the tiered plan built on the survey is now stale.
Why
§3 already covers the empty-input synthesizer (confabulates from nothing) and the settled-tree re-read (re-reads an already-fixed file). This is the distinct third case: the survey ran, returned non-empty, and every finding was a confidently-wrong lead — a substring count of "66 three.js sites" that was 2 files, "byte-identical" components that diverged on a prop and a fallback, a "NumField duplication" that dissolved into two incompatible families, a "dead" component with a live registry entry — each reversal re-ordering the plan.
Class-distilled from a mining pass over the owner's own sessions (no code taken). Ships
unprobedper the covenant..github/checks.pygreen.🤖 Generated with Claude Code