Files
Chronos/docs/requests
Alby96andClaude Opus 5.5 988068ee8e
CI / Build and test (push) Successful in 11m19s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 9s
Release / Build, test and publish (push) Successful in 15m56s
CI / PostgreSQL 16 integration (push) Successful in 10m56s
CI / PostgreSQL 17 integration (push) Successful in 12m14s
CI / Docker image (push) Successful in 1m24s
Release / Server image (push) Successful in 1m33s
chore(release): 1.0.0, the first stable release (#63)
Builds without a release tag say 1.0.0; CHANGELOG [1.0.0] and [0.1.0-rc.14]; STATUS, DECISIONS and the request files record rc.14 and 1.0.0.

Closes #23

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
2026-11-06 20:16:55 +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.