Skip to main content
SuperformOS Intent History - read-only strategy execution ledger Intent History is the operator-facing execution explorer for Strategy and OMS activity. Use it to answer: what strategy fired, where the intent is in the lifecycle, what filled, what transaction mined, and why execution failed.

​
What it shows

ViewUse it for
Intent listSearch and filter intents across vaults and strategies.
FacetsCount by state, action, chain, vault, and strategy.
Lifecycle stripSee the current OMS lifecycle state and timestamps.
Fills tableInspect per-fill venue, token in/out, amounts, gas, fees, and fill time.
OMS eventsAudit message type, sequence, payload, and source.
Signal snapshotSee the Strategy Engine signal context that produced the intent.

​
Lifecycle states

The explorer uses the OMS lifecycle vocabulary: RECEIVED, ACKED, STAGED, PLANNED, EXECUTING, COMPLETED, ABORTED, EXPIRED, FAILED, CANCELED, and UNKNOWN for rows that cannot be normalized.

​
How it maps to OMS

The Strategy Engine projects OMS events and backfills into strategy_intent_log. Each row can include:
  • intent_id, execution_id, correlation_id
  • strategy and vault IDs
  • last event sequence and message type
  • ack/executing/completed/terminal timestamps
  • error code and message
  • total amount in/out
  • total gas used
  • fills count
  • signal snapshot and summary
  • source: engine, nats, or backfill

​
API mapping

EndpointPurpose
GET /api/v1/intentsGlobal intent search.
GET /api/v1/intents/facetsFacet counts for filters.
GET /api/v1/intents/{intent_id}Intent detail.
GET /api/v1/intents/{intent_id}/fillsFills for one intent.
GET /api/v1/intents/{intent_id}/eventsOMS event audit rows.
GET /api/v1/fillsGlobal fill search.

​
Common reads

SymptomCheck
Intent never minedLook at EXECUTING events, hook transaction fields, and gas budget.
Intent completed with no visible position changeCheck fills and amount out fields; some fields can be null until OMS hydration completes.
Strategy appears blockedCheck emergency locks, kill switch, session-key readiness, and merkle proof availability.
Duplicate-looking rowsCompare intent_id, execution_id, and correlation_id; retries and backfills can share context.