Create something that outlives the turn where it runs (a cron, a service)
create.schedule.host: which products grant it, what stands in the way, what narrows it, and who wants it.
Source: https://what-can-it-do.games.sgit.ai/map/capabilities/create.schedule.host/index.html↗ · site v0.8.0 · this file is generated from the same content
as the page, so the two cannot drift. Every page on this site has a .md twin; internal links
below point at them.
Play↗ / The map↗ / The capabilities↗ / Create something that outlives the turn where it runs (a cron, a service)
Create something that outlives the turn where it runs (a cron, a service)
create.schedule.host — create × schedule at host reach (the machine, container or account it runs as). Family: schedule. Effect: undone by the same actor with no loss.
Granted by 4 of 9
| Profile | Control on the path | Evidence | Via |
|---|---|---|---|
| Claude Code — web container↗ | ○ boundary | observed | shell (Bash) |
| Claude Code — local · confirm off↗ | ● none | derived | shell (Bash) |
| Claude Code — local · confirm on↗ | ● none | derived | shell (Bash) |
| Scheduled job — service account↗ | ● none | derived | the job |
What narrows it
The setting: no scheduler in the agent's environment; anything that outlives the turn goes through a person
What it costs: you create the routine
Tier after: boundary
In the mandates
- not wanted by A coding assistant on my machine↗
Edit the primitives ↗ · edit the reductions ↗