Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 c06bae1bc5 docs: record phase 5c and translate its strings
DECISIONS, BRIEF, CHANGELOG, STATUS, ARCHITECTURE and the request files now
describe the workspace originals, local render and send, clean-up, trash
and move as built and reviewed; the 5b entries move under rc.10. The 184
new strings are translated into the 36 machine-translated languages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 18:00:43 +01:00
..

Owner change requests

One file per request from the product owner, named <date>-<slug>.md. Each file keeps:

  1. the owner's text, verbatim;
  2. the working interpretation, numbered (R1, R2, …);
  3. the questions asked and the owner's answers;
  4. the delivery plan, phase by phase, with each phase's state, commit, BRIEF/DESIGN sections amended and DECISIONS rows.

A request amends the BRIEF: the amended paragraphs say so, and BRIEF §24 lists every amendment with the request that made it. DECISIONS rows written for a request cite it (R4, owner review 1). Read the request file first to rebuild why a part of Chronos is the way it is.