The column now holds five arena SOPs — and none of them says what to do Monday morning. The gap between a standard procedure and an operating machine is itself structured; five layers, each with its own fill:
1. The binding layer (a decision, not research)
The operation's target shape is the matrix — projects × arenas, the grid run as a whole (账号矩阵 is standard industry practice, not an invention; MCNs run exactly this). Each cell of the matrix is a bound tuple — project × arena × format × cadence — and an SOP executes one cell. What stays singular is not the operation but the owner's live attention: one concentration cell at a time (§4b); AI-driven probe cells fill the rest of the grid wherever the judge tolerates machines. Until cells are bound, every SOP is hypothetical. The binding is the owner's decision; what research supplies is the decision table — the labor-price table below, and the fit table here (which is precisely the matrix's map: each row×column intersection is a candidate cell).
The fit table (audience = buyers, per x-account-sop step 1 and when-the-playbook-sells-products principle 2; entries follow the arena files' documented audiences):
| project | buyer | fitting arenas | anti-fit |
|---|---|---|---|
| FlexMesh | gig parcel couriers (CA, incl. 华人) | short-video (the scan demo — cal-ai-the-screen-is-the-ad shape), xiaohongshu (empty driver niche), Reddit (r/couriersofreddit tier) | LinkedIn (couriers aren't there) |
| StandMeet | networked thinkers / builders / recruiters-of-them | Reddit (considered-tool vouching + answer-engine feedstock), X (builder density) | short-video (wrong consumption mode) |
| YouTeacher | B2B school/recruiter buyers | LinkedIn (the buyer sits in the feed) | xiaohongshu consumer lanes |
| Lucerna | language learners (zh) | xiaohongshu (education vertical monetizes — xiaohongshu-open-niches), short-video | Reddit (thin zh-learner presence) |
The resonance criterion (added after the acceptance test exposed its absence): beyond audience-fit and labor-cost, prefer the arena whose mechanism demonstrates the product's own thesis — the generalization of tibo-the-reflexive-pickaxe's principle 1 (sell the pickaxe by swinging it in public). StandMeet × Reddit is the worked example: the arena's answer-engine-feedstock property is the product's interpretation-economy thesis running live; every artifact doubles as proof.
The hours/week rule (no aggregation formula exists here or in the literature; the honest procedure is capacity-first): choose the weekly hour ceiling from real calendar capacity, then admit only SOP components whose documented floors fit under it (floors in the labor-price table). This inverts the natural temptation (pick ambitions, discover the hours don't exist) and matches how the single-channel doctrine below allocates: depth in one, zero in the rest.
2. The room-and-keyword layer (research, fillable immediately)
"Find the right subreddit" and "build the query list" are steps that name their own gap: the actual room list and keyword inventory don't exist until someone assembles them for a specific product. This is agent-work, done once per project×arena. (First fill: FlexMesh × xiaohongshu — flexmesh/growth/xiaohongshu-channel-kit.)
3. The inventory layer (the 10:1 ammunition)
Every SOP demands an idea inventory an order of magnitude larger than output. The seed stock is usually already lying around — for FlexMesh, the Search Console top-25 queries are literally a ranked list of what the audience asks. An inventory is a file with a filter column, not a mood.
4. The instrument layer (SOP steps become tools)
For an operator whose strength is mechanization, a manual SOP step is an unbuilt tool. The three instruments every arena needs:
- idea inventory — one file per project: title-shaped ideas, source, target query, status (the 1000→10 filter needs a place to happen);
- per-post log — date, arena, format variable under test, the arena's binding metrics (the experiment-per-artifact discipline is only real if pre-registered somewhere);
- winners scraper — per arena: pull the niche's top artifacts on schedule, extract invariants (Jenny's method as a cron job; on X it can read the judge's own repo diff too).
4b. The sequencing layer (parallel probes, one concentration)
The tested doctrine is Bullseye (Weinberg & Mares, Traction) — stated precisely, because a compressed version misled the first acceptance-test run: the inner-ring testing stage runs multiple channels in parallel, cheaply; "focus on one" applies to the scaling stage, after a dominant channel shows itself, and holds until saturation or rising costs. The column's cases confirm the concentration trigger is a measured plateau, never a calendar date: Cal AI's organic capped at ~$2M/month before the paid handoff (cal-ai-the-screen-is-the-ad); Tibo's mature acquisition went ~70% non-audience (tibo-the-reflexive-pickaxe); FlexMesh's own search channel flattened at ~1.1k impressions/day.
The AI-automation amendment (owner's corrections, 2026-07-16). The matrix's economics rest on one premise: the agent loop is the production line (an agent loop driving a real browser with a real account — Claude-Code-plus-Playwright class tooling; community skills of exactly this shape exist for every major platform). Without the loop, "production is free" is false and the whole probe tier collapses back to classic Bullseye. With it:
- Probe tier — start every compounding clock on day 1. Arenas with compounding assets run from day 1 at floor cadence, agent-produced, owner-reviewed. Long time-to-signal becomes an argument for early start, not deferral: calendar time cannot be compressed later.
- Per-cell native production, never repurposing. Each cell's agent executes its own arena's SOP — the acceptance test proved an agent can follow one natively. The one-draft-everywhere failure (Jenny's 1M-TikTok/1K-YouTube lesson, jenny-hoyos-craft-is-scrapeable) is a property of naive cross-posting pipelines, and this architecture excludes it by construction.
- "No automation" restated honestly — the judge observes the output stream, not the hands. The Reddit graveyard's actual causes of death were velocity beyond human plausibility, generic slop text, and promo density (reddit-industrialize-and-die) — visible statistics, not automation per se; few platforms can truly detect a real browser, a real account, and per-thread unique answers at human cadence. So the per-arena constraint is a triple: (velocity cap, quality bar, account capital at risk) — keep the stream inside human-plausible rate, pass the human jury's quality read, and know that the account is the stake (terms-of-service forbid undisclosed automation on Reddit; a caught pattern forfeits the account and its karma-capital). Human-jury arenas thus run at human-shaped throughput regardless of who produces — the loop buys draft quality and consistency there, not volume.
- The scarcity ledger rewrites, it doesn't empty: binding inputs become owner review bandwidth (every artifact passes the taste gate — unreviewed agent output rots; the content version of the mechanized-constraints law), idea supply, and experiment-loop attention (N cells = N weekly single-variable reviews). The load-bearing unbuilt components are two, and the order matters: the context pack (per-artifact input assembly — the primary anti-slop control, slop-is-a-context-deficit; its composition and refresh schedule are not designed but derived from the SOP's own dataflow, context-derives-from-the-sop) and the content lint (the mechanical output gate: format rules, redlines, provenance, one-variable tag) as the backstop before the review queue.
Rule, amended: probe cells everywhere from day 1 at floor cadence under the (velocity, quality, capital) triple; concentration one cell at a time, moved only on measured plateau.
4c. The pre-launch layer (what to publish before there are numbers)
The SOPs' provenance-gated genres (revenue counters, transparency posts — metrics-carry-provenance) assume numbers that a pre-launch product lacks. The documented pre-metrics repertoire, from the case files themselves:
- Build the audience before the product: Robinson posted near-daily for two years and 40M impressions before RB2B existed (adam-robinson-radical-transparency); Butcher ran 11 months of daily practice with zero product revenue (jack-butcher-the-format-factory).
- A public, dated, falsifiable goal needs no revenue: Levels' 12-startups-in-12-months was a counter before there was anything to count (when-the-playbook-sells-products; airrack-the-collab-ladder principle 3).
- Process is provenance too: what's verifiable pre-launch is the work itself — commits, designs, experiments, failures. The counter's currency switches from dollars to dated artifacts; the discipline (verifiable, dated, losses included) is unchanged.
- Measurement pre-funnel: the documented pre-launch operators tracked audience accumulation (followers, impressions, list signups) — the funnel gauges (click→trial→paid) attach at launch, not before.
5. The ignition layer (day 0–30 is not the steady state)
SOPs describe running machines. Cold-start is its own checklist per arena: account creation choices (personal vs business, xiaohongshu-redlines), profile-as-landing-page (every arena's "follow" decision happens there), the first 10 artifacts chosen for learning speed not reach, and the measurement hookup (branded-search tracking, referrer tagging) before the first post — or the experiment loop starts blind. The mechanical day-0 checklist — handle/identity locks, the account-path decision, credential hygiene, and the debunking of "account warmup" — is spelled out in account-bootstrap.
The labor-price table (from the case files)
| Arena | documented floor | documented extreme | marginal cost shape | time to first signal (documented) |
|---|---|---|---|---|
| 20 min/day (gummysearch-reply-not-post) | — | flat; capped by no-automation rule | weeks — 60 customers in 45 days (reddit-conversion-receipts) | |
| Xiaohongshu | batched writing, ~2–3 notes/week | — | low; notes compound via search | weeks–months; search tail pays 6–12 mo (xiaohongshu-search-is-the-moat) |
| X | 1 insight <5 sentences/day (nikita-bier-sell-the-spike) | 700 posts/yr (Welsh) | linear in posts | ~6 months — the floor formula's own horizon (Bier) |
| ~30 min around publishing | 4–5 h/day (lara-acosta-outwork-the-feed) | linear in engagement time | months–years — Robinson posted 2 yrs pre-product (adam-robinson-radical-transparency) | |
| Short video | atomize from existing footage | 80–100/day (okamoto-the-cadence-extremum) | high fixed (production) unless the product makes the footage (cal-ai-the-screen-is-the-ad) | per-artifact — a zero-follower account can hit day one |
The composite rule, derived from the table's two cost columns (not from arena names): a solo operator's first arena is the one where hour-floor fits the budget AND time-to-first-signal fits the decision horizon — cheap minutes with a six-month signal horizon (X's floor) is not the same bet as cheap minutes with a 45-day receipt (Reddit). Linear/high-cost arenas are entered only with a format that amortizes (fixed grammar, atomization) or the product manufacturing the content itself. (Wording amended 2026-07-16 after the acceptance-test executor was steered by the rule's original phrasing — which pre-named arenas — rather than by the table's data; the missing variable was time-to-signal.)