Owner review 1 phase 6 asks for Docker, Unraid and deploy documentation. docs/deploy/ now covers the image tags, volumes, every CHRONOS_* variable with its default, ports and public ports (the owner's host 8087/8444 mapping), TLS modes and the fingerprint, upgrades and forward-only migrations, backup and restore, PostgreSQL, troubleshooting, and the desktop Setup, portable mode and update channel. The owner review 4 request (2026-11-06) is recorded with its interpretation and plan; BRIEF §14.9 lists CHRONOS_TRUSTED_PROXIES, which the server already read, §19.6 points to the Unraid guide, and §24 gains the rows of owner review 4 and phase 6. STATUS shows both in progress for v0.1.0-rc.14, then v1.0.0. Refs #22 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner change requests
One file per request from the product owner, named <date>-<slug>.md. Each file keeps:
- the owner's text, verbatim;
- the working interpretation, numbered (R1, R2, …);
- the questions asked and the owner's answers;
- 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.