11 / Additional projectIndependent project · Josh Fuller

StableTrace.

A payment deserves more context
than a transaction hash.

StableTrace is a provider-neutral payment-observability prototype. It compares what was expected with incoming evidence, builds a trace, and brings exceptions to a human operator.

Kind
Operations / data workflows
Platforms
Web · private
Stage
Private MVP · simulation only
Evidence
Existing interface captures · synthetic simulations
01 / Follow the evidenceSynthetic simulation · Demo mode

Expected and actual, side by side.

An existing simulation trace connects a synthetic intent, the events observed and the lifecycle transitions, so the timeline preserves how the state was reached.

Existing StableTrace Demo mode screen with synthetic expected-versus-actual values and the evidence timeline.
A payment trace · underpayment past the grace periodSynthetic data · existing captureView full capture (opens in a new tab)
  • Demo mode · Simulation tools are enabled — payment data here is synthetic and can be reset.

    Every recorded screen carries the banner.

  • Expected vs actual

    The business record is kept apart from the incoming transaction evidence.

  • Timeline · Lifecycle: Confirmed → Completed

    The state is computed from recorded events, and the timeline keeps the route it took.

  • Matched via Explicit intent id · Certain

    A match says how it was made and how certain it is.

02 / An exception to reviewA separate duplicate-payment simulation

The facts beside the decision.

A separate simulation raises an exception. The screen sets out the facts, then a recommendation marked as requiring human approval.

Existing StableTrace Demo mode exception screen showing a synthetic duplicate-payment event, facts and a human-approval requirement.
Exceptions · possible duplicate paymentSynthetic data · existing captureView full capture (opens in a new tab)
  • Possible duplicate payment: 100 USDC received again

    The exception names what happened in plain words.

  • Do not send or pay again, and verify carefully before considering any refund.

    Its guidance errs on the side of caution.

  • Recommended action · Certain · Requires human approval

    A recommendation arrives with its confidence and the approval it needs.

03 / Rehearsed, not liveExisting development screenshot · synthetic data

Fixed scenarios, stated outcomes.

The simulation lab runs deterministic scenarios through the full pipeline with synthetic data. Each scenario states the result it expects before it runs.

Detail. StableTrace’s actual simulation lab, explicitly labeled Demo mode with synthetic payment scenarios.
Simulation lab · top of the recorded frameSynthetic data · date and build unknownView full capture (opens in a new tab)

Settlement

  • Happy path settlement
  • Refund amount mismatch
  • Off-ramp payout held

Amount

  • Partial payment inside the grace period
  • Underpayment past the grace period
  • Top-up clears an underpayment
  • Single transfer overpayment

One considered decision

The operator decides; the trace explains.

Recommended actions stay tied to the facts that produced them. Recording an approval is deliberately separate from executing a transfer.

Where it stands

  • StagePrivate MVP · simulation only
  • MoneyIt never takes custody or moves money; an approval records an operator decision.
  • ReadinessNot audited, load-tested or intended for production money operations.

About the evidence

Retained development captures with the product’s Demo mode banner. All payment data is synthetic. Exact capture dates and builds are unknown; these were not freshly executed. This private prototype is not offered for production money operations and never moves funds.

Let’s make
something useful.

Bring the idea you’ve been turning over. We’ll find a clear place to begin.

Start a project