A.6.B:6.1 — Explicit reference rule

Preface node heading:a-6-b-6-1-explicit-reference-rule:15399

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

If a claim’s meaning materially depends on another L/A/D/E-classified claim, that dependency MUST be represented as an explicit reference to its ID or canonical location. A faithful restatement may explain the referenced content; it does not define an alternative rule.

A reader can then follow the explanation back to its governing claim and reconsider dependent uses when that claim changes.


Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)