What Flows just did
Based on your request to build Cross-Session Project State, Flows created 4 implementation stages and 12 checks.
You asked for: Build an externalized project-state system: a canonical state document maintained across sessions, with load, advance, and handoff protocols.. Flows generated 4 stages because the application requires A canonical PROJECT_STATE document: goal, milestones, current position, decisions, blockers; A session-start protocol loading state and orienting the agent; A session-end protocol advancing state with what changed. 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: Plans living in chat history, evaporating at session end; State documents that describe the past but not the current position and next action; Sessions editing state destructively so history and rationale vanish.
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
4 stages · 12 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 seven sections populated
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 Logged-out users cannot open protected pages
- api_probe Protected API rejects requests without credentials
- api_probe Expired session cannot mutate data
- browser_automation Logout in one tab invalidates mutations from another
- cross_account_probe User B cannot see or change User A’s data
- cross_account_probe Participant cannot call coach/admin endpoints
- cross_account_probe URL/body ID tampering cannot cross tenant boundary
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 4
Not startedDesign the project-state document
The document a stranger could continue from is the standard.
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
- Cross-Session Project State
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.
Design PROJECT_STATE.md. Sections: GOAL (the outcome, verbatim from the owner), MILESTONES (ordered, with status: done/active/pending and completion evidence for done ones), CURRENT POSITION (exactly where work stands: active milestone, last completed step, the very next action), DECISIONS (dated: decision, reason, alternatives rejected), BLOCKERS & RISKS (open issues with owner), WORKSPACE MAP (key files/dirs this project touches, one line each), CHANGELOG (dated deltas per session). Write the initial document for my actual project now, populating every section honestly - especially the next action, which must be executable as written.
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 populated PROJECT_STATE.md whose next action is executable as written.
Should not happen
- ✕Plans living in chat history, evaporating at session end
- ✕State documents that describe the past but not the current position and next action
- ✕Sessions editing state destructively so history and rationale vanish
- ✕State drifting from code reality until it misleads instead of orients
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…
- !Plans living in chat history, evaporating at session end
- !State documents that describe the past but not the current position and next action
- !Sessions editing state destructively so history and rationale vanish
- !State drifting from code reality until it misleads instead of orients
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
CURRENT POSITION is vague ('working on backend'). Rewrite to the resolution of a single next command or edit: a stranger with this doc should know exactly what to do in the first five minutes.
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.