substrate · the system every external draft passes through before it ships.

Eight layers. Nine principles. Thirty-nine patterns. Eleven contradictions. Thirty-seven runnable skills. v1.0 to v1.2 in four days, in public, with the commit log as the proof.

What it is, in one sentence

Substrate is the system every external draft passes through before it ships. It is open source, MIT, on github at github.com/k3sava/substrate.

Why it exists

The output of a senior product marketer is a stream of artifacts: positioning docs, homepage rewrites, win-loss reads, launch plans, internal memos. Each artifact has a structural ancestry. The structural ancestry is what AI cannot reconstruct from a prompt. Substrate is that ancestry, written down.

Structural choices

• Each layer is a file. Not a section heading. A file. A reader can clone the repo and grep.
• Each pattern cites three or more operators. A pattern with one citation is a hunch. Three is the minimum for "this generalizes."
• Each skill is runnable from one dispatcher. The dispatcher is a small CLI. Skills are not paragraphs. They are procedures, callable.
• The principles layer is the only one that says no. The other seven layers describe and compose. Principles is the layer with veto.

The eight layers, in dependency order

1. context/. who the operator is, what they carry, what they measure.
2. skills/. 37 procedural moves, runnable from one dispatcher.
3. goals/. what the operator is trying to move, in measurable terms.
4. routines/. when to deploy which skill. cadence and triggers.
5. ux/. the read order. cadence and form of every artifact.
6. calibration/. tier-A insights, brier-scored. what to trust.
7. principles/. the nine code-enforceable rules.
8. reconciliation/. what to do when the system contradicts itself. the eleven known contradictions, each with a resolution path.

The diff, v1.0 to v1.2

What this case proves

Three things, in increasing order of difficulty. One, the operator can write a system. Two, the operator can iterate the system on a public commit log without losing structural coherence. Three, the operator can author a system that an AI can actually read and act on, without the operator hand-holding it.

How to verify

1. Clone github.com/k3sava/substrate.
2. Read PRINCIPLES.md. Pick one principle. Search the patterns folder for the cited examples. Confirm three operators.
3. Run ./dispatch <skill-name>. Confirm the skill executes.