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

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 08:40:10 UTC

A.19.CHR:4.2.1 - CHR SlotKind Lexicon (suite‑wide minimum)

Tell. To prevent SlotKind drift across the CHR mechanism chain and across SoTA wiring modules, CHR mechanism declarations SHOULD use the SlotKind tokens from this lexicon whenever they refer to the corresponding semantic roles. New SlotKinds MAY be introduced, but only by first extending this lexicon (suite‑governed), then citing the new SlotKind from the affected mechanism card.

Lexicon (minimum). Tokens below are SlotKind names (not types). Concrete meanings, ValueKind / reference designation and binding rules come from the governing A.6.1 operation-local declarations; A.19 and G.0 constrain their domain use. A.6.5 relation SlotSpecs are not the source of these operation positions.

  • Core suite SlotKinds

    • CharacteristicSpaceSlot
    • CNSpecSlot
    • CGSpecSlot
    • ContextSlot

  • Indicatorization

    • IndicatorChoicePolicySlot
    • IndicatorSetSlot — A.19.UINDM’s selected declaration-local basis positions, retained with the exact CharacteristicSpace basis; each position keeps its Characteristic and Scale
    • JustificationSlot

  • Scoring

    • InputProfileSlot
    • ScoreProfileSlot

  • Aggregation

    • MeasureSetSlot
    • GammaFoldSlot
    • GammaTimeRuleSlot (optional)
    • AggregatedMeasureSlot
    • ContributorSetSlot (optional)

  • Comparison

    • LeftProfileSlot
    • RightProfileSlot
    • ComparatorSpecSlot
    • ComparisonResultSlot

  • Selection

    • CandidateSetSlot
    • CriteriaSlot
    • TaskSignatureSlot (optional)
    • SelectionSlot

  • Evidence / admissibility (optional, policy‑bound)

    • MinimalEvidenceSlot (optional)

Note. This lexicon is intentionally small and role‑based: it constrains naming, not method semantics. Method/discipline specifics belong in SoTA packs (G.2) and wiring‑only GPatternExtension modules, not in the suite core.