The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Test workflow composition by attempting to replace one sub-workflow without breaking others—if replacement forces changes to adjacent workflows, interfaces are leaking.
Every boundary between composed workflows must preserve an intermediate output as a concrete artifact to enable resumption, failure recovery, and reuse.
Insert AI sub-workflows between composed workflow stages by providing the previous stage's output plus a specific transformation instruction, treating AI as a transformation step not a decision maker.
Review workflows weekly for execution status, monthly for portfolio health, and quarterly for strategic alignment—each altitude catches different kinds of drift.
Retire workflows that have not been executed in 60+ days unless they are seasonal or event-triggered, as inactive workflows accumulate maintenance debt without providing value.
Make workflows context-independent by naming specific tools and providing alternatives, not by eliminating specificity—separate essential logic from incidental implementation.
Test workflow shareability by having an unfamiliar person execute it without your help—every stumble reveals tacit knowledge you failed to externalize.
In shared workflows, explicitly mark which steps are fixed (deviation breaks the workflow) and which are customizable (reader can substitute tools/preferences).
Progress workflow sharing from private notes to team documentation to public templates only after the current level is validated—premature publication of under-tested workflows creates more problems than value.
Apply workflow design methodology only to recurring activities with consistency requirements—protect spontaneous, creative, and variable activities from systematization.
Treat the ideal week template as a gravitational field that pulls actual weeks toward designed structure rather than as a mandate requiring perfect execution—measure success by adherence trend over time, not weekly perfection.
Never apply the two-minute rule during maker-time blocks—capture small tasks for later processing instead, as a 2-minute interruption during deep work costs 25+ minutes in context recovery time.
Consolidate all meetings into one or two designated days per week rather than scattering them across every day, because meeting distribution destroys more productive capacity than meeting duration.
Implement office hours for coordination requests rather than accepting meeting invitations throughout the week—reverse the default from 'available unless blocked' to 'unavailable except during designated windows'.
When a meeting request arrives during a blocked maker session, move the meeting to a manager-mode block rather than accepting the fragmentation—treat maker blocks with equal calendar commitment as external client meetings.
Change default meeting durations to 25 or 50 minutes instead of 30 or 60 to automatically create buffers between consecutive meetings without requiring individual negotiation for each transition.
Schedule 5-minute buffers between meetings of similar type, 10-15 minute buffers between cognitively different activity types, and 20-minute buffers after intense or emotional interactions to contain context-switching costs within designated intervals.
After incomplete tasks, insert longer transition buffers than after completed tasks, because unfinished work generates stronger attention residue that degrades subsequent performance.
Schedule one 15-minute unallocated overflow buffer for every 2-3 hours of scheduled activity to absorb inevitable overruns and interruptions without cascading disruption through the rest of your day.
Fill the early-to-mid afternoon trough period (typically 1-3 PM for morning types) with administrative work that requires competence but not analytical depth, rather than scheduling demanding cognitive work that will feel disproportionately difficult.
Before any task over 30 minutes, write your time estimate; after completion, write actual time—do this for two weeks minimum to generate sufficient data for personal estimation ratio calculation.
Generate three estimates (optimistic, realistic, pessimistic) for each significant task and calculate weighted average as (optimistic + 4×realistic + pessimistic)/6 to counteract automatic optimism bias in single-point estimates.
Apply your measured personal estimation ratio as a multiplier to all future estimates—if actual/estimated consistently = 1.8, budget tasks at 1.8× your initial estimate to achieve calibrated forecasting.
When estimating tasks, separately account for setup time, core work time, interruption/recovery time, and teardown/transition time—omitting these categories causes systematic 30-60% underestimation of total duration.