pastilhasandClaude Opus 5
ba9920fcd6
Started in the platform checkout and named "Platform Deploys", the second intake read TODO.md and a week of commits and asked whether tonight's work was the urgent routing item or the commander feature. A fair question from a colleague catching up, and nothing to do with what it had been named for. Two things were missing. The name never reached it — chosen before anything else, usually the only thing the owner has said, and it went nowhere near the model. And nothing said what orientation is FOR. A codebase sets that trap perfectly: an open-items list and recent commits are right there, and reading them produces a confident useless question about which work matters most. So: the name settles the subject, and the search is for something that HAPPENS AGAIN — what event recurs here, and what does somebody do by hand every time it does. Current priorities are not a trigger. Nothing you can only do once is a commander. 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.