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

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 13:05:11 UTC

G.8:4.2 - Kit: objects and naming discipline (LEX heads; twin‑register safe)

Objects / surfaces (pattern-governed).

  • SoS‑LOG.Rule An executable tri‑state decision schema {pass | degrade(mode) | abstain} for (TaskSignature, MethodFamily), cited by a rule id. (“pass” may be described as “admit” in prose, but the normative tri‑state vocabulary is G.Core’s {pass|degrade|abstain}.) Semantics are governed by C.23. G.8 only packages rule ids and binding pins.

  • SoS‑LOGBundle@Context A selector‑facing, notation‑independent packaging object published to UTS.

  • AdmissibilityLedger@Context A run‑time ledger view that records admissibility outcomes, cited evidence paths, branch tokens, and the pins required for audit/refresh.

  • MethodFamily.MaturityCardDescription@Context A maturity ladder description published as a citable artefact: ordinal/poset, closed rungs, ReferencePlane declared; no thresholds inside.

Naming discipline (E.10 + “Spaces ≠ Maps”).

  • Technical heads are normative; Plain twins are didactic only and MUST NOT cross kinds.

  • Do not alias CharacteristicSpace and DescriptorMap.

    • DescriptorMapRef is a map‑reference (typically used with QD archives).
    • CharacteristicSpaceRef is a space‑reference (grid/cell semantics, if used).

  • Editions are pinned on …Ref.edition fields (not on informal names).