Workflow overlay

CFD Trade Execution

Govern leveraged CFD trade requests with margin guardrails, exit controls, and broker-order execution checks.

Key
cfd_trade_execution
Version
cfd_trade_execution-v1
Rules
2
Domain
CFD_TRADE_EXECUTION

Rules, in the order the evaluator tries them

Highest priority first. The first rule whose conditions all hold decides; with none, the decision is a REVIEW.

  1. Evidence completeness gate

    priority 120

    evidence-required · CFD_TRADE_EXECUTION

    When
    • evidence.attachments < 1
    Then

    REQUEST_INFO → REVIEW · elevated · SLA 45 min

    Do not finalize high-consequence decisions without evidence.

  2. Owner and escalation accountability

    priority 100

    owner-accountability · CFD_TRADE_EXECUTION

    When
    • intake.owner exists
    Then

    REQUIRE_REVIEW → REVIEW · routine · SLA 60 min

    Every routed decision must have a named accountable owner.

Evaluate under it

Locally, with @decionis/mcp: the payload becomes the request's context, and its action the decision type. On the hosted protocol, once the bundle is stored for your organization, name vertical_pack, policy_version and require_exact_policy_version: true.

decionis_evaluate arguments

{ "policy_pack": "cfd_trade_execution", "payload": { "action": "<decision type>" } }

In a hosted evaluate-decision request

"vertical_pack": "cfd_trade_execution",
"policy_version": "cfd_trade_execution-v1",
"require_exact_policy_version": true

Workflow keys that resolve to this pack: cfd_trade_execution.

What its rules read

Every fact below comes from the request's context.

  • evidence.attachments
  • intake.owner

Signals it maps

  • decision_cycle_countcfd_trade_execution
  • escalation_ratiocfd_trade_execution
  • evidence_completeness_ratecfd_trade_execution