Name the load and lock its temporary scope.
Directional operating view · between strategy and station detail
The issue operating blueprint
What starts a run, who owns each movement, where Steve approves, what stops the line, and where failed work returns. The factory page explains the stations; this page explains the direction.
One named issue moves forward. Every rejection moves backward to a named owner and station.
Control principle
No conversation creates a process change by itself. This blueprint changes only when an observed run exposes a gap and Steve explicitly approves the scoped correction.
Entry conditions
Three triggers open the same line
The load changes. The production path and approvals do not.
ClockDaily micro-run
Small real load used to expose friction.
CalendarSunday issue run
Full source window for Monday delivery.
SteveManual commission
A named test, special issue, or directed brief.
Required artifactRun charter
Issue name, date, audience, scope, source window, and purpose.
Primary direction
Trigger to published evidence
Owner labels sit above the work. Gate steps can stop or return the issue; ordinary steps cannot approve themselves.
Work movementSteve approvalEvidence checkExternal stop
Links, dates, provenance, context, and candidate signals.
Confirm the record, novelty, relevance, and prior use.
Choose what earns attention and build the issue thesis.
Subject, opening, headlines, pace, transitions, and payoff.
Recheck claims, logic, novelty, balance, and overstatement.
Editorial package complete↓Production and release
Approve this named lineup and copy—or return it.
Apply V5.6 hierarchy, imagery, links, poll, and footer.
Confirm Steve is the sole recipient and obtain approval for this one test.
Gmail desktop, phone, actual From address, links, image loading, and footer.
Approve the exact send after received-form proof.
Deliver, observe response, and open the next evidence loop.
Return directions
Where the work goes when it fails
A failed check repairs one station. It does not rewrite the entire operating system.
Evidence fails←Source pack
Correct, replace, or kill the candidate.
Issue is dull←Copywriter
Repair the hook, thesis, pace, and reader payoff.
Language outruns proof←Copywriter + source
Narrow the claim or strengthen the evidence.
Steve returns it←Named failed station
His approval note identifies where it goes—not a global rewrite.
Received form breaks←Design & assembly
Repair the rendered email, then send another private proof.
From display is materially wrong■Return to Beehiiv setup
Repair only if the received proof shows a real delivery or trust problem.
Approval architecture
Four gates, three scoped human decisions
Steve approves editorial direction, the private self-test, and final release. Evidence gates enforce objective conditions.
| Gate | Owner | Pass condition | Failure direction |
|---|---|---|---|
| Evidence | Research worker + skeptical editor | Reachable record, current date, relevant event, no material unsupported claim. | Back to source pack or remove the story. |
| Editorial | Steve | The named lineup and copy are worth the reader's attention. | Back to selection, copywriter, or challenge—as named. |
| Private test | Steve + received proof | The exact issue is approved for one-recipient delivery and the real From display, links, layout, poll, and footer are inspected. | Back to the failed production station; do not publish. |
| Release | Steve | The exact received-form issue is approved to send. | Back to the failed production station. |
What this blueprint governs
- The direction of one issue through production.
- Named ownership and handoffs.
- Stop/go approvals and return routes.
- Evidence captured from the delivered result.
What remains flexible
- Which AI model performs a worker role.
- The size of a daily micro-run.
- Optional sections that do not earn content.
- Candidate craft techniques that have not been selected.