Shared dependency graph

The configuration checks a first agent, one shared peer, a communication probe and a router. Run compatible handlers on localhost ports 8080–8082, then run:

agenthealth check examples/graph-check/agenthealth.yaml --format json

The first agent handler must implement the agent interface, including an explicitly safe probe that contacts the selected peer. The router endpoint supplies a read-only HTTP health signal. See the graph guide for policies, budgets and evidence semantics.

Kubernetes compatibility

Mount this graph only after replacing localhost addresses and reviewing its active communication probe. Shared-node execution and independent edge policies remain unchanged. See deployment scenarios and the deployment guide.

Configuration files

agenthealth.yaml

version: v1
concurrency: 4
targets:
  - id: first
    name: Research Agent
    type: agent
    endpoint: http://localhost:8080/health
    budget_ms: 3000
    dependencies:
      - ref: peer
        relationship: downstream
      - ref: first-peer-path
        relationship: path
      - ref: router
        relationship: router
  - id: peer
    name: Search Agent
    type: agent
    endpoint: http://localhost:8081/health
  - id: first-peer-path
    name: Search communication
    type: agent
    endpoint: http://localhost:8080/health
    checks: [configuration, functional]
    agent:
      functional:
        safe: true
        text: Return a fixed health acknowledgement from the search peer.
        downstream: Search Agent
  - id: router
    name: Router
    type: router
    endpoint: http://localhost:8082/health
    dependencies:
      - ref: peer
        relationship: downstream
        critical: false