What Flows just did
Based on your request to build Fluxo de inscrição funcional, Flows created 8 implementation stages and 40 checks.
You asked for: Entregar um fluxo de inscrição completo e funcional, do formulário ao armazenamento e confirmação, sem telas falsas nem interações apenas visuais.. Flows generated 8 stages because the application requires Criar página ou seção de inscrição com formulário visível e acessível; Coletar pelo menos nome e e-mail, com possibilidade de campos extras como telefone ou empresa; Validar campos obrigatórios no cliente e no servidor. 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: Criar um formulário bonito que não salva nada em backend real; Validar apenas no frontend e aceitar dados inválidos no servidor; Mostrar mensagem de sucesso fixa mesmo quando a gravação falha.
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
8 stages · 40 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: Existe lista explícita de campos com tipos e obr…
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 8
Not startedDefinir escopo e contrato de dados da inscrição
Estabelecer exatamente quais campos existem, quais são obrigatórios e como o backend deve receber e armazenar a inscrição.
Se o builder começar a criar UI antes de definir payload, peça primeiro o contrato de dados e regras de validação.
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
- Fluxo de inscrição funcional
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.
Quero construir um fluxo de inscrição funcional em uma aplicação web. Antes de gerar interface, defina o contrato de dados completo da inscrição com: campos do formulário, tipos, obrigatoriedade, regras de validação, estratégia de deduplicação por e-mail, timestamps, formato do payload enviado ao backend, formato da resposta de sucesso e de erro, e estados de UI necessários. Considere no mínimo nome e e-mail, e sugira campos extras opcionais somente se fizer sentido. Organize a resposta para implementação imediata.
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
Uma especificação clara dos campos, validações, payloads e regras do fluxo.
Should not happen
- ✕Criar um formulário bonito que não salva nada em backend real
- ✕Validar apenas no frontend e aceitar dados inválidos no servidor
- ✕Mostrar mensagem de sucesso fixa mesmo quando a gravação falha
- ✕Não impedir envios duplicados por cliques repetidos ou e-mails repetidos
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…
- !Criar um formulário bonito que não salva nada em backend real
- !Validar apenas no frontend e aceitar dados inválidos no servidor
- !Mostrar mensagem de sucesso fixa mesmo quando a gravação falha
- !Não impedir envios duplicados por cliques repetidos ou e-mails repetidos
- !Deixar o banco ou endpoint desconectado da interface
- !Usar dados mockados e apresentar isso como funcional
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
Refaça sem desenhar UI ainda. Entregue apenas a especificação implementável do fluxo de inscrição: campos, tipos, validações, payload de envio, resposta da API, regra anti-duplicidade e estrutura do registro persistido.
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.