DEC-0012: Project Log as Canonical Website Log
Decision
project-log/ is the canonical website log for the companion site.
Website changes are recorded inside the existing project-log structure rather
than in a separate changelog or one-off notes. chronicle/ carries the regular
site-update narrative, decisions/ records lasting site decisions, and
snapshots/ records milestone summaries of the site's current state.
Codex is the default maintainer of this website log unless the human assigns that duty elsewhere for a given session.
Context
The repo already had a mature documentary layer in project-log/, but no
explicit operating rule saying that the same system also functions as the
website log. As the site grew, that left a risk of drift: public-facing changes
could land without a durable record of what users now see, why the change
happened, and which commits or prompt relays produced it.
The human clarified that the project log should serve as the website log. This decision formalizes that instruction and sets a default maintenance owner.
Rationale
Using the existing project-log/ structure avoids a second documentary system.
The project already needs historical records for the meta-project, and site
changes are part of that history. Folding the website log into the same system:
- keeps process history and product history in one place
- reduces duplication across changelogs, notes, and relay prompts
- makes site evolution legible for future agents and for Episode 0 material
- gives the team a consistent rule for when site changes must be recorded
Assigning Codex as the default maintainer fits Codex's cross-cutting technical role without turning the Documentarian into an exclusive agent identity.
Operating Rule
Create or update a website-log entry when:
- a user-facing site feature ships to
main - episode media wiring changes what the site serves publicly
- a deploy blocker, build failure, or production incident affects the site
- the human makes a lasting website architecture or UX decision
During active site work, log at least one consolidated chronicle entry per day if site changes landed that day.