{"slug":"product/workbench","title":"SpineWorkspace — Human Workbench Information Architecture","section":"product","sectionLabel":"Product","status":"unclassified","type":"document","path":"product/workbench.mdx","bytes":5329,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n\n\n**Status:** CANONICAL TARGET  \n**Product:** SpineWorkspace  \n**Surface:** Human Workbench  \n**Foundation:** Business Context Spine (THE semantic foundation)\n\n## 1. Purpose\n\nThe Human Workbench is the user's operational surface for understanding, deciding on and progressing Work.\n\n**It exists to present Business Context in a form the human can act on.** Without Business Context, the Workbench is empty. With it, the Workbench already knows what matters, what changed, what needs attention, and what the human should focus on next.\n\nIt is a projection over shared Business Context.\n\nIt is not:\n\n- a departmental database;\n- a second source of truth;\n- an integration console;\n- an AI chat shell.\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** Without Business Context, the Workbench has nothing to present. With it, the Workbench already knows what matters, what changed, and what needs attention.\n\n## 2. IA model\n\n```text\nSPINEWORKSPACE HUMAN WORKBENCH\n│\n├── ORIENTATION\n│   ├── Home\n│   ├── Today\n│   ├── My Work\n│   ├── My Queue\n│   ├── Tasks\n│   └── Recent Work\n│\n├── COMMUNICATION\n│   ├── Email\n│   ├── Chat\n│   ├── Calendar\n│   ├── Meetings\n│   ├── Calls\n│   └── Shared Documents\n│\n├── ORGANIZATIONAL MEMORY\n│   ├── Knowledge\n│   ├── Decisions\n│   ├── Documents\n│   ├── Policies\n│   ├── Processes\n│   ├── Meeting Memory\n│   └── Work History\n│\n├── WORK\n│   ├── Active\n│   ├── Waiting\n│   ├── Needs Decision\n│   ├── Needs Approval\n│   ├── Delegated\n│   ├── Blocked\n│   ├── Escalated\n│   └── Completed\n│\n├── BUSINESS DOMAINS\n│   ├── Sales\n│   ├── Marketing\n│   ├── Account Success\n│   ├── Technical Account Success\n│   ├── Finance\n│   ├── RevOps\n│   └── Organization-specific domains\n│\n└── WORK SURFACE\n    ├── Tables\n    ├── Boards\n    ├── Canvas\n    ├── Timeline\n    ├── Entity View\n    ├── Workflow View\n    └── Document / Knowledge View\n```\n\n## 3. Main interaction model\n\nThe Workbench is action-oriented at the top and context-rich underneath.\n\n```text\nUSER SEES WORK\n ↓\nCURRENT STATE\n ↓\nCONTEXT\n ↓\nWHAT CHANGED\n ↓\nWHAT NEEDS ATTENTION\n ↓\nWHAT THE TWIN RECOMMENDS\n ↓\nWHAT THE HUMAN MUST DECIDE\n ↓\nWHAT HAPPENS NEXT\n```\n\n## 4. Adaptive projection\n\n```text\nOrganization\n× Role\n× Domain\n× Responsibility\n× Authority\n× Permissions\n× Current Work\n× Business Context\n× Policy\n× User Preferences\n        ↓\nProjection\n        ↓\nHuman Workbench\n```\n\nThe same underlying organization can produce different projections for different users.\n\n## 5. Workbench operating semantics\n\nThe Workbench supports these semantics without requiring fixed buttons:\n\n- **Store** — retain governed information in the appropriate context/memory scope.\n- **Ask** — ask the Twin for context, analysis or recommendation.\n- **Decide** — make a human decision.\n- **Approve** — authorize a governed consequential action.\n- **Reject** — refuse a proposal.\n- **Redirect** — change the objective/constraints.\n- **Consult** — communicate with another human.\n- **Delegate** — transfer Work through the governed assignment layer.\n- **Verify** — inspect the actual outcome.\n- **Continue** — advance the Work after reconciliation.\n\n## 6. Context Drawer / active context\n\nThe Workbench may expose:\n\n```text\nEntity\nCurrent State\nRelated Work\nRelevant History\nCommunications\nDecisions\nEvidence\nPolicies\nRisks\nDependencies\nTwin Context\n```\n\nThese are projections. The Workbench does not become the owner of those records.\n\n## 7. Adaptive boundary\n\nAutomatically adaptive:\n\n- view order;\n- density;\n- prefetch;\n- notification ranking;\n- capability placement;\n- personal shortcuts.\n\nGoverned:\n\n- canonical truth;\n- shared schema;\n- authority;\n- permissions;\n- policies;\n- governance thresholds;\n- organizational memory publication;\n- external side effects.\n\n## 8. Human/Twin surface relationship\n\n```text\n                 SHARED WORK\n                     │\n          ┌──────────┴──────────┐\n          │                     │\n   HUMAN WORKBENCH        TWIN WORKBENCH\n          │                     │\n     Human judgment        AI coordination\n     Human authority       Delegation\n     Relationship          Execution\n     Approval              Monitoring\n     Accountability        Reporting\n```\n\nThe surfaces are complementary, not competing.\n\n## 9. Acceptance criteria\n\nA Workbench implementation is aligned when:\n\n1. it projects shared Spine state rather than creating a departmental copy;\n2. active context is assembled around Work;\n3. role/domain/responsibility/authority affect projection;\n4. AI receives sandbox context rather than canonical access;\n5. consequential actions require the governance path;\n6. communications remain linked to Work;\n7. source-system outcomes return through reconciliation;\n8. published Organizational Memory is clearly distinct from pending candidates.\n"}