{"slug":"closure/execution-closure","title":"22 · Execution Closure","section":"closure","sectionLabel":"Closure","status":"unclassified","type":"document","path":"closure/execution-closure.mdx","bytes":2391,"description":"The system is not finished when an API returns success. Intent → Plan → Govern → Execute → Re-ingest → Verify → Reconcile → Spine → Rehydrate — the critical differentiator.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Not Finished When the API Returns Success\n\n```text\nIntent\n ↓\nPlan\n ↓\nGovern (may it be done? → approval → authorization)\n ↓\nExecute (Hermes → external system)\n ↓\nExternal Outcome\n ↓\nRe-ingest (Loader → Normalizer)\n ↓\nVerify (expected vs observed)\n ↓\nReconcile (resolve mismatch, decide what becomes truth)\n ↓\nUpdate Spine (governed write)\n ↓\nInvalidate / Refresh Projection\n ↓\nRehydrate (Human Workbench + AI Workbench)\n ↓\nContinue Work / Next Work\n```\n\n\n**Provider success is not completion.** A 200 from Salesforce is an *observed outcome*, not truth. The loop closes only after the outcome is re-ingested, verified, reconciled, and the Spine has been updated under governance.\n\n\n## Why This Matters\n\n* SaaS APIs lie, race, and partially succeed.\n* Work state diverges from reality if you trust the response body.\n* Audit collapses if you cannot reconstruct *expected vs observed* and *what was eventually promoted to truth*.\n\n## Verified Closure Checklist\n\n1. Outcome was re-ingested via the pipeline (provenance captured).\n2. Verification judged expected vs observed.\n3. Reconciliation resolved mismatch and chose the Spine update.\n4. Governed Writer updated the Business Context Spine.\n5. Projection invalidated; both workbenches rehydrated.\n6. Full chain is reconstructable via trace, approval, capability, execution, evidence, and reconciliation lineage.\n\nSee [Verification & Reconciliation](/closure/verification-reconciliation) for the stage detail and [Spine Architecture](/spine/spine-architecture) for what becomes THE memory.\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    Expected vs observed, evidence, mismatch, promotion, invalidation.\n  \n  \n    The Work-centric view of this closure flow.\n  \n  \n    Where Hermes sits in the end-to-end runtime.\n  \n</CardGroup>\n"}