Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 291aa6217e
CI / Build and test (pull_request) Successful in 13m9s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 16s
CI / PostgreSQL 16 integration (pull_request) Successful in 11m12s
CI / PostgreSQL 17 integration (pull_request) Successful in 11m42s
CI / Docker image (pull_request) Successful in 2m11s
chore(release): 1.1.0; owner review 5 strings in all languages
Translates the new and changed strings into the 36 other languages,
sets the default version to 1.1.0 and closes the request, STATUS and
CHANGELOG for the release.

Refs #64 #65 #66 #67

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