What Flows just did
Based on your request to build Add Push Notifications to Existing App, Flows created 7 implementation stages and 21 checks.
You asked for: Add real push notification capability using Firebase Cloud Messaging, persisting device tokens, and providing an admin UI to send test messages.. Flows generated 7 stages because the application requires Use Firebase Cloud Messaging (FCM) for push delivery.; Store each device token in PostgreSQL linked to a user.; Provide a secure backend endpoint to send notifications to a specific user.. 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 returns placeholder keys or dummy JSON instead of real Firebase credentials.; Missing or incorrect modifications to Android build.gradle causing compile errors.; Client code skips the network request or uses a mock URL..
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
7 stages · 21 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: Credentials JSON includes googleServicesFile, fi…
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 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
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 7
Not startedCreate Firebase Project & Obtain Credentials
Provide the cloud messaging service and keys needed for both client and server.
The existing app is a React Native front‑end with a Node/Express backend and PostgreSQL. No Firebase config exists yet.
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
- Add Push Notifications to Existing App
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.
1. Log in to Firebase console and create a new project named after the existing app. 2. In the project settings, add an Android app (package ID from the React Native app) and download the generated google-services.json file. 3. Copy the web app config (apiKey, authDomain, projectId, storageBucket, messagingSenderId, appId) into a JSON snippet. 4. In Cloud Messaging settings, locate the Server key (legacy) and the Sender ID. 5. Return a JSON object containing: { "googleServicesFile": "<base64‑encoded google-services.json>", "firebaseConfig": {…}, "serverKey": "<FCM Server Key>", "senderId": "<Messaging Sender ID>" } No placeholders; include real base64 content and keys.
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 JSON file with real Firebase credentials ready for integration.
Should not happen
- ✕AI returns placeholder keys or dummy JSON instead of real Firebase credentials.
- ✕Missing or incorrect modifications to Android build.gradle causing compile errors.
- ✕Client code skips the network request or uses a mock URL.
- ✕Backend route does not validate auth or lacks ON CONFLICT handling, leading to duplicate token errors.
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 returns placeholder keys or dummy JSON instead of real Firebase credentials.
- !Missing or incorrect modifications to Android build.gradle causing compile errors.
- !Client code skips the network request or uses a mock URL.
- !Backend route does not validate auth or lacks ON CONFLICT handling, leading to duplicate token errors.
- !Push sender uses a fake FCM endpoint or omits the Authorization header.
- !Admin UI lacks proper navigation entry or does not display response.
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 previous output contained placeholders or missing fields. Provide the exact Firebase credentials as specified, ensuring no dummy data.
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.