Inject one condition
Model a timeout, a delayed response, a 429, or a stale payload within an agreed fixture.
FlakeMap Trust Proof / Proposed module 03
Test the
interruption.
Change one tool condition and follow its consequence across retries and delayed responses. Isolate the point at which the candidate diverges.
SEED 104 / STOCK API
00:00Order lookup
00:04Timeout injected
00:06Retry → PO-204-A
00:12Late response → PO-204-B
Failing transition: second draft creation
DEMO — SYNTHETIC DATA
The question this module answers
Which transition changes the outcome?
- Input
- A stubbed tool call and selected fault
- Output
- An event timeline and failing transition
Follow event order
Distinguish a retry from the late original response; both can reach artifact creation.
Explain the failure
Link the changed transition to the duplicate draft instead of showing an unexplained red score.
Follow the proposed workflow
A visible path from
input to decision.
01
Select the tool transition
A stubbed tool call and selected fault
Proposed process / synthetic exampleModule boundaries
Useful evidence.
Honest limits.
Is Trust Proof live?
This module is available to explore in the synthetic demo. A first pilot would test one scoped module with approved fixtures.
What does the demo execute?
It selects deterministic stub fixtures and changes local mock states. It does not call models, write to tools, import customer traces, or modify CI.
How is value validated?
Compare with the existing eval gate and confirm a meaningful missed regression independently. A named engineering owner must commit a gate or fund a trial before expansion.
A smaller test. A clearer decision.
Start with the workflow
you can’t afford to guess.
Agree on one task criterion, an approved fixture, and a named engineering owner.
Request a replay study