Skip to content

Synthetic proof, with its limits attached.

This rehearsal uses invented data against the local intake fixture. It is not a client result, availability claim, external-provider test, or live production monitor.

Evidence class
Studio-owned synthetic demonstration
Schema 1 · local fixture only
Generated 2026-10-05T22:24:29.000Z

Durable intake

HTTP 201

TT-A5105FE06B54 was returned only after the synthetic record committed.

Idempotent retry

HTTP 200

duplicate: true and same_reference: true. The retry did not create a second record.

Malformed input

HTTP 422

The fixture returned validation and did not produce a success receipt.

Notification retry

retry 1

synthetic_downstream_unavailable failed once. The owned-file fixture later delivered 2 queued notifications. No external provider was called.

Workflow incident recovery

failed → passed

A owned_intake_e2e check opened an incident when loopback HTTP was unavailable. A later HTTP commit matched the durable database record and recovered that same incident. Evidence references: loopback HTTP unavailable, loopback HTTP commit matched.

What this rehearsal proves—and what it does not.

The published values come from the regenerated local fixture artifact. They demonstrate the intake and recovery mechanism with owned synthetic data; they do not establish production availability or third-party delivery.

Exercised

Durable commit, an idempotent retry, malformed input rejection, one injected notification failure with owned-file retry, and recovery of one workflow-check incident through the loopback HTTP and durable database path.

Limitations

  • No customer data.
  • No external provider call.
  • No production runtime or delivery claim.

Download the sanitized JSON evidence

See the existing proof archive · Read provenance-labeled field notes · Browse reference work and sample outputs