17 · Hermes Execution View

Execute What Has Been Authorized

Hermes is the execution plane. It answers: execute what has been authorized.

Capability Fabric
       ↓
 "What can be done?"
       ↓
   Governance
       ↓
 "May it be done?" → Verdict: allow
       ↓
     Hermes
       ↓
 "Execute it."  →  Provider / External System
       ↓
  Outcome + Evidence
       ↓
  Verify → Reconcile → Spine

Hermes does not decide authority. It executes only authorized plans and returns outcome + evidence. Replacing Hermes changes how work is executed, not whether it is allowed.

Important Separation

Capability Fabric          Governance                Hermes
 "What can be done?"  →  "May it be done?"  →  "Execute it."
   ADK / MCP               Policy /               Provider
  resolution               Approval               execution

• Capability Fabric resolves provider-neutral capabilities to routes.
• Governance approves or denies the plan for this identity, Work, and Business Context.
• Hermes executes the approved plan against the external system and captures the result as evidence.

What Hermes Captures

• Outcome — what the provider returned (success, error, partial).
• Evidence — durable receipts for audit, verification, and reconciliation.
• Trace — linkage back to Work, governance verdict, capability, and identity.

Hermes success is not closure. Closure requires re-ingest, verification, reconciliation, and governed Spine update.

Where to Go Next

<CardGroup cols={2}>

Why the system is not finished when the API returns success.


How outcomes are verified and what becomes Spine truth.


Where Hermes sits in the end-to-end Work pipeline.

</CardGroup>