- SDK gathers market, runtime, and portfolio state.
- Deterministic code ranks and rejects candidates.
- Agent SDK writes a bounded analyst note from the shortlist.
- Execution is a separate policy-gated call with explicit confirmation.
Quant gate first
tokenId into the execution plan. The same loop shape applies; only the venue identifier and compliance gates differ.
Agent note second
Policy-gated execution third
Production notes
- Never let the model pick an unbounded ticker universe.
- Keep execution out of the first read-only agent run.
- Use
allowedTickers,maxOrderCostCents,requireLimitPrice, andconfirmToken. - Use
allowedVenues,blockedJurisdictions, andrequireJurisdictionwhen the workflow can touch venue-specific compliance boundaries. - Persist the shortlist, model note, order request, and runtime status for audit.
Next steps
SDK execution guardrails
Runtime-first SDK execution pattern.
Stability and side effects
Contract side-effect and cost classes.