NEXT
45–60 MIN · FOCUSED · READY
Verify the paid checkout path
Walk the real subscription and Beehiiv/Stripe checkout path end to end without buying, changing billing, or publishing.
Flexible operating surface · working snapshot
Move the next constraint.
The board follows available time and attention—not office hours. Pick the capacity you have; the system shows useful work that can move without reopening the whole project.
Last live production check6 Sep 2026Static snapshot. Reconcile against NOW.md and live services before changing state.
The current run
A fresh V5.6 issue now reaches clean desktop and mobile review
Issue 02 is sourced, written, claim-checked, and rendered. It has not entered Beehiiv. X and Grok Bot remain parked; the next gates are Steve's editorial review, checkout proof, and controlled received-email QA.
01 · complete small testSource packGmail + Innermost Loop
02 · completeCopywriterIssue language selected
03 · scoped approvalEditorial directionClosed for this draft
04 · verifiedBeehiiv assemblyV5.6 desktop + mobile
05 · liveWebsite + signupRoot site → Beehiiv
06 · waitingProof → releaseReceived Gmail form
Evidence in handCandidateSteve decisionBlockedDownstream
Capacity selector
What kind of session do you have in you?
This changes the recommendation only. It does not schedule work, change status, or write a rule.
High level → detail
Six business lines share one operating spine
Enter only the line needed for the decision or work in front of you.
01
Product engineSignals become a useful weekly issueBlueprint → factory → craft
Current line
02Source engineFind, verify, preserve provenanceGmail + Innermost Loop active for test; X parked
Partial
03Reader experienceBrand, email, website, voiceProduct site live + V5.6 template verified
Working
04DeliveryBeehiiv, received-form proof, releaseDraft verified; test send requires scoped approval
Open gate
05RevenueAudience, acquisition, payment, renewalRails mapped; first complete loop unproved
Open
06Operating spineAuthority, versions, assets, handoffsGitHub pointers + R2 manifest + Steve gates
Working
Parking area
Visible, contained, and off the critical path
No workaround. Resume the narrow X-scout only after Steve resolves the account connection.
The V5.6 draft is ready. A private test may go only to Steve after explicit approval; nothing is scheduled or published.
These are ZTS operating rails, not TNP production work. They stay outside this board’s critical path.
The guide set
Move from the board into the exact level of detail
01
Big Board
02Product promise, enterprise loop, reference landscape, and horizons.
Operating Model
03Who controls the work, where continuity lives, and how evidence returns.
Operating Blueprint
04Triggers, file handoffs, approvals, stops, and named return routes.
Factory Floor
05The issue-production line, its stations, and the small-run/full-run contract.
Technology Stack
06Inputs, workers, GitHub, R2, publication surfaces, and observed results.
Authority + Assets
07What can speak, what cannot promote itself, and where each file belongs.
Craft Studio
08Copywriting, skeptical editing, image direction, design, and taste development.
Brand Identity
09Core system, scoped email application, and actual product examples.
Revenue Engine
10Audience spine, controlled channels, conversion, payment, and renewal.
Readiness
11Recorded state, next proofs, external stops, and downstream work.
Project + Worktree Model
How Steve runs concurrent tasks without becoming the memory courier or letting chats collide.