fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 34628–34640

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:00:05 UTC

A.19.CHR:4.4 - Suite spec pins

CHRMechanismSuiteDescription.suite_spec_pins MUST be refs‑only and MUST include:

  1. Required spec refs: {CNSpecRef, CGSpecRef} (as required pins, not copied content).

  2. Required planned baseline: cite the exact A.15.2 WorkPlan and content locator carrying the selected suite, declaration and spec editions. A typed A.15.3 item is additional only when §4.1.2 applies.

  3. Required edition pins / policy pins (when applicable):

    • editions{CG‑Spec, ComparatorSet, UNM.TransportRegistryΦ, …} when the chosen protocol path is edition‑sensitive,
    • policy‑id pins for Φ/Ψ/Φ_plane when crossings are expected.

Tell (discipline). Spec pins are anchors; they do not embed tables (CL ladders, Φ registries) and do not introduce transport edges.