comply

Rule compliance is checked in deterministic steps around one dispatch step. The protocols live in the CLI so they cannot drift from the checker. Emit them and follow them exactly.

Determine the touch-list

$ARGUMENTS names either a plan and lets its touch-list be derived, or the touch-list itself:

• If $ARGUMENTS is one or more repo-relative paths (no spaces, each ending in a known extension), use them directly as the touch-list.
• If $ARGUMENTS names one markdown file, treat it as the plan and derive its touch-list from every backticked, repo-relative path with a known extension (.ts, .md, .json, .jsonl, .yml/.yaml, .sh) that it mentions — the same convention nullius-kit pipeline touched-areas uses to derive a proposal's own touched paths.
• If $ARGUMENTS is empty, use the most recently modified .md file in the plans directory (.claude/plans or ~/.claude/plans, newest first) as the plan, and derive its touch-list the same way.

Call the touch-list <paths...> below and the plan (if one was used) <plan>.

1. Select the rules that bind

npx -y @nullius-inverba/claims rules select --paths <paths...>

Deterministic, no model involved: it prints the id of every rule under .claude/rules/ whose applies_to matches at least one path in the touch-list, then the excluded count. Keep the excluded count — report it to the user later even if it is zero, because a selection that silently narrows is the failure this verb exists to prevent.

If zero rules are selected, say so and stop: there is nothing to dispatch, and that is a real answer, not a failure to find work.

2. Dispatch one starved brief per selected rule

For each rule id rules select printed:

npx -y @nullius-inverba/claims rules select --paths <paths...> --emit-brief <rule-id>

This prints one starved compliance brief on stdout, and nothing else — the rule's id and full text, plus the touch-list, with no sibling rules, no plan rationale, no narrative.