This page explains the strongest current product path after a run already exists:
keep the evidence bundle, use recovery before guesswork, and build one review-ready packet before you widen handoff or promotion.
That is where ProofTrail feels different from a pile of browser scripts or a single replay log.
You already have a retained run, and now the real question is no longer “did it run?” but:
If you do not have a retained run yet, go back first:
ProofTrail does not stop at “the automation ran.”
It keeps three layers attached to the same run:
Evidence tells you what happened and whether the retained run is still strong enough to inspect.
Use it to answer:
retained, partial, missing, or empty?Start here:
Recovery tells you what to do next when the run is blocked, incomplete, or failed.
Use it to answer:
Continue here:
The review workspace packages the run into one maintainer-facing packet.
Use it when you need one place that can carry:
Continue here:
If one retained run is already selected, use this order:
That order matters because it keeps promotion downstream of evidence and review instead of turning it into the first button you click.
If you want the shortest mental model, treat it like an evidence ladder:
The current repo ships a local-first review packet, not a hosted review product.
The packet is useful because it brings together the exact things a maintainer usually has to gather by hand:
| Packet part | Why it matters |
|---|---|
| retained run detail | anchors the packet to one specific evidence run |
| failure explanation | gives the first grounded reading before raw logs |
| share pack | turns the reading into a handoff-friendly summary |
| compare context | strengthens judgment when a baseline run helps |
| promotion guidance | stays last, after the packet is already explainable |
That matches the current API shape described here:
This loop is useful when:
This is also why the page belongs in the outward matrix. It is not a vague “operations concept.” It is one of the strongest current proofs that the repo keeps evidence, judgment, and handoff connected.
Use the current public matrix in this order:
If you only need the shortest evidence-and-handoff route, use this tighter path:
This page does not claim:
It only claims the bounded current repo reality: