{"slug":"architecture/HUMAN_WORKBENCH","title":"Human Workbench","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/HUMAN_WORKBENCH.mdx","bytes":5756,"description":"One workspace for all human work — the single surface where every person does their job","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n\n**One Workspace for All Human Work.**\n\nThe Human Workbench is the single surface where every person in the organization does their job. No context switching between apps. No juggling between tools. One workspace, tailored to each role.\n\n## Design Principles\n\n1. **One surface** — Every person has one place to work\n2. **Role projection** — The workbench projects differently per role\n3. **Domain awareness** — Surfaces adapt to the business domain\n4. **KPI visibility** — Key metrics are always in view\n5. **Zero friction** — Work flows through, not around, the workspace\n\n---\n\n## Navigation Structure\n\n### Primary Sidebar\n\n| Section | Icon | Purpose |\n|---------|------|---------|\n| **My Work** | 📋 | Personal work items and priorities |\n| **My Queue** | 📥 | Ordered work waiting for attention |\n| **Today** | 📅 | Today's focus, timeline, and priorities |\n| **Alerts** | 🔔 | Notifications requiring attention |\n| **Approvals** | ✅ | Items awaiting human approval |\n| **Decisions** | ⚖️ | Decisions requiring human judgment |\n| **Reports & KPIs** | 📊 | Analytics and performance metrics |\n| **Settings** | ⚙️ | Configuration and preferences |\n\n### Work Surface Tabs\n\n| Tab | Purpose |\n|-----|---------|\n| **Orientation** | Context and situational awareness — what's happening, what matters |\n| **Work** | Active work items, tasks, and assignments |\n| **Communications** | All conversations, messages, and updates |\n| **Organizations** | Company, customer, and partner context |\n| **Knowledge / Memory** | Organizational knowledge base and learnings |\n| **Domain Work Surfaces** | Role-specific deep-dive views |\n\n---\n\n## Domain Work Surfaces\n\nEach role gets a tailored view of the work surface. The domain work surface is a projection of the Spine filtered to the user's role, permissions, and current context.\n\n### Sales\n\n| Surface | Contents |\n|---------|----------|\n| **Pipeline** | Active deals, stages, probability |\n| **Opportunities** | Qualified opportunities, next actions |\n| **Forecasts** | Revenue forecasts, projections |\n\n### Account Success\n\n| Surface | Contents |\n|---------|----------|\n| **Health** | Customer health scores, trends |\n| **Renewals** | Upcoming renewals, risk assessment |\n| **Expansion** | Upsell and cross-sell opportunities |\n\n### Finance\n\n| Surface | Contents |\n|---------|----------|\n| **Revenue** | Revenue recognition, accruals |\n| **Billing** | Invoice status, payment tracking |\n| **Collections** | Outstanding balances, follow-ups |\n\n### Support\n\n| Surface | Contents |\n|---------|----------|\n| **Tickets** | Open tickets, priority, SLA status |\n| **SLAs** | Service level compliance |\n| **Escalations** | Escalated issues, resolution paths |\n\n### Operations\n\n| Surface | Contents |\n|---------|----------|\n| **Projects** | Active projects, milestones |\n| **Tasks** | Task assignments, deadlines |\n| **Workflows** | Process status, bottlenecks |\n\n### Custom Views\n\nRole-specific and domain-specific projections built from the Spine. Users can create, save, and share custom work surfaces.\n\n---\n\n## Business KPI / Health Overview\n\nThe workbench surfaces key metrics at a glance, drawn from the Spine's canonical data:\n\n| Metric | Description | Example |\n|--------|-------------|---------|\n| **Revenue** | Total recognized revenue | $8.4M (+12%) |\n| **Pipeline** | Total pipeline value | $27.6M (+8%) |\n| **Revenue at Risk** | Revenue at risk of churn | $1.2M (+15%) |\n| **Customer Health** | Aggregate health score | 76 (+4 pts) |\n| **Open Work** | Total open work items | 128 (+2) |\n| **SLA Risk** | Items at risk of SLA breach | 5 (View all KPIs →) |\n\n### KPI Rules\n\n- KPIs are computed from the Spine, not cached or stale\n- Each KPI links to the underlying data for drill-down\n- KPIs are role-scoped — each role sees their relevant metrics\n- Trend indicators show direction and magnitude\n\n---\n\n## Work Flow\n\nEvery piece of work in the Human Workbench follows this flow:\n\n```\nIncoming → Orientation → Assessment → Action → Reconciliation → Memory\n```\n\n1. **Incoming** — Work arrives via integration, communication, or system event\n2. **Orientation** — User understands the context and priority\n3. **Assessment** — User evaluates options (optionally with Twin assistance)\n4. **Action** — User takes action (with or without Twin suggestion)\n5. **Reconciliation** — Outcome is verified and recorded\n6. **Memory** — Learning feeds back into the Spine\n\n---\n\n## Interaction with Twin\n\nThe Human Workbench and Twin Workbench are two views of the same work:\n\n- The Human Workbench shows the **human's view** of work\n- The Twin Workbench shows the **AI's view** of the same work\n- Both read from and write to the same Spine\n- The Four Buttons control the interaction:\n  - **Store in Spine** — Capture truth\n  - **Ask your Twin** — Understand the work\n  - **Assign your Twin** — Delegate intent\n  - **Approve Twin's Action** — Authorize execution\n\n---\n\n## Data Sources\n\nThe Human Workbench reads from:\n\n| Source | Data |\n|--------|------|\n| **Spine Fabric** | Canonical business context, entities, work graph |\n| **Communications Layer** | Messages, emails, meetings |\n| **Bridge Layer** | External system data |\n| **KPI Engine** | Computed metrics and health scores |\n| **Memory Store** | Organizational knowledge and learnings |\n\nThe Human Workbench writes to:\n\n| Target | Data |\n|--------|------|\n| **Spine Fabric** | Work updates, decisions, context |\n| **Communications Layer** | Messages, responses |\n| **Governance Layer** | Approval requests |\n| **Execution Fabric** | Work initiation |\n"}