The docs commit 59235e7c predates the third to sixth verification rounds.
The brief now says how Integrate decides who may trash a server photo (per
sequence, owner or admin with Delete; otherwise the server's version stays
out of its Main), that the Details stage stops on a server change, how a
merge re-plans, keeps its links undoable and names its classes, the
Two versions... list of owner Q3, the three-button rows and twins with a
sibling only, with an amendment row per round. DESIGN, ARCHITECTURE,
DECISIONS, CHANGELOG, STATUS 8.7 and the request doc follow; the Windows
captures are no longer listed as open.
The glossaries gain the match terms in every language, read from the
shipped strings. Hindi merging reads मर्ज, apart from मिलान (match);
Croatian names the matching sequence podudarna sekvenca; Finnish no
longer puts kohteen right after a count.
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.