Repository navigation
Tracker: GOVERNANCE.md > Durable Knowledge and Self-Improvement #1361
Description
Activity
Two further pre-existing findings from the whole-unit read the #1317 class 2 pull request ran over this unit, gathered here per the tracker's rule:
- "A skill's own trigger going unread by the session at all, by contrast, is a loading problem, fixed by getting the rule into context (the
CLAUDE.mdimportingAGENTS.md), not by a hook." The parenthetical names a fix that does not reach the failure it is attached to: theCLAUDE.mdimport loadsAGENTS.mdtext, and a skill's trigger reaches a session only through the skills install, whichAGENTS.md"Where the Rules Live" itself names as the fix for a rule that keeps needing restating. - "so it was promoted to a
gh-write-guardhook rule." The unit locates its other two mechanisms (.husky/pre-push, theagent-conductSkill path) but namesgh-write-guardwith no location, so a reader with only this unit cannot verify the promoted rule exists. It does, inhost-setup/agent-safety/claude/gh-write-guard.py.
- "A skill's own trigger going unread by the session at all, by contrast, is a loading problem, fixed by getting the rule into context (the
Two more from the second whole-unit read on the same pull request:
- "The triggering shape is decidable from the tool call's own text, arguments, and working directory alone" is the condition the bullet later says "still binds" a committed hook, but a committed git hook sees no tool call. It sees a git operation's refs, object ids, and tree. Applied literally to the
.husky/pre-pushexample the unit itself gives, the condition does not fit its own wording. - "belongs in a committed governance file (
GOVERNANCE.mdfor a cross-cutting rule,AGENTS.md,CODESTYLE.md,WORKFLOW.md, or a committed backlog the repository already keeps)" lists a backlog as a member of the set "governance file", which it is not, so the parenthetical misstates its own category.
- "The triggering shape is decidable from the tool call's own text, arguments, and working directory alone" is the condition the bullet later says "still binds" a committed hook, but a committed git hook sees no tool call. It sees a git operation's refs, object ids, and tree. Applied literally to the
- added a commit that references this issue
on Sep 5, 2026
Tracker for
GOVERNANCE.md > Durable Knowledge and Self-Improvement. Filed under #1315's roll-up of the open prose backlog: every finding a bundle issue enumerated against this unit is listed here once, one line each, naming the issue it came from, and the bundle is closed as a duplicate of this tracker so the finding is not lost and the bundle stops being a unit of work. A newpre-existingfinding on this unit gathers here perpr-review-conduct's Merge Gate, numbering continuing this list. This tracker closes when the unit is rewritten and each line below is settled or superseded.