Operator-published, day-stamped. Updated weekly. Members react with the five reaction kinds; the operator publishes a one-line note when reactions shift the plan. Indications are non-binding — only Hall proposal votes are.
This week — week of 2026-04-27
The first wave is content + the Stripe live transition. Specifically:
- Seed the first 5 cited Elephants. Refusals against TikTok / Instagram / LinkedIn / Meta + a general-incumbent refusal. Each requires ≥2 verbatim citations from the incumbent's own engineering blog or public statements.
- Stripe live in production. Beat 3 of the homepage graduates from Reserve to Become Founding Patron #N — payments take place via Stripe Checkout, the webhook lands the role row, the welcome email goes out.
- Founder + sons + collaborator become Patrons #1 through #4. The wall starts populating. The 4× tier counter starts ticking down.
- Publish ADR 0002 (Attention Discipline) and ADR 0003 (Operator-power Sunsets). Both have markdown bodies on disk + DB rows registered via
/hall/admin/adr/new. - Open the first OpenQuestion — "What should the first paid flagship product be?" — at
/questions. Members indicate non-bindingly between 4 categories.
What's coming next week — week of 2026-05-04
- First wave of personal-network outreach. ~10–20 individual messages to people who already follow the operator's work. Each carrying a referral.
- First daily wrap-up published at
/build-log/day/<date>. Narrates the launch-week progress. - Second batch of Elephants (3–5 more refusals). Different incumbents.
- First member-drafted Comparison expected (anyone signed in can draft via
/features/[slug]/compare/new; operator reviews and publishes).
Beyond — month of May 2026
- Patron #50. First milestone wrap-up + open the second OpenQuestion (driven by the first one's indications).
- First Wishes from members outside the operator team. When a non-operator member posts via
/wishes/from-app, the chain is no longer operator-only. - First member draft promoted to a published Comparison. Dual byline appears for the first time.
How this page works
The operator publishes intentions; members can't bind the operator with reactions, but reaction patterns inform what the operator picks up next. The page updates weekly. The history is visible in the git log of content/en/next.md — every edit is a commit.
If you want to push back on any of this:
- Open a wish at /wishes/from-app — naming the incumbent and the betrayal you'd want refused next.
- Sign the Constitution to lock the eleven commitments above the operator's daily plan.
- Become a Founding Patron — the wall is the first row of accountability; one click on your name lets you read every commit since you joined.
The roadmap is operator-owned for v1. The visible-causality memo notes a future surface where members spend daily priority points across upcoming items; that's deferred to v2 once the first 1,000 Patrons are real and the rhythm is established. For now, indication is the right friction.