SATURNSWARM BUILDING

SATURN SWARM · FLEET SHELL

Cursor-class. Never idle.

Fleet shell for huge AFK multi-agent swarms that keep growing the portfolio — measure, queue, claim, craft, ship, prove, arm. SaturnDesign craft and revenue/ads automation sit first-class. Public posts stay a human Gate.

No download yet — client still building. Honest next step is waitlist: izzy@izzy.la · bri@izzy.la. Paper market terminal at /awake/ is SATURN TRADING — a different plate.

The fleet shell

Mandate board and continuous rail are primary. Craft, research, and growth sit side by side — scoped to the three money surfaces. Editor opens when a human needs it.

Visual mock only — not interactive. Shows a fleet list, three-surface mandate cards for craft, research, and growth, a continuous measure-queue-claim-craft-ship-prove-arm rail, and a gate tray for credentials, money, and public publish.

Three money surfaces

Never-idle fleets claim work against the real host map — audience split, not brand cosplay.

Continuous growth

The product assumes you are always growing the three money surfaces — not a sandbox of idle agents on a single page.

Why not stock AI IDEs

Same class of product as Cursor. Different optimization target: continuous multi-agent growth across a three-surface money map.

  1. Swarm orchestration first-class Fleet pane and mandate board — not a single chat with agents bolted on.
  2. Never-idle continuous growth Improve or research-to-improve, always. Loop arm is the product, not a script beside it.
  3. Three money surfaces in-shell Proof · store · local studio are first-class surface map nodes — not one undifferentiated site thrash.
  4. Revenue & marketing in-shell Ads, SEO, and growth automation sit on the board next to code mandates, scoped per host job.
  5. Full ship→prove→arm rail One writer per surface; sole-ship; live prove; re-arm. Force-push is not a feature.
  6. Human publish Gate Public posts, money, and credentials cannot be bypassed by the fleet.

How the loop works

  1. 01Measure — live truth across three hosts (manifest, health, honest probes).
  2. 02Queue — residual craft, research→apply, growth per money surface.
  3. 03Claim — one writer per host/job cell; respect peer exclusive holds.
  4. 04Craft — code, copy, ads automation; SaturnDesign before invent.
  5. 05Ship — sole-ship only; no force-push.
  6. 06Prove — live bytes on the right host / checkable claim / health green.
  7. 07Arm — re-enter the loop; idle is failure.

Roadmap

Honest stages. Spec sheet, not vapor milestones with dates we cannot keep.

NOW MVP
This product page + durable plan (fleet shell + continuous growth + three-surface law). Dogfood on Cursor + SWARM + continuous handoff docs.
NEXT V1
Thin client: Fleet, three-surface map, craft/research/growth mandates, claims, full continuous rail, Gate tray with public publish.
LATER V2
Ads automation workers first-class, multi-worktree map, portfolio sense+revenue wizard, residual/grow scoring.