What Flows just did
Based on your request to build Tool Permissioning Tiers, Flows created 4 implementation stages and 12 checks.
You asked for: Implement permission tiers across my toolset: risk classification, tier enforcement in the dispatch path, session grants, and a complete decision log.. Flows generated 4 stages because the application requires Every tool (and risky parameter pattern) classified into tiers: safe, session, ask, never; Tier enforcement in the tool dispatch path - not in tool code, not in the prompt; Session grants: approved once, allowed for the session, revocable. 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: All-or-nothing permissions: either everything asks or nothing does; Enforcement via prompt instructions the model can rationalize around; Session grants that never expire and quietly become permanent.
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: Every tool assigned with justification
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
- 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 4
Not startedClassify the toolset by risk
Reversibility and blast radius decide the tier.
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
- Tool Permissioning Tiers
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.
Classify every tool. Tiers: SAFE (read-only, no side effects: file reads, searches, listings) - auto-allow; SESSION (mutating but contained and reversible: file edits in the workspace, git commits) - first use asks, approval covers the session; ASK (consequential or hard to reverse: shell commands by default, network calls, package installs) - every use asks unless a narrow rule says otherwise; NEVER (catastrophic or out of scope: credential file access, force-push, bulk deletion) - blocked outright. For parameterized tools, write argument rules: run_command with a read-only known-safe binary (ls, cat, git status) may drop to SAFE; anything matching destructive patterns (rm -rf, DROP TABLE, force flags) escalates to ASK or NEVER. Deliver the classification table with a one-line justification per tier assignment.
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 tiered classification with parameter rules.
Should not happen
- ✕All-or-nothing permissions: either everything asks or nothing does
- ✕Enforcement via prompt instructions the model can rationalize around
- ✕Session grants that never expire and quietly become permanent
- ✕No log, so nobody can answer 'what approved this?' after an incident
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…
- !All-or-nothing permissions: either everything asks or nothing does
- !Enforcement via prompt instructions the model can rationalize around
- !Session grants that never expire and quietly become permanent
- !No log, so nobody can answer 'what approved this?' after an incident
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
Everything landed in ASK, which users will not tolerate. Re-classify with the reversibility test: if git or a file restore undoes it in seconds, SESSION is usually right - reserve ASK for real consequence.
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.