2.9 · Stale-cell detection, cascade & refresh 4B preview

Staleness is the differentiator: a confidently-worded but superseded authority is the failure mode that ends careers. Stale states exist in the enums READ-P3; the roll-up pill, the cascade view and the per-cell refresh job are new JOB-NEW / API-NEW. Refresh does not block the grid.

‹ Matters Acme v Beta · UK ⚠ 2 cells stale ▾

Doc	Liability cap	Indemnities
MSA v3	~ £1m (stale)⚠ 1	● Mutual
Side letter	● n/a	~ Carve-out (stale)

Doc

Liability cap

Indemnities

MSA v3

~ £1m (stale)⚠ 1

● Mutual

Side letter

● n/a

~ Carve-out (stale)

MSA v3 · “Liability cap”

~ support: stale

Stale cascade

Document version superseded (MSA v2 → v3)

extraction stale

claim stale

Why: warning source_version_stale

Refresh evidence JOB-NEW

Re-runs retrieval for this cell and recomputes support + warnings.

queued → running → recomputed

The grid is not blocked; the cell shows a skeleton meanwhile. If it stays stale or fails, the reason is shown and manual authority lookup is offered.

Open question (blueprint §7.3): does accepting a cell freeze its evidence snapshot? If a source later changes, does an accepted cell go stale, or is acceptance bound to the evidence state at decision time?