E.17.ID.CR:4.3.c - Fuller Declaration Extension Guidance

A fuller declaration record becomes warranted only when a local condition changes the actual first move: reader-fit is doing real work, overread risk is high, a mixed case depends on A.6.3.* or E.17.EFP, bridge-mediated relation is live, or the same review unit still has unstable reviewed-source, comparative-move identification, or outside-work boundary after local repair.

The fuller declaration extension can inherit already-declared case ids, source pins, and provenance references instead of restating them inline. When recorded as a claim-bearing review unit, that extension normally captures the ordinary minimum block plus only the neighboring-pattern fields that govern the mixed case.

Do not answer PublicationUnit instability by stacking more local fields onto the fuller declaration extension. If E.17.AUD.LHR (Local Head Restoration) has already repaired the local lexical-head pressure and the same review unit still has unstable reviewed-source, publication-unit, comparative-move identification, or outside-work boundary, stabilize that PublicationUnit question with E.17.AUD.OOTD (PublicationUnit Primary-Subject Discipline) before deciding how much declaration weight stays here.