📋 User stories

As an operator with several projectsI want each project to appear as a world card with its real, derived historySo that I can pick a fight knowing exactly what has actually shipped and failed there

As a player moving around a worldI want each surface on its own labeled screen with a persistent navSo that I always know what I am looking at and nothing else fights it for the page

As the operator of a world with a bound repoI want the delivered app running, embedded, and controllable from the world hubSo that I can use what the SDLC built at any time without touching the SDLC itself

Shipping is never the end of the SDLC (operator ruling 2026-07-25): theengine watches the running app's log for errors, dedupes what it sees into"sightings", and shows the evidence on the world hub so the conveyor canfile and fix them.

The world hub shows the campaign PRD's declared surfaces and flows as data,with deterministic visuals rendered FROM that data, and per-surfacecoverage that states plainly what has not yet been designed.

As a player returning to a worldI want the hub to open on a quest log ordered milestone → epic → story → task → slicesSo that I read what the work IS before any battle theater plays

As a playerI want to describe work in plain words and have it filed at the right tierSo that a posted ticket becomes a real run without me learning the taxonomy first

As a player reading a run transcriptI want every product, design, and review turn to be a real recorded model call with checked inputs and outputsSo that no verdict, story, or mockup in the story is theater

As a player watching a runI want the left rail to list the real agent turns in execution order and light up who is actingSo that the "party" reads as the actual delivery pipeline it is

As a reader meeting an agent anywhere in the gameI want the same matter-of-fact sheet for it everywhereSo that I always know what it really does before I see its costume

As a playerI want each fight rendered as a scrubbable battle whose every beat traces to a recorded eventSo that the spectacle is a skin over the run, never a script

As an operator who wants the unskinned truthI want a terminal view of the selected fight's transcript, row for rowSo that I can read exactly what each agent was told, answered, ran, and proved

As the person who posted the questI want to open the actual files the agents built and the runs that proved themSo that "shipped" always means inspectable code, not a status flag

As a playerI want the world's whole history drawn as a gold trunk with branches, nodes, pulls, and scarsSo that one glance shows what happened, when, and what it cost

As a playerI want XP, achievements, and loot that trace to recorded runs on their own screenSo that progression is a scoreboard of reality, not a slot machine buried in another page

As an auditor of an AI-driven cycleI want every transition, check, command, and diff shown with the evidence that earned itSo that no claim in the game survives without a recorded basis

The /lifecycle page renders the ACTUAL machines that drive the factory —never a hand-drawn diagram that can drift. Every state and transitiondescription is collected from the machine definition itself (G1), and thedrift gate holds the allowlist empty.

As a new player or a skeptical readerI want every game concept explained in plain language with the honesty contract spelled outSo that I can understand any surface without decoding the flavor first

As a reader of any game surfaceI want tooltips that add depth without ever being the only place meaning livesSo that every surface reads at a glance and hovering only enriches it

As the operator of an autonomous factoryI want one surface that tells me whether the machine is moving, stuck, ordrifting — with the proof, the blockers, the action I owe, and the ETASo that I never have to read a transcript to learn my factory died an hour agoA dashboard of green counters is exactly how a stalled campaign hides. Everyclaim on this panel is COMPUTED from real recorded rows (transcript, ledger,design stores, a live HTTP fetch of the app) and carries the evidence thatearned it. An unproven stage reads NOT DONE with the reason — never blank,never assumed.

As an operator who wants status, not theaterI want a plain project → milestone → epic → story → task view with blockersSo that I can read what is delivered and what is blocked at a glance