#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:12572

#What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

#Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

#Content

A.6.P defines a controlled escalation discipline 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 declared optional by the relation specification 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 or view, reference or representation schemes, and witnesses,
   • refine the RelationKind token to a more specific one (new relation specification 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).

---

Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)