From ebb9384693bdd3f25009b43a343a41c3ee35caa2 Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Mon, 21 Sep 2026 17:02:34 +0000 Subject: [PATCH] Manifesto: we *are* the moat Co-Authored-By: Claude Fable 5.1 --- manifesto.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/manifesto.md b/manifesto.md index ada85c3..389b8ce 100644 --- a/manifesto.md +++ b/manifesto.md @@ -10,6 +10,7 @@ A fleet is agents. Dozens of them, coding, deploying, posting and fixing at the - `--yolo` mode enabled. - We scale when we need to. - Everything ships with a TUI, a CLI, an MCP and an API. +- We *are* the moat. ## Notes @@ -29,6 +30,8 @@ A fleet is agents. Dozens of them, coding, deploying, posting and fixing at the **A TUI, a CLI, an MCP and an API.** Everything we build ships all four, because the sysop works from a terminal and the agents work from a socket, and both need the same thing. +**We *are* the moat.** There is no model, no framework and no cloud account that a competitor cannot buy tomorrow. What they cannot buy is a sysop who has run a fleet through a thousand prods and the agents, tools and habits that came out of it. The moat is us. + ## The sysop One person. A fleet of agents. Call it fleet coding if you like; the job is not to write the code. The job is to run the fleet: pick the work, read what came back, kill what went wrong, merge what did not. Everything above exists so one sysop can run many agents and still know what the fleet did.