This revision starts with a reckoning, because the last memo earned one. Its #1 pitch (conviction 9) reduced to a single human act: press send on the Friday newsletter draft. In the sixteen days since, the draft cron ran faithfully every Friday, and the send count is zero; /changelog still says the first issue lands soon. Meanwhile the commit graph gained roughly a dozen brand-new surfaces, three new games, two complete audio-show infrastructures holding one episode each, and a full Ukrainian edition. The strongest work of the window was real (the workflow kernel, its first product, and a consolidation wave that started paying down sprawl), and one correction in fairness: client work IS live in the project portals, so the machine has served real people. But the experiment's result is unambiguous: when a distribution act competes with a building act, building wins every time. The full audit behind this memo is on file in the repo's strategy docs. So this memo changes genre. The last one made bets; every pitch below is a mechanism, a sale, a writeup, or a pruning. The site is no longer the thing being built. The audience and the first dollar are.
PITCH 01 · THIS WEEK, THEN STANDING
Default Send
The last memo asked a human to press send every Friday, and named the failure mode itself: silence, not bugs. That is exactly what happened, twice. The lesson is not try harder; it is that gates requiring an active approval go unapproved when approval competes with building. So invert the gate: the newsletter and the social studio go default-publish with a 24-hour veto window. Distribution stops being willpower and becomes plumbing, which is the one material this site never runs out of.
Already on the board
- The Friday draft pipeline runs on schedule and works; two complete issues have already been drafted and are waiting
- The social studio drafts per-network posts through a critic and a human gate, with Telegram-side approval already wired
- One shared, tested red-line module (src/lib/red-lines.mjs) now runs on the LinkedIn, social, and newsletter paths, so a default-send cannot ship what a gate check blocks
- /changelog, the feeds, and the subscriber list are live and have been since June
The bet
Flip the newsletter to send-unless-vetoed and the social studio to publish-three-a-week-unless-vetoed. The veto arrives on Telegram with a full preview and a day to act. This is roughly two days of work against the single highest-leverage behavior change available: it converts the demonstrated 100% building-beats-sending record from a character problem into a solved engineering problem, and every other pitch on this page inherits the rails.
First 90 days
- Ship the veto-window send path for the newsletter; the first default-sent issue goes out this Friday
- Same inversion for the social studio at three posts per week
- Success metric, stated in advance: eight consecutive weekly issues sent by September 1
The honest risk
An unvetoed mediocre issue ships publicly; the red-line checks and the preview window are the guard, and a mediocre sent issue still beats a perfect unsent one. The deeper risk is vetoing everything, which rebuilds the old failure with extra steps. If the veto rate exceeds half, that is the signal to fix the drafts, not the mechanism.
The Priced Engagement
Last memo's Studio of One was the only pitch that got real follow-through, and it stopped precisely where code ends and selling begins: the offer page went up without a price, and a complete delivery spine was built for a customer nobody has yet contacted. The remaining work is not a commit. Put a number on the page and run a real outbound motion. One signed engagement retires more uncertainty about the independent path than everything shipped since June.
Already on the board
- /hire/agentic-workflows is live: the productized install-an-agentic-workflow offer with FAQ and structured data
- The full engagements delivery spine: lifecycle, templates, delivery admin, client nudges, handoff packets, case-study leg
- The billing rail is configured live end-to-end; the proposal pipeline and outreach console exist with drafted campaigns waiting
- Proof artifacts a buyer can verify in the public repo: the workflow kernel, the playtest rig, the ops harness, the court-collections console
The bet
A fixed price on the page (a number, not a call to settle it), then ten targeted contacts a week for six weeks aimed at teams adopting agent workflows, run through the outreach and proposal machinery that already exists. The offer sells the exact capability this repo demonstrates in public, which is the rare position where the portfolio and the product are the same artifact.
First 90 days
- Put the fixed price on /hire/agentic-workflows this week
- Ten outbound contacts per week for six weeks; every one logged in the pipeline it will be worked in
- Close one design-partner engagement; publish the case study through the (now default-sending) rails when it lands
The honest risk
Outbound is the muscle with zero recorded reps, and the honest risk is not rejection but substitution: building one more surface instead of sending ten emails. The other cost is real too: a signed engagement eats the calendar that currently feeds the commit graph. That trade is the whole point.
The Front Door
A stranger gets ninety seconds, and right now those seconds land on 349 routes where the correlation between impressive and visible runs close to negative: the strongest engineering is deliberately private, while the public face leads with volume. The same inventory, curated, reads completely differently. Lead with five artifacts, demote everything else to an index, and clear the credibility landmines a skeptic finds in five minutes.
Already on the board
- The five lead artifacts exist and are public: the agent-operating discipline itself, the workflow kernel and its governance, the court-collections console's trust boundary, the self-verifying Claims Ledger, and the smart-house manager's honest telemetry
- /architecture already maps the whole system and is the raw material for the curated tour
- The landmines are named and filed as issues: the temporarily public admin tool, the synthetic benchmark data, the credits recovery gap, and committed personal data
The bet
Curation is days of work, not weeks, and it converts the repo's illegible depth into a legible reputation for every audience at once: the engineer who might hire, the reader who might subscribe, the client who might buy. Close the four filed issues first; a public evals page with placeholder numbers and an ungated admin tool each undo more credibility than a new surface can add.
First 90 days
- Close the four landmine issues (#1803, #1804, #1805, #1806)
- Rewrite the homepage to lead with the five artifacts and an honest one-line story: one person plus agents, everything verifiable
- Write the court-collections case study as the first client-facing proof page
The honest risk
Curation means demoting things that were fun to build, and the temptation is a sixth tile, then a seventh, until the front door is the old homepage again. Five means five. The other risk is treating the landmines as someday-cleanup; they are the cheapest credibility on the page.
PITCH 05 · NOW, THEN STANDING
Close the Studios, Count the Burn
Fully-furnished empty studios read to outsiders as a character trait: a podcast with complete tooling and one guest, a critique show with one self-audit, an empty broadcast archive, rich media for 2 of 192 anthology selections. Each was cheap to build and none is free to keep. Meanwhile roughly 47 scheduled jobs call models on cron and no consolidated number says what that costs per month against zero revenue. Independence is a runway equation, and the burn is the unmeasured half.
Already on the board
- The consolidation wave already started and proved the instinct: shared tenancy, calendar, and feed cores extracted, eight game shells collapsed, one retirement honestly marked blocked
- The status page and health canaries exist to absorb a mothball register
- The surface-doc system gives every surface a place to be marked frozen, with its crons disabled in the same PR
The bet
A formal mothball ledger (frozen surfaces stay frozen until the thing they lack exists: a booked guest, a real episode, a real benchmark run) plus the one dashboard the site does not have: which scheduled jobs fired last week, which silently did nothing, and one monthly model-spend number with a hard ceiling. Pruning is what makes the four pitches above believable, because it is the visible proof that building is no longer the default response.
First 90 days
- Publish the mothball register and disable the frozen surfaces' scheduled jobs
- One real benchmark run replaces the synthetic data, or the page unships
- Ship the spend-and-fired dashboard with a monthly cap, and cite its number in the next memo
The honest risk
Mothballing feels like admitting failure, and reopening is always one commit away. The register only holds if reopening requires the missing ingredient rather than enthusiasm. And the burn number may be embarrassing in either direction: too high says the factory is expensive, too low says the constraint was never money. Both are worth knowing.
If I had to pick the order
01 first and this week: it is two days of work, and every other pitch inherits rails that actually fire. The landmine subset of 04 goes right behind it (the issues are filed; each is hours). 02 is the quarter's real deliverable: the price goes on the page now, and the outbound cadence runs the whole window. 03 feeds 02 one essay a week, and 05 runs alongside as the standing discipline that keeps the factory from reabsorbing the calendar. The rule that makes this a memo instead of a wish, stated plainly: until September, a week with zero new surfaces and one act of distribution is a good week, and any new public surface is a memo violation. The scoreboard the next revision will be graded on: issues sent, contacts made, one engagement signed, and the burn number, all cited as numbers. Not commits. Commits were never the constraint.