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:20:20 UTC

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).