E.17.AUD.OOTD:4.4 - Claim-bearing extension and quick boundary summary

Use the heavier extension only after the ordinary declaration is stable and a concrete neighboring claim or downstream use needs more detail. It is for heavier declaration, not for rescuing a unit that still cannot keep one primary subject, one carried move, and one outside-work boundary in place.

Then add only the fields needed by the current claim or downstream use:

• publicationUnitFormCue;
• primaryInterpretation;
• transitionPolicy;
• modelingLensPolicy;
• downstreamDecisionPolicy;
• entityOfConcernProjection, only for the exact C.2.1 case stated in 4.1.b.

These fields do not create a rival rule track. publicationUnitFormCue names words such as note, sheet, screen, and table as form clues only; it does not make those clues subjects, entity kinds, or claim kinds. entityOfConcernProjection records an already justified equality with the exact entity participant of one identified episteme; it neither creates that participant nor turns a topic into an entity. The remaining fields clarify the relevant boundary only when the ordinary declaration is not enough for a named later use.

Quick boundary to neighboring patterns and project records

• use E.17.AUD.LHR (Local Head Restoration) when the instability is still local to one lexical head, qualifier, or interpretation word;
• use E.17.ID.CR when the same publication unit already holds one stable primary subject, one carried move, and one outside-work boundary, and the question under repair is one bounded comparative review move over already available source epistemes or publications;
• use this pattern when one publication unit still has unstable subject, concern, carried-move, downstream-use, or outside-work interpretation after honest local repair;
• use the neighboring pattern that addresses the view, face, carrier, entityOfConcernRef-preserving transform, explanation, bridge, ontology, gate, approval, or execution question; keep any required project record with that question.