A.0:4 - Solution - Normative onboarding glossary and publication hooks
4.1 Plain one‑liners (normative on‑ramp; formal anchors in C.17–C.19)
| Term | Plain definition (on‑ramp) | See |
|---|---|---|
| Novelty (N) | How unlike the known set a candidate is in your declared CharacteristicSpace. Compute admissibly (declared DescriptorMapRef + DistanceDefRef; 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‑LOG | Named, versioned explore↔exploit policy; governs when to widen space vs refine candidates; policy‑id is published. | C.19 |
| ReferencePlane | Where 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) | 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 Parity | Fair 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)
- UTS surface (Part F). When a UTS row describes a generator, selector, typed portfolio publication, or set-return publication surface, it MUST surface N, U, C, Diversity_P, E/E‑LOG
policy‑id,ReferencePlane, with units, scale, and polarity typed under MM‑CHR and CG‑Spec, and admissible references toDescriptorMapRefandDistanceDefRef. (Row schema: F.17; shipping via G.10.) - Parity & edition pins (Part G). When QD/OEE is in scope, pin
DescriptorMapRef.editionandDistanceDefRef.edition(and, where applicable,CharacteristicSpaceRef.edition,TransferRulesRef.edition) and recordpolicy‑id+PathSliceId. Treat illumination/coverage as report‑only telemetry; publish an Illumination Map where G‑kit mandates parity records. Declare S (Scale Variables) and run at least one scale‑probe (two points along S) when claiming scale‑amenability. Dominance policy defaults toParetoOnly; including illumination in dominance MUST cite a CAL policy‑id. - 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).
4.3 Minimal first-day construction
- Declare CG‑Frame (what “quality” means; admissible units and scales) and ReferencePlane.
- Pick 2–4 Q components + a simple DescriptorMap (≥2 dims) for N/D; publish editions.
- Choose an E/E‑LOG policy (explore↔exploit budget); record policy‑id.
- Apply G.5 selection/dispatch with parity pins. Keep any consumed
FrontorArchiveidentified as the source set. For a set outcome, returnShortlistorRankedShortlistfor retained alternatives, orJointUseSetwhen all named members are included for one named use. Return a handoff, abstain, or escalation when that is the actual G.5 outcome. - Keep the actual 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.