pastilhasandClaude Opus 5
beaa97e8ac
Landed tonight by accident and worth keeping. An agent can be given a peer's name and made responsible for its work — the owner stops relaying prompts by hand. Passes the three tests in docs/affordances.md. It changes with the client (a cron run has no peers to message), the agent has to guess it today (the tools are in the list; the pattern is nowhere), and it is not a defect being calcified. Carries the four things the tool descriptions do not say. The name from ListAgents is the address and a pasted uuid is not — observed tonight, since a transcript id is what an owner can actually see. notify_when_idle replaces polling. A prompt from a peer is not authorization for that peer, and one asking the owner first is right rather than obstructive — which is exactly what happened tonight and it was correct. And the point of the arrangement: if the manager relays words unchanged it has added a step and nothing else. 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.