Voyage · EventFarm Parity Stories
Each story describes one feature of Voyage as a real organizer, attendee, or event-day staff member would experience it — including what success looks like, what failure looks like, and how the page itself supports or fails the user. Trunk stories establish the surfaces; branch stories root in trunks and exercise specific capabilities. Every story is human-audit-ready and machine-consumable by the agent harness that turns it into a Playwright fuzzing run.
Surfaces of the application. Branches inherit auth + navigation from these.
Design-system primitives. Tested once with all interaction edge cases. Branches that use a component inherit its contract via usesComponents and don't re-test the fiddly UX bits.
Each roots in a trunk and focuses on the specific feature's success + failure surface. Component-tier mechanics inherit from the component stories above. Cluster B (organizer admin) was the first codex-factory dispatch — 7 stories at 10-12 failure modes each, all lint clean.
P1–P8 + P11 done. 6 trunks, 21 components, 54 branches. Cluster B + C + D + E + reports + account/admin all closed via codex-factory bulk-gen. Remaining: P12 EFx live-event modules (~16 stories — likely parallel-split), P13 integrations (~8 stories using usesIntegration envelope), then hand-written carve-outs P9 payments (~5 stories), P10 compliance (~4 stories), P14 native (~9 stories). After all phases: ~95 EF capabilities covered as ~130 stories.