The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Track your shallow-to-deep work ratio weekly and treat ratios exceeding 50% shallow as signals of structural calendar problems requiring role negotiation rather than personal discipline improvement.
Rate your decision quality, comprehension speed, and emotional regulation daily on a 1-5 scale across five consecutive workdays to detect attention debt accumulation before subjective awareness registers the degradation.
Use automated time-tracking tools alongside manual 30-minute increment logs simultaneously for three consecutive workdays to capture both digital activity and non-digital context that neither method alone reveals.
Before reviewing any attention tracking data, write explicit predictions about your time allocation percentages across categories, then calculate prediction-reality gaps to identify your largest attention blind spots.
When approval steps in a process have produced zero changes in the last twenty instances, eliminate the approval gate as pure waste regardless of its historical rationale.
For decisions blocking three or more downstream dependencies, calculate cost of delay by multiplying the decision's delay duration by the combined capacity waiting idle, then prioritize decisions by this metric rather than by perceived importance.
Make your current bottleneck metric physically visible in a location you cannot minimize or avoid (sticky note on monitor, whiteboard in workspace) and update it daily rather than relying on digital dashboards.
Display bottleneck metrics using only four elements—constraint name, current value, target value, and trend direction—eliminating all decoration to maximize signal-to-noise ratio.
Begin every team standup with the current constraint metric before individual updates to keep collective attention focused on the binding bottleneck.
When cards accumulate in one column of a kanban board creating a visible queue, treat that column as the current bottleneck without requiring separate cycle time analysis.
Add 20% time buffers around constraint activities that fail or degrade most frequently under pressure, rather than distributing slack evenly across all workflow steps.
Maintain one completed output in reserve after your constraint step (stock buffer) to decouple production cadence from delivery cadence when the constraint step has high variability.
Document one alternative method or backup person who can execute your constraint step at 80% quality to serve as capacity buffer during disruptions, rather than pursuing redundancy everywhere.
When throughput improvement stalls despite continued effort at the current constraint location, immediately re-run constraint identification to detect whether the bottleneck has migrated.
When experiencing chronic difficulty with complex cognitive tasks across multiple domains simultaneously, diagnose for attention debt rather than domain-specific skill gaps, because attentional degradation produces domain-general impairment that mimics multiple independent deficiencies.
Record bottleneck journal entries in under two minutes using six fields only (date, constraint name, severity 1-5, type, intervention, result) to maintain practice sustainability.
Before investing in constraint elevation, verify that constraint capacity is being used at 100% for highest-value work rather than dissipated across low-priority tasks.
Maintain commitment-to-capacity ratio between 0.70 and 0.85 to preserve system stability, keeping 15-30% of capacity uncommitted as structural buffer for variance absorption.
When daily capacity rating is 1-2 (depleted/foggy), limit focused work to 1 hour maximum and allocate remaining time to administrative tasks, recovery, or maintenance rather than forcing deep work.
Rate your daily capacity on a 1-5 scale within the first 30 minutes of your workday before starting any tasks, using the rating to select which tier of work plan to execute that day.
When commitment-to-capacity ratio exceeds 1.0, intervene only through cut (remove commitment entirely), defer (move to future period with capacity), or delegate (transfer to someone else)—productivity techniques cannot solve overcommitment caused by arithmetic mismatch.
Treat common-cause capacity variation (daily fluctuations within your normal 2-5 hour range) as system-inherent rather than problems requiring intervention; investigate and respond only to special-cause variation (events falling outside normal range).
Allocate weekly focused work hours unevenly based on predicted daily capacity levels (more hours to high-capacity days, fewer to low-capacity days) rather than distributing work uniformly across all days.
After measuring five days of actual focused work time, use the daily average (not the best day or hoped-for number) as your baseline planning capacity for all future scheduling decisions.