How it was built with Codex | Developer docs

Developer docs. You want to read, run, deploy or change the code. Not what you came for? Find the right docs.

The project is an entry in the Codex x TwitchCon hackathon, which requires the work to be built with OpenAI Codex. The team's process, as recorded in the repository:

Specs first. The PRD and SRS are the source of truth for scope, copy, safety and implementation. AGENTS.md tells every coding agent which spec wins, what it must never break, and that it may not add a feature, endpoint, dependency or table the specs do not list.
Tickets, tests first. Work is split into numbered tickets on the project board. Agents write the tests the SRS names, watch them fail, then implement; npm test and npm run typecheck must pass.
Humans review and decide. The PRD describes the builder as Codex writing most of the code from SRS tickets, with humans reviewing, testing and deciding. Commits are authored by the human builders.
A written trail. docs/LOG.md records decisions, day-0 results and a note per working session.
Claude Code for the design and documentation pass. The brand kit's colour tokens were generated with a Claude Code skill checked in under .claude/skills/artistic-color-palettes/, and the UI v2 and documentation work was done with Claude Code agents under the owner's direction. The runtime uses no AI service by default.

The Codex session ID for the submission is provided in the Devpost entry.