[WaylandYang]

Found while reproducing #987 (every relation of an entity reads "undated" on a base built from dated reports).

Reproduction on dev. A Chinese report whose first lines state 提报日期：2026/09/04, uploaded and extracted:

step	result
time words inside sentences	resolved, four of four at grade A
the document's own date	read: doc_time = 2026-09-04, source content
the facts' attested_from	2026-09-28 04:26, the moment the document was processed

Cause. Extraction runs before dating. A statement is written while the document has no date, so attested_from takes now(). When the resolver later reads the date from the text, set_content_date wrote it on the document and nowhere else. Reads take the lower bound of a fact with no start from COALESCE(valid_from, attested_from), so a report from 2020 uploaded today has its facts read as known since today: the upload time entering world time, which #714 says must not happen.

Fix.

• documents::set_content_date does it in one transaction: writes the date on the document and on the version the evidence sits on (Per-object document updates lose observation-time ordering during reconciliation #900), locks the timelines of the facts that cite the document, moves their anchors to the earliest dated evidence, carries typed rows along with the statement they came from, and recomputes those timelines (the engine orders start-less rows by evidence date). Anchors only move earlier, the rule attest_earlier already keeps; an ending said without a date (attested_to) moves the same way. The dated-evidence expression is the one temporal::DATED_AT uses.
• Migration 0100 does the same for rows already written (constant 90).
• The resolver logs how many anchors moved and emits a graph event.

After the fix, the same reproduction: every fact of the report is attested from 2026-09-04.

Tests. a_document_date_reaches_its_facts: the statement and the typed row it became move to the document's date; an anchor already earlier stays; a fact of another document is not touched; reading the same date again moves nothing. Store suite, server time tests and clippy pass.

Not in this PR. The entity panel shows "undated" for a fact with no start even when it has an attested date; showing that date is the second half of #987 and comes separately.

Refs #987.

🤖 Generated with Claude Code

[WaylandYang]

Reviewed and ran it on a fresh database with dev merged in: store 292, server 522, CLI 13, clippy clean. The fix is the right shape: one transaction, anchors only move earlier, typed rows follow the statement they came from, the timelines are recomputed, and the dated-evidence expression is the one DATED_AT uses.

One commit pushed: the description says constant 90, but dev reached 90 files with #986, so with 0100 the constant is 91. Without it the CLI schema test fails.

For the second half of #987: a typed row merged from several statements follows only from_statement_id here; if its other sources are earlier, typed_fact_sources is where to look.

[WaylandYang]

Superseded by ADR 0064 (#989). This moved attested_from from the processing moment to a single document date and backfilled it; 0064 drops the single document date: attestation is null unless the time context gives the statement an as-of, and a fact with no time holds at every moment. The diagnosis stands (extraction runs before dating, COALESCE($7, now()) writes the processing moment) and is carried into 0064 cut 3.