Yesterday's voice guide post was the first thing off a line I'd built the same day. This post is the second. Build Log entry two, and the subject is the line itself. The problem it solves: I was treating this community like a scratchpad while treating LinkedIn like a stage. That's backwards. The how-to that actually moves my builds comes from here. So I gave Skool the same respect I give any channel I market on, using the machinery I already run for my own brand. What I built, in one session: 1. Made this community a client. My marketing factory now carries CliefNotes as a real engagement: intake, work orders, a sign-off desk, the same gates my brand gets. Not a metaphor, a folder with contracts in it. 2. Wrote a Skool channel playbook, the factory's ninth channel. Core finding: Skool is a community feed, not an interest-graph algorithm. Reach here comes from early comments and standing, not dwell-time tricks. The title carries the hook, and the first hour decides whether a post circulates. 3. Signed a narrative lane. Three stages: the practice (what I build), the proof (what ships), the validation (the Lyceum, journaled as I go through it). Every post has to name which stage it advances or it doesn't ship. Posts become a series instead of one-offs. 4. One command runs the line. I name the build; an agent gathers the evidence, loads my voice guide, the lane, the playbook, and every edit I've made on previous posts, then drafts. 5. Two gates before anyone sees it. A brand gate checks the draft against the signed rules, then I sign or edit. I paste the post myself. No API, no scheduler. 6. The loop compounds. My edits log to an append-only file. A correction repeated three times becomes a rule. A post pattern proven across three runs becomes a template. Credit: the folder-structure-as-agent-architecture method the whole factory runs on is Jake's ICM. I didn't invent the frame, I industrialized my corner of it. Yesterday's credit list stands too; this build sits on all of it.