create.record.world
Publish packages, images or pages under the name it holds. Its effect is no: cannot be undone.
What this id is made of
This is not a string. It is create↗.record↗.world↗, three nodes joined by three edges, and each of them has an address, a page and a JSON file. Follow any of them and you get the query for that word rather than a definition of it.
| Node | Edge | Reads as |
|---|---|---|
create↗ | has_verb | this capability has the verb create |
record↗ | acts_on | this capability acts on record |
world↗ | reaches | this capability reaches world |
code↗ | in_family | this capability is in the code family |
no↗ | has_undo_class | this capability has the undo class no |
The gloss above is a convenience, not the definition. A node carries no inherent meaning: what
create.record.worldis emerges from the edges traceable from it. The strongest case isworld↗, where the deployment shapes that use it do not agree about what it means, and the page keeps the disagreement rather than averaging it.
In 3 of 17 published shapes
| Deployment shape | Barrier there | Known by | Whose material | Note | |
|---|---|---|---|---|---|
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | documented | not stated | if a registry token is in the home directory |
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | documented | not stated | if a registry token is in the home directory |
| ○ | The official Dropbox MCP server (contributed by riskmandate.ai) | boundary | documented | mixed | a shared link "for a file or folder, with the option to invite up to 25 viewers by email"; a file request "so others can upload files to a folder you choose". Both publish something under the account's name to whoever holds the URL. |
| Barrier | What stands in the way | Is it a control | |
|---|---|---|---|
| ● | none | nothing in the way | no |
| ◉ | expectation | a rule in prose, enforced by nobody | no |
| ◐ | setting | a switch the agent's own account can flip | no |
| ○ | boundary | enforced above the grant, out of the agent's reach | yes |
What the starting mandates say about it
| The mandate says | Which mandates |
|---|---|
| authorised | none |
| refused | A coding assistant on my machine, Chat in the browser, nothing connected, Find and read my files |
| unstated | A coding assistant in a container on the web, The desktop app, with local tools switched on, Chat, with connectors switched on, A CI job on a hosted runner, A browser extension I installed, A scheduled job under a service account, A reader on my mailbox, Find things in the inbox, draft replies, never send, A reader on my drive, Search our tenant, read-only, An assistant over my Workspace, reading, A sandbox: build and run one AI-agent workflow, What the agent inferred it was authorised to do, from one session |
Unstated is not authorised. A mandate that never mentioned a capability did not authorise it, and the delta on every example page counts it as excess and says which kind it was.
What would move it to the fourth barrier
| What | What it costs | The barrier afterwards |
|---|---|---|
| no publishing token in the agent's environment; publish from CI with a token the agent does not hold | an afternoon to move the publish step | boundary |
This is a published reduction, not a recommendation. Whether it is worth doing depends on the assets and the consequences, which are not in this document and are not this site's to guess. Since v0.4.3 it is also a node,
setting/create.record.world, in the deployment shape universe↗: it narrows this capability and moves it to the barrier named in the third column, which is the path the prohibitions table's last column is a projection of.
The capability grammar↗ · This primitive as JSON↗
Site index for agents↗ · HTML version↗