{"slug":"work/pipeline-view","title":"06 · Pipeline View","section":"work","sectionLabel":"Work","status":"unclassified","type":"document","path":"work/pipeline-view.mdx","bytes":4828,"description":"How Work moves through the system — Business Intent → Context Assembly → Work → Plan → Capability → Governance → Execution → Outcome → Verify → Spine. The most important technical/product view.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## How Work Moves\n\nThis is one of the most important technical/product views.\n\n```text\nBusiness Intent\n      ↓\nContext Assembly        (Spine → Projection → Active Context Bundle)\n      ↓\nWork                  (common unit, with objective + state)\n      ↓\nPlan                  (capability selection, sequencing)\n      ↓\nCapability Resolution (Capability Fabric: what can be done?)\n      ↓\nGovernance            (may it be done? policy → verdict)\n      ↓\nApproval / Authority  (human or delegated, scoped)\n      ↓\nExecution             (Hermes: execute what has been authorized)\n      ↓\nOutcome               (external system response + evidence)\n      ↓\nEvidence\n      ↓\nVerification          (expected vs observed)\n      ↓\nReconciliation        (resolve mismatch, decide what becomes truth)\n      ↓\nSpine / Memory / Projection\n      ↓\nRehydrate             (Human Workbench + AI Workbench invalidate & refresh)\n      ↓\nContinue Work / Next Work\n```\n\n\n**Execution is not closure.** Provider success is not completion. The loop closes only after verify → reconcile → governed Spine update → rehydration.\n\n\n## Stage by Stage\n\n\n  \n    The Spine projects a Business Context slice for the participant and Work. The UI and AI both hydrate from the **Active Context Bundle** (Business Context + Work + evidence + authority + continuity). No participant works from raw SaaS payloads.\n  \n  \n    Work carries objective, participants, state, and history. Agents take subtasks of Work, not free-floating tool calls. Handoffs transfer Work state and evidence, not transcripts.\n  \n  \n    The Capability Fabric resolves a provider-neutral capability to an available execution route (MCP, native, external). Availability is discovered and activated per tenant/runtime — see [Capability Fabric](/platform/capability-fabric-view) and [Discovery & Activation](/platform/discovery-activation-view).\n  \n  \n    Identity → Authority → Policy → Plan → Approval → Authorization → Evidence. Governance verdicts are durable and auditable. See [Governance & Authority](/platform/governance-authority-view).\n  \n  \n    Hermes executes only authorized plans. It does not decide authority. It returns outcome + evidence. See [Hermes Execution](/platform/hermes-execution-view).\n  \n  \n    Expected vs observed outcome, evidence capture, mismatch handling, and governed promotion to the Business Context Spine. Projection invalidation and workbench rehydration follow. See [Verification & Reconciliation](/closure/verification-reconciliation).\n  \n\n\n## Separation That Matters\n\n```text\nCapability Fabric          Governance                Hermes\n \"What can be done?\"  →  \"May it be done?\"  →  \"Execute it.\"\n       │                       │                      │\n   ADK / MCP               Policy /               Provider\n  resolution               Approval               execution\n```\n\nHermes does **not** become an authority of its own.\n\n## What Answers Where\n\n| Question | Answer lives in |\n|---|---|\n| What exists / what is available? | [Discovery & Activation](/platform/discovery-activation-view) |\n| What can be done? | [Capability Fabric](/platform/capability-fabric-view) |\n| May it be done? | [Governance](/platform/governance-authority-view) |\n| Execute it | [Hermes](/platform/hermes-execution-view) |\n| Did it become truth? | [Verification & Reconciliation](/closure/verification-reconciliation) |\n| How to see it? | [Projection & Context Assembly](/spine/projection-context-assembly) |\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    What happens when AI receives this Work.\n  \n  \n    The IntegrateWise runtime that runs this pipeline end-to-end.\n  \n  \n    The critical differentiator: why we don't close on provider success.\n  \n</CardGroup>\n"}