What Flows just did
Based on your request to build Test Every User Path, Flows created 5 implementation stages and 15 checks.
You asked for: Map all user paths, execute each with variations, and fix everything that fails.. Flows generated 5 stages because the application requires A complete user-path map (happy, alternate, error paths); Executed tests with recorded results per path; Edge and error variations per path. Each stage tells your AI builder what to do, tests whether it actually worked, and gives a repair instruction when it fails. These checks are designed to catch: Testing only the happy path; Skipping logged-out/fresh-account perspectives; Marking paths passed from code reading.
Example failure
The form reported success, but no database record was created.
What Flows does
Flows detects the failure, generates a repair instruction, reruns the test, and stores the passing evidence.
Stages — Plan → Build → Test → Fix → Prove → Ship
5 stages · 15 checks · progressive disclosure — open a stage for details
Copy to external builder
Copies a prompt for Claude/Cursor/etc. Records prompt_copied only — not execution, commits, or checks.
Execute through Oort
Requires Sign in with Oort + a provider connection (BYOK). Keys stay on Oort. A model name in the dropdown is not the same as a live connection.
Next
Check off: All personas/states covered
Add a proof note on each check — a checkbox alone is weak proof.
Probes & advanced tools are under “More verification tools”. Experience level: Settings.
Project (saved with proof)
Project binding: Unbound — complete project binding before trusting this run · missing repositoryUrl, repositoryStartCommit, environment, stack
More verification tools (probes, timeline, adapters)Show
App persistence (create → read → assert token)
Body template: {"probe":"{{token}}","title":"flows-probe-{{token}}"}. Needs CORS-readable public create/list endpoints (or inconclusive). Badge only when create→read→refresh finds the token (detects false success).
Two-account authorization (User B cannot see/change User A)
Authorization evidence source: Cross-account ownership test (trust level 5/6). These are not equivalent. Unauthenticated probe alone is weaker (source: unauthenticated API probe). Tokens stay in this browser session only — not uploaded to Flows servers.
Generated edge-case tests (review / approve)
- api_probe Submitting the form empty is rejected with a clear error
- api_probe Each required field can be omitted and fails validation
- api_probe Malformed email is rejected
- api_probe Malformed phone is rejected when phone is collected
- api_probe Duplicate submission does not create two records
- api_probe Double-click submit creates only one record
- false_success_probe Failed request does not show success
- browser_automation Refresh during submission does not leave corrupt state
- api_probe Oversized input is rejected
- api_probe Unsafe strings do not execute or break storage
Generated from this route’s signals — you approve; you do not invent security tests.
Content probe (GET body contains text)
In-product content probe reads response text when CORS allows — not full DOM/click automation. Playwright script is optional and external.
Proof strength
thin · 0/100
Heuristic from notes + probes + gates — not a production certification.
Verification adapters
- ● Deploy URL probe · idle
- ● API path probe · idle
- ● Authz probe (unauth → 401/403) · idle
- ● Browser persistence · idle
- ● App persistence (create→read) · idle
- ● Content / body text probe · idle
- ○ In-product Playwright DOM · not embedded (download external script)
Filled circles = available here. Empty = not shipped. Probes are not a production audit. Adapter docs
Step 1 of 5
Not startedMap every user path
You test what you have mapped - build the complete path inventory.
Flows keeps plan, checks, failures, and next steps connected
Your AI tool writes or changes the code
Repository grounds the plan only after inspect
Checks always carry a validation tier
How this plan was created
Plan from project details
Flows creates steps using the goal, requirements, stack, platform, and details you provide.
- Project description
- Selected template / route
- User-entered stack
- Constraints and notes
- Test Every User Path
No repository inspection implied. Connect and inspect a codebase to ground steps in real files.
Codebase access
Checking GitHub…
Or paste a repository URL manually
Use these instructions in Claude, ChatGPT, Cursor, Emergent, or another builder.
Map every user path in this app. Produce a table organized by persona/state (new visitor, logged-out, new user, returning user, admin if exists): each path as a numbered sequence of actions (e.g. 'land on home -> search X -> open result -> start action -> complete'). Include: all happy paths, alternate paths (back buttons, cancels, edits), and error paths (invalid input, missing data, unauthorized access). Number every path for tracking.
Project context
Copies the project goal, technical details, current step, previous progress, and checks so your AI tool understands what it is working on.
Expected after this step
A numbered inventory of happy, alternate, and error paths per persona.
Should not happen
- ✕Testing only the happy path
- ✕Skipping logged-out/fresh-account perspectives
- ✕Marking paths passed from code reading
- ✕Fixing bugs without re-running the failed path
Verify gate — prove this step works before continuing
Do not move on until every check is true. Add proof notes — a checked box alone is weak proof. Checks are manual by default; deploy/API probes live under “More verification tools” and do not auto-check boxes.
Do not continue if…
- !Testing only the happy path
- !Skipping logged-out/fresh-account perspectives
- !Marking paths passed from code reading
- !Fixing bugs without re-running the failed path
Repair path — if this step fails
Use the Repair Prompt when a verify gate fails. Loop: Detected → Diagnosed → Repair issued → Changed → Retested → Resolved
Show repair prompt textShow
The map only lists happy paths. Add for every feature: the cancel/back variation, the invalid-input variation, and the wrong-state variation (logged-out, empty account).
Your notes for this step
Definition of Done
Final route-level requirements. Manual checks — separate from per-step verify gates. Completing step gates does not auto-check these. Route completion is not a production-ready claim.