The 9-Month DSA Fortress¶

Master Command Document¶

The M9 pitch sentence — designed first, everything else built backward from it:

“An applied ML engineer who rebuilt CS foundations from scratch — complexity theory through competitive solving — over 9 months, shipping 6 public proof-of-work artifacts that demonstrate systematic algorithmic thinking.”

What This Is¶

This fortress is a complete operational system for one person to go from “ML engineer who lost themselves in AI code-churning” to someone who sits down at a Hard LeetCode problem, recognizes the structure, and enjoys the hunt. It is not a curriculum. It is not a course outline. It is a 9-month machine with phases, sprints, discipline protocols, failure-mode coverage, and portfolio artifacts — all of which exist to serve one human outcome: genuine proficiency, genuine joy, and genuine proof of both.

What this is not: a job-switch preparation package, a 6-week crash course, a collection of problem lists, or motivation porn. Every file in this fortress is actionable or adversarial. If you can’t do something specific after reading a file, that file was wasted. Report failures in your lab notebook and pivot.

Start date: July 27, 2026. End date: April 27, 2027. Time budget: 10–15 hours per week, personal time alongside a full-time job at Zoho.

The 3 Principles (The Constitution)¶

These three principles overrule everything else in this fortress when they conflict:

1. Understanding over coverage. One algorithm you can derive from first principles is worth more than twenty you’ve memorized. You will be tested on variations, not on the original. If you can’t explain WHY a solution works, you haven’t learned it — you’ve borrowed it.

2. Deliberate practice over volume. Solving 5 problems while asking “why does this work?” beats solving 20 problems on autopilot. The measure of a session is not how many problems you touched — it’s how many patterns became genuinely yours.

3. The plan serves you. You do not serve the plan. When life demands presence — a family event, a health crisis, a Zoho deadline — the plan pauses. It does not decay. The restart protocol in 99_pre_mortem/08_life_health_family.md exists precisely for this. Read it now. Before you need it.

Phase Map¶

Portfolio Ladder Table¶

Rung	Artifact	Month	Platform	Hard Gate?
1	Complexity Audit Repository	M1–M2	GitHub	No
2	Data Structure Library from Scratch	M2–M3	GitHub	No
3	“Explain the Algorithm” Blog Series (5 posts)	M3–M4	Dev.to / Hashnode	No
4	LeetCode 100 Hard Milestone + Annotated Log	M4–M6	GitHub + Blog	No
5	Graph Algorithm Showcase (5 algorithms, real data)	M6–M7	GitHub + Video	No
6	DP Pattern Handbook (all 7 patterns, your voice)	M7–M8	GitHub + Community	YES — by M8.5
7	Codeforces Rating ≥ 1200 (5 rated contests minimum)	M8–M9	Codeforces	YES — by M9
8	M9 Capstone Narrative (links all artifacts)	M9 final 2 weeks	GitHub + LinkedIn	No

Hard Gate Rungs: 6 and 7. These are non-negotiable. Everything else is evidence; these two are proof.

Fortress Tour¶

Directory	What Lives There	Who Reads It
`00_command/`	Master plan, monthly schedule, sprint calendar, KPIs, pitch	Read first. Return weekly.
`01_foundations_complexity/`	Big-O, recurrence, math thinking, pseudocode	Phase 0 (M1–M1.5)
`02_core_data_structures/`	Arrays, linked lists, stacks, queues, hash maps, heaps	Phase 1 (M1.5–M3)
`03_recursion_and_trees/`	Recursion, D&C, binary trees, BSTs, backtracking, tries	Phase 2 (M3–M4.5)
`04_graphs_and_search/`	BFS, DFS, topo sort, shortest paths, Union-Find, MST	Phase 3 (M4.5–M6)
`05_dynamic_programming/`	All 7 DP patterns, state design, pattern taxonomy	Phase 4 (M6–M7.5)
`06_advanced_algorithms/`	Segment trees, BIT, greedy, KMP, bit manipulation	Phase 5 (M7.5–M8.5)
`07_competitive_mastery/`	Contest strategy, speed, templates, deliberate practice	Phase 6 (M8.5–M9)
`09_resources/`	Book/course/platform canon with community verdicts	Reference throughout
`10_communities/`	Where practitioners actually live online	Join Week 1. Stay.
`11_tools_setup/`	Day 1 setup, IDE, tracking, CP tooling	Complete before Day 1
`12_portfolio/`	All 8 portfolio rungs with acceptance criteria	Build throughout
`13_discipline/`	Sprint system, daily habit, failure modes, health	Read weekly
`99_pre_mortem/`	8 failure modes, reset protocol, permission slip	Read now. Re-read at M4.

How to Read This Fortress¶

Week 1 onboarding sequence (do this in order):

Read 99_pre_mortem/08_life_health_family.md — the permission slip. Especially the protected festival dates.
Read 99_pre_mortem/01_the_ai_crutch.md — the failure mode most likely for you specifically.
Read 13_discipline/README.md — the operating philosophy.
Complete 11_tools_setup/04_day1_checklist.md — set up your environment.
Read 01_foundations_complexity/README.md — begin Phase 0.
Start 13_discipline/01_sprint_cadence.md — plan Sprint 1.

Ongoing rhythm:

Daily: 13_discipline/04_daily_practice.md protocol.
Weekly: Update lab notebook (13_discipline/02_lab_notebook.md). Check sprint goals.
Every 2 weeks: Sprint review + next sprint plan.
Monthly: KPI check (00_command/05_kpi_dashboard.md). Portfolio rung status.
At phase transitions: Read the next phase README before the previous phase exit criteria are fully met.

The Valley of Despair¶

Months 4–5 (approximately Oct 27 – Dec 26, 2026) will feel wrong. Graphs and DP are arriving simultaneously. You will not feel like you’re making progress. You are. Name it when it arrives: “I am in the valley.” Then do the 30-minute minimum session. Nothing more. See 13_discipline/07_motivation_sustainment.md for the full arc.

Closing Note¶

You said you want to find sense in what you’re doing. This plan is built for exactly that. Not for a job switch, not for a rating number — for the day you sit down at a hard problem and feel the gears turn. For the first Codeforces submission that passes. For the moment a DP problem that seemed impossible becomes obvious because you built the framework to see it.

That day is coming. It requires these 9 months. Start tomorrow.

Fortress built: July 27, 2026. All subagents deployed and confirmed complete.

Next: 01_month_by_month.md