Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 7273eec2bb feat: screenshot baselines from the development PC, fixed capture values, ports strings in all languages
The owner chose to capture the baselines on the development PC (owner
review 3, R2): 156 screens go to tests/visual/baselines and CI no longer
pushes a ci-screenshots branch. While --capture freezes AppClock, free
space, a server's latency and the last sync are fixed sample values; they
moved the Server and Import screens past the diff tolerance at random.
The 22 new or changed Admin strings are translated into the 36 other
languages, and the request file records the owner's text and answers.

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