Discover
Collect current signals and primary records. The old four-layer source scheme is useful evidence, but it is not promoted into this new line without a live run.
Operating view · current baseline plus tested history
The issue factory
A miniature daily issue and the full Sunday issue use the same line. Volume changes; the stations do not. The next run is designed to expose breaks, not disguise them.
Open the line small. Find the break. Repair the station. Run it again.
One production contract
Every issue carries sources, a named copywriter pass, an independent challenge, visual treatment, Steve's approval, a delivery proof, and a recorded result. A failure returns to the station that caused it.
Traditional production-line view
The line, the checks, and the return routes
The belt carries one named issue. Diamonds are stop/go decisions. The blue return line carries observed evidence back into the next run.
Production movementHuman approvalProof requiredFeedback return
Daily test: a small load on this same belt. Sunday run: the full load.Nothing downstream of a failed gate moves forward.
Four operating zones
Raw signal to delivered issue
Current or observedCarried from evidenceMust be provenBlocked
Zone 01
Wire room
Normalize & dedupe
Turn mixed inputs into a consistent source package and prevent the same event from masquerading as multiple stories.
Evidence screen
Confirm the actor, date, reachable record, and whether the event has already run. Old kill-gate language is a candidate starting point, not newly approved doctrine.
Zone 02
Editorial line
Select & order
Choose what earns attention now and order it for the reader. Issue 00 proves that judgment can produce an issue; the current selection method still needs a clean test.
Copywriter pass
After evidence and order are settled, rewrite for attention: subject, human opening, governing thesis, headlines, transitions, pacing, and reader payoff. An accurate analytical draft does not satisfy this station.
Challenge & check
After the copywriter pass, check claims, links, completeness, tone, and whether the language outruns the source before the issue reaches Steve.
Zone 03
Production floor
Visual treatment
Apply V5.6: official logo, email palette, six-level type hierarchy, weighted imagery, lead CTA, binary poll, and minimal footer.
Beehiiv assembly
The current V5.6 template and miniature issue contain the full section structure, direct sources, native poll, and clean desktop/mobile previews.
Steve review
Steve approves or cuts the named issue. Approval of an issue does not silently approve every method used to make it.
Zone 04
Shipping dock
Sender & compliance
The shared Beehiiv sender is acceptable for the current baseline. Verify its actual display in the received proof; revisit a custom domain only if evidence warrants it.
Private test send
After Steve's scoped approval, send the miniature issue only to Steve, inspect Gmail desktop and phone, and correct only the failures exposed outside the editor.
Publish & learn
After proof, publish the named issue, observe delivery and reader behavior, and return the evidence to the next production cycle.
The repeatable loop
Small test and full issue
The daily exercise is a small issue through the real factory, not a new template every day.
1 · Open the run
Name the issue, date, target, and what the run is meant to prove.
2 · Build source pack
Gather evidence and preserve links, dates, and provenance before drafting.
3 · Copywriter pass
Turn the verified story order into an issue someone would open and finish. Accuracy alone does not pass.
4 · Challenge the copy
Recheck evidence, overstatement, novelty, logic, and whether every section earns its space.
5 · Assemble & test
Build in V5.6, then inspect the received desktop and phone form, links, poll, sender, and footer.
6 · Steve gate
Approve the named send or return it to the failed station.
7 · Publish
Use the same line for a tiny daily test or the complete Monday product.
8 · Record result
Capture what actually worked, failed, changed, and remains uncertain.
9 · Improve one station
Repair the observed fault. Do not convert every workaround or conversation into doctrine.
Failure loop
A broken From display, link, layout, source claim, or poll returns to its station. It does not trigger a system-wide rewrite unless the evidence shows a structural problem.
Learning loop
Useful reader response, delivery evidence, and Steve's explicit choices update the next run. A repeated pattern may later justify a scoped rule—but only through the promotion gate.
Daily micro-run
- One lead or a very small story set.
- Real evidence and real Beehiiv assembly.
- Private send until the line is trusted.
- Purpose: expose friction quickly.
Sunday production run
- Full source window and complete issue.
- All current sections filled only by content that earns them.
- Full received-form QA and Steve gate.
- Purpose: deliver Monday's reader product.