Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Separate creation and editing into different calendar…
Schedule creation and editing as two separate calendar blocks with a minimum gap of thirty minutes (preferably overnight) to allow defamiliarization and enable fresh-eyes error detection.
Three sequential editing passes for high-polish outputs
For outputs requiring high polish, structure editing as three sequential passes—structural edit (organization), line edit (sentence clarity), copy edit (mechanics)—to prevent simultaneous optimization across incompatible dimensions.
Default pass policies by output type
Build default two-pass policies by output type—emails under five sentences single-pass, documents over one page mandatory two-pass, strategic outputs three-pass with overnight incubation—to prevent case-by-case deliberation.
Prioritize long half-life + high reach outputs over short…
Route attention and effort disproportionately to outputs with long half-lives (months-to-years) and high audience reach over outputs with short half-lives (hours-to-days) and narrow reach when both compete for finite production time.
Name the specific output before consuming information…
Before consuming any information during learning sessions, define the specific output that consumption will feed into—if no output can be named, the learning session does not belong on the calendar.
Design near-complete templates for recurring outputs…
For recurring operational outputs (status reports, bug reports, meeting minutes), design templates with nearly complete structure including section headings, formatting, and boilerplate text, requiring only variable content insertion.
Extract templates from your 3 best past examples…
Extract templates from your three best past examples of an output type by identifying common structure across those instances, rather than designing templates from theory.
Define minimum viable output
Define the minimum viable output by identifying the recipient, the action they should take, and the minimum content needed to enable that action—then produce only to that threshold before shipping.
Pre-produce 3-5 buffer outputs before launching any public…
Before launching a public output cadence, pre-produce three to five buffer outputs to absorb inevitable disruptions without breaking the chain.
Complete all preparation before the production session…
Complete all batch preparation (gather materials, load contexts, prepare templates) before the production session begins, so that session time is pure execution without information-gathering pauses.
Sequence batches
Within a batch session, start with the easiest or most familiar output to build momentum, tackle demanding outputs at peak cognitive capacity, and save formulaic outputs for the end when pattern-matching remains strong but creative energy wanes.
Define the distribution plan before starting production…
Before beginning any significant output, define its distribution plan by identifying specific audiences, channels, formats, and timing rather than treating distribution as a post-production task.
Move outputs forward through pipeline stages…
Move outputs sequentially through pipeline stages (Draft → Review → Polish → Deliver) without skipping stages or oscillating backward except through explicit, documented regression decisions.
Check 3-5 yes/no gate criteria at each pipeline stage…
At each pipeline stage transition, check explicit gate criteria (3-5 yes/no questions) before advancing the output, and if any answer is no, keep the output in its current stage until deficiencies are addressed.
One cognitive mode per stage
During draft stage, generate content and follow templates without editing or polishing; during review stage, evaluate structure without wordsmithing; during polish stage, refine language without restructuring—never mix activities from different stages in a single work session.
Work the most downstream pipeline stage first — Deliver…
Before every work session, consult your pipeline board and work on the most downstream stage that contains items (Deliver before Polish, Polish before Review, Review before Draft) to pull from bottlenecks rather than accumulating work-in-progress.
Set WIP limits per pipeline stage (solo
Set work-in-progress limits for each pipeline stage (typical solo creator: Draft—3, Review—2, Polish—2) and do not start new items in a stage until existing items advance, to prevent attention fragmentation and increase throughput.
Scale versioning to stakes
For high-stakes outputs with long lifecycles, implement full versioning with named versions, changelogs, and archived copies; for medium-stakes outputs, use lightweight date-stamped versioning; for low-stakes outputs, skip active versioning entirely to match overhead to value.
Snapshot the current state before each pipeline stage…
Before an output advances from one pipeline stage to the next (draft to review, review to polish), snapshot the current state as a version to create recoverable checkpoints throughout the production process.
Push distribution for known audiences + time-sensitive…
Use push distribution (direct delivery to inbox/channel) for known audiences with time-sensitive needs, and pull distribution (searchable repositories) for unknown future audiences seeking information over time—deploy both for significant outputs, not one or the other.
Four audience-mapping questions before finalizing any output
For every output, answer four audience-mapping questions before finalizing: (1) Who specifically needs this? (2) What do they need from it? (3) Where do they consume information? (4) When do they need it?—then format and time distribution accordingly.
Rewrite for each format — don't copy-paste across mediums…
When translating an output to a new format, rewrite the content in the language, tone, structure, and emphasis that format demands—do not copy verbatim across formats, because each medium requires different cognitive packaging to serve its audience effectively.
Cascade derivative formats over days/weeks after…
Cascade derivative format releases over days or weeks after the pillar ships (rather than publishing all simultaneously) to extend the life of the original research, prevent audience fatigue, and create multiple touchpoints across time.
Track four output dimensions
Build a personal output scorecard tracking four dimensions (reach, resonance, downstream action, personal growth) rather than any single metric, reviewing monthly to identify which output types score highest on the dimension that matters most to your goals.