IIID CO. — FANTASYLAND FOOTBALL
2026 Scouting Database — Build Roadmap
Three months to take the inputs mapped in the Data Flow diagram all the way to scores, reports, and visuals Zach can open on his own — with a fourth month held in reserve for the first weeks of in-season use. Two tracks run in parallel: the build, and Zach's shaping of the composite scoring.
Companion to Scouting Database — Data Flow · derived from ROADMAP.md, 2026-07-14
Your build work
Zach's scoring input
Optional month (contingent)
Milestone
Roadmap · two parallel tracks over three months
Three months to build. A fourth if the season calls for it.
Read it as: Two lanes run side by side. In Month 1 you stand up the database and prove every input gathers cleanly (orange) while Zach sketches the scoring shape (stone) — they finish together. That shape becomes real formulas in Month 2, and backtesting past seasons starts immediately and runs into Month 3, where the work turns to tuning and getting real reports in front of Zach. The dashed amber fourth month isn't committed — it's a reserve for supporting live use once the season is underway. The stone dot in Month 2 marks the CFB kickoff, which lands mid-build, not at the finish.
Definition of done · what each month must clear to advance
Exit gates
Month 1 · exit gate
Data flows, and the scores make sense on paper
Every input — PFF, CFBD, recruiting, mock drafts, film/scout — maps to a DB field and reliably gathers and structures data. Zach and you have agreed the shape of the composite scoring.
Month 2 · exit gate
Scores are live and being tested
The composite formulas live in the database and compute off ingested data. The backtest harness is running prior seasons through the scores, with first results in view.
Month 3 · exit gate
Validated, and Zach can actually use it
Scores are validated against past results to Zach's satisfaction, and reports plus visualized data generate in a form he can open and read on his own.
Month 4 · optional
First in-season weeks, supported
Held in reserve. If Months 1-3 need reinforcement or the live weekly cadence needs babysitting, this month supports the first weeks of real use during the season.
A note on dependencies.
- Scoring build waits on scoring shape. The Month 2 formula work can't finalize until Zach's Month 1 thinking on the composite scoring lands — the equations in the database are a direct expression of that sign-off.
- Backtesting waits on clean ingestion. Testing past seasons is only trustworthy if the Month 1 database is producing clean, structured historical data to score against.
- The season is already running during the build. CFB kicks off around late August (inside Month 2), so anything meant to run live must be stable before then — the optional Month 4 exists precisely because real use begins mid-build.
- Dates are directional. They assume a mid-July start and shift proportionally with the kickoff; the sequence and dependencies hold regardless of the exact calendar.
Traced from ROADMAP.md 2026-07-14 — regenerate if the plan or the scope changes.