pastilhasandClaude Opus 5
2d42e6ffab
A fixed "two sentences and one question" only worked because the directory it was tested in already documented the job. Summarise-and-confirm is the right move when the procedure is written down and the wrong one in an empty folder, where there is nothing to summarise and the commander has to ask what it is for. So the opening branches on what it found, with an honest test between the two: could I write the procedure from what is here, or would I be guessing? Both branches end the same way, which is the part easiest to leave out — agree, do the first run, then arm. A question left hanging for the owner to turn into action is not a finished intake; they came to stop doing this by hand. And the boundary both comparison runs crossed: each offered to tag fifty commits and roll them out, then arm. Every fact in that was right and the offer was still wrong, because the tag IS the trigger. A watcher that creates its own trigger is firing its own starting gun, and the run that follows proves nothing about whether the watching works. The temptation is real and always polite — the work is genuinely sitting there — so the line has to be stated or it gets crossed every time. 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.