Unclassified

15 · Capability Fabric View

What can be done? Capability catalogue, resolution, metadata, MCP, native capabilities, ADK, external capabilities, and availability.

What Can Be Done?

The 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.

             Discovery + Activation
                     │
                     ▼
           CAPABILITY FABRIC
        ─────────────────────────
        Catalogue · Metadata
        Resolution · ADK · MCP
        Native + External
                     │
            ┌────────┴────────┐
            ▼                 ▼
     Twin / Agents       Governance
      (propose)        (may it be done?)
                           │
                           ▼
                        Hermes

Capabilities 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.

What Lives in the Fabric

  • Capability catalogue — the full set of active capabilities for a tenant/runtime/Work context.
  • Capability metadata — contracts, inputs/outputs, required authority, evidence shape, side-effect class.
  • Resolution — maps a capability name to one or more execution routes (native, MCP-routed, ADK-resolved).
  • MCP — governed tool/context surface exposed to AI, routed through the MCP Pool.
  • ADK — agent development kit path for agent-authored capabilities.
  • Native + external — first-party capabilities and those contributed via ecosystems/Marketplace.
  • Availability — not every capability is available everywhere; Discovery + Activation + tenancy + Work context determine visibility.

Resolution Is Contextual

A capability resolves differently depending on:

  • Which ecosystems are connected and authorized for this tenant
  • Which routes are active for this Work type
  • Which identity is requesting (user, Twin, agent — with what authority)

That is why planning happens after context assembly and before governance — the plan's capabilities are already contextual.

Fabric ≠ Governance ≠ Hermes

Capability Fabric          Governance                Hermes
 "What can be done?"  →  "May it be done?"  →  "Execute it."
  catalogue +           policy + approval       authorized
  resolution            → authorization          execution

Where to Go Next

<CardGroup cols={2}> 
How the plan is approved or denied before anything executes.


How the authorized plan is executed with evidence.


What makes a capability exist and become active here.
</CardGroup>