{"slug":"architecture/L1_WORKBENCH","title":"L1 WORKBENCH","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/L1_WORKBENCH.mdx","bytes":4184,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Canonical Reference:** [CANONICAL_PLATFORM_ARCHITECTURE.md](../architecture/CANONICAL_PLATFORM_ARCHITECTURE.md)  \n> _This document is downstream of the canonical architecture. Refer to the canonical source for current truth._\n\nStatus: CURRENT\nScope: Human product grammar, surface doctrine, Context Lenses\nCanonical Owner: Product\nLast Verified: 2026-07-11\nEvidence Basis: docs/CANON.md, docs/architecture/PRODUCT_ARCHITECTURE.md, docs/architecture/WORKBENCH_DOCTRINE.md, docs/platform-specs/03-workspace-runtime.md, Option B evidence\nSupersedes: none\nSuperseded By: none\n\n---\n\n## 1. PRODUCT TARGET: ONE L1 WORKBENCH\n\nThe human product is a single L1 Workbench.\n\nThe human does not leave L1. Intelligence is a silent partner inside L1. Governance appears when policy requires it.\n\n```text\nL1 OPERATIONAL WORKBENCH\n```\n\n---\n\n## 2. PRODUCT GRAMMAR\n\n```text\nCONTEXT LENS\n→ ENTITY COLLECTION\n→ ENTITY 360\n→ ACTIVITY\n→ CONTEXTUAL INTELLIGENCE\n→ ACTION\n→ GOVERNANCE WHEN REQUIRED\n→ EXECUTION STATE\n→ CONTINUITY\n```\n\nThis is the operating grammar. All human operational interaction resolves through this sequence or a contextual subset.\n\nL2/L3 are not separate screens. They are panel states inside L1.\n\n---\n\n## 3. CONTEXT LENS DOCTRINE\n\n```text\nSAME ENTITY\n+\nDIFFERENT CONTEXT LENS\n=\nDIFFERENT OPERATIONAL EMPHASIS\n```\n\nContext Lenses are roles, departments, industries, and capability clusters applied to the same underlying entity.\n\nExamples:\n\n- Account Success lens\n- Finance lens\n- BizOps lens\n- IT Administration lens\n\nNone of these lenses is automatically a separate product boundary. Each is a projection unless separate product evidence authorizes otherwise.\n\nDepartment surfaces seen in repository code/docs should be documented as Context Lenses unless a repo-check proves product boundary necessity.\n\n---\n\n## 4. TWIN INSIDE L1\n\nTwin is not a separate product interface.\n\n```text\n┌──────────────────────────────────────────────────────────────────┐\n│                      FOUR-BUTTON OODA GRAMMAR                   │\n├──────────────────────────────────────────────────────────────────┤\n│ OBSERVE  → STORE IN SPINE        (persist truth to Spine)      │\n│ ORIENT   → ASK YOUR TWIN         (query Twin for insight)      │\n│ DECIDE   → ASSIGN YOUR TWIN      (delegate to Twin for plan)   │\n│ ACT      → APPROVE TWIN'S ACTION (human approval gates exec)   │\n└──────────────────────────────────────────────────────────────────┘\n```\n\nTwin never gets a direct Act button. Every consequential execution is gated by human approval.\n\nNo pop-ups, no chat window, no “How can I help?” greeting.\n\n---\n\n## 5. REUSABLE PRODUCT GRAMMAR\n\nCanonical reference patterns from current corpus:\n\n- Leads and Lead Detail surfaces provide the strongest known entity collection and entity 360 grammar reference. They demonstrate canonical interaction patterns without implying CRM product scope.\n\n- Entity Collection grammar: filterable, sortable, role/content-lens-aware view of operational entities.\n\n- Entity 360 grammar: single entity continuation view with activity, intelligence, action, governance, execution state, and continuity.\n\n- Activity grammar: continuation markers, unresolved state, prior decision awareness, model/context continuation.\n\n- Intelligence grammar: contextual, not modal. Appears inline when policy, entity state, or user action asks for it.\n\n- Action grammar: propose, govern, execute, remember.\n\n---\n\n## 6. WHAT L1 IS NOT\n\n```text\nL1 ≠ CRM\nL1 ≠ Chat\nL1 ≠ Dashboard\nL1 ≠ Admin shell\nL1 ≠ Department portal\nL1 ≠ L2 chat drawer\nL1 ≠ Twin portal\nL1 ≠ Report builder\n```\n\nL1 is the operational work surface governed by continuity. It projects capability and continues operational memory.\n"}