OpenEXA Request access

Nothing settles that didn’t pass.

The Execution Council checks every proposal against your policy.

Try changing a record

Schematic
01The ledger

Change one record and every link after it fails.

Any state can be replayed with the inputs that produced it, by an operator, an auditor or a regulator.

Lifecycle 01 · IBIT · create Chain intact
  1. #4f1aPROPOSEDstrategy s-0412 · create 2,600
  2. #4f1bREJECTEDcouncil · notional cap exceeded
  3. #4f1cPROPOSEDstrategy s-0412 · create 2,000
  4. #4f1dVALIDATEDschema ✓ policy ✓ caps ✓ hours ✓
  5. #4f1eAPPROVEDcouncil · auto-with-approval · op-02
  6. #4f1fSUBMITTEDexec e-0088 · venue=dark
  7. #4f20PARTIAL1,400 / 2,000
  8. #4f21FILLED2,000 / 2,000
  9. #4f22RECONCILEDinternal ≡ broker · Δ 0
Illustrative · Real SHA-256, computed in your browser
02Control plane

Limits are enforced below the boundary.

Applied in the deterministic execution layer, before an action exists, not in the agent that proposed it.

  1. Instruments & venues

  2. Position & notional caps

  3. Market-hours gates

  4. Who signs

  5. Emergency halt

  6. Positions, NAV, fills, decisions

03Custody

Assets stay with your broker.

They remain in your brokerage account. Agents act through scoped permissions, revocable per agent, and can never withdraw.

04Plain language

What the agents do not do.

  • They do not promise guaranteed returns.
  • They do not hide decisions inside a model.
  • They do not act outside the mode you set.

Review this with your compliance team.

Request access The platform