Runner · Request context & routing

Job submission

Route an admitted operation to exactly one supported worker and return a durable job identity or a named refusal.

Workflow

1. Receive admitted requestRouting starts only after request and policy evidence exist.
2. Resolve operation handlerSelect the handler from the operation name without broad fallback.
3. Return routing refusalUnsupported operations and incompatible payloads produce a named refusal without creating a job.
4. Create or reuse durable jobThe handler creates or reuses the operation job according to its idempotency contract.
5. Return job receiptReturn the durable identity and explicit queued/running state for later progress and control.

Failure boundaries

• Unknown operationRefused: Do not create job
• Same key changed payloadConflict refusal: Use new key or original payload
• Receipt without observable jobRouting defect: Do not report submitted

runner.route.submit