32 · Terminology

One Meaning per Term

Term	Canonical meaning
Spine / Business Context Spine	The durable, governed substrate that holds Business Context — THE organization's memory. Not a database, not a data lake.
Business Context	The semantic concept — the connected business reality. The Spine holds it.
Work	The common unit of activity carrying objective, participants, context, state, evidence, dependencies, outcomes, and handoffs.
Workspace (SpineWorkspace)	The self-organizing workspace over the Business Context Spine where humans and AI work on the same reality with separate continuity.
Workbench	A projection over Business Context for a participant and Work. Two kinds: Human Workbench and AI Workbench.
Human Workbench	The primary daily product — Human Workbench as projection over Business Context + Personal Contextual Memory.
AI Workbench	The AI operating environment over Business Context + AI Continuity Memory. Not a chat panel. Twin lives inside it.
Twin	The human-facing AI coworker inside the AI Workbench — twin:{userId}, one per human, tenant-scoped.
Spine Agent	A governed organizational actor with identity, role, authority, capability access, Work ownership, evidence, and continuity.
Memory	Durable context that persists. Three domains — organizational (THE) vs personal contextual vs AI continuity (serving).
Continuity	What persists across sessions, devices, and agents so Work can continue intelligently.
Organizational Memory	Durable business memory inside the Spine that the organization has accepted as truth.
Personal Contextual Memory	Human working continuity — private unless deliberately shared/promoted; serves Business Context.
AI Continuity Memory	Twin/agent working continuity that maintains AI state while grounded in Business Context; serves Business Context. G-10: semantic scope defined, substrate decision open.
Capability	A provider-neutral action the system can do (resolved via Fabric before governance).
Capability Fabric	The active, resolved catalogue of what can be done — ADK, MCP, native + external.
Governance	The verdict on may it be done? — identity → authority → policy → plan → approval → authorization.
Hermes	The execution plane — executes only authorized plans, returns outcome + evidence. Does not decide authority.
Projection	A governed, participant-scoped rendering of one Spine reality — Human vs AI projections over the same Business Context.
Active Context Bundle	Business Context slice + Work + evidence + authority + continuity — what both workbenches hydrate from.
Pipeline	Work movement: Business Intent → Context → Work → Plan → Capability → Governance → Hermes → Verify → Reconcile → Spine → Rehydrate.
Shared Work	The durable Work-anchored medium through which humans, Twin, and agents hand off with context and evidence.
Ecosystem	An external system/plane where business reality lives (Salesforce, M365, Jira …).
MCP / MCP Pool	Governed tool/context surface for AI, routed via the Pool — not an open public MCP.
Loader / Normalizer / Governed Writer	The only pipeline that may update Spine truth — provider schema is never canonical.
Verification / Reconciliation	Expected vs observed judged, mismatch resolved, promotion to Spine decided, projections invalidated.
Tenancy	Isolation boundary: one Spine, one projection regime, one memory regime per tenant.

If a doc uses one of these terms to mean something else, the doc — not the glossary — is wrong.

Where to Go Next

<CardGroup cols={2}>

The only document allowed to redefine these meanings.


Authority-ranked register of what decided these meanings.


Decisions and what each supersedes.

</CardGroup>