T

pastilhas c5dc886141 commands go in a fence, because a fence has a copy button

reported after it happened repeatedly: commands rendered as inline backticks,
which the user then has to select by hand — on a phone especially.

it passes the tests in docs/affordances.md rather than being a defect worn as
one. a terminal client would not care; this one has a copy button on fenced
blocks and none on inline code, so it is a fact about the surface. and the
partial code fix available — click-to-copy on inline code — would not make it
right anyway: a command still wants its own line and unambiguous boundaries.

the deciding argument is that this already existed as a private memory, in one
project, for one agent. it has never helped another agent and never would. an
affordance is how a fact like that stops being one agent's note.

says not to include a `$` prompt, because that gets copied too and then it
does not run — which is the specific way a well-meant fence still fails.

2026-08-19 23:31:49 +00:00

affordances/officer/core

commands go in a fence, because a fence has a copy button

2026-08-19 23:31:49 +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.