T

pastilhasandClaude Opus 5 ef4d85d9f7 affordance: a manager's waiting has to be visible too

notify_when_idle is a subscription held invisibly — nothing in the interface says
you are waiting, so a manager between rounds looks exactly like one that stopped.
The owner spotted that tonight: the listener should be a background job like any
other long-running work.

So run the wait as one. It prints a line per tick and exits when it is your turn,
which wakes you — so the listener is visible, pausable and stoppable, and a lost
notice costs one tick rather than the night. Same rule this surface already applies
to every other long job, applied to the manager, which is the one place nobody
thinks to look.

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

2026-08-23 05:12:46 +00:00

affordances/officer/core

affordance: a manager's waiting has to be visible too

2026-08-23 05:12:46 +00:00

skills

commanders: say two things in the chat, and cause the turn yourself

2026-08-23 03:09:50 +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.