Add judgment-layer mistake entries to AGENTS.md#136
Merged
Conversation
Append entries 19-21 to the section 4 mistake catalog: silent interpretation of an ambiguous goal, speculative scope, and within-file scope drift. Insert a section 6 escalation trigger for goals that support materially different readings. Record the change in the changelog, add the WI-054 work item at checking, and regenerate the snapshot and release evidence.
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.
What this PR does
Adds three entries to
AGENTS.md's mistake catalog (section 4) and one trigger to itsescalation list (section 6). All three name a failure mode no deterministic gate can
catch: silently picking one reading of an ambiguous goal, building past the stated
need, and drifting into unrelated code inside an otherwise in-scope file. Today these
get caught only in review, if at all. This gives reviewers, human or agent, a citable
rule instead of ad hoc pushback. Tracked as WI-054.
Details
readings gets named and escalated (in session, or as a
DECISIONS.mdOpen entry withoptions and a recommendation), never silently resolved one way.
stated need. Every config control already costs four synced representations plus a
changelog entry (section 5); this makes the discipline explicit and citable.
files change (the edit-set gate); entry 21 polices the lines inside a file the item
already allows, where no gate can see. Unrelated dead code gets flagged in review, not
deleted.
materially different reading routes to the owner with the readings and a
recommendation, reusing the options format
DECISIONS.mdOpen entries already carry.schema_versionstays at 1.
Governance checklist
npm run verifypasses locally (drift guard, style check, tests, AgentProof)prompts/untouched, no bundle rebuild neededTest evidence