Home / The model / The capabilities / create.schedule.host
create.schedule.host
Create something that outlives the turn where it runs (a cron, a service). Its effect is yes: undone.
What this id is made of
This is not a string. It is create.schedule.host, 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 |
schedule | acts_on | this capability acts on schedule |
host | reaches | this capability reaches host |
schedule | in_family | this capability is in the schedule family |
yes | has_undo_class | this capability has the undo class yes |
The gloss above is a convenience, not the definition. A node carries no inherent meaning: what
create.schedule.host is emerges from the edges traceable from it. The strongest case is host, 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 4 of 17 published shapes
| Deployment shape | Barrier there | Known by | Whose material | Note | |
|---|---|---|---|---|---|
| ○ | Claude Code on the web (a remote session container) | boundary | observed | not stated | systemctl and /etc/cron.d exist, so a cron can be written - and dies with the container; the real scheduler is the platform's routines, on the harness row |
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | derived | not stated | a shell as you can write a crontab |
| ● | Claude Code (the CLI, on your own machine) | none (not a control) | derived | not stated | a shell as you can write a crontab |
| ● | A scheduled job running as a service account | none (not a control) | derived | not stated | it is one |
| 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 |
| unstated | A coding assistant in a container on the web, The desktop app, with local tools switched on, Chat, with connectors switched on, Chat in the browser, nothing connected, 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, Find and read my files, 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 scheduler in the agent's environment; anything that outlives the turn goes through a person | you create the routine | 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.schedule.host, 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.