Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 58ed737310 refactor: share the update check; owner review 5 request
Move UpdateCheck, UpdateDownload and ProductLinks to Chronos.Core/Updates and
UpdateFlow to Chronos.Ui/Updates, so the Uploader can reuse the update check
(#64) and the check and download tests run on Linux in Core.Tests. No
behaviour change: only namespaces and usings moved. Record owner review 5
(request, interpretation R1-R5, answers Q1-Q3, the v1.1.0 phase).

Refs #64

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 12:29:46 +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.