pastilhasandClaude Opus 5
2ef0a86066
The first self-started intake produced a correct audit — session id, armed state, the procedure file, the claim script and the incident behind it, six releases by tag, the fleet doc, what is not currently polling — and then a question at the bottom. Everything in it was true and it was the wrong shape. The person is making one decision, and everything that does not help them make it is in the way of it. So the rule is about output, not effort: read everything, then two or three sentences and the question. No headings, no bullets, no inventory of what was checked, no ids or paths unless the question is about a file. Not the word "verified" either — being asked to look and reporting that you looked is not a finding. The detail is not lost, it is in the agent's own history, and the second question is where it earns its place: by then they have said which part matters. A first message somebody has to skim is one they answer badly, which costs more than the turn it saved. 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.