Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

A.0:4 - Solution - Normative onboarding glossary and publication hooks

A.0: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 a candidate is in your declared CharacteristicSpace. Use the declared DescriptorMapRef and DistanceDefRef, with no ad-hoc normalisation.C.17, C.18
Use‑Value (U / ValueGain)What the candidate 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 (declared retained set)Coverage or dispersion of the declared retained set under a named measurement policy; declare ReferencePlane. Its change on adding one candidate is DeltaDiversity_P.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). For a plane relation, retain its source/target planes and basis. Cite CL^plane for a used or required calibration and the Φ_plane policy and loss model for a used or required loss calculation; any numerical assurance penalty requires an applicable B.3 model.F.9, G.Core:4.2.3
Scale Variables (S)Ordered settings such as iteration budget, data exposure or resolution. For a scale claim, identify which settings vary, the tasks, the response of interest and the range examined.C.18.1
Scale Elasticity (χ)A supported response class (rising, knee, flat or declining) over the tested settings, or a wider range when a model or bound justifies the extension. Leave the class open when evidence is insufficient.C.18.1
BLP (Bitter‑Lesson Preference)A preference supported by a comparable, uncertainty-qualified scale comparison; begin with a cheap scale-claim probe. No scale claim yet or no scale-based preference are valid results. A local generality policy is a separate declared basis.C.19.1, C.24
Iso‑Scale ParityA comparison of candidates at matched resource settings under a justified common basis. To assess change with scale, compare responses at distinct settings. A knee needs at least three ordered settings along one coordinate or specified path, with evidence for the change in slope.G.9, C.18.1

(Use LEX‑BUNDLE for the applicable measurement and scope terminology.)

A.0:4.2 - Publication & telemetry duties (where these terms show up)

  1. UTS surface (Part F). When a UTS row describes a generator, selector, typed portfolio publication, or set-return publication surface, it MUST surface each glossary value or policy used by the declared operation or independently required by the receiving use. Type each reported value’s applicable units, scale, polarity and ReferencePlane under MM‑CHR and CG‑Spec, and cite its defining basis, including DescriptorMapRef and DistanceDefRef when used or required. (Row schema: F.17; shipping via G.10.)
  2. Parity & edition pins (Part G). When QD/OEE is in scope, pin the editions and policies used by the operation or required by its receiving use, including DescriptorMapRef.edition, DistanceDefRef.edition, the CharacteristicSpaceRef with its separate characteristicSpaceDescriptionRef: U.EpistemeRef under A.19:5.1.1.1 and TransferRulesRef.edition where applicable; record PathSliceId when required by that use. G.9 supplies the pin requirements for a parity use. Treat illumination/coverage as report‑only telemetry; publish an Illumination Map where G‑kit mandates parity records. For an empirical claim about how performance changes with scale, declare S and use comparison evidence at distinct settings. Reuse an applicable scale‑probe. A theoretical prediction states the assumptions and range that support it. Dominance policy defaults to ParetoOnly; including illumination in dominance MUST cite a CAL policy‑id.
  3. Tell‑Show‑Show (E.7/E.8). Any architectural pattern that claims generative behaviour MUST embed both a U.System and a U.Episteme illustration using this glossary (manager‑first didactics).

A.0:4.3 - Putting the glossary to use

  1. Declare CG‑Frame (what “quality” means; admissible units and scales) and ReferencePlane.
  2. Choose the Q components and DescriptorMap coordinates needed by the intended operation; retain their meanings and applicable editions.
  3. Choose an E/E‑LOG policy and record its policy‑id when the operation or receiving use requires explore↔exploit control.
  4. Apply G.5 selection/dispatch with its applicable basis pins; add parity pins for a parity use. Keep any consumed Front or Archive identified as the source set. For a set outcome, return Shortlist or RankedShortlist for retained alternatives, or JointUseSet when all named members are included for one named use. Return a handoff, abstain, or escalation when that is the G.5 outcome.
  5. Keep the G.5 outcome’s required content and basis pins. Publish that result only when the receiving use calls for publication, with its applicable PathIds/PathSliceId. Add a UTS row for a named governed value only when F.17’s independent naming and reuse conditions hold; otherwise reuse its existing designation. Follow the outcome’s continuation or stop. An Illumination Map remains report‑only telemetry by default.