Runtime and routing

How a request moves from Hermes through routing to a provider

Runtime and routing How a request moves from Hermes through routing to a provider 01 / Request 02 / Routing 03 / Provider selection 04 / Execution Hermes Agent Core · prompt request · 01 / Request · origin Hermes Agent Core prompt request origin router · routes to providers · 02 / Routing · router router routes to providers router Groq · candidate · 03 / Provider selection · provider Groq candidate provider OpenCode Go · candidate · 03 / Provider selection · provider OpenCode Go candidate provider OpenRouter · candidate · 03 / Provider selection · provider OpenRouter candidate provider Hermes / AI · response · 04 / Execution · consumer Hermes / AI response consumer monitor-hub · observed runtime · 04 / Execution · observability monitor-hub observed runtime observability prompt request primary candidate route candidate candidate route candidate candidate route candidate response primary response primary response primary observes execution observability Legend primary data async batch

Durable provenance (canonical Markdown)

  • • 02-Systems/Hermes-Core.md
  • • 03-Machines/Laptop.md
  • • 03-Machines/PC.md
  • • AUTHORITY.md
  • • SYSTEM-MAP.md

Observed runtime (read-only, annotation only)

  • • service_cups: {'state': 'active'}
  • • service_gdm: {'state': 'active'}
  • • service_hermes_gateway: {'state': 'active'}
  • • x003: {'state': 'inactive'}
  • • service_hermes_gateway_ops: {'state': 'active'}
  • • service_hermes_laptop_tunnel: {'state': 'inactive'}
  • • service_monitor_agent: {'state': 'active'}
  • • service_monitor_hub: {'state': 'active'}
  • • service_networkmanager: {'state': 'active'}
  • • service_nvidia_persistenced: {'state': 'active'}