A.15.4:6 - Consequences

Consequence	Trade-off and cost	Mitigation
Work can continue at the lightest use supported by a recovered relation instead of stopping on every suspicious display.	The practitioner names the claim being made and the required relation or project reference before relying on the appearance.	Follow the opening progressive path; add structured rows only when its stated conditions apply.
Appearance-based approval, evidence, assurance, gate, and work-occurrence overreads are blocked.	Some convenient dashboard or copied-text shortcuts become unusable until source-currentness relation is recovered.	Keep orientation, source-finding, and bounded reversible probes available when no external-impact reliance is being made.
Repeated ambiguity becomes prerequisite-rule or source-relation repair work rather than repeated manual heroics.	The repair may reveal missing register entries, stale selected source epistemes, non-current or unresolved `EpistemePublicationRelation` occurrence refs, or underspecified gate and evidence relations.	Assign only prospective repair work or source-relation gap work; do not backdate evidence, gate passage, work occurrence, or assurance.