#A.6.P:4.6 — Progressive elaboration (the “precision dial” rule)

Preface node heading:a-6-p-4-6-progressive-elaboration-the-precision-dial-rule:10829

#Content

A.6.P supports a controlled escalation path that preserves meaning and prevents drift:

1. Start with a minimal explicit RelationKind token + principal endpoints (a binary projection is allowed only if every omitted participant/qualifier slot is contractually optional and irrelevant for the downstream lane(s)).

2. When ambiguity emerges, do one (or more) explicitly:

   • add missing participants as additional slots (turn the projection into n‑ary),
   • add explicit qualifiers (scope / Γ_time / viewpoint/view / schemes / witnesses),
   • refine the RelationKind token to a more specific one (new contract skeleton; changeRelationKind),
   • introduce Bridges + CL (and loss notes) when crossing Contexts/planes.

3. Authors MUST keep the transition monotone:

   • no silent re‑typing,
   • no implicit polarity flips,
   • no “edit‑in‑place” that changes meaning (use edition fences + explicit continuity/withdrawal links).