| tenant | the client who deploys the station. Its config is a YAML file, identified by tenant_id. |
| API | a service of the tenant, described by its OpenAPI. Only the listed operations (operations) can be reached, and each says whether it reads or writes (access). |
| capability | an allowed operation of an API. Nothing else can be reached. |
| item | a possible action: buy an article, pick a time slot, approve a timesheet, refund an invoice line. |
skill (skills:) | what an agent sees: a capability it calls (invoke), with what is needed to use it. A skill that declares kinds turns its rows into items a person can choose (select) and execute (submit); without kinds, it answers with what it reads. Raw capabilities are never exposed. |
| kind | the category of an item (dish, pickup, delivery), declared in its skill's kinds. A kind is recognised on the row by its when, and can have its own select and submit. |
| room | a person's space with the station, the same on every door. It keeps their selection, their journey and their receipts. |
| selection | what the person has chosen in their room, ahead of the submit. It is made of parts, one per skill with kinds. |
| select guard | what must be true for an item to enter the selection: an ordered list: a form (form), a condition (require), the tenant's check (check), a price computed by the tenant (update: {price}); each may carry when. |
| submit | the execution of the selection: each skill calls its operation (mode: request), sends the person to the tenant's site (handover), or triggers nothing (self). |
| submit guard | what is required once, before the submit: accepted terms, an explicit confirmation. |
| playbook | a set of tasks that leads to a result: what a selection must cover before it can be submitted, and in which order. |