{"slug":"internal/architecture/CAPABILITY_EXECUTION_EVIDENCE_MATRIX_2026-08-13","title":"Capability Execution Evidence Matrix — 2026-08-13","section":"internal","sectionLabel":"Internal","status":"unclassified","type":"document","path":"internal/architecture/CAPABILITY_EXECUTION_EVIDENCE_MATRIX_2026-08-13.mdx","bytes":5125,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Evidence inventory for v2.2 integration.  \n**Rule:** A declarative `CapabilityRef` is not a claim that a provider action is live.\n\n## Required proof chain\n\n```text\nSpine/context eligibility\n→ connector + schema validation\n→ tenant/principal policy decision\n→ optional dry-run / scoped approval\n→ bounded handler\n→ receipt + audit/evidence\n→ reconciliation and projection refresh\n```\n\nThe integration branch must mark a capability **bound** only when the complete chain is evidenced in source and focused tests. Otherwise it remains **declaration-only**.\n\n## Priority inventory\n\n| Priority | Capability / contract             | Current source evidence                                                                                            | Handler-to-reconciliation evidence                                                                                              | Status                                  | Integration action                                                                            |\n| -------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | --------------------------------------------------------------------------------------------- |\n| P0       | `sales.deal.create`               | v2.2 `packages/workbenches/src/sales/capabilities.ts`; provider binding `crm.opportunity.create`; policy `allowed` | No matching binding/handler reference found in the source inspection.                                                           | declaration-only                        | Do not market as live; add adapter contract/test only when a real connector path is selected. |\n| P0       | `sales.deal.close`                | Same Sales manifest; `approval_required`                                                                           | No matching provider handler or scoped-approval-to-receipt flow found for this declaration.                                     | declaration-only                        | Highest candidate for an approval/reconciliation proof once a real bounded handler exists.    |\n| P0       | `sales.quote.generate`            | Sales manifest; `approval_required`; `cpq.quote.create`                                                            | No matching CPQ handler reference found.                                                                                        | declaration-only                        | Retain as product inventory only.                                                             |\n| P0       | contextual proposal / approval    | Existing contracts reference `twin.propose` and `human.approve` in `packages/contracts/src/surfaces/chat.ts`.      | Requires a live route/handler and outcome reconciliation test before execution claim.                                           | contract-present, runtime proof pending | Use as the first testable governed flow if the existing handler chain is verified.            |\n| P1       | MCP capability binding            | Platform MCP client types and v2.2 Product Package contract describe tenant bindings/grants.                       | The incoming diff primarily modifies existing MCP code; no complete live binding-to-action proof was established by this audit. | contract-present, runtime proof pending | Verify one actual MCP server/binding path without external credentials before claims.         |\n| P1       | Workbench capability availability | v2.2 projection contract requires phase, connector, tenant policy and RBAC gating.                                 | Domain capability files are declarative; no end-to-end registry resolution proof was found in the new package.                  | declaration-only                        | Add a deterministic in-process eligibility test against the real registry when selected.      |\n\n## Test program order\n\n1. Run the already-present entry-host parser and Gateway CORS tests after the isolated-worktree dependency installation is complete.\n2. Identify one existing non-mutating or dry-run capability handler with no external account requirement.\n3. Add an end-to-end contract test that supplies tenant/context/connector capability inputs and proves: ineligible denial; dry-run has no side effect; approval-required cannot execute without a scoped artifact; receipt/audit is written; reconciliation is required before projection refresh.\n4. Add one MCP binding test that proves a binding/grant is context-scoped and cannot transfer provider credentials.\n\n## Non-claims\n\n- No provider endpoint is invented or exercised by this evidence matrix.\n- No external account, credential, or production action is required for the proposed tests.\n- “Capability-first” means first-class product and contract treatment; it does not mean every listed action has a proven live handler today.\n"}