Skip to content

Add a pre-action risk gate pattern before order placement #3

Description

@aion-blue-labs

Hi — small suggestion for the skill docs.

The current skill does a good job teaching agents how to authenticate, read markets, stream data and place orders. One pattern that may be worth documenting explicitly is a pre-action risk gate immediately before order placement.

The shape I mean:

market data / strategy signal
        ↓
pre-action gate
        ↓
READY / CAUTION / DO_NOT_ACT / INSUFFICIENT_EVIDENCE
        ↓
place order only if policy allows

This is not about predicting prices. It is about preventing an agent from moving capital when a market/action is not executable under the agent's own policy.

Examples of checks that can live in this gate:

  • market/resolution/dispute status;
  • requested size vs public book depth;
  • max slippage policy;
  • stale or missing book data;
  • ambiguous market state;
  • whether the agent has enough evidence to act.

Suggested docs addition:

  • a short pre-action-guards.md or section in order-patterns.md;
  • a minimal pseudocode example:
verdict = risk_gate.check(
    market_id=market_id,
    side=side,
    notional_usd=notional_usd,
    max_slippage_bps=150,
)

if verdict.decision in ("DO_NOT_ACT", "INSUFFICIENT_EVIDENCE"):
    return {"skipped": True, "reason": verdict.reason_codes}

if verdict.decision == "CAUTION":
    notional_usd = min(notional_usd, verdict.safe_operating_limits.max_notional_usd)

# only then create/post the order

The useful invariant for agents is:

every capital-moving call should have a machine-readable decision immediately before it, and the agent should log the evidence/receipt it used.

I can draft a small docs PR if this pattern fits the repo's direction.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions