Reef orchestration
Architecture boundary
Keep orchestration, policy and product authority distinct
A reliable agent system has three explicit authorities: the product, Reef and Router.
Product authority
The product authenticates the end user, authorizes data and owns side effects. It decides which records, tools and actions the workflow may access.
Reef authority
Reef manages workflow steps, tool dispatch, state, stop conditions and recovery. It does not receive upstream provider credentials.
Router authority
Router validates the workspace service identity, applies governance and dispatches only to eligible provider routes. It does not own agent memory or product content.
Correlate without merging stores
Pass non-sensitive run and request correlation IDs so operators can join evidence. Do not copy prompts, outputs or product records into Router audit solely for convenience.
