Evidence · Tier 1 plan checks (self-checked)
Youth soccer management: workflow validated, not independently proven
An independent agent followed the complete 11-step Flows plan and produced a working application that passed the plan’s 59 automated checks. Because the plan and checks came from the same workflow, this validates route execution but does not independently prove reliability. For true Tier 3/4, use the external fixed suiteyouth-soccer-external-v1 with multi-tenant verifier isolation (builder ≠ evaluator) — see project Verification tab orsuite JSON.
Verdict
Partially validated
Workflow validated · independent reliability not yet proven
Plan checks (Tier 1)
59 / 59
Self-checked — same plan authored the checks
Route steps
11
Prompt edits
0
Selected route
| Title | Build a Youth Soccer Team Management App |
|---|---|
| Slug | build-youth-soccer-team-management-app |
| Trust tier | Generated Draft |
| Difficulty | Advanced |
| Estimated duration | 180-300 minutes |
| Verify checks (route) | 53 |
| Builder platform | Grok coding tools · Node.js / Express / SQLite (not Emergent) |
| Discovery note | Default search previously hid generated routes. Productization fix: All routes includes curated + generated with trust badges. |
Application produced
Working coach/admin app for a single youth team with real database persistence and server-side role checks — not a static mockup.
- ✓Coach/participant authentication with protected mutations
- ✓Roster with jersey numbers, positions, active filter
- ✓Guardians via PlayerGuardianLink (multi-guardian)
- ✓Schedule: practice, game, tournament
- ✓RSVP / availability (unique player+event)
- ✓Attendance (separate from RSVP)
- ✓Game-only lineup assignments
- ✓Dashboard aggregates + announcements
Architecture (builder choice)
Flows did not prescribe the stack. The independent builder chose the following — this is not attributed as a Flows output.
Runtime
Node.js 22
HTTP
Express 5
Database
SQLite + FK/UNIQUE
Flows evaluation scores (1–10)
Strongest evidence for Flows
- RSVP ≠ attendance enforced by schema and checks
- UNIQUE(player, event) on availability and attendance
- Server-side 403 for participant mutations
- Game-only lineup rejection for practices
- Ordered 11-step rail reduced feature hopping
Strongest evidence against / limits
- Generated routes were invisible under default search (now fixed here)
- Repair prompts not stress-tested under live failure
- No public HTTPS deploy of the soccer app in the original run
- Builder was a capable coding agent — nontechnical performance unknown
- Stack underspecified by the route
Methodology
- Opened Flows; filtered source to generated; selected soccer route
- Copied Context Pack; used Full Build / detailed prompts only (0 edits)
- Implemented each step against the prompt requirements
- Ran automated verify suite aligned to route checklists (59 assertions)
- Documented verdict: Partially validated
Full technical report and build log from the original validation live under the validator’s workspace (flows-validation/FINAL_REPORT.md). This page is the product-facing evidence summary.
What we changed in productization
Searching “soccer” under All routes now finds this generated route. Trust badges distinguish Flows Curated from Generated Draft. Empty curated searches surface a generated-route nudge instead of a dead end.
- Verify adapters: deploy, API, authz, browser/app persistence, content probe
- Build Evidence Report + portable run/draft packs for handoff
- Local continuous build recording (timeline) and evidence strength heuristic
- Private drafts appear on Runs with correct continue links
Adapter honesty and limits: /verification. Public HTTPS deploy of this soccer app is still a separate ops task — not claimed as shipped product hosting.
Automated suite by step
From the independent validator's 59/59 run (Express + SQLite suite), not from the Flows web product auto-running the app.
Step 1
6/6
Step 2
5/5
Step 3
8/8
Step 4
5/5
Step 5
5/5
Step 6
5/5
Step 7
4/4
Step 8
5/5
Step 9
4/4
Step 10
6/6
Step 11
6/6