THE WEEKLY PLAN
Twelve weeks.
Evidence every week.
The original core has an 84-hour planning budget. Twelve additional depth topics have a separate 36-hour budget. They do not need to be completed within the core schedule.
WEEK 1
Set your baseline
Evidence: Interpreter note, diagnostic results and first script
WEEK 2
Functions with a contract
Evidence: Three tested pure functions using EGP minor units
WEEK 3
Debug with evidence
Evidence: A boundary-case log and a corrected function
WEEK 4
Shape and iterate
Evidence: List transformations with empty-input checks
WEEK 5
Group, reconcile, reject
Evidence: Category totals, orphan IDs and useful error messages
WEEK 6
Give the code a home
Evidence: A modular CSV/JSON command-line tool
WEEK 7
Finish the EGP ledger
Evidence: Build 01 with reconciliation and a clear README
WEEK 8
Translate SQL into pandas
Evidence: A join-cardinality experiment and matching totals
WEEK 9
Validate PixelFed inputs
Evidence: Build 02 plus optional ML leakage checklist
WEEK 10
Define external contracts
Evidence: API failure matrix and idempotent fixture load
WEEK 11
Build one complete path
Evidence: Build 03, reject report and scheduling/runbook design
WEEK 12
Prove and connect the work
Evidence: Case study, source links and a next-branch decision
After the core
Choose an optional depth topic based on the next project’s requirements.