foundationThe Prolific Publisher
Publishing is not a mood. It is an engineered loop: capture → draft → compress → distribute → feedback.

Does this sound familiar?
- You have ideas, but they leak before they land anywhere
- You start drafts, then stall inside editing and research
- You publish inconsistently and call it a "quality bar"
- You treat distribution as optional and hope the work spreads
- You end weeks with drafts and tabs, not shipped assets
- Rely on inspiration and memory
- Mix planning, drafting, and editing until you stall
- Use research as productive avoidance
- Post and pray
- Capture signal with low-friction nets
- Draft in sprints with mode separation
- Compress hard to increase signal
- Run measurable distribution loops
Common Myth
Prolific output requires more discipline and more inspiration.
Mechanism
The 5 Publishing Systems
Click a system to explore its habits

Idea Capture Nets
Reduce idea half-life. Close open loops. Keep a ready queue of draftable seeds.

Drafting Sprint Engine
Separate modes. Write on a timer. Protect flow by banning research and micro-editing.

Distribution Loops
Package for transmission. Measure channels. Convert peers and readers into repeatable growth.

Editorial Compression
Increase signal-to-noise with mechanical edits: cut, activate verbs, remove wind-ups.

Writer Hardware & Identity
Protect sleep and prime cognition. Reinforce an output identity by tracking shipments, not hours.
Progression
Habit Tiers
Foundation
Under 10 minutes. Remove friction. Install capture surfaces. Start sprints. Add shipping cues.
Growth
5–45 minutes. Make loops measurable: one-tap capture, UTM tracking, repeatable hook checks, structured edits.
Mastery
Weekly operating cadence. Triage the inbox, chain sprints, run partner pipelines, and review performance.
Titan
Acute tests. Publish daily for a week. Draft without backspace. Run long input-free output blocks.
The Protocol
Morning: output first
20mWrite before messages. Get a proof-of-work chain started.
During the day: capture without negotiation
15s–2mCapture quickly, tag immediately, and dump into one inbox.
Drafting: sprint mode
20mWrite continuously. No research. Use <TK> markers.
Before shipping: compress and package
30–60mCut 10%, remove wind-ups, strengthen verbs, then write the hook and add a practical asset.
Weekly: review and re-aim
30mAudit what shipped and what performed. Fix one system, not everything.
Getting Started
Week 1: stop the leakage
Install capture surfaces and a one-tap button. Tag everything at capture. Build a small queue.
Week 2: draft on a timer
Run daily 20-minute sprints. Use placeholders. Protect flow by closing inbox tabs and moving the phone.
Week 3: ship with transmission
Run STEPPS checks, add visual anchors, and make distribution measurable with UTMs.
Week 4+: make it a loop
Add weekly triage + Sunday review. Prospect partners. Systematize what works and kill what doesn’t.
Frequently Asked Questions
Protocol Playbooks
Curated sequences of habits designed to be practiced together. Click a playbook to see its cards in the deck below.

Zero-Friction Capture Install
Stop losing ideas. Build a reliable capture surface and a draftable queue.
+4 more habits

Two-Sprint Draft-to-Ship
Draft fast without research thrash, then compress hard and ship.
+6 more habits

Pre-Publish Transmission Audit
Package for spread: hook, STEPPS, visual anchor, and measurable links.
+3 more habits

Sunday Publishing Review
Close loops, improve one system, and plan next week’s shipping.
+2 more habits

4-Hour Output Block
A mastery test: no new inputs, stable execution, and a shipped artifact.
+3 more habits
Quests
Challenges to accelerate your transformation. Click a quest to see its target cards.
The Signal-to-Draft Bridge
Install capture tools, enforce the 20-second rule, and complete your first shitty draft with TK placeholders.
"Stop waiting for the muse. We build nets for the signal and engines for the raw output."
The Sprint Engine Protocol
Master the Drafting Sprint Engine by removing distractions, chaining sprints, and writing without a backspace key.
"Writing isn't thinking; it's a mechanical process of extraction. Keep the keys moving until the draft is done."
The Monastic Output Block
Execute a 4-hour input-free block to prep and publish a piece, then ship an edited asset in 60 minutes.
"The ultimate test of a publisher: four hours, zero inputs, one shipped artifact. Close the loop."
The Full Deck
40 habits across 5 core systems
foundation
foundationEnforce the 20-Second Capture Rule
foundationTag Ideas at Capture
growthCreate a One-Tap Capture Button
growthDictate a Voice Note to Your Inbox
masteryRun a Weekly Capture Triage
masteryBuild a Controlled Tag Vocabulary
titanCapture 20 Ideas in One Walk
foundationStart a 20-Minute Writing Sprint
foundationWrite a Shitty First Draft
foundationInsert Placeholders Instead of Researching
growthClose All Inbox Tabs Before Drafting
growthMove Your Phone Out of Reach
masteryChain Two Sprints Back-to-Back
masteryWarm Up With Copywork
titanDraft One Piece Without Backspace
foundationRun a STEPPS Check
foundationWrite a Curiosity-Gap Hook
foundationAsk for a Reply in the Welcome Email
growthAttach a Visual Anchor
growthAdd UTM Tracking to Promotions
masteryProspect Five Similar-Size Partners
masterySend a Swap Outreach Email
titanPublish a Week of Daily Assets
foundationCut 10% of the Draft
foundationDelete Wind-Up Sentences
foundationRewrite One Paragraph With Active Verbs
growthApply the Paramedic Method to One Page
growthCompress the Title Into a Promise
masteryHunt and Replace Weak Modifiers
masteryAdd a Practical Asset Before Publishing
titanShip an Edited Piece in 60 Minutes
foundationRead the Draft Before Sleep
foundationWrite Before Checking Messages
foundationModel the Reader's Objection
growthAsk Your Brain a Question Before Bed
growthInspect Five Sources Instead of Reading One
masteryTrack Shipments, Not Hours
masteryRun a Sunday Publishing Review
titanBuild a 4-Hour Input-Free Block
Sources & References
External reading that informed this stack.
- 01
On Finished and Unfinished Tasks (Zeigarnik Effect)
Zeigarnik (1927)
gwern.net
- 02
Attention residue when switching between work tasks
Leroy (2009)
ideas.repec.org
- 03
A Cognitive Process Theory of Writing
Flower & Hayes (1981)
fsuprelims.weebly.com
- 04
Contagious Framework (STEPPS)
Jonah Berger
jonahberger.com
- 05
Paramedic Method for Revising Prose (PDF)
Purdue OWL
cla.purdue.edu
- 06
Creative Networks: coupling of default and executive control networks
Beaty et al. (2015)
scottbarrykaufman.com
- 07
Brain Drain: The Mere Presence of One’s Own Smartphone Reduces Available Cognitive Capacity
Ward, Duke, Gneezy, Bos (2017)
repositories.lib.utexas.edu
Explore More Identity Stacks

The Analog Anchor
A protocol stack for interrupting compulsive dopamine loops, rebuilding baseline calm, and restoring deep focus with analog friction.

The Antifragile Stoic
A protocol for turning stress into signal: controlled exposure, ruthless control, recovery baselines, attention discipline, and after-action review.

The Process Purist
Eradicate performance anxiety by blinding yourself to outcomes and obsessing over the mechanical execution of your daily kernel.