The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Begin project estimates with reference class forecasting from 3-5 comparable past projects before considering project-specific details, as base rates predict outcomes more accurately than inside-view planning.
Before committing to any significant project plan, conduct a 5-15 minute pre-mortem by assuming failure has occurred and listing 3-5 specific failure causes to surface risks that forward-looking analysis systematically misses.
Calibrate your personal two-minute threshold by comparing management overhead (processing, organizing, reviewing, re-engaging) against execution time for 10 recent tasks—set threshold where overhead equals execution cost.
During meeting-heavy days with fragmented administrative windows, lower your dispatch threshold to ~1 minute; during dedicated administrative blocks, raise it to ~5 minutes to match available processing capacity.
When batching similar tasks, group by cognitive context type (communication, financial, scheduling) rather than by chronological arrival order to minimize context-switching overhead.
Before starting any meeting, verify that four structural elements exist: stated purpose (what decision/problem), timed agenda with allocations, hard stop time, and defined outputs—if any element is missing, either add it or cancel the meeting.
Distribute pre-read documents before meetings and open with 15-20 minutes of silent reading to ensure all participants enter discussion with identical context, eliminating the information-transfer phase that consumes the first half of unprepared meetings.
Limit meeting attendance to 6-8 people maximum to prevent communication complexity from scaling combinatorially (n(n-1)/2 conversational pairs) and social cost from suppressing genuine discussion.
Compress meeting schedules into contiguous blocks on designated days rather than distributing them evenly across the week to preserve multi-hour maker time blocks on remaining days.
Replace recurring status update meetings with asynchronous written updates unless the meeting serves an additional coordination function beyond information transfer.
Immediately block recovered time on your calendar for specific priority work before recovering it—recovery without preallocation creates a vacuum that entropy fills with new low-value activities within weeks.
Use AI to analyze routine execution logs across multiple cycles, identifying which deviations correlate with missed executions, to diagnose structural fragility points invisible from inside the experience.
When a single element of your routine fails, execute the minimum viable versions of remaining load-bearing elements rather than abandoning the entire routine structure.
Classify each routine element as load-bearing (removing it degrades output or wellbeing) or cosmetic (preferred but not essential) to distinguish what must survive disruption from what can be sacrificed.
Plan for seven to eight hours of committed work when you have ten productive hours available, leaving two to three hours as unallocated slack to absorb disruptions without cascade failures.
Conduct seasonal time audits by pulling calendar data from the previous twelve months and rating each month as low-demand, baseline, high-demand, or crisis to identify recurring annual patterns.
For each identified high-demand period, make at least one structural adjustment before the period arrives by pushing deadlines, reducing project count, or front-loading preparation during preceding calm periods.
Schedule recovery time proportional to the intensity and duration of each high-demand period immediately after the period ends, as a structural calendar commitment rather than a vague intention.
Use reference class forecasting from last year's actual capacity during the same seasonal period rather than estimating from your current state when planning high-demand periods.
Reduce project commitments by approximately thirty percent during months you have identified as high-demand compared to baseline months, based on your measured capacity data.
Begin each weekly planning session by reviewing the previous week's plan against actual outcomes, identifying the single biggest gap between intention and reality without judgment.
When processing any recurring information inbox, work sequentially from top to bottom rather than cherry-picking items, to prevent repeatedly skipping difficult decisions that form the 'maybe pile'.
For any reference item you store, write the title using the words your future self will search for when they need it, not the words that categorize what it is.
Separate reference material (static information for lookup) from working notes (evolving thinking) into distinct systems, as mixing them corrupts both retrieval and development.