Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 3ade4b8d6c docs: document phase 5b, the server as a project home
Phase 5b had only module rows and the review's DECISIONS and CHANGELOG lines.
The brief now describes the server home as the code does after the review
fixes: the projects API, projectChanged, the capability, the settings PATCH
under the lease, renders of a project version, the panel's Projects section,
and the desktop's server projects (open, copy, sync, chip, renders, viewers).

DECISIONS gains the phase's own rows; the 5b rows are dated 2026-10-26 like
the other review-2 phases, and three 5a rows are marked partly superseded.
CHANGELOG, STATUS, the request's 5b row and ARCHITECTURE follow the code
(frames stamp, stored reads, the .thumb marker, followed renames, the
editor's sign-in).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 13:19:55 +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.