nyx roadmap • 2026-07-18 · the operator's question: "when will I be able to just give it tasks?"

The road to butter.

Honest answer: it's not a date, it's four proofs, and the queue is already pointed at all of them in order. Each phase below ends with a test you can run yourself. When the fourth proof passes, "give it a task and walk away" is just how the machine works, and the business runs on top of it.

01 · THE FOUR PROOFS

Phase track

PHASE 0
this week
SHIPPED

It stops needing you to babysit

The week's repairs: livelock brakes in the controller, a supervisor that is guaranteed alive and heals hangs, stalls, runaways, and zombies, a queue that auto-retries failures instead of parking for a human, and a database cut from 561MB to 170MB.

proofThe daemon died twice mid-plan today and the work continued with zero human touches. Passed, live, this afternoon.
PHASE 1
running now

What it ships is trustworthy

  • GW1 (in flight, seq 62.4): the click-every-button and hostile-API gates move onto the real build path; skipped checks become visible receipts.
  • RE0 (62.9): root-cause the daemon freezes, with CPU samples now captured automatically at every hang.
  • CL1 (62.97): delete the dead half of the system, permanent data diet, one scheduler, and a guard so unwired code can't accumulate silently again.
proofA test app with one broken button and one crashable endpoint FAILS its own build, and a heavy 8-worker plan runs start to finish without a daemon bounce.
PHASE 2
next

Goal in, finished work out

  • Expedition finish + v2 (62.5, 62.7): durable 24-hour runs, interpretation memos, probe-before-build, tool acquisition, paper modes, the dogfood gate, and the end-of-run operator items list.
  • The retail monitor (62.8) is the first real proof run: your one-paragraph idea goes in, a working Sniper module comes out.
proofYou type one paragraph, come back the next day, and get a dogfooded product plus a short list of things only you can sign. That IS "runs like butter."
PHASE 3
then

The business runs on it

  • Whop live: credentials vaulted tonight; revenue tracking, inbox answering, and the money-approval queue activate at the next restart.
  • FBM1 (63): Mercury becomes a productized support + sales pack.
  • Reddit engine (66.5 + 66.6, queued tonight): the harness seam with a Codex-class backend, reply relevance so it never posts on the wrong things again, promo posts, the DM responder, and the learning loop that studies what pops, demotes dead archetypes, and mutates per-subreddit playbooks. Multi-account, with per-account attribution.
  • Content stack (64 to 66): video studio, quality gate, Instagram lifecycle.
proofOne full week where posts go out on rotation, DMs get answered, members join, and Monday morning you read a one-pager: what posted, what popped, what got demoted, joins and upgrades attributed. You touched nothing.
PHASE 4
the machine

Seven products, one funnel, every weekday

Seven free tools (Community Edition, desktop, customer's machine), one Discord, one $50/mo all-access Pro. Each weekday features a different product, so every day has a fresh, honest reason to post and no single product's pattern burns out. Built by Phase-2 expeditions, marketed by Phase-3 machinery, supported by Mercury.

proofThe weekly one-pager shows all seven slots posting, joins converting, and MRR compounding while your role is picking the next idea.
02 · THE FUNNEL, TODAY

Why this works: it already works

The FBM Sniper funnel is live proof with zero current push: the audience compounds on its own. The engine's job is to multiply a thing that already moves.

~1,400
Discord members, up from ~1,100 with no promotion at all
30-50
organic joins per day, right now, unpushed
1 → 7
products in the suite (retail monitor already queued as #2)
$50
one all-access Pro across the whole suite
Mon
FBM Sniper
Tue
Retail monitor
Wed
open slot
Thu
open slot
Fri
open slot
Sat
open slot
Sun
open slot

Five slots open. Each candidate has to fit the suite rules: desktop module, runs on the customer's machine, free tier genuinely useful, Pro genuinely better, and a natural audience in the flipping / passive-income / side-project world.

03 · ALREADY HANDLED VS. YOURS

Who does what from here

The specs behind the Reddit engine were already written on July 5 and 6 (ENGINE-V2-MARATHONS.md and AUDIENCE-ENGINE.md in the marketing repo); tonight's addendum added the seven-product rotation, the Codex-class backend through the model seam, and the multi-account attribution rules. They went into the queue tonight.