A.6.B:7 — Mini-register: Claim Register (informative, recommended)
Preface node
heading:a-6-b-7-mini-register-claim-register-informative-recommended:12669
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 Claim Register is a drift‑control device that lists every classifiable statement verbatim with classification metadata. It is not a new meaning authority.
Guidance (informative):
- The Statement cell should contain the normative text as authored (copied by value), not a paraphrase.
- Canonical location should point to the one place the statement “lives” (e.g.,
Signature.Laws,Mechanism.AdmissibilityConditions,TechCard.NormsCommitments,Evidence.Carriers), so other faces can cite its ID or canonical location. - Stack layer should be one of
{Signature, Mechanism, Norms-and-commitments, Evidence-and-carriers}to make classification auditable. - A.7 primary layer identifies the claim's EntityOfConcern, with its kind when needed. The concern may itself be a Description episteme or publication carrier; it remains distinct from the episteme carrying the claim.
- viewRef and viewpointRef are used when the corresponding view or viewpoint identity matters under E.17;
U.Viewmembership requires E.17.0 conformance. - Use References for explicit cross‑quadrant links: for example, which
D-*states a requirement or individual duty to enforce whichA-*predicate, whichE-*reports the result or evidence used to adjudicate which commitment, and whichL-*defines a metric used byE-*. Add external standards or policies where applicable.
Last Updated: 2026-10-12 — upstream FPF commit f2bc67dd (github.com/ailev/FPF)