Canon

09 — Capability Fabric and ADK

Canonical reference: 00-SPINEWORKSPACE-INTEGRATEWISE-CANON.md §18
Status: Canonical

1. Capability Fabric

Capability Fabric is the provider-neutral execution language between intent and implementation.

A user or Twin should think in business capabilities such as prepare_renewal, schedule_review, update_project_state or send_followup, not in raw provider endpoints.

2. Capability resolution routes

Capability Fabric resolves how authorized intent can be performed through route families including:

  • tool-to-tool
  • memory fetch
  • MCP
  • agent-to-agent
  • API connector
  • API wrapper/function
  • local execution
  • AI execution
  • browser, workflow or human execution where needed

3. Capability contract

Every executable capability declares: version, input/output schema, authority scope, risk, execution mode, sync mode, idempotency, evidence requirements, provider routes, health, timeout, retry, compensation and verification behavior.

4. Responsibility split

Twin / Workbench      = what the user is trying to achieve
Capability Discovery  = what executable options exist
Capability Fabric     = how it could be done
Governance            = whether it may be done and under whose authority
Hermes                = how approved execution is coordinated reliably
Reconciliation        = whether reality actually changed as intended

5. Capability Discovery

Discovery identifies available capabilities from: connectors, MCP servers, agents, workflows, APIs and platform services. Discovery is read-only; it does not authorize execution.