FPF Reference

4) Solution — Normative onboarding glossary and publication hooks

Preface node heading:4-solution-normative-onboarding-glossary-and-publication-hooks:798

Content

4.1 Plain one‑liners (normative on‑ramp; formal anchors in C.17–C.19)

TermPlain definition (on‑ramp)See
Novelty (N)*How unlike the known set in your declared CharacteristicSpace. Compute lawfully (declared DescriptorMapRef + DistanceDefRef; no ad‑hoc normalisation).C.17, C.18
Use‑Value (U / ValueGain)*What it helps you achieve now under your CG‑Frame; tie to acceptance/tests; publish units, scale kind, polarity, ReferencePlane.C.17, C.18
Constraint‑Fit (C)Satisfies must‑constraints (Resource/Risk/Ethics); legality via CG‑Spec; unknowns propagate (never coerce to zero).C.18, G.4
Diversity_P (portfolio)*Adds a new niche to the portfolio; measured against the active archive/grid, not a single list; declare ReferencePlane for each head.C.17, C.18
E/E‑LOGNamed, versioned explore↔exploit policy; governs when to widen space vs refine candidates; policy‑id is published.C.19
ReferencePlaneWhere a value lives: world (system), concept (definition), episteme (about a claim). Plane‑crossings add CL^plane (penalties to R only); cite policy‑id.F.9, G.6
Scale Variables (S)The monotone knobs along which improvement is expected (e.g., parameterisation breadth, data exposure, iteration budget, resolution). Declare S for any generator/selector claimed to scale.C.18.1
Scale Elasticity (χ)Qualitative class of improvement when moving along S (e.g., rising, knee, flat in the declared window). Used as a selection lens; numeric laws live in domain contexts.C.18.1
BLP (Bitter‑Lesson Preference)Default policy that prefers general, scale‑amenable methods over domain‑specific heuristics, unless forbidden by deontics or overturned by a scale‑probe.C.19.1, C.24
Iso‑Scale ParityFair comparison across candidates at equalised scale budgets along S; may also include scale‑probes (two points) to test elasticity.G.9, C.18.1

(Registers & forbidden forms per LEX‑BUNDLE; avoid “axis/dimension/validity/process” for measurement and scope.)

4.2 Publication & telemetry duties (where these terms show up)

  1. UTS surface (Part F). When a UTS row describes a generator, selector, or portfolio, it MUST surface N, U, C, Diversity_P, E/E‑LOG policy‑id, ReferencePlane, with units/scale/polarity typed under MM‑CHR / CG‑Spec, and lawful references to DescriptorMapRef/DistanceDefRef. (Row schema: F.17; shipping via G.10.)
  2. Parity & edition pins (Part G). When QD/OEE is in scope, pin DescriptorMapRef.edition and DistanceDefRef.edition (and, where applicable, CharacteristicSpaceRef.edition, TransferRulesRef.edition) and record policy‑id + PathSliceId. Treat illumination/coverage as report‑only telemetry; publish an Illumination Map where G‑kit mandates parity artefacts. Declare S (Scale Variables) and run at least one scale‑probe (two points along S) when claiming scale‑amenability. Dominance policy defaults to ParetoOnly; including illumination in dominance MUST cite a CAL policy‑id.
  3. Tell‑Show‑Show (E.7/E.8). Any arhitectural pattern that claims generative behaviour MUST embed both a U.System and a U.Episteme illustration using this glossary (manager‑first didactics).

4.3 Minimal recipe (run this on day one)

  1. Declare CG‑Frame (what “quality” means; lawful units/scales) and ReferencePlane.
  2. Pick 2–4 Q components + a simple DescriptorMap (≥2 dims) for N/D; publish editions.
  3. Choose an E/E‑LOG policy (explore↔exploit budget); record policy‑id.
  4. Call the selector under G.5 with parity pins; return a set (Pareto/Archive), not a single score.
  5. Publish to UTS + PathIds/PathSliceId; Illumination Map is report‑only telemetry by default.