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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:15:10 UTC

G.3:4.2 - Output surface: CHR Pack@CG‑Frame (normative)

CHR Pack@CG‑Frame is the CHR kit payload that downstream patterns cite and pin (it is not a “shadow spec” for CN/CG).

Minimum exported objects (kit surface):

  • CHR.Characteristic[]
  • CHR.Scale[]
  • CHR.Level[] (when the scale type requires explicit level sets / order structure)
  • CHR.Coordinate[] (encodings + legality annotations; never an implicit “upgrade” of measurement structure)
  • CHR.Guards (guard macro surface; semantics governed by cited definitions; see G.Core and A.18)
  • CHR.LegalityMatrix (admissible operations per scale type / unit / polarity regimes)
  • CHR.AggregationSpecs (typed aggregators/comparators + proof hooks + edition pins where applicable)
  • UTS publication bundle: Name Cards (twin labels), public-id continuity notes, and (when applicable) bridge and loss notes
  • RSCR artefacts: RSCRTestId[] + worked examples + provenance pins (ReferencePlane, Path/PathSlice, policy ids)

Mandatory provenance pins (conceptual, notation‑independent):

  • ReferencePlane
  • PathId/PathSliceId citations for worked examples/tests
  • R‑anchors (conceptual; KD‑CAL lanes when used) realised via PathId/PathSliceId and, where applicable, A.10 anchor/carrier refs
  • policy pins used by crossings or plane moves (when exercised)
  • edition pins for any referenced method or metric definitions that affect interpretation