Unclassified

SpineWorkspace — Human Workbench Information Architecture

<!-- DOCUMENT CLASS: PUBLIC | SOURCE: 06_SPINEWORKSPACE_HUMAN_WORKBENCH_IA.md --> <!-- STATUS: Aligned with Founder Canon (31 August 2026) -->

SpineWorkspace — Human Workbench Information Architecture

Status: CANONICAL TARGET
Product: SpineWorkspace
Surface: Human Workbench
Foundation: Business Context Spine (THE semantic foundation)

1. Purpose

The Human Workbench is the user's operational surface for understanding, deciding on and progressing Work.

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.

It is a projection over shared Business Context.

It is not:

  • a departmental database;
  • a second source of truth;
  • an integration console;
  • an AI chat shell.

The Tier-0 Principle

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.

2. IA model

SPINEWORKSPACE HUMAN WORKBENCH
│
├── ORIENTATION
│   ├── Home
│   ├── Today
│   ├── My Work
│   ├── My Queue
│   ├── Tasks
│   └── Recent Work
│
├── COMMUNICATION
│   ├── Email
│   ├── Chat
│   ├── Calendar
│   ├── Meetings
│   ├── Calls
│   └── Shared Documents
│
├── ORGANIZATIONAL MEMORY
│   ├── Knowledge
│   ├── Decisions
│   ├── Documents
│   ├── Policies
│   ├── Processes
│   ├── Meeting Memory
│   └── Work History
│
├── WORK
│   ├── Active
│   ├── Waiting
│   ├── Needs Decision
│   ├── Needs Approval
│   ├── Delegated
│   ├── Blocked
│   ├── Escalated
│   └── Completed
│
├── BUSINESS DOMAINS
│   ├── Sales
│   ├── Marketing
│   ├── Account Success
│   ├── Technical Account Success
│   ├── Finance
│   ├── RevOps
│   └── Organization-specific domains
│
└── WORK SURFACE
    ├── Tables
    ├── Boards
    ├── Canvas
    ├── Timeline
    ├── Entity View
    ├── Workflow View
    └── Document / Knowledge View

3. Main interaction model

The Workbench is action-oriented at the top and context-rich underneath.

USER SEES WORK
 ↓
CURRENT STATE
 ↓
CONTEXT
 ↓
WHAT CHANGED
 ↓
WHAT NEEDS ATTENTION
 ↓
WHAT THE TWIN RECOMMENDS
 ↓
WHAT THE HUMAN MUST DECIDE
 ↓
WHAT HAPPENS NEXT

4. Adaptive projection

Organization
× Role
× Domain
× Responsibility
× Authority
× Permissions
× Current Work
× Business Context
× Policy
× User Preferences
        ↓
Projection
        ↓
Human Workbench

The same underlying organization can produce different projections for different users.

5. Workbench operating semantics

The Workbench supports these semantics without requiring fixed buttons:

  • Store — retain governed information in the appropriate context/memory scope.
  • Ask — ask the Twin for context, analysis or recommendation.
  • Decide — make a human decision.
  • Approve — authorize a governed consequential action.
  • Reject — refuse a proposal.
  • Redirect — change the objective/constraints.
  • Consult — communicate with another human.
  • Delegate — transfer Work through the governed assignment layer.
  • Verify — inspect the actual outcome.
  • Continue — advance the Work after reconciliation.

6. Context Drawer / active context

The Workbench may expose:

Entity
Current State
Related Work
Relevant History
Communications
Decisions
Evidence
Policies
Risks
Dependencies
Twin Context

These are projections. The Workbench does not become the owner of those records.

7. Adaptive boundary

Automatically adaptive:

  • view order;
  • density;
  • prefetch;
  • notification ranking;
  • capability placement;
  • personal shortcuts.

Governed:

  • canonical truth;
  • shared schema;
  • authority;
  • permissions;
  • policies;
  • governance thresholds;
  • organizational memory publication;
  • external side effects.

8. Human/Twin surface relationship

                 SHARED WORK
                     │
          ┌──────────┴──────────┐
          │                     │
   HUMAN WORKBENCH        TWIN WORKBENCH
          │                     │
     Human judgment        AI coordination
     Human authority       Delegation
     Relationship          Execution
     Approval              Monitoring
     Accountability        Reporting

The surfaces are complementary, not competing.

9. Acceptance criteria

A Workbench implementation is aligned when:

  1. it projects shared Spine state rather than creating a departmental copy;
  2. active context is assembled around Work;
  3. role/domain/responsibility/authority affect projection;
  4. AI receives sandbox context rather than canonical access;
  5. consequential actions require the governance path;
  6. communications remain linked to Work;
  7. source-system outcomes return through reconciliation;
  8. published Organizational Memory is clearly distinct from pending candidates.