{"slug":"development/contracts/reconciliation","title":"Reconciliation & Operational Continuity","section":"development","sectionLabel":"Development","status":"unclassified","type":"document","path":"development/contracts/reconciliation.md","bytes":1017,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 27_RECONCILIATION_CONTINUITY.md -->\n\n# Reconciliation & Operational Continuity\n\n## Core rule\n\n> Execution is not completion until actual business state is reconciled.\n\n## Lifecycle\n\n```text\nIntent\n→ Execution\n→ Provider Receipt\n→ Actual External State\n→ Re-ingestion\n→ Comparison\n→ Reconciliation\n→ Outcome\n→ Continuity Update\n```\n\n## Reconciliation states\n\n```text\nConfirmed\nFailed\nUnknown\nDivergent\nPartially Complete\nPending Reconciliation\n```\n\n## Unknown-result rule\n\nDo not automatically retry consequential mutation when the external state is unknown.\n\nFirst reconcile.\n\n## Continuity update\n\nAfter reconciliation:\n\n- update Work;\n- update entity state;\n- update relationships if applicable;\n- refresh projections;\n- refresh Twin context;\n- capture evidence;\n- create memory candidate if material.\n\n## Knowledge evolution\n\n```text\nReconciled Outcome\n→ Interpretation\n→ Triage\n→ Governed Promotion\n→ Organizational Memory\n→ Future Context\n```\n"}