Stories A promise's telling · drafted 2026-09-24
Story fleet
A story told once generates its own plan: tell, review, tests red, promise, cross-model review, workflow — worked by people and agents across every model door, as wide as the box allows.
The seven beats
- World
- Group one — a board of thousands of rows, three flows told separately, one box that has funded one build at a time.
- Cast
- The chairman, the CEO, the heads, and agents on Claude, Codex, Kimi, DeepSeek, Gemini and Astra.
- Knock
- The operator asks for one chain from story to workflow.
- Want
- One command that walks a story to a workflow, reviewed by a second model.
- Way
- Meeting, CEO routes, agents hand to peers; each close marks the path.
- Turn
- A different model reviews the promise.
- Lesson
- Open — until someone has learned it.
This story carries its beats but no written telling yet — text/story-fleet.md has no “The story” section.
Connected to
Every link here was checked against the repo when the page was built. 4 names the story uses could not be found and are shown without a link.
People
- the operator
- the chairman's convened heads
Agents
Each opens a chat with that agent.
Skills
Each opens the skill's page.
- storytelling
- meeting
- planning
- promise-make
- promise-settle
- models
- voice
Paths
The flows this story walks — trigger → step → step.
- human: chairman holds the meeting (meeting skill) → agent: ceo assembles the team → tool: tasks:bulk assigns the rows → agent: each assignee works its row → tool: tasks:announce hands the next row to a peer
- trigger: story told → agent: review-engineer (rubric) → condition: composite ≥ 0.65 and goal-fit ≥ 0.50 → agent: test-engineer (red) → agent: architect (promise) → agent: cross-model reviewer → agent: workflow author
Tools
Receivers and scripts it signals.
- m.sh
- agent:run
- factory-width.sh
- tasks:board
- tasks:bulk
- tasks:announce
- world:route
- do-promise-lint.sh
- factory-executor
Promises
What it holds; a told promise opens its own story.
- story-fleet
- story-flow
- ads-flow
- ecommerce-flow
Docs
What derives from this file.
Events
Every event is a signal; each names the path it marks or warns.
- tasks:status · from the agent that closed the row mark (story-fleet → assignee) on a green accept; warn on a failed one tags: story-fleet
- tasks:announce · from the ceo, or a peer handing on reach, never delivery — matched is how many staked, not who acted tags: story-fleet
Transactions
- agent:run credit on prod's key, per call — none until billing is sorted and row F3 is confirmed
Analytics
- rows closed per wave — one tasks board --tag story-fleet
- rubric vectors per review — text/rubrics.md
- model per close — VERIFY: nothing records which door ran a row yet