{"slug":"platform/capability-fabric-view","title":"15 · Capability Fabric View","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/capability-fabric-view.mdx","bytes":3270,"description":"What can be done? Capability catalogue, resolution, metadata, MCP, native capabilities, ADK, external capabilities, and availability.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## What Can Be Done?\n\nThe Capability Fabric is the **provider-neutral catalogue of what the system can do** — the answer to *what can be done?* before governance answers *may it be done?* and Hermes answers *execute it*.\n\n```text\n             Discovery + Activation\n                     │\n                     ▼\n           CAPABILITY FABRIC\n        ─────────────────────────\n        Catalogue · Metadata\n        Resolution · ADK · MCP\n        Native + External\n                     │\n            ┌────────┴────────┐\n            ▼                 ▼\n     Twin / Agents       Governance\n      (propose)        (may it be done?)\n                           │\n                           ▼\n                        Hermes\n```\n\n\nCapabilities are **provider-neutral**. `UpdateRenewalRisk` is a capability; `PATCH /salesforce/opportunity/{id}` is a route. The Fabric resolves the former to the latter only when active and authorized.\n\n\n## What Lives in the Fabric\n\n* **Capability catalogue** — the full set of active capabilities for a tenant/runtime/Work context.\n* **Capability metadata** — contracts, inputs/outputs, required authority, evidence shape, side-effect class.\n* **Resolution** — maps a capability name to one or more execution routes (native, MCP-routed, ADK-resolved).\n* **MCP** — governed tool/context surface exposed to AI, routed through the MCP Pool.\n* **ADK** — agent development kit path for agent-authored capabilities.\n* **Native + external** — first-party capabilities and those contributed via ecosystems/Marketplace.\n* **Availability** — not every capability is available everywhere; Discovery + Activation + tenancy + Work context determine visibility.\n\n## Resolution Is Contextual\n\nA capability resolves differently depending on:\n\n* Which ecosystems are connected and authorized for this tenant\n* Which routes are active for this Work type\n* Which identity is requesting (user, Twin, agent — with what authority)\n\nThat is why planning happens **after** context assembly and **before** governance — the plan's capabilities are already contextual.\n\n## Fabric ≠ Governance ≠ Hermes\n\n```text\nCapability Fabric          Governance                Hermes\n \"What can be done?\"  →  \"May it be done?\"  →  \"Execute it.\"\n  catalogue +           policy + approval       authorized\n  resolution            → authorization          execution\n```\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    How the plan is approved or denied before anything executes.\n  \n  \n    How the authorized plan is executed with evidence.\n  \n  \n    What makes a capability exist and become active here.\n  \n</CardGroup>\n"}