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 05:16:27 UTC · snapshot created 2026-10-03 05:17:06 UTC · last check 2026-10-03 05:25:10 UTC

G.13:4.3 - Generation‑first interop flow (notation‑independent; governing-definition delegating)

  1. Register source editions. Author ExternalIndexCard@Context for each external source/snapshot used for SoTA authoring, including ExternalEdition and the entityOfConcern plane anchor.

  2. Author mapping recipes. Create ClaimMapperCard@Context describing which FPF artefacts are produced (ClaimSheets, BridgeHints, feature sets, UTS proposals), and which policies/specs constrain the mapping (policy refs + optional PlaneMapRef / ScaleEmbeddingSpecRef).

  3. Produce FPF‑native inputs. Use the alignment recipe outputs as inputs to:

    • G.2 harvesting (ClaimSheets / operator & object inventories / candidate bridge hints),
    • G.3 CHR typing (when numeric signals are formalized as CHR characteristics/scales/coordinates),
    • G.4 acceptance/threshold policies (when a downstream decision requires explicit CAL policy rather than telemetry),
    • G.12 dashboards (when derived SoS features support DHC readings; measurement claims consume C.16 results with the C.21 replay basis required by their use).
  4. Feed selection/parity/shipping without smuggling semantics.

    • G.5 consumes the produced artefacts under its own governing spec refs and returns its declared outcome, including the applicable set-result kind, narrowed handoff, abstain, or escalation result (selector semantics remain governed by G.5 + G.Core).
    • G.9 parity consumes pinned editions/windows and produces traceable parity reports.
    • G.10 shipping may include interop surfaces as cited publications or records; G.13 does not govern shipping.
  5. Emit telemetry and refresh causes. On any change in external editions, alignment policies, plane maps, or embedding specs, emit:

    • a canonical RSCRTriggerKindId (per G.Core),
    • a scope (PathSliceId[] and/or PatternScopeId),
    • payload pins (editions/policies/UTS rows), enabling G.11 to plan slice‑scoped refresh.