cap: Documentation
Browse Sign In

Integration Recipes

Implementation-backed request and execution patterns

Recipe: End-to-End Runtime Request

  1. Host/runtime handshake establishes limits.
  2. Client sends REQ with cap URN.
  3. Input streams arrive via STREAM_START/CHUNK/STREAM_END.
  4. Plugin returns output stream(s) and END.

Failure path: invalid frames or routing mismatches produce ERR and terminate request flow.

Recipe: Graph Execution (Macino)

  • Build execution DAG from cap graph.
  • Run independent branches in parallel where possible.
  • Fan-in nodes wait for all upstream dependencies.
  • Cycle detection rejects invalid graphs before execution.

Recipe: Missing Capability

If no cap accepts the request URN, registry/host returns an explicit no-handler error.

Test Anchors