Show your work: the folder structure behind my Skool post production line

Yesterday I posted that I built a production line for these posts. This is the walkthrough, in the category built for it. If folder trees bore you, skip this one.

The whole system is folders and markdown. No database, no framework, no orchestration code. One agent walks the structure and the structure does the orchestrating, which is Jake's ICM in one sentence.

The tree, client-identifying detail removed:

```

marketing-factory/

_config/channels/skool.md <- channel playbook (the 9th channel)

clients/cliefnotes/

CLAUDE.md <- engagement identity: two pointers, no copies

STATE.md <- jobs table, position only

work-orders/ <- one brief per job, intake to close

campaigns/skool-posts/

brief.md <- the signed narrative lane

calendar.md <- series map: which run advances which arc

STATE.md <- campaign position, one writer

runs/01..03/ <- evidence.md, draft.md, learning.md per post

signoff/ <- drafts wait for my signature here

approved/ <- the only exit

```

How it actually runs:

1. Two pointers instead of copies. The engagement identity file holds two lines that matter: business truth points at the community workspace's own identity file, and voice points at my signed voice guide. Neither is ever copied in. One source of truth each, so nothing drifts.

2. Plans and position never share a file. brief.md and calendar.md are plans. STATE.md is position, and only the step that moves work writes it. When something reads wrong, you know exactly which file lied.

3. A run is three files. evidence.md proves the build happened and names which stage of the signed arc the post serves. No stage named, no post. draft.md is the copy. learning.md is append-only and captures every edit I make at sign-off.

4. Two gates, one exit. Drafts are checked against the signed artifacts: voice guide, channel playbook, the lane, and a disclosure sweep that fails the draft if a client name, a dollar figure, or an infrastructure identifier shows up. Pass that and it reaches my signoff desk. approved/ is the only door out and I hold it.

5. One command runs the line. I name the build, the agent walks everything above, I see a finished draft. This post shipped through a series that didn't exist this morning. Adding the series was edits to three markdown files and a signature.

The validation is structural, not ceremonial: routing files stay small, content lives on the shelves, and state is plain files a human can open. If you can't tell what state the system is in by reading the folder, the structure failed.

Credit stands where it has all week: the frame is Jake's ICM. The industrialization is my corner of it.

Steal the contract set: one identity file holding pointers, one state file with one writer, one signed brief naming your arc, one append-only log of your own edits. Four files and you have the discipline without any of my machinery.

Drafted by the line, edited and signed by me. Third time.

0 comments

Show your work: the folder structure behind my Skool post production line