{"slug":"platform/platform-execution-view","title":"11 · Platform Execution View","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/platform-execution-view.mdx","bytes":3714,"description":"The IntegrateWise runtime — how the platform executes business work end-to-end: IW One Auth → Spine Network → Ecosystems → Capability → Governance → Hermes → Outcome → Re-ingest → Spine.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## How the Platform Executes Business Work\n\n```text\nIW One Auth\n      ↓\nIW Spine Network\n      ↓\nEcosystems\n      ↓\nDiscovery            (what exists / what is available?)\n      ↓\nActivation           (what should become active for this tenant/runtime/context?)\n      ↓\nCapability Fabric    (what can be done? — provider-neutral)\n      ↓\nGovernance           (may it be done? — policy → approval → authorization)\n      ↓\nHermes               (execute what has been authorized)\n      ↓\nExecution            (external system)\n      ↓\nOutcome + Evidence\n      ↓\nRe-ingestion         (Loader → Normalizer → Pipeline → Governed Writer)\n      ↓\nVerification         (expected vs observed)\n      ↓\nReconciliation       (resolve, decide what becomes truth)\n      ↓\nBusiness Context Spine\n      ↓\nProjection invalidation → Human + AI Workbench rehydrate\n```\n\n\n**No stage is optional for closure.** The pipeline answers *what can be done*, governance answers *may it be done*, Hermes answers *execute it* — but only verification → reconciliation → Spine turns outcome into truth.\n\n\n## Stage Responsibilities\n\n| Stage | Answers | Key contract |\n|---|---|---|\n| **IW One Auth** | Who is acting, in which tenant, with what identity? | [Identity & Authority](/platform/identity-authority-view) |\n| **Spine Network** | How does context travel across nodes/tenants? | Marketplace & network spec |\n| **Ecosystems** | Which external systems are connected, with what scopes? | [Ecosystem & Integration](/platform/ecosystem-integration-view) |\n| **Discovery** | What capabilities exist across ecosystems? | [Discovery & Activation](/platform/discovery-activation-view) |\n| **Activation** | What should become active for this org/runtime/context? | Same |\n| **Capability Fabric** | What can be done, provider-neutral? | [Capability Fabric](/platform/capability-fabric-view) |\n| **Governance** | May it be done, by whom, under which policy? | [Governance & Authority](/platform/governance-authority-view) |\n| **Hermes** | Execute the authorized plan and return evidence | [Hermes Execution](/platform/hermes-execution-view) |\n| **Outcome / Evidence** | What did the external system actually do? | Trace + receipts |\n| **Re-ingest / Verify / Reconcile** | Did reality change as expected? What becomes Spine truth? | [Closure](/closure/execution-closure) |\n\n## Why This Order Is Invariant\n\nDiscovery without activation exposes unavailable routes. Capability without governance executes without authority. Hermes without verification treats provider success as truth. The pipeline is a **governance and truth pipeline**, not just an integration bus.\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    IW One Auth — organizational, user, AI, and agent identity + tenancy + delegation.\n  \n  \n    Ecosystems, connectors, APIs, webhooks, MCP, and sync.\n  \n  \n    What exists vs what should become active — Bridge, Engine, Manager.\n  \n  \n    The Work-centric view of the same flow.\n  \n</CardGroup>\n"}