{"slug":"implementation/testing-verification","title":"31 · Testing & Verification","section":"implementation","sectionLabel":"Implementation","status":"unclassified","type":"document","path":"implementation/testing-verification.mdx","bytes":1969,"description":"How the platform's execution, reconciliation, agent, memory, and projection behavior is tested — unit, contract, integration, runtime, end-to-end.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## What Is Tested\n\n| Level | Covers |\n|---|---|\n| **Unit** | Canonical ontology, normalizer, authority resolver, Work state machine |\n| **Contract** | Loader/normalizer/pipeline/governed-writer, capability, projection, governance verdict shapes |\n| **Integration** | Connector → pipeline → Spine, Capability Fabric → Governance → Hermes, re-ingest path |\n| **Runtime** | Wiring (live vs orphaned — G-07), Model routing / ADK, MCP Pool routing boundary |\n| **Execution** | Plan → approval → Hermes → evidence for happy, denied, and failure paths |\n| **Reconciliation** | Expected vs observed mismatch, partial success, stale-read retries, compensation |\n| **Agent** | Twin and Spine Agent Work ownership, handoff, evidence, continuity |\n| **Memory** | Promotion boundaries (personal/AI → organizational), G-10 substrate behavior |\n| **Projection** | Active Context Bundle assembly, scoping, invalidation, rehydration |\n| **End-to-end** | Business Intent → Context → Work → Govern → Execute → Verify → Spine → Rehydrate under real tenant isolation |\n\n\nVerification and reconciliation are **logic**, not optimism. They are tested against mismatches and partial successes, not just happy paths.\n\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    Why provider success alone is not the E2E assertion.\n  \n  \n    What every test asserts against.\n  \n  \n    How production confirms what tests predicted.\n  \n</CardGroup>\n"}