Choose exact runnable representations from signed Run Cards.

Callers provide only task, rig identity, runtime, context, quality, license constraints, and up to 16 opaque Run Card ids. Policy, executable state, receipts, source identity, files, runtime commands, and clock are loaded inside one bounded read-only PostgreSQL authority transaction. Returns no more than three exact-file recommendations and explicit exclusions.

Inputs. No path or query fields are required. The request body schema lists accepted fields and required values.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Write and protocol operations can have separate route-specific limits. Read Retry-After and retry_after_s when present; do not infer a write allowance from the public read budget.

Example setup. This example is not executed by documentation checks. Review the operation and obtain any required user consent before sending it. Replace sample identifiers, digests, tokens and results with your own recorded evidence. Report only runs or outcomes you observed. Read any license obligations before accepting them.