sample - Haia Trace

haia-trace sample [template]

Replays a bundled fixture run through the real assembler. It is build with the events coming from a file that ships with the CLI instead of from a capture — nothing is mocked, and nothing is written to disk.

Arguments and options

Argument / option	Meaning
`[template]`	Template to sample, which also selects its fixture set. Default: `x402-buyer`.
`--dir <path>`	Root holding `events/`, `receipts/` and `templates/`. Default: `.trace`.
`--templates-dir <path>`	Where your own templates live. Overrides `--dir`. Default: `<dir>/templates/`.

All four shipped templates have a fixture set: x402-buyer, x402-seller, x402-facilitator and escrow-arc.

Example

haia-trace sample

Sampling x402-buyer · 3 operations from bundled fixtures

🧾 x402-buyer · op-1 · FULL

  ✔ challenge   confirmed
  ✔ payment     confirmed
  ✔ settlement  confirmed

  operation completed

  ────────────────────────────
🧾 x402-buyer · op-2 · PARTIAL

  ✔ challenge   confirmed
  ✔ payment     confirmed
  ✖ settlement  not confirmed  required

  missing
    settlement — the payment was submitted, but no settlement response was observed

  operation not complete

  ────────────────────────────
🧾 x402-buyer · op-3 · PARTIAL

  ✔ challenge   confirmed
  ✔ payment     confirmed
  ✖ settlement  not confirmed  required

  exceptions
    ⚠ x402.settle.failed

  missing
    settlement — the payment was submitted, but no settlement response was observed

  operation not complete

Each x402 fixture set holds three operations, so one command shows the whole model. Note the difference between op-2 and op-3: the same unclosed milestone, but op-2 is simply unobserved, while op-3 carries an observed fault — the server reported that settlement failed. sample escrow-arc shows a longer operation — and four of them, because an escrow has two ways to end. Its first two are both FULL: one released to the provider after the work was delivered and evaluated, one refunded to the client with the deal called off before either happened.

🧾 escrow-arc · 0x7e5c1a000000000000000000000000000000000001 · FULL

  ✔ agreement    confirmed
  ✔ deposit      confirmed
  ✔ delivery     confirmed
  ✔ criteria     confirmed
  ✖ review       not confirmed  optional
  ✔ disposition  confirmed

  operation completed

  ────────────────────────────
🧾 escrow-arc · 0x7e5c1a000000000000000000000000000000000002 · FULL

  ✔ agreement    confirmed
  ✔ deposit      confirmed
  ✖ delivery     not confirmed  optional
  ✖ criteria     not confirmed  optional
  ✖ review       not confirmed  optional
  ✔ disposition  confirmed

  operation completed

FULL there means resolved, not succeeded: both closings leave no money in limbo, so delivery and criteria are optional — the refund path never reaches them and must not read as incomplete for it. Which closing happened is on the receipt regardless, in the event that closed disposition. The third operation is the one that is limbo — funds locked and then nothing:

🧾 escrow-arc · 0x7e5c1a000000000000000000000000000000000003 · PARTIAL

  ✔ agreement    confirmed
  ✔ deposit      confirmed
  ✖ delivery     not confirmed  optional
  ✖ criteria     not confirmed  optional
  ✖ review       not confirmed  optional
  ✖ disposition  not confirmed  required

  missing
    disposition — neither a release nor a refund was observed — nothing shows the escrowed funds were settled either way

  operation not complete

The fourth is a funding attempt that failed on chain: agreement closed, deposit never did, and circle.transaction.outbound.failed is on the receipt as an exception.

Which template you are seeing

The template is resolved exactly as build resolves it — your own .trace/templates/ first, the shipped set second — so a name means the same file in both commands. Editing .trace/templates/x402-buyer.yaml changes what you sample, and sample then prints the path it loaded:

Sampling x402-buyer · 3 operations from bundled fixtures

  template: .trace/templates/x402-buyer.yaml

That is also why --dir and --templates-dir exist here: they have to reach the same file build would. Only the events are always built-in. A template with no bundled fixture set — one of your own, say — has nothing to replay, and says so rather than showing an empty run:

error: no sample fixtures for template: my-op

What the stages, gaps and faults above mean is the Operation Receipt model.

​Arguments and options

​Example

​Which template you are seeing

Arguments and options

Example

Which template you are seeing