What Flows just did
Based on your request to build Build a Functional Coffee Shop Website, Flows created 9 implementation stages and 44 checks.
You asked for: Create a responsive, multi-section coffee shop website with real navigation, complete content structure, working interactions, and a functional contact form.. Flows generated 9 stages because the application requires Create a homepage with hero section, brand message, and clear call-to-action; Add a menu section with at least 3 categories and multiple items per category; Display business hours, address, and contact information clearly. 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: AI generates a pretty landing page with no real content depth beyond the hero section; Form UI is created but submission, validation, or feedback states do not actually work; Navigation links point to missing sections or dead anchors.
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
9 stages · 44 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: Header navigation is visible
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
- api_probe Create then refresh still shows the record
- api_probe Edit then refresh keeps the edit
- api_probe Delete then refresh removes the record
- api_probe Nonexistent record ID fails cleanly
- cross_account_probe Cross-user record identifier is rejected
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 9
Not startedDefine the coffee shop website structure
Establish the full page structure, content sections, and functional scope before building.
This prevents the builder from generating only a stylish hero page with missing business sections.
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
- Build a Functional Coffee Shop Website
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.
Create a complete coffee shop website structure for a local cafe. Include these sections: header navigation, hero, about/story, featured drinks, full menu with categories, hours, location, contact form, and footer. Use realistic coffee shop sample content, not lorem ipsum. Set up real section IDs for navigation. Make sure the content hierarchy is clear and suitable for mobile and desktop.
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 complete site skeleton exists with all major sections and realistic starter content.
Should not happen
- ✕AI generates a pretty landing page with no real content depth beyond the hero section
- ✕Form UI is created but submission, validation, or feedback states do not actually work
- ✕Navigation links point to missing sections or dead anchors
- ✕Menu cards look good visually but contain repetitive placeholder items
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…
- !AI generates a pretty landing page with no real content depth beyond the hero section
- !Form UI is created but submission, validation, or feedback states do not actually work
- !Navigation links point to missing sections or dead anchors
- !Menu cards look good visually but contain repetitive placeholder items
- !Responsive layout breaks on small screens or overlapping text appears
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
You created an incomplete landing page. Expand it into a full coffee shop website with these real sections: header, hero, about, menu, hours, location, contact form, and footer. Replace placeholder content with realistic cafe content and ensure every nav link points to an actual section ID.
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.