Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 6ec91dcf33
CI / Build and test (pull_request) Successful in 9m5s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 25s
CI / PostgreSQL 16 integration (pull_request) Successful in 11m4s
CI / PostgreSQL 17 integration (pull_request) Failing after 11m18s
CI / Docker image (pull_request) Successful in 2m8s
docs: changelog section and status for 0.1.0-rc.3
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 23:52:02 +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.