The rules had leaked toward the one commander that exists. Audited by grepping the commander skill for
deploy vocabulary rather than by rereading it, which found five places where a general rule was written in
terms of the specific job it came from:
- the baseline rule's headline example was "watch for a new tag" — the one case, standing in for all of them.
Now "watch for new X, whatever X is: a tag, a file in a folder, a row, an unread message, an alert".
- the loop "cannot weigh a host" → cannot weigh a situation.
- OFFICER_ROOT being empty "makes every release look permanently undeployed" → makes anything the loop writes
to record its own progress land where nothing reads it, so a watcher has no baseline and acts on the same
work for ever. Same defect, stated as what it costs any watcher.
- "a procedure in a file makes the deploy repeatable next month" → makes the same job repeatable, and
reviewable by somebody else.
- the local-address rule was fleet-specific AND duplicated what the deploy skill already says. Generalised to
"reach what you are watching by the shortest path available", with the Officer-specific instance left where
it belongs.
The cross-reference now names the Deploying Officer SKILL rather than a file path, because a skill has a
description in the index and a file path has to be known about first.
What the audit was checking: a user describing something that has nothing to do with releases must get the
same rules — baseline, claim once, ask before arming if the condition is not clear, spawn for judgement, say
what you did not do. Those were always general. The examples around them were not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pastilhasandClaude Opus 5
5161304f12