schedule (object)
The object schedule as a node: the 2 capability primitives it appears in, what they reach, and how it connects. Meaning from connectivity, not from a definition.
Source: https://abp.sgit.ai/model/lexicon/objects/schedule/index.html↗ · site v0.11.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.
Home↗ / The model↗ / The lexicon↗ / schedule
schedule
The object schedule, and every primitive it appears in. This page is a query, not a definition.
A node carries no inherent meaning. What
schedulemeans here emerges from the edges traceable from it, and confidence in that meaning is proportional to how richly it is connected. It is connected to 2 of 23 primitives here. That, and not the sentence above, is what it means. The discipline this follows ↗.
The 2 primitives with this object
| Primitive | Published gloss | Spelled out | Undo | In how many shapes |
|---|---|---|---|---|
create.schedule.host↗ | Create something that outlives the turn where it runs (a cron, a service) | create↗.schedule↗.host↗ | yes | 4 of 17 |
create.schedule.tenant↗ | Create something that outlives the session, on the platform (a routine, a scheduled trigger, a new session) | create↗.schedule↗.tenant↗ | yes | 3 of 17 |
How this node connects
| Edge | Reads as | To |
|---|---|---|
acted_on_by | schedule is the object class of these 2 primitives | 2 capabilities |
acts_on | the inverse, walked the other way, with different fan out | one capability at a time |
This node as JSON↗ · The lexicon↗ · The edge vocabulary↗