{"slug":"architecture/006-capability-fabric-executes-actions","title":"ADR-006: Capability Fabric Executes Actions","section":"architecture","sectionLabel":"Architecture","status":"unclassified","type":"document","path":"architecture/006-capability-fabric-executes-actions.mdx","bytes":1387,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Accepted  \n**Date:** 2026-07-21  \n**Deciders:** Nirmal (Founder)\n\n---\n\n## Context\n\nActions (create task, send email, update record) need a consistent execution path. If actions execute through ad-hoc service calls, governance and audit become impossible.\n\n## Decision\n\nThe **Capability Fabric** is the exclusive execution path for all workspace actions. When a user or Twin triggers an action, it flows through:\n\n1. Governance evaluation (allowed/approval_required/denied)\n2. Capability Fabric execution (tool routing, agent routing, MCP routing)\n3. Outcome written back to Spine by Loader Runtime\n\nCapabilities never mutate the Spine directly. They go through governed write paths.\n\n## Consequences\n\n- **Positive:** All actions are governance-evaluated and auditable. Single execution path.\n- **Negative:** Adds a routing layer for all actions. May introduce latency for simple operations.\n- **Mitigation:** Capability Fabric may prepare a low-latency execution plan for\n  low-risk actions, but execution still waits for an explicit human approval\n  token.\n\n## Evidence\n\n- `packages/projection-engine/src/evaluators/governance-evaluator.ts` — governance gate\n- `packages/projection-engine/src/resolvers/capability-resolver.ts` — capability resolution\n- `contracts/shared-workbench/v1.ts` — `actions`, `governance` fields\n"}