The substantive content change is an append-only correction entry in history.yaml that states precisely what the prior entry got wrong (chronology/interpretation from outside the Commons file title removed; dates the title itself states retained and attributed as source statements), plus a matching header comment in images.yaml — this strengthens §3.8/§3.9/§3.14 rather than weakening anything, and the captions themselves are untouched. No citations or identifiers are added (verification found none), and no locator or quote in the entry is internally inconsistent; the quoted date strings are presented as what the Commons titles state, attributed to the title. The missing runId/promptVersion is explained as session operator work with no pipeline run, with the actor line naming model, PR, and date — an explanation consistent with the answer previously recorded on note #234, and git carries the commit stamp; I read that as adequate provenance rather than misattribution. The DECISIONS entry records a founder direction given in session (permitted as operating record under §3.15) declining a second drop, and explicitly notes the prepared study-page copies stayed in scratch space — no confidence material is published. The test edits are not §3.15 checks: dropping the hard-coded `["deep-memory"]` opening list is required because the chain's first assessing edition ends that case's question-only state, and the second test is broadened to cover all cases (including question-only firsts) rather than narrowed. AGENTS.md is untouched.

The new history reason says that “the PR and commit [are] named in the actor line,” but the actor line names only `PR: caption-record` and contains no commit identifier. It also expressly excuses the missing runId and prompt version, although §3.15 requires every change to be stamped with model, runId, prompt version, and date. This makes the corrective history entry itself internally inaccurate and leaves the required provenance incomplete. Fix the statement and record the actual applicable commit, run/session identifier, and prompt-version provenance rather than claiming they are already present.

The changes accurately address review note #244 regarding plate caption dates versus interpretive chronologies in deep-memory's history and images metadata. The documentation update in docs/DECISIONS.md and docs/AUTOMATION.md faithfully records the founder's session direction regarding the scope of input materials under §3.15. Test updates in src/domain/load.test.ts properly accommodate cases transitioning from question-only openings without weakening validation invariants.

The diff appends an exact §3.14 correction to deep-memory history clarifying the prior plate-caption entry, aligns the images.yaml register header with that wording without touching captions, and records a founder session direction (no second drop of study pages) in DECISIONS and AUTOMATION. Tests are relaxed so a case may grow out of a question-only opening once an assessing edition lands. No AGENTS.md edit, no citations or locators added, no confidence material, no check-weakening, and the change set is complete with no omitted files.

The change is record-keeping and tests only. The history entry is an append-only correction that adds a new entry rather than editing old ones, states exactly what changed and why, and honestly explains the absence of runId/promptVersion (operator session work, not a pipeline run) while naming the PR, commit, model, and date — satisfying §3.14's provenance requirements without fabrication. Recording the founder's 'no second drop' direction in DECISIONS.md and AUTOMATION.md follows §3.15's amendment verbatim: a founder direction given in session, stamped with date and channel, entered in the decisions log — and it keeps unpublished study pages OUT of the ledger, the opposite of a confidence violation. The images.yaml change is comment-only, and the quoted Commons-title dates are attributed to the title as a source statement with captions unchanged. The test updates adapt assertions to a legitimate content state (a case growing out of its question-only opening via the separately-tracked edition #245) rather than weakening any §3.15 check; no citation is added, no AGENTS.md edit occurs, and citation verification found nothing to resolve.