Canon
SpineWorkspace Canonical Glossary — Ubiquitous Language
This document freezes the load-bearing vocabulary of the SpineWorkspace operating model. Every
canonical document, ADR, gap-register entry and agent response must use these terms with exactly
these meanings. See 01-SPINEWORKSPACE-OPERATING-MODEL.md
for the integrated model.
Company, product and surfaces
| Term | Frozen meaning |
|---|---|
| IntegrateWise | The company and infrastructure platform (integratewise.ai). Not the product. |
| SpineWorkspace | The product and shared work environment (spineworkspace.com). Not the company. |
| Human Workbench | Primary user-facing operating surface inside SpineWorkspace; role-projected, stable shell, adaptive work. |
| AI Workbench | AI-side operating environment hosting Twin and Spine Agents. The label "Twin Workbench" is retired. |
| SharedWorkbench | The canonical, versioned projection contract produced only by the Projection Engine; Canvas and other renderers render it, never own it. |
| Platform Console | Operator/admin surface for the substrate; not a competing daily work destination. |
Entry, identity and access
| Term | Frozen meaning |
|---|---|
| OneAuth | The single host-controlled entry and trust boundary: resolves identity, org, workspace, host identity, roles, existing host connections, allowed connector projections, plugins, MCP capabilities, activation policy. Never copies provider credentials. |
| Host | A runtime in which the Workbench is deployed (ChatGPT, web, Slack, Microsoft, embedded, desktop, customer-hosted, marketplace, agent host). Both a rendering environment and an integration context. |
| Host-native capability | A read/action capability exposed by the active host under current user/workspace permissions; availability is confirmed | declared | unknown. |
| ConnectionBinding | Mapping between a host connection, a canonical principal, and an optional IntegrateWise integration. |
| Connector projection | A governed per-workload projection of a host-owned connection (read / sync / search / event / approved-write); carries scopes, approval requirements, retention, classification, rate limits, revocation state. Never a credential copy. |
| Managed connector | An IntegrateWise-owned connector used only as managed completion where host-native capability is absent; consented, scoped, mapping-activated, revocable. |
Context, memory and state
| Term | Frozen meaning |
|---|---|
| Business Context Spine / Spine Fabric | The tenant-scoped governed canonical context network — operational truth, work, relationships, decisions, evidence, knowledge, history, organizational memory. Not a database, not an ESB. |
| Fortress Spine | The authoritative persistence layer of the Spine. Never directly exposed to hosts or agents; access is only through governed query/projection/cache paths. |
| Spine Cache | Read-optimized, policy-filtered, LLM-readable projection of the Spine; the default agent read surface; always rebuildable; never truth. |
| Organizational Memory | Durable organization-owned memory that has passed the governed promotion boundary. |
| Personal Contextual Memory | User-bound personal work continuity; private by default; only the owner may cite it. |
| AI Continuity Memory | Twin/agent working continuity across turns, model changes, sessions and handoffs; never canonical truth. |
| Spine Network | The navigable relationship graph beneath the Workbench (entities, source identities, relationships, connections, capabilities, tools, documents, knowledge, memory, signals, decisions, actions). |
| Continuity primitives | Event · Entity · Relationship · Synthesis — the four root object types from which everything else derives. |
| State planes | The eleven separated state boundaries: Business Context Spine, Personal Contextual Memory, AI Continuity Memory, Spine Cache, Knowledge, Blobs, Session Logs, Audit Logs, Sync State, Config State, Ephemeral Runtime. |
| Effective Spine | Mandatory Base Spine ∪ department ∪ industry ∪ role ∪ connector ∪ tenant ∪ contextual expansion — additive only. |
Work and coordination
| Term | Frozen meaning |
|---|---|
| Work | The durable unit of human-AI coordination and handoff: work_id, objective, context references, owner, current executor, state, subtasks, evidence, commitments, proposals, authority envelope, capabilities, expected/actual outcome, handoff history, trace IDs. |
| Work identity rule | No participating worker begins meaningful work without a Spine-derived authorized context and Work identity. |
| Twin | The user's contextual, human-facing AI co-worker inside the AI Workbench. One bounded Twin per user. |
| Spine Agent | A governed AI worker with identity, tenant, purpose, owner, delegated authority, scopes, capability access, memory namespace, model profile, risk policy and audit identity; coordinates through shared Work state and evidence. |
| Coworker | The contextual companion between active Workbench use and the Twin: observes active work, gathers context, retrieves information, supports communication. Not a second authority. |
| Active Context Bundle | The assembled, policy-filtered context for one request: actor, host context, entities, relationships, continuity, commitments, signals, decisions, evidence, available actions, policy, completeness level (host-local / partial / canonical). |
| Context Package | The bounded package an agent receives: tenant, work, purpose, entities, state, constraints, authority, allowed capabilities, evidence, freshness, sensitivity, expiry, provenance. |
| OODA | Internal operating grammar (Observe → Orient → Decide → Act); user-facing primitives are Store in Spine / Ask Twin / Assign Twin / Approve Twin Action. |
Communication
| Term | Frozen meaning |
|---|---|
| Bridge | The governed communication substrate over which messages, context references, decisions, approvals, handoffs and execution signals move — always attached to Work, carrying authority context and provenance. Many interaction surfaces; one continuity substrate. |
| ACP | Agent Communication Protocol: agent ↔ agent / agent ↔ Twin governed work/context handoff. A transport, never an authority grant. |
| MCP | AI ↔ tool/resource/capability interoperability mechanism. Interoperability only; never authority, never the product identity. |
| IW Spine Network MCP | The hosted outward MCP boundary for external AI surfaces; Gateway-routed; governed proposals, no storage credentials. |
| MCP Pool | The inward tenant registry of approved external MCP servers/tools: runtime registration, routing, sessions, health, isolation. |
| Continuity Bridge | The distribution/access product for external AI hosts (ChatGPT, Claude, Perplexity, MCP clients, embedded apps, SDK/ADK, marketplaces, APIs) — governed context and capability access without making MCP the product. |
Execution and governance
| Term | Frozen meaning |
|---|---|
| Capability Fabric | Provider-neutral registry/resolver for how authorized intent can be performed (tool-to-tool, memory, MCP, agent-to-agent, API, local, AI execution, browser, workflow, human). |
| Capability | What may be done: identity, version, category, inputs/outputs, authority scope, risk, evidence requirements, execution/sync modes, idempotency, compensation, observability. Cognitive Capability (understand/reason/generate/propose) is distinct from Tool Capability (read/write/invoke/execute). |
| Governance | The cross-cutting authority boundary. Outcomes: ALLOW · DENY · REQUIRE APPROVAL · DELEGATE / ALLOW WITH BOUNDED AUTHORITY. Confidence never grants authority. |
| Hermes | Coordinator of approved execution: dispatch, retries, timeouts, recovery, evidence capture, verification and reconciliation workflows. Not the AI brain; never owns canonical truth. |
| Outcome Event | An observed provider result — not automatically verified business truth. |
| Verification / Reconciliation | Expected-vs-actual closure determining whether reality changed as intended; execution is complete only after both. |
| ContinuityRun | The traceable lifecycle from intent through context, capability, governance, execution, outcome, verification, reconciliation and rehydration; reconstructable via trace/approval/capability_run/execution/verification/reconciliation/continuity_run IDs. |
| Projection Engine | The sole composer of authorized versioned Workbench/context contracts. Role × Department × Industry × Connector Category × Active Context × Policy. |
| Triage | Classifies, links, dedupes, detects conflicts/ambiguity, evaluates materiality/sensitivity/freshness/completeness, stages candidates, routes review. Doctrine: Triage classifies. Governance decides. The Pipeline promotes. Spine owns organizational memory. Twin consumes the governed result. |
| Governed Spine Writer | The only path that commits canonical state, enforcing tenant scope, schema, policy, provenance, evidence, idempotency, atomicity. |
Retired and superseded vocabulary (never reintroduce)
| Retired term | Status / replacement |
|---|---|
| "Cognitive Twin" | Twin. |
"Digital Twin" / DigitalTwin as product language | Twin (the legacy tenant-schema object name may persist in code only). |
| "Twin Workbench" (as a surface label) | AI Workbench (ADR-2026-08-31-01); the deck QA tooling scans for it. |
| "IQ Hub" | Personal knowledge surfaces + Spine knowledge promotion; derived-intelligence plane per ADR-005. |
| "Governor Slack", "AI-Relay Gateway", "Business OS" | January 2026 v11.0 marketing pack — superseded (ADR-2026-09-04-01 §F-3). |
| "Monolithic AI Orchestrator" | Separated: Twin (cognition) · model routing · ADK · Capability Fabric · Governance · Hermes. |
| "Spine database" as the product definition | The Spine is a logical contract; physical storage is a deployment ADR. |
| Direct agent canonical writes; provider success as final truth; blank manually-built workspace as onboarding; MCP as the core data plane | All prohibited — see the twenty canonical laws. |
| "Coworker" as a retired concept | Restored as a distinct concept by ADR-2026-09-04-03 (contextual companion; not a second authority). |