Home / The model / The capabilities / create.schedule.tenant
create.schedule.tenant
Create something that outlives the session, on the platform (a routine, a scheduled trigger, a new session). Verb create, object schedule, reach tenant, family schedule. Its effect is yes: undone.
In 1 of 9 published shapes
| Deployment shape | Barrier there | Known by | Note | |
|---|---|---|---|---|
| ◐ | Claude Code on the web (a remote session container) | setting (not a control) | self-reported | a routine or a scheduled trigger resumes this session or spawns another later: it outlives the container |
| 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 in a container on the web, Chat in the browser, nothing connected |
| unstated | A coding assistant on my machine, 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 |
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.