{"slug":"spineworkspace/workspace-experience","title":"03 · Workspace Experience View","section":"spineworkspace","sectionLabel":"SpineWorkspace","status":"unclassified","type":"document","path":"spineworkspace/workspace-experience.mdx","bytes":5553,"description":"What the human actually experiences. The architecture disappears behind the experience — Human Workbench, projections, work, communication, decisions, and approvals.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## The Architecture Disappears Behind the Experience\n\nThe human does not experience \"the Spine\" or \"Hermes\" or \"the four flows.\" They experience **a workspace that already knows their business**.\n\n\nThe Human Workbench and AI Workbench are **two projections over the same business reality**. The user never has to reconstruct context for the AI. Both workbenches rehydrate from the same verified Spine.\n\n\n```text\n                 BUSINESS CONTEXT SPINE\n                          │\n              ┌───────────┴───────────┐\n              ▼                       ▼\n        HUMAN PROJECTION        AI PROJECTION\n              │                       │\n              ▼                       ▼\n       HUMAN WORKBENCH          AI WORKBENCH\n              │                       │\n        Personal Memory          AI Continuity\n              │                       │\n              └───────────┬───────────┘\n                          ▼\n                     SHARED WORK\n```\n\n## What the Human Actually Sees\n\n| Surface | What it is | Business Context question it answers |\n|---|---|---|\n| **Navigation** | Tenant-aware workspace shell | Where am I in the business? |\n| **Contextual surfaces** | Account, opportunity, case, person, work surfaces | What is this business entity and its current truth? |\n| **Projections** | Participant-specific views of the same Spine | What should *I* see of the business reality? |\n| **Active Context** | The bundle the UI and AI both hydrate from | What context is active for this work right now? |\n| **Work** | The list, board, and detail of Work | What needs to happen, who owns it, what is next? |\n| **Communication** | Threads, handoffs, agent updates | What was said in the context of this Work? |\n| **Decisions** | Approvals, denials, delegations | What was decided, by whom, under what authority? |\n| **Notifications** | Governed signals, not noise | What needs my attention that I am authorized to act on? |\n| **Search / discovery** | Business-aware retrieval | What does the organization know that is relevant here? |\n\nEvery surface is a **projection** — a governed rendering of the Spine for a participant (human, Twin, agent) in a Work context.\n\n## Human Workbench\n\nThe primary daily product. The human works from governed business context with continuity.\n\n* **Identity-bound** — every view is scoped to user, role, tenant, and authority.\n* **Context-assembled** — the Workbench hydrates from the Spine, not from raw SaaS APIs.\n* **Continuity-preserving** — Personal Contextual Memory carries what the human needs across sessions without silently becoming organizational truth.\n* **Governance-aware** — actions that mutate the outside world route through approval and authorization.\n\n## How a Task Feels\n\n\n  \n    The Workbench already shows Shared Work involving this person, team, or account — ranked by relevance, not manual triage.\n  \n  \n    The surface assembles account, history, related Work, decisions, and evidence — no SaaS-hopping.\n  \n  \n    Twin is present in the Workbench as the AI coworker. A Spine Agent can take a subtask with its own identity and continuity — the human never re-explains the business.\n  \n  \n    Governance surfaces what is allowed, what needs approval, and who can grant it.\n  \n  \n    Hermes executes the authorized plan, the outcome is re-ingested and verified, the Spine updates, and the Workbench rehydrates — the next person continues from new truth.\n  \n\n\n## Active Context Bundle\n\nThe Workbench and the AI Workbench hydrate from the same **Active Context Bundle**:\n\n* **Business Context** slice — the relevant entities, relationships, and state\n* **Work** — the Work object, its objective, and its current state\n* **Evidence** — what has already been proven to have happened\n* **Authority** — what this participant may do in this context\n* **Continuity** — personal or AI working memory relevant to this Work\n\nThis is why handoff is cheap: the next participant does not need a new briefing.\n\n## What Is Not Shown\n\n* Raw pipeline internals, four-flow routing, or normalization logs\n* Unverified provider payloads\n* AI private reasoning traces beyond what is governed and auditable\n* Cross-tenant or unauthorized slices of the Spine\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    Who does what — human responsibility vs AI assistance, Twin vs agent.\n  \n  \n    How one business reality becomes different participant projections.\n  \n  \n    Work as the common unit that both workbenches coordinate through.\n  \n  \n    How Work moves from intent to verified Spine update.\n  \n</CardGroup>\n"}