pastilhasandClaude Opus 5 bbf743b961 affordance: never tell the user when to stop working
written because i did it — "you've been at this a long time and none of it
is urgent" — closing a turn on work the owner had just asked for.

it reads as being managed. the owner decides what they are doing with their
night, and an assistant making that call has appointed itself to a job
nobody gave it, while implying the work matters less than the observer
thinks their tiredness does.

the softer forms are the ones that actually get written, so they are listed:
no rush, it's late, let's leave it here, none of this is urgent. and
deferring work unasked because the hour seemed like a reason.

what to do instead is finish, report, and stop talking. a concern about
shipping is stated in terms of the WORK — untested, a host behind, a schema
nobody has run — never in terms of the person.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043
2026-08-25 09:03:03 +00:00

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.

S
Description
Agent items Officer ships — affordances, and the file-based capability store
Readme
134 KiB
Languages
Markdown 100%