Reef orchestration
Reef
Agent execution above a governed Router boundary
Reef is the orchestration layer for multi-step work. Octoryn Router remains the policy enforcement point for every model request; the two systems integrate over an explicit API boundary.
Responsibilities
Reef decides what happens next, owns workflow state and calls tools. Router authenticates the workload, evaluates policy, selects an eligible provider, enforces budget and records content-free evidence.
Why they remain separate
Agent state, product databases, Documents, Media, Memory and Knowledge do not move into Router. Router does not import Reef or product code.
Use capability-stable routes
Bind a workflow to policy aliases whose approved providers preserve required tools, structured outputs, modalities, context and region.
Start with a governed call
Give the Reef workload a scoped Router service identity and pass safe correlation metadata. Keep product user authorization in the product boundary.