decision-rights-doctrine
Skill3 starsChanged 3 months agoMITView on GitHub
Shared doctrine reference for which decisions an agent MUST escalate to the operator vs may decide autonomously. Holds the two-tier escalation model (Tier 1 hard-escalate, Tier 2 self-check-then-escalate-if-material), the six-category taxonomy (A-F) mined from guardian PRs, the alignment-audit self-check procedure, and the escalation mechanics. This skill has no operations — it is reference content read by any agent facing a decision it is unsure it has the standing to make. Never inline this doctrine into a consumer skill or worker brief — operator-confirmed rules must persist in one place.
In this repository41 other files it gives its agents.
- cadence-goalsSkill
- ci-feedback-loopSkill
- compoundSkill
- diataxisSkill
- dispatch-gateSkill
- drift-checkSkill
- family-checkSkill
- fix-then-re-review-ladderSkill
- github-projectsSkill
- gitSkill
- goal-treeSkill
- handoffSkill
- improvement-loopSkill
- kb-captureSkill
- kb-compileSkill
- kb-coreSkill
- kb-lessons-bridgeSkill
- kb-lintSkill
- l1-supervisorSkill
- l2-supervisorSkill
- lessons-learnedSkill
- lN-lifecycle-doctrineSkill
- lN-review-doctrineSkill
- medical-recordsSkill
- operator-interview-doctrineSkill
- operator-interviewSkill
- operator-reviewSkill
- planning-workflowSkill
- pr-review-fanoutSkill
- pull-taskSkill
- ralph-wiggumSkill
- reviewSkill
- root-cause-depthSkill
- scan-documentSkill
- self-improvementSkill
- self-verifySkill
- skillifySkill
- task-workflowSkill
- testing-without-mocksSkill
- vault-cloudSkill
- verify-inherited-premiseSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Every decision an agent faces during a turn falls into exactly one of six categories (A-F, defined in references/taxonomy.md).
- Distinctive: line 43
Self-recognized escalation carries special force: If the agent has already flagged a predicate or decision as ambiguous or reserved earlier …
- Very specific: line 51
If a rule in references/taxonomy.md is wrong for the current iteration, fix it here via PR against pfeff/claude-skills.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
decision-rights-doctrine — shared operator-reserved-decision doctrine
This skill is a doctrine-only reference. It defines which decisions belong to the operator regardless of who is nominally "driving" a turn, and which an agent may resolve on its own judgment. It closes a miscalibration observed in mission-session transcripts: agents absorbing operator-reserved decisions — setting long-term-objective values, downgrading risk classifications, resolving ambiguous stop-conditions, finalizing an irreversible action's fuzzy predicate, choosing a blast-radius-bearing mechanism, or pre-shaping a nominally-independent verdict — without surfacing the call.
Consumers (dispatch-gate, self-verify, and any agent brief) load this doctrine at
decision time. It has no operations of its own.
Source of truth
| File | Purpose |
references/taxonomy.md | The two-tier model, the A-F category taxonomy with one guardian-PR example each, the Tier 2 alignment-audit self-check procedure, and the escalation mechanics ("how to escalate"). |
Invariants
Every decision an agent faces during a turn falls into exactly one of six categories
(A-F, defined in references/taxonomy.md). The categories partition into two tiers:
- Tier 1 (D, F, B) — MUST-ESCALATE. The agent does not proceed without an operator decision. It surfaces its assessment and the reserved decision, and stops.
- Tier 2 (A, C, E) — SELF-CHECK THEN ESCALATE-IF-MATERIAL. The agent runs the alignment-audit self-check before proceeding; it escalates only if the check finds the element ungrounded in an operator decision/spec AND material.
The tier assignment is fixed by this doctrine — a consumer skill does not re-derive it, promote a Tier 2 category to "usually fine to skip," or demote a Tier 1 category to "self-check first." Category-to-tier mapping changes are doctrine edits, landed here.
Self-recognized escalation carries special force. If the agent has already flagged
a predicate or decision as ambiguous or reserved earlier in the same turn, it may not
talk itself back down under momentum and resolve it anyway — the earlier flag stands
and the decision routes to the operator (this is the exact failure mode in the
Category D canonical example; see references/taxonomy.md).
When this doctrine is wrong
If a rule in references/taxonomy.md is wrong for the current iteration, fix it
here via PR against pfeff/claude-skills. Do not patch the rule inside a consumer
skill or worker brief — that's the doctrine-drift failure mode this split exists to
prevent.
See also
lN-lifecycle-doctrine(references/lifecycle.md, "Escalation invariant — reality vs. manifest") — the adjacent, narrower rule this doctrine generalizes: a child whose observed reality disagrees with its frozen task-context/manifest stops and reports rather than improvising. That invariant is the manifest-drift instance of the broader Category D/Tier 1 principle stated here (fuzzy predicate at the moment of an irreversible action) — read this doctrine for the full six-category taxonomy the manifest case is one instance of.dispatch-gateskill, Step 6 ("Frozen manifest (post-dispatch)") — the concrete stop-and-report mechanism a dispatched job uses to surface a Tier 1 mismatch to its dispatcher.self-verifyskill — checks, as part of its own axis evaluation, that a job did not silently absorb a Tier 1 decision instead of escalating it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

