Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 31df8beb9a
CI / Build and test (pull_request) Successful in 8m15s
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 10s
CI / PostgreSQL 16 integration (pull_request) Successful in 8m46s
CI / PostgreSQL 17 integration (pull_request) Successful in 9m51s
CI / Docker image (pull_request) Successful in 1m45s
docs(i18n): translate the phase 5b strings and split the changelog by release
The 119 new phase 5b strings are translated into the 36 machine-translated
languages. The changelog separates what shipped in 0.1.0-rc.9 (ports and
baselines) from the unreleased phase 5b work, and the index settings decision
names the rare cases where a newer project.json is kept as version 1.

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