Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 5209579631 docs: owner review 2 request
The owner's second review (2026-10-26) with its interpretation R1-R12, the
answers to the questions and the phase plan; also fills in owner review 1's
phase 3b row, whose state and commit were left as placeholders.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 21:13:56 +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.