Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

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 10:15:17 UTC

G.0:4 - Solution — CG‑Spec as the design-time legality gate

CG‑Spec is a notation-independent UTS-published object that, for a given CG‑Frame, defines:

  • the ComparatorSet (explicit, finite, typed) permitted in this frame,
  • the ScaleComplianceProfile (SCP) that constrains lawful operations per characteristic,
  • MinimalEvidence requirements per characteristic (lanes, carriers, freshness windows, crossing allowances, failure behavior),
  • the frame’s penalty and trust folding wiring (by explicit policy ids and edition pins),
  • AcceptanceStubs as design-time templates (thresholds remain governed by CAL, not by CG‑Spec),
  • optional method-family hooks (e.g., illumination/QD or explore↔exploit guards) as wiring only, with semantics governed by the corresponding patterns.

CG‑Spec constrains downstream gate checks by being referenced and pinned; it is not itself an admissibility mechanism.

G.0:4.1 - G.Core linkage (normative)

Builds on: G.Core (Part-G core invariants; governing-pattern citation)

GCoreLinkageManifest (normative; size-controlled via profiles/sets).

Effective obligations/pins/triggers are computed by union expansion of the referenced ids (per G.Core:4.2). Profiles/sets + explicit deltas; Nil‑elision applies.

  • CoreConformanceProfileIds :=
    • GCoreConformanceProfileId.PartG.AuthoringBase
    • GCoreConformanceProfileId.PartG.TriStateGuard
    • GCoreConformanceProfileId.PartG.UTSWhenPublicIdsMinted
  • CorePinSetIds :=
    • GCorePinSetId.PartG.AuthoringMinimal
    • GCorePinSetId.PartG.CrossingVisibilityPins
  • CorePinsRequired := (delta over PinSets)
    • UTSRowId[]
    • ReferenceMap
    • ComparatorSetRef.edition
    • SCPRef.edition
    • ΓFoldRef.edition?
    • MinimalEvidenceRef.edition?
    • FailureBehaviorPolicyId?
  • DefaultsConsumed := {DefaultId.GammaFoldForR_eff} (governing definition: CC‑G5.4 per G.Core.DefaultGoverningDefinitionIndex)
  • RSCRTriggerSetIds := {GCoreTriggerSetId.CGSpecGate}
  • RSCRTriggerKindIds := (delta over TriggerSets)
    • RSCRTriggerKindId.EvidenceSurfaceEdit
    • RSCRTriggerKindId.TokenizationOrNameChange
    • RSCRTriggerKindId.DefaultGoverningDefinitionChange
  • TriggerAliasMapRef := ∅

G.0:4.2 - CG‑Spec object model (normative)

CG‑Spec is authored per CG‑Frame. It SHALL:

  • be published to UTS as a notation-independent object,
  • reference CHR characteristics by id (measurement semantics remain governed by CHR packs),
  • constrain what comparisons and aggregations are lawful in this frame via explicit comparator specs and SCP bindings,
  • declare minimal evidence gates per characteristic, including explicit failure behavior wiring,
  • cite CN‑Spec for normalization/comparability policies (no duplication and no shadow specs),
  • publish edition pins and policy ids so downstream selection, parity, shipping, and refresh can be reproducible and RSCR-aware.

G.0:4.3 - CG‑Spec conceptual model (normative)

CG‑Spec :=
⟨
  UTS.id, Edition,
  Context, Purpose, Audience,

  Scope := USM.ScopeSlice(G) ⊕ Boundary{TaskKinds, ObjectKinds},

  entityOfConcern := ⟨GroundingHolon, ReferencePlane ∈ {world|concept|episteme}⟩,
  WorldRegime? ∈ {prep|live},          // only refines ReferencePlane=world; introduces no new planes

  ReferenceMap := minimal map{term/id → UTS|CHR|SoTA-pack refs},

  CNSpecRef := ⟨CN‑Spec ref, CNSpecRef.edition⟩,          // CN‑Spec is the governance card defined in A.19.CN (one governing definition)

  Characteristics := [CHR.Characteristic.id…],          // pointers only; authored in G.3 CHR pack

  // Edition-addressable segments (pins MUST be exposed)
  ComparatorSet := ⟨ComparatorSetId, ComparatorSetRef.edition, [ComparatorSpec…]⟩,
  SCP := ⟨SCPId, SCPRef.edition, map Characteristic.id → SCPEntry⟩,
  MinimalEvidence := ⟨MinEvId, MinimalEvidenceRef.edition?, map Characteristic.id → MinEvidenceEntry⟩,  // min pin: CGSpecRef.edition

  Γ‑fold := ⟨GammaFoldId, ΓFoldRef.edition?,   // pin the actual model/policy when a numerical fold is used
             defaultRef := DefaultId.GammaFoldForR_eff,
             override? := ⟨overrideRef, proof_refs, boundary_notes⟩
           ⟩,

  // Penalty routing and plane policies are by explicit policy ids.
  // For semantics (tri-state, penalties→R_eff-only, crossing visibility, set-return), cite G.Core and the governing definitions it identifies.
  CL‑Routing := ⟨policy_id, map Bridge.CL → penalty_spec⟩,
  Φ := ⟨phi_policy_id, phi_table_ref?, psi_policy_id?, phi_plane_policy_id?⟩,

  AcceptanceStubs := [AcceptanceStubId…],     // templates only; thresholds remain governed by CAL (G.4)

  // Optional hooks are wiring-only; semantics are governed by governing definitions.
  E/E‑LOG Guard? := ⟨policy_id, pins…⟩,
  Illumination? := ⟨
    Q_refs ⊆ Characteristics, D_refs ⊆ Characteristics,
    DescriptorMapRef.edition?, DistanceDefRef.edition?, DHCMethodRef.edition?,
    InsertionPolicyRef?, PromotionPolicyId?
  ⟩,

  RSCR := ⟨
  RSCRTestId[]?,             // SHOULD cover: illegal_op_refusals; unit and scale legality checks; freshness windows; // partial-order scalarisation refusals; threshold semantics; CL→R_eff routing;
                            // and refusal of degrade.order on unit mismatches (MM‑CHR).
    RSCRTriggerKindId[]
  ⟩,

  Naming := UTS Name Cards (twin labels plus bridge notes),
  PublicIdContinuity := ⟨governing definition, DRR link, refresh cadence, decay and aging policy, deprecations⟩,
  Provenance := ⟨carrier types, SoTA-pack refs, DRR/SCR linkage⟩
⟩

Local typing notes (non-exhaustive; normative intent but no shadow specs).

  • ComparatorSpec MUST be typed against SCP/CHR constraints. Examples of lawful comparators are frame-local choices and are authored here (e.g., dominance where lawful; lexicographic over typed traits; medoid/median for ordinal where lawful; explicit weighted sums only where legality is proven and units are aligned).
  • MinimalEvidenceEntry MUST declare: lane requirements, evidence carriers, freshness window (if any), and explicit failure behavior wiring. The semantics of {pass|degrade|abstain} and degrade(mode=…) are delegated to G.Core.

G.0:4.4 - Interfaces (normative)

InterfaceConsumesProduces / constrains
G.0‑1 CharterCG‑Frame brief, USM scope signalsCG‑Spec.Scope, entityOfConcern, ReferenceMap
G.0‑2 SCPCHR pack refs (G.3), legality proofsCG‑Spec.SCP + bindings to lawful operators/aggregators
G.0‑3 EvidenceSoTA inputs (G.2), source and carrier provenance account (A.10)CG‑Spec.MinimalEvidence, Γ‑fold segment pins, CL‑Routing, Φ ids
G.0‑4 PublishAll aboveVersioned CG‑Spec@UTS plus Name Cards, public-id continuity records, and RSCR tests and trigger kinds
G.0‑5 Expose_CrossingHooksCG‑Spec + crossing/plane/policy pinsGateCrossing inputs for GateChecks (E.18/A.21): plane checks, lane purity, lexical SD pins
→ G.1CG‑SpecGenerator guardrails (Comparator/SCP/MinEv pins); degrade/abstain wiring
→ G.2CG‑SpecHarvesting inclusion/exclusion and crossing policy constraints
→ G.3CG‑SpecRequired CHR characteristics/scales/operators to exist
→ G.4CG‑SpecAcceptance templates; evidence minima; Γ‑fold override proof hooks
→ G.5CG‑SpecEligibility gates and explainability pins (Path/UTS/policy ids)
→ G.6CG‑SpecEvidenceGraph/SCR pinning surface (policy ids + Path/PathSlice discipline)

G.0:4.5 - CG‑Spec authoring chassis (informative)

  1. Charter the frame. Declare Context, Scope, entityOfConcern, boundary examples/non-examples, and ReferenceMap.
  2. Draft ComparatorSet and SCP. Enumerate permitted comparator forms and bind each to CHR characteristics and legality constraints (scale/unit/polarity discipline). Attach guard bindings as explicit references/pins.
  3. Bind Characteristics. For every comparison, identify the CHR characteristics of the quantities being compared and cite them by id (reuse/mint via UTS discipline).
  4. Declare MinimalEvidence. For each characteristic: required lanes/carriers, freshness window, crossing allowances (if any), and explicit failure behavior wiring (tri-state semantics delegated to G.Core).
  5. Pin the support-composition basis. Cite DefaultId.GammaFoldForR_eff for the model-qualified rule. A numerical fold or loss pins its actual receiving model, compatible inputs, dependency assumptions, and justification refs; monotonicity and boundedness alone are insufficient. When no common aggregate is justified, the referenced rule retains separate support and a bounded synthesis. Publish any actually used Φ/CL policy ids; keep acceptance thresholds in G.4.
  6. Publish and register regression tests. Publish CG‑Spec@UTS with edition-pinned segments; register RSCR tests for the frame’s legality surfaces and evidence minima.
  7. Public-id continuity and refresh readiness. Declare refresh cadence and deprecations with lexical continuity notes; ensure RSCR trigger kinds are emitted as canonical ids.

G.0:4.6 - Extensions (pattern-scoped; non-core)

All blocks below are GPatternExtension modules (PatternScopeId; not new PatternIds). They store wiring only and cite governing patterns.

GPatternExtension: SpecRefSurfaces

  • PatternScopeId: G.0:Ext.SpecRefSurfaces

  • GPatternExtensionId: SpecRefSurfaces

  • GPatternExtensionKind: InteropSpecific

  • GoverningPatternId: A.19.CN

  • Uses: {A.19.CN}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • CNSpecRef.edition (and any CN-side policy ids referenced by CG‑Spec fields)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.LegalitySurfaceEdit}

  • Notes (wiring-only): CG‑Spec SHALL cite CN‑Spec; it SHALL NOT restate normalization/comparability semantics.

GPatternExtension: BridgeAndCLWiring

  • PatternScopeId: G.0:Ext.BridgeAndCLWiring

  • GPatternExtensionId: BridgeAndCLWiring

  • GPatternExtensionKind: InteropSpecific

  • GoverningPatternId: F.9

  • Uses: {F.9, G.7}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • BridgeCardId/BridgeId (when crossings are permitted)
    • CL / CL^k and Φ/Φ_plane policy ids (when penalties are in play)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.CrossingBundleEdit, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.ReferencePlaneEdit}

  • Notes (wiring-only): Crossing semantics and penalty routing are delegated to G.Core; this module only lists the required pins used by CG‑Spec entries.

GPatternExtension: SoTAPaletteInputs

  • PatternScopeId: G.0:Ext.SoTAPaletteInputs

  • GPatternExtensionId: SoTAPaletteInputs

  • GPatternExtensionKind: DisciplineSpecific

  • GoverningPatternId: G.2

  • Uses: {G.2}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • SoTA-Pack@CG‑Frame refs used to justify comparator admissibility, evidence minima, and crossing allowances (e.g., claim sheets, operator inventory, bridge matrix ids)
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EvidenceSurfaceEdit, RSCRTriggerKindId.CrossingBundleEdit, RSCRTriggerKindId.FreshnessOrDecayEvent}

  • Notes (wiring-only): Any SoTA palette/tradition semantics are governed by G.2. G.0 only requires that CG‑Spec entries cite the needed SoTA artefacts for auditability.

GPatternExtension: QDAndExplorationHooks

  • PatternScopeId: G.0:Ext.QDAndExplorationHooks

  • GPatternExtensionId: QDAndExplorationHooks

  • GPatternExtensionKind: MethodSpecific

  • GoverningPatternId: C.18

  • Uses: {C.18, C.19, C.23}

  • ⊑/⊑⁺: ∅

  • RequiredPins/EditionPins/PolicyPins (minimum):

    • DescriptorMapRef.edition?, DistanceDefRef.edition?, InsertionPolicyRef?
    • FailureBehaviorPolicyId / SoS‑LOG branch policy id when degrade(mode=…) is used
  • RSCRTriggerKindIds: {RSCRTriggerKindId.EditionPinChange, RSCRTriggerKindId.PolicyPinChange, RSCRTriggerKindId.TelemetryDelta, RSCRTriggerKindId.FreshnessOrDecayEvent}

  • Notes (wiring-only): CG‑Spec may declare optional QD/exploration hooks; semantics remain governed by the referenced method patterns.