Files
Chronos/docs/requests
Alby96 23403f1c07 docs: phase 4a fix rounds 4 and 5
The phase 4a docs were written before the last two fix rounds landed. They
now describe the code at 8c2b9f1b: a sequence left as it was inside a moving
folder is taken along instead of keeping that folder in place; a held plan on
an offline archive keeps its plan and fails as offline; render filing answers
503 folder_moved; a rebase never moves the rows of the sequence that took the
old folder (with its known limitation); every writer refuses a folder another
sequence holds (SequenceFolders.Holds). Three DECISIONS rows added, six
updated; five fix rounds in STATUS and the request.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 31d479c5f4dd0b7076b39331246815e95895a1fa)
2026-10-27 20:57:25 +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.