The 13-Month Machine Learning Fortress

Master Command Document

Here it is.

You built this. Not the files — the decision to take 13 months and rebuild everything from first principles while working full-time at Zoho, in India, in 2026, when the entire field is moving at a speed that makes most practitioners quietly panic. That decision is the hardest thing in this document. Everything else is execution.

This is not a curriculum. Curricula are consumed. This is a fortress: a system for producing a specific human being at Month 13 — one who is genuinely rare, genuinely capable, and genuinely prepared.


The Three Principles (The Constitution)

Principle 1: Build, Then Understand — Then Build Again. You do not understand gradient descent by reading about it. You understand it by implementing it, watching it fail on a badly conditioned matrix, fixing it, and then reading the theory to understand why the fix worked. Theory without code is philosophy. Code without theory is cargo cult. The order here is: implement a rough version → read the canonical source → implement a precise version → break it intentionally → fix it. Every phase follows this loop.

Principle 2: The Public Record Is the Degree. At Month 13, you will not have a PhD. You will have something more useful: a verifiable public record of 8 shipped artifacts that prove specific capabilities to anyone willing to look. A fine-tuned model on HuggingFace. A production monitoring dashboard with real drift data. A paper reproduction with deviation analysis. These are not portfolio decorations. They are the evidence. Treat every project with the same rigor you would treat something you’re shipping to 10,000 users.

Principle 3: The Roadmap Serves You. You Do Not Serve the Roadmap. Illness, family, job pressure, the Valley of Despair at Month 6 — these are not plan failures. They are inputs to a living system. The sprint structure has 4 buffer weeks built in precisely because life is not a Gantt chart. If you fall behind, the protocol is in 99_pre_mortem/09_summary_and_reset_protocol.md. You do not abandon the fortress because of one bad month. You use the reset protocol and continue.


The M13 Pitch Sentence

“I’m an applied ML engineer who rebuilt the discipline from first principles over 13 months — from linear algebra and probability through transformers, diffusion, and LLM alignment — and can now design, implement, debug, and take to production any ML system, read and critique the research behind it, and explain it to anyone; one of a few hundred practitioners globally who are genuinely both builders and scholars.”

Everything in this fortress — every file, every project, every sprint — exists to make that sentence true and verifiable, not just sayable.


Phase Map


Portfolio Ladder (Quick Reference)

Rung

Month

Artifact

Hard Gate

1

M2

Math From Scratch — SVD + gradient descent notebook

2

M4

Classical ML Battle — 3-model Kaggle benchmark repo

3

M6

Deep Learning From Scratch — full backprop + training loop

4

M8

Transformer Lab — nanoGPT + domain fine-tune + DDPM MNIST

5

M10

LLM Engineering — QLoRA + RAG + evaluation + live demo

⛔ GATE

6

M12

Production ML System — live pipeline, monitoring, runbook

⛔ GATE

7

M12

Paper Reproduction — published result + deviation analysis

8

M13

Technical Writing — 3 posts + talk/review submission

Hard Gate Definition: Gates 5 and 6 are non-negotiable. If either is missing at the required month, the plan has failed its primary objective. No amount of theoretical knowledge substitutes. See 12_portfolio/05_rung_5_llm_engineering.md and 12_portfolio/06_rung_6_production_ml_system.md for exact acceptance criteria.


Fortress Tour (All Directories)

Directory

What It Is

00_command/

This directory. The master layer. Read this first, revisit monthly.

01_phase_0_mathematical_foundations/

Linear algebra, calculus, probability, information theory. The irreducible floor.

02_phase_1_classical_ml/

Supervised/unsupervised, sklearn, feature engineering, classical production.

03_phase_2_deep_learning_core/

NNs from scratch, PyTorch, CNNs, sequence models, training dynamics.

04_phase_3_modern_architectures/

Transformers, BERT/GPT, ViT, diffusion models, GNNs.

05_phase_4_generative_ai_frontier/

RLHF/DPO, PEFT/QLoRA, RAG, LLM agents, multimodal.

06_phase_5_production_and_mlops/

Experiment tracking, serving (vLLM), containers, monitoring, CI/CD.

07_phase_6_research_and_mastery/

Paper reading, frontier papers 2024-25, OSS contribution, technical opinion, identity.

09_resources/

12 books, 12 courses, 28 papers, tools, datasets — all verified canonical, no dead links.

10_communities/

Reddit, Discord, newsletters, India-specific. Where practitioners actually live.

11_tools_setup/

Python env, GPU/compute, VS Code, DVC, version control for ML.

12_portfolio/

8 portfolio rungs, presentation guide, full timeline. The evidence layer.

13_discipline/

Sprint cadence, lab notebook, daily practice, failure modes, motivation, health.

99_pre_mortem/

8 adversarial failure modes + reset protocol. Read this when things go wrong.


How to Read This Fortress

Week 1 (Onboarding — do this before anything else):

  1. Read this file completely.

  2. Read 00_command/01_month_by_month.md — understand your entire arc.

  3. Read 13_discipline/01_sprint_cadence.md — internalize the 2-week sprint system.

  4. Read 99_pre_mortem/README.md — know your failure modes before you enter the arena.

  5. Open 01_phase_0_mathematical_foundations/README.md — start Sprint 1.

Ongoing (every 2 weeks):

  • Sprint retro using 13_discipline/02_lab_notebook.md template.

  • KPI check using 00_command/05_kpi_dashboard.md.

  • Update portfolio rung status in 00_command/03_north_star_artifacts.md.

Monthly:

  • Read the current month’s entry in 00_command/01_month_by_month.md.

  • Check Zoho alignment strategy in 00_command/06_background_alignment.md.

  • If in distress: go to 99_pre_mortem/09_summary_and_reset_protocol.md.


A Note Before You Begin

You are not trying to become the person who has read the most papers. You are trying to become the person who, when handed any ML problem — from a corrupted dataset to a misaligned LLM — can find the root cause, implement a fix, measure whether it worked, and explain every decision in the chain.

That person exists. There are maybe a few hundred of them globally who are both builders and scholars. This fortress is the 13-month path to joining them.

It starts Monday. It starts with a notebook, a pen, and Gilbert Strang’s first lecture.

Go.


Return to: [Top of this file] · Next: 01_month_by_month.md