The Canonical Week¶
Hour-by-Hour Structure for Full-Time Job + 10-15h Personal Study¶
This is not aspirational. This is the actual structure that has to work every week for 52 weeks, accounting for a full-time job at Zoho, family and life in India, energy depletion from real work, and the cognitive demands of genuinely hard material. It is designed for sustainability, not maximum throughput.
The rule: a good week is any week where you complete the primary focus block and at least one secondary block. A bad week is when neither happens. Log both. The difference between finishing and not finishing this fortress is almost entirely in whether you protect the Primary Deep Work block on Tuesday/Thursday evenings.
Constraints (The Hard Reality)¶
Full-time job: ~9 hours/day, ~45 hours/week
Commute or decompression buffer: 30-45 min post-work before study is viable
Sleep: 7 hours minimum. Non-negotiable. Sleep debt degrades learning retention more than any other variable.
Weekend mornings are the highest-quality study time. Protect them.
India-specific: heat in May-June makes evening study difficult. Shift to early morning (5:30-7:30am) during peak summer.
The Canonical Week (10-12 hour load)¶
Day |
Time Block |
Duration |
Activity |
Notes |
|---|---|---|---|---|
Monday |
Evening 8:00–9:30pm |
1.5h |
Reading/Theory block — read the fortress file for the current sprint |
Low-intensity. Reading only. No implementation. |
Tuesday |
Evening 8:00–10:30pm |
2.5h |
PRIMARY DEEP WORK — implementation/coding |
This is the anchor. Never cancel this. |
Wednesday |
Evening 8:00–9:00pm |
1h |
Lab notebook entry — predict, then measure, then write |
30 min reviewing Tuesday’s work, 30 min writing |
Thursday |
Evening 8:00–10:30pm |
2.5h |
PRIMARY DEEP WORK — implementation/coding (continued) |
Pair with Tuesday. These two blocks carry the week. |
Friday |
Rest or light review |
0–1h |
Optional: watch a lecture video, skim a paper |
No coding. No pressure. |
Saturday |
Morning 7:00–10:00am |
3h |
WEEKEND DEEP WORK — project work, harder problems |
Best cognitive hours of the week. Guard them. |
Sunday |
Morning 8:00–9:30am |
1.5h |
Weekly review + sprint planning |
Review lab notebook. Set Tuesday/Thursday goals. |
Total: ~12 hours/week standard load.
Extended Week (13-15 hour load — hard gate sprints only)¶
Add these to the canonical week during Very High load sprints (S19, S20, S23, S24):
Addition |
Duration |
Notes |
|---|---|---|
Saturday afternoon 2:00–4:00pm |
+2h |
Debugging, cleanup, documentation |
Sunday afternoon 2:00–3:30pm |
+1.5h |
Paper reading or project extension |
Use extended weeks sparingly. Running at 15h/week for more than 4 consecutive weeks leads to burnout. The schedule has been designed so that only the hard gate sprints require this load.
The Primary Deep Work Block Rules¶
The Tuesday and Thursday 2.5h blocks are non-negotiable. Everything else in this schedule is flexible. These two are not.
The block structure:
0:00–0:15 — Setup: open the fortress file, review what you planned to implement, write one sentence of intent in your lab notebook
0:15–2:00 — Implementation: write code, run experiments, debug. Headphones on.
2:00–2:30 — Cleanup: push code to GitHub, write a 3-sentence note in lab notebook about what you learned
Block protection rules:
Phone off or in another room
Notifications off
If something unavoidably intrudes: reschedule to the same night (if possible) or Saturday morning. Never skip entirely.
Slippage Rules (Green / Yellow / Red)¶
Status |
Definition |
Response |
|---|---|---|
🟢 Green |
Both primary deep work blocks completed this week |
Continue. Log in lab notebook. |
🟡 Yellow |
One primary block completed + at least one secondary |
Continue with mild concern. Write why in lab notebook. Don’t repeat. |
🔴 Red |
Zero primary blocks completed |
This week doesn’t count toward sprint progress. Do not move forward. Identify why, fix the cause, not the symptom. If 2 red weeks in a row: activate |
The system is designed so that a single yellow week costs nothing. Two reds in a row is a signal the schedule structure is broken, not that you are broken.
India-Specific Notes¶
Summer heat (April–June): Replace evening study with early morning. Pattern: 5:30–7:30am before work. This requires sleeping by 10:00pm the night before. The cognitive quality at 5:30am after adequate sleep exceeds 8pm post-work quality by a measurable margin.
Festival season (October–November: Navratri, Diwali, etc.): Plan for 2 reduced weeks during Diwali. Use Buffer Week 16 strategically if it falls here. Do not try to study during festival gatherings. The lost 2 weeks is accounted for in the buffer structure.
Monsoon (July–September): Power and internet disruptions. Download all required resources locally during Week 1. Keep a local backup of your lab notebook. Use offline-capable tools (Jupyter, VSCode with local kernels) as your primary environment.
Work crunch periods at Zoho: Zoho’s typical product release cycles create quarterly crunch pressure. Q3 (July-September) and Q1 (January-March) are historically the highest-pressure periods. During crunch weeks: drop to single primary block (Thursday only). Never drop to zero.
Energy Management¶
The 3-task rule for deep work sessions: Before each Tuesday/Thursday block, write exactly 3 tasks you will attempt. Not 7. Not 1. Three. This prevents both under-ambition and the spiral of an ambitious plan that fragments into nothing.
Post-work decompression: The 30–45 minutes between leaving Zoho and starting study matters. Do not try to study immediately after a difficult work day. Use the buffer: dinner, 20-min walk, or 20 minutes of completely non-technical activity. Then open the laptop.
The Sunday preview habit: On Sunday morning, spend 10 minutes reading the next sprint’s primary file (not deeply — just scan). This seeds your unconscious with the upcoming material so Monday’s reading block lands on prepared soil.
When Life Interrupts (And It Will)¶
Week-level disruptions (illness, family, travel): skip, log, continue. Do not try to compensate with double-sessions. The sprint structure absorbs one missed week cleanly.
Sprint-level disruptions (hospitalization, major family event, job crisis): activate the reset protocol. Read 99_pre_mortem/08_life_and_family_risk.md first.
The fortress has 4 buffer weeks precisely because you are a human being with a job and a life and occasional broken infrastructure. Use them without guilt.
Return to: README.md · Next: 05_kpi_dashboard.md