Owner review 6 asks Chronos to recognise the same time-lapse on a server and on this PC, show the differences and let the user keep the two apart or integrate and sync them. The request file keeps the owner's words, the reading R1-R8, the eight answers and the delivery plan; the brief now describes matches, the Compare dialog, Integrate, the merge of two local sequences, the automatic photos of integrated pairs, the photo lookup and uploads into a target, and amends 14.5 so other projects cross only through Integrate or a merge. DECISIONS records the design choices and those taken while building it; the changelog, status, architecture and design notes follow, and the version moves to 1.2.0. Refs #73 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.