KCAE.CHANGE:4.6 - Test update, recovery and dependent use

Construct changes that exercise the intended guarantees: add a decisive passage; alter a condition; move an unchanged block under a different heading; split a section; delete a source; change a permission; fail a vector build; interrupt before and after pointer publication; reopen from persisted state; and read across the switch. Select cases from the actual architecture rather than treating this list as exhaustive.

Compare incremental and fresh construction on a stable input. For deterministic representations, compare exact membership and expected values. For stochastic extraction or approximate retrieval, compare the intended semantic and retrieval properties with recorded variation; byte inequality is not automatically a defect, and job completion is not equivalence. Repeat questions whose answers depend on the change and unchanged controls that should retain their result.

Follow dependencies into cached assessments, composed relations, deliveries and episode memory. Invalidate, recompute or retain each at its actual basis. A failed source update and a changed model have different consequences. Preserve sound unaffected results, but do not let a valid low-level hash become an all-purpose reuse certificate.