pastilhasandClaude Opus 5
5161304f12
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>
Officer capabilities
The file-based store Officer reads agent items from. This repository holds the ones the platform ships; everything else in this directory is yours.
affordances/officer/core/ ← shipped here
skills/ tools/ tasks/ processes/ extensions/ agents/
Those six directories are created by the platform at boot and are where you and your agents author
items. They are deliberately not tracked here — your work is not ours to version. extensions/tool-loader
is written by the platform from its own source and will reappear if you delete it.
Affordances
An affordance is what the surface on the other end of the conversation offers the agent: what the client will render, accept or ignore. Not what the agent can do — what it will get away with.
The platform compiles every affordance into one block and appends it to each agent session, so an agent
knows things it could not otherwise discover from the filesystem. plugins/CLAUDE.md in the platform is
the authority on the format and on what belongs in one.
Layout is <publisher>/<plugin>/, with core in the plugin slot for the platform's own. A plugin ships
its own affordances/ directory and installing it copies them in.
Updating
git pull, or press Update all on the platform's marketplace screen, which updates this alongside
every installed plugin.
Your own untracked items are unaffected by either.