Chronicle Protocol

The chronicle/ directory is the day-by-day narrative record of what happened in the repo. It is also the primary home for the website log.

When to Write a Chronicle Entry

Add a chronicle entry when:

a user-facing site feature ships to main
a meaningful site feature lands on develop and changes the preview/dev experience in a way the team needs to track
episode media wiring changes what the site serves publicly
navigation, layout, player, search, explore, imagery, RSS, or AI surfaces change
a deploy failure, build break, or production incident affects the site
a work session lands multiple related site changes that should be recorded together

Cadence

During active website work, write at least one consolidated chronicle entry per day if site changes landed that day
For a one-off but important site fix, write the chronicle entry in the same work session as the code change
Prefer one coherent entry per day or per shipping batch, not a stream of tiny notes

What a Website Chronicle Entry Should Capture

What the public-facing change was
Why it happened
Which agents and human decisions shaped it
Which files carried the change
Which commit hashes or prompt relays are relevant
Whether the work landed on develop, main, or both
What remains unfinished or deferred

Suggested Structure

---
id: "CHRON-XXXX"
date: "YYYY-MM-DD"
author: "codex"
title: "Short descriptive title"
scope: "What changed in this site work session"
---

# CHRON-XXXX: Title

## What Happened

Narrative summary in third-person observational voice.

## Site Impact

- Public-facing effect
- Key surfaces affected
- Constraints or incidents that shaped the outcome

## Files and Commits

- `site/...`
- `docs/...`
- `prompts/...`
- Commit hashes

## Follow-Up

- Remaining work
- Deferred decisions
- Known risks

Ownership

Codex is the default maintainer of website chronicle entries, but any agent or the human may write them while acting in the Documentarian role.