{"slug":"docs/canonical/03-HUMAN-WORKBENCH-AND-PERSONAL-MEMORY","title":"03 — Human Workbench and Personal Contextual Memory","section":"docs","sectionLabel":"Docs","status":"unclassified","type":"document","path":"docs/canonical/03-HUMAN-WORKBENCH-AND-PERSONAL-MEMORY.md","bytes":4292,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Canonical reference:** `00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md` §7, §4.2  \n**Status:** Canonical\n\n---\n\n## 1. Human Workbench definition\n\nThe Human Workbench is the primary daily product surface inside SpineWorkspace. It is not a dashboard, a database UI, a role-specific isolated SaaS app, or a chatbot with integrations.\n\nThe Workbench composes the fields, records, relationships, knowledge, evidence, communications, work, capabilities, approvals and Twin context relevant to the user's role and active situation.\n\n**The Workbench 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\n## 2. Stable shell, adaptive work\n\nNavigation stays stable enough to be learnable. The work surface adapts.\n\nA representative information architecture:\n\n- **Home**\n- **My Work:** Inbox, Tasks, Queue, Approvals, Notifications, Recent, Favorites\n- **Communications:** Activity, Email, Calendar, Meetings, Chat, Calls, Shared Documents\n- **Personal:** Notes, Personal Knowledge, Brainstorming, Activity and permitted personal utilities\n- **Work:** adaptive role/department/lifecycle projections\n- **Platform/Administration** for authorized operators only\n\nThe platform should adapt visibility, default routes, views, fields, actions and capabilities without making the global product taxonomy unstable.\n\n## 3. Self-organizing Workbench\n\nSelf-organization is a technical composition rule, not a marketing metaphor.\n\n```text\nEffective Human Workbench\n= Mandatory Workbench Standard\n+ Business Context Projection\n+ Personal Contextual Memory\n+ Role and Responsibility\n+ Department and Industry Context\n+ Active Lifecycle and Current Work\n+ Connected Data Coverage\n+ Knowledge and Evidence\n+ Available Capabilities\n+ Governance and Entitlements\n+ User Preferences\n+ Freshness and Readiness\n```\n\nThe user should not have to create every database, design every view, map every tool, build every dashboard or repeatedly explain the same context to AI.\n\n## 4. Tables, views, pages and operational surfaces\n\nSpineWorkspace can expose multiple form factors over the same context:\n\n- **Tables** for structured operational data\n- **Views** for filtered, grouped and role-routed lenses\n- **Pages/Docs** for narrative, planning, linked context and evidence\n- **Boards** for state and lifecycle\n- **Queues** for action-ready work\n- **Calendar/Timeline** for time projections\n- **Canvas** for free-form operational composition\n- **Entity 360-style projections** for cross-system business objects\n- **Twin** for contextual reasoning and preparation\n\nThe form factor does not own truth. The projection contract does.\n\n## 5. Human Active Context\n\n```text\nHuman Active Context\n= Business Context Projection\n+ Personal Contextual Memory\n+ Current Work\n+ Current Interaction Context\n+ Authorized Knowledge/Evidence\n+ Policy\n+ Capabilities\n```\n\n## 6. Personal Contextual Memory\n\n**Personal Contextual Memory belongs to the human's working context, subject to enterprise privacy, compliance and retention policy.** It exists because a human carries important continuity that should not automatically become company truth.\n\nExamples: personal notes, drafts, reminders, priorities, bookmarks, private working knowledge, what the user was investigating, unfinished thoughts, personal task ordering, preferences, recurring work patterns and context the user wants available across sessions.\n\nPersonal Contextual Memory is private by default. Sharing or promoting an item into organizational memory is an explicit governed transition, not an automatic side effect of writing a note.\n\n### Constitutional rule\n\n```text\nPersonal Contextual Memory\n≠ Organizational Truth\n```\n\nA personal note remains personal unless deliberately promoted through the appropriate governance path.\n\n## 7. Adaptive boundary\n\nAutomatically adaptive: view order, density, prefetch, notification ranking, capability placement, personal shortcuts.\n\nGoverned: canonical truth, shared schema, authority, permissions, policies, governance thresholds, organizational memory publication, external side effects.\n"}