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.
→ Roadmap → Methodology · 4 axes → Audit trail · cycles + escapes
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.
Higher-order compositions harvested from the 94-story corpus. Each appears in 5+ branch stories — extracted once, ratchets all consumers automatically. Full analysis in TIER3-HARVEST.md; tier model in TIERS.md.
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–P14 complete. 6 trunks, 21 components, 94 branches covering 99/100 EF capabilities. EF-068 (CLEAR Health Pass) is intentionally deferred (context-obsolete in 2026 — the COVID-era health-pass infrastructure isn't relevant). Native runner (Detox/XCUITest) is unwired; native stories rely on Gate-7-style signed-build manual evidence packets.
Tightening pass: re-audit corpus for tier-3 compound components and reusable functional groups (e.g., async-job-admin-page, oauth-connection-card, audit-log-viewer, public-form-flow, audience-picker). Goal: extract once, reuse pervasively.