Platform vocabulary

Glossary

Use these words exactly. The console is built around them.

Term	Definition
Service	The repeatable offering a team renders for someone else. Contains processes, shared context, and stakeholder defaults.
Subject	A real-world entity (company, person, policy) in an account-level registry, shared across services.
Engagement	One rendering of a Service for a Subject — the roll-up container for runs, handoffs, and stakeholder grants.
Process	One team's SOP-skill plus its review surface and config. Owned by exactly one Service.
Process version	An immutable build of a process (`SOP` + app + config). Runs pin a version.
Run	One execution of a process version inside an engagement.
Inbox	The per-person queue of work that needs verification or input.
Knowledge base	Human-readable, human-editable notes and SOPs the service accumulates as runs complete.
Stakeholder	A named person attached to an engagement through an access grant.
Workspace / drive	The durable filesystem for a service where agents and people collaborate on files.
Dispatch	The coordinator that resolves triggers, mints runs, spawns sandboxes, and parks for human input.
Console	The always-warm operator UI for boards, inbox, authoring, and settings.

Approvals, deliverables, corrections, lineage, and SLAs are fields and actions — not additional nouns.