This blog has a master syllabus. Over 190 posts organized across five phases, seven concept threads, and five domains. Every post has a seed status, a domain tag, a type classification, and a sequence number. The syllabus is a spreadsheet. The execution is an assembly line.

I built the content strategy the same way I build everything else. Decompose the problem. Scaffold the structure. Constrain the execution. Monitor for drift.

Decomposition: “Write a blog” is a compound instruction the same way “evaluate this portfolio” is a compound instruction. It’s twelve problems disguised as one. What’s the thesis? What’s the curriculum structure? What domains does it cover? What’s the posting cadence? How do individual posts relate to each other? Each question needs its own answer.

The thesis is one sentence: the structural problems that show up when humans work with complex systems are the same problems regardless of material. Every post tests that thesis in a specific context.

Scaffolding: The master syllabus is the scaffold. It tells me what to write next without requiring a decision. Monday I look at the syllabus. The next DEEP seed is the next draft. I don’t choose what to write. The system chose weeks ago when I organized the curriculum. Executive function goes toward the writing, not toward the selection.

The seed statuses (DEEP, SHALLOW, NEEDS SEED) tell me how much work a draft needs before I can compile it. DEEP means I have enough context from three years of conversations. SHALLOW means I need to confirm one detail. NEEDS SEED means Peter has to provide the real moment before the draft can proceed. Each status maps to a different workflow.

Constraint: Every post crosses at least two domains. Every post declares its domain in the opening. Every concept thread follows the same structure: vocabulary definition, then domain applications, then failure mode. The constraints prevent the blog from drifting into a general “thoughts about stuff” channel. Each post has a specific job in the curriculum.

Drift monitoring: The EI compiler tracks which posts are drafted, which are seeded, which are live. The horizon dashboard tracks how many are published against the target. When the numbers drift from the plan, the dashboard makes it visible before I need to figure out what happened.

The meta-layer is that this content strategy is itself an example of the methodology it documents. Decomposition, scaffolding, constraint, drift monitoring. The blog about the method was built using the method, and the execution is where you can see whether it holds.