Stories A promise's telling

The Factory, chapter one

The platform builds itself, and absence becomes visible — every intended capability is a deliverable that is either proven or named as uncovered.

The seven beats

World: The monorepo and group one — wires built but not firing, and nothing that said so.
Cast: The operator and the agents that build, review and convene.
Knock: Four built-not-firing failures, each found by accident.
Want: A ladder from objective to proof, so absence is a row.
Way: Each deliverable is carried through the gate or shown as uncovered; closes mark the path.
Turn: uncovered() names the dark wires first.
Lesson: Open — until someone has learned it.

This story carries its beats but no written telling yet — text/factory-v1.md has no “The story” section.

Every link here was checked against the repo when the page was built. 1 name the story uses could not be found and is shown without a link.

Each opens a chat with that agent.

Each opens the skill's page.

The flows this story walks — trigger → step → step.

condition: ready-tasks(plan) non-empty → tool: factory-width.sh → agent: factory-executor builds each row in its own worktree → tool: factory-walk.sh proves it
condition: gaps(plan) non-empty → agent: the stage that produces the missing rung
human: deadlocked(plan) non-empty → human:notify the operator

Receivers and scripts it signals.

What it holds; a told promise opens its own story.

Every event is a signal; each names the path it marks or warns.

factory:gap-closed · from the close that carried an uncovered deliverable through mark objective → deliverable tags: factory
factory:fail-open · from a factory query that returned empty because it was unwired warn the query's path tags: factory

none — the factory spends agent credit through agent:run; VERIFY: nothing meters a factory run separately