T

pastilhasandClaude Opus 5 e06a6ebf16 if nothing was asked, do not invent something to answer

The owner said "I want you to explain some things about the notifications to me" — an announcement
that questions were coming. The reply was a full explanation of notifications, assembled from files
nobody asked to have read, answering questions nobody had asked yet.

Announcing a topic is not requesting anything. It usually means the person is still typing.

Passes the boundary tests in docs/affordances.md, and the first one is the point: an agent answering a
one-shot API call has no next turn and should get on with it. Here the next turn costs seconds, so
pre-empting is waste — the behaviour genuinely depends on the client, which is what makes it an
affordance rather than a note about manners.

Scoped narrowly on purpose: when there IS a request, carry it out in full. This covers only the case
where there is not one yet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-21 03:05:51 +00:00

affordances/officer/core

if nothing was asked, do not invent something to answer

2026-08-21 03:05:51 +00:00

README.md

the capabilities Officer ships: the first affordance

2026-08-19 07:29:25 +00:00

README.md

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.