The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
For any recurring activity, explicitly define three elements—the specific output being measured, the standard for comparison, and the adjustment rule triggered by deviation—to create a complete minimal feedback loop.
Before attempting to improve any feedback loop, measure the current delay between action and signal in concrete time units (seconds, minutes, hours, days) rather than accepting vague assessments, because unmeasured delays appear shorter than they actually are through habituation.
Find a faster correlated signal that approximates delayed feedback rather than waiting for the original signal, accepting that speed compensates for increased noise in the approximation.
For daily activities, if feedback latency exceeds one week, or for strategic activities if latency exceeds one month, design a leading indicator or checkpoint that shortens the delay before drift compounds.
Build measurement dashboards and leading indicators at the same time you design the strategy they measure, not after problems appear, because instrumentation designed during crisis measures symptoms rather than causes.
Strengthen a reinforcing loop you want to amplify by reducing friction at any node, increasing gain at a single node, or shortening cycle time, implementing one intervention per loop rather than attempting simultaneous multi-variable changes.
Before attempting to improve a feedback loop component, verify it is actually the constraint by measuring whether improvements there would increase total system throughput, as optimizing non-constraints produces local gains without system-level improvement.
When feedback consistently arrives in days or weeks while the behavior repeats daily, the brain cannot reliably attribute consequences to specific actions due to temporal credit assignment failure—requiring external tracking systems to maintain the causal connection.
Schedule forcing functions (weekly reviews, monthly retrospectives, quarterly strategy assessments) at intervals shorter than the natural feedback latency to artificially tighten loops that cannot be structurally accelerated.
Treat any deviation from established standards as a potential normalization-of-deviance signal requiring documented evaluation rather than silent acceptance, because repeated deviations without consequence train the system to accept the deviation as normal.
Convert vicious cycles into virtuous ones by intervening at a single node to reverse signal direction rather than attempting to dismantle the entire loop structure, because loop topology is often more stable than loop content.
When a feedback loop identifies a discrepancy between current and target state, translate the evaluation into a specific behavioral adjustment for the next cycle rather than stopping at awareness, because learning occurs during adjustment not observation.
Map any broken feedback loop onto the four-part structure (Act, Observe, Evaluate, Adjust) to diagnose which specific component is missing, because each missing part produces a distinct failure signature.
Before adding corrective action in a delayed-feedback system, inventory pending actions already taken but not yet producing results to avoid pipeline overfilling and subsequent overshoot.
Separate the decision to continue a slow-feedback strategy from subjective feelings of progress by defining persistence duration in advance, because delayed systems provide zero felt momentum before delivering concentrated results.
Separate feedback reception from feedback evaluation by implementing a mandatory 48-hour delay between receiving criticism and deciding whether to act on it, as identity triggers fire faster than analytical capacity and premature evaluation guarantees defensive rejection.
When feedback triggers immediate counter-argument before you finish listening, treat the speed of that dismissal as diagnostic evidence that the feedback addresses an important blind spot rather than as evidence the feedback is invalid.
For each feedback mechanism you build, verify within the first cycle that the data reveals something unknown, that measurement effort is sustainable, and that you can specify one concrete adjustment based on results—if any component fails, redesign before continuing.
When a metric has been used to drive decisions for more than three months without revision, conduct a three-question audit: what behavior does this metric actually incentivize, is the proxy still correlated with the outcome, and what would gaming this metric look like compared to current behavior.
Retire metrics entirely when they no longer distinguish between gaming behavior and genuine progress, as continued use of a decoupled metric produces wrong information you trust rather than mere absence of information.
Treat major life or work transitions as mandatory recalibration events requiring review of all existing feedback loops, as changed context invalidates proxy-outcome correlations that held under previous conditions.
When improvement effort in a domain has stalled despite sustained attention, shift focus from single-loop correction (adjusting actions) to double-loop correction (questioning the framework generating actions) by explicitly listing and testing the assumptions underlying your approach.
When building any recurring system (workflow, habit, routine), design an explicit degraded-mode version that preserves core function at reduced scope before the system encounters its first disruption.
For each detected error in a system, explicitly classify whether it represents an execution failure (wrong doing), knowledge failure (missing information), or judgment failure (incorrect assessment) before designing any correction.