One flow
Create an agent task → tool call fails → founder reviews retained work → accepts, rejects or exports → release handoff is recorded.
The report shape a founder receives after scope, evidence and payment are accepted.
This inspectable example freezes one agent-product flow, separates observations from unknowns, ranks five small actions and shows how the single factual correction round closes.
1 flowfrozen review boundary
4 inputsfictional/redacted evidence register
5 findingsprioritised observations, not verdicts
1 roundfactual correction, not new scope
Wholly fictional composite: FlowPilot is not a real customer or product. Every screenshot, version, event and observation below is invented to demonstrate the paid deliverable. This is not a testimonial, security assessment, production finding or launch guarantee.
Accepted review brief
The work is useful because the boundary is narrow enough to finish and inspect—not because it claims to audit an entire product.
One decision
Is the fictional recovery-and-acceptance path clear enough to include in the first founder-led beta demo?
Included
Up to five observations, evidence state, priority, smallest next action and one factual correction round.
Excluded
Private repository access, production testing, secret handling, penetration testing, compliance advice, fixes and launch approval.
Frozen evidence register
This register is the source boundary for the report. A later build, new screen or undocumented production behavior is not silently treated as reviewed evidence.
| ID | Fixture | Observed version | State | Permitted use |
|---|---|---|---|---|
| E-01 | Public landing-page copy | Fictional capture · 22 Aug | fixture | Promise and first-evaluator language only |
| E-02 | Redacted 96-second demo | Fictional build FP-0822 | observed | Visible task, failure and review states |
| E-03 | Recovery-state screenshot | Fictional build FP-0822 | observed | Displayed copy and controls only |
| E-04 | Release handoff note | Fictional Markdown fixture | partial | Named owner and checklist; no production execution claim |
Delivered: five prioritised observations
Each item states what the fictional fixture shows, what remains unknown and the smallest action that would improve the named beta-demo path.
Priority 1 · demo blockerRecovery state
The interruption screen offers “Continue” before it explains what work is retained.
Fixture evidence
E-02 ends on a tool rejection; E-03 shows “Run interrupted” with one Continue button. Neither fixture names saved draft files, logs or the last completed step.
Unknown
Actual persistence, retry semantics and data durability were not tested and remain unknown.
Smallest next action: add a retained-state summary before the action buttons: last completed step, saved artifacts, timestamp and one explicit “what continuing does” sentence.
Priority 2 · decision boundaryHuman acceptance
“Apply result” does not make the founder’s acceptance criteria visible.
Fixture evidence
E-02 shows three changed files and an Apply result control. The fixture does not show tests run/not run, expected behavior, owner or reject reason before apply.
Unknown
No claim is made about whether the fictional backend validates, isolates or safely applies changes.
Smallest next action: place four fields above Accept / Edit / Reject: intended outcome, changed files, tests run/not run and named decision owner.
Priority 3 · cost clarityUsage boundary
The retry choice appears before the fictional evaluator can see whether it starts new usage.
Fixture evidence
E-03 labels the primary action Continue. The accepted materials contain no confirmed fictional billing rule for retries or resumed runs.
Unknown
Price, metering and provider cost behavior remain outside the supplied evidence.
Smallest next action: if the real rule is confirmed, place the exact usage consequence beside Resume. Until then, use neutral copy and link to the authoritative usage policy rather than inventing “free retry” language.
Priority 4 · handoffRelease ownership
The workflow reaches “ready” without naming who owns the separate release step.
Fixture evidence
E-04 contains a release checklist but its owner field is blank. E-02 ends after result acceptance and does not show a distinct merge/deploy handoff.
Unknown
No deployment, rollback or production-access path was reviewed.
Smallest next action: end the demo with a handoff receipt: accepted by, release owner, evidence attached and “not deployed” status. Keep merge/deploy visibly separate.
Priority 5 · promise alignmentLanding copy
The public promise says “stay in control,” while the demo does not yet show the control receipt.
Fixture evidence
E-01 uses the invented phrase “ship agent work while staying in control.” E-02 shows accept/reject controls but no final record of what was accepted, by whom and what remains unreleased.
Unknown
The review does not determine whether the product is safe, reliable or suitable for production use.
Smallest next action: add one final receipt screen to the demo. If that screen is not ready, narrow the landing claim to the exact review controls currently demonstrated.
Recommended action order
The report ends with an executable sequence, not a pile of feature requests.
Clarify interruption
Add retained-state and retry consequence copy before expanding the demo.
Expose acceptance
Show evidence, decision owner and explicit Accept / Edit / Reject choices.
Close with a receipt
Record accepted work and preserve a separate, named release handoff.
One factual correction round
A correction fixes a misunderstanding against the frozen evidence. It does not add another flow, a new build or implementation work.
Fictional founder correction
Observation: #4
Request: E-04 does name a release owner in the document metadata,
although the visible checklist field is blank.
Evidence reference: E-04 metadata line 3.
Accepted correction: observation #4 is revised to say the visible handoff does not expose the owner; the frozen metadata does name one. Priority and next action remain unchanged. Correction round status: closed.
Would be separately scoped: reviewing a new build, testing production behavior, adding a second flow, validating a fix or changing the product.
Delivery close-out
Delivered
- Accepted-flow restatement
- Frozen evidence register
- Five prioritised observations
- Three-step action order
- One factual correction round
Not claimed
- No production test or repository review
- No defect, security or compliance verdict
- No fix implementation or retest
- No launch, conversion or revenue guarantee
- No customer result—this example is fictional
Start free; inspect the paid boundary before paying.
Send one public or founder-redacted flow for a free three-observation pass. If it is useful, the A$149 scope, evidence register and decision question are confirmed in writing before payment.