Files
Chronos/docs/requests
Alby96 af868c2175
CI / Build and test (pull_request) Successful in 8m36s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 18s
CI / PostgreSQL 16 integration (pull_request) Successful in 10m13s
CI / PostgreSQL 17 integration (pull_request) Successful in 11m34s
CI / Docker image (pull_request) Successful in 3m57s
docs: record owner review 1 phase 4
BRIEF, DECISIONS, CHANGELOG, STATUS, ARCHITECTURE and the request files now
describe the visual crop locked to the output, rotate, mirror, flip and
straighten, the colour looks and "proportions win" as built and reviewed.
The CHANGELOG carries the upgrade note (existing projects at a chosen aspect
change output size, settings format 2 opens read-only in older builds,
servers and nodes announce the settings format they read), and the 5c
entries move under rc.11. DESIGN and the Editor mockup put Reset framing on
its own line, as the panel has it.

Refs #19
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 00:27:07 +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.