The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
When sprint pace (exceeding sustainable pace) is maintained for more than two consecutive weeks, expect proportional recovery debt requiring at least one week of reduced output to repay accumulated cognitive deficit.
When giving feedback in code reviews or technical discussions, state observable facts (nesting levels, exit paths, line numbers) before applying evaluative labels to enable problem-solving rather than defensiveness.
During capacity measurement, rate output quality at the end of each work block (strong/acceptable/weak) and identify the cumulative hour mark where strong output stops as your effective capacity ceiling for planning purposes.
Decompose tasks due on peak-load days into components that can start independently, then pre-load early components into low-load days to smooth temporal distribution.
Place most important committed work early in the week and early in the day so that end-of-week and end-of-day buffers can absorb delays without threatening highest-priority deliverables.
Track weekly buffer consumption rate—if consistently consuming more than 80% of buffer, increase buffer size; if consistently consuming less than 20%, buffer can be tightened.
When more than one-third of your active commitments are late, incomplete, or lower quality than promised, stop accepting new commitments until the ratio improves to preserve remaining trust accounts.
Sequence work blocks across different cognitive pools (creative, then analytical, then social, then administrative) rather than stacking same-type work, to allow depleted pools to recover while fresh pools carry the load.
When a cognitive pool (creative, analytical, social) shows degradation markers—repetition, forced output, errors, disengagement—switch to a different pool type rather than pushing through, even if scheduled time remains.
When capacity building, increase target output by 10% per week only if quality metrics held steady or improved AND you met target on at least 4 of 5 days in the previous week.
When capacity building fails to meet progression criteria for two consecutive weeks, reduce target by 10% to deload—you have overshot sustainable progression rate and need to consolidate at a lower level.
When building capacity from a new baseline, measure current honest output over at least three representative days—not best days or aspirational targets—to establish accurate starting point.
In blameless postmortems, frame questions as 'what was the system state at [time]' and 'what information was available' rather than 'who caused this' to shift from evaluation to observation and enable information sharing.
When your commitment-to-capacity ratio exceeds 0.85, respond to new requests with explicit counter-offers stating either a later start date or a specific trade-off rather than accepting or declining without alternatives.
Design capacity signals with neutral, operational framing (traffic light status, numerical availability) rather than emotional or complaint-based language, delivering them before requests arrive rather than as request-time justifications.
Create annual capacity maps rating each month 1-5 based on historical data, then distribute annual commitments proportionally to predicted monthly capacity rather than dividing by twelve uniformly.
When utilization exceeds 85% and a high-stakes request arrives, respond with the trade-off question format: 'If I add this, which of my current commitments should I deprioritize?' directed to the requester with decision authority.
Maintain a commitment-to-capacity ratio below 0.85 to accommodate variance, treating any ratio above 1.0 as mathematical proof that some commitments will fail regardless of willpower or prioritization.
When the same operational constraint appears in three consecutive weekly reviews, treat it as a structural issue requiring architectural change rather than tactical adjustment, escalating it from the weekly action item to a dedicated project.
When a deferred maintenance task's recovery cost exceeds its immediate execution cost by 3x or more, prioritize it above tasks with lower cost multiplication ratios.
Maintain an operational debt register that records what was deferred, when, why, and the estimated cost of continued deferral, reviewing it during weekly rhythms to distinguish strategic from accidental debt.
Validate simplified systems by running them for at least two full cycles before declaring success, as one cycle cannot distinguish between successful simplification and lucky conditions.
When a system's operational debt register grows despite consistent repayment, shift from maintenance to simplification rather than increasing maintenance effort.
Before acting on snap judgments during debugging or incident response, read system logs and dashboards for five minutes without proposing theories to prevent hypothesis anchoring from corrupting observation.