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

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 22:54:38 UTC

G.0:5 - Archetypal Grounding — Tell–Show–Show; System / Episteme

G.0:5.1 - Archetype 1: System comparability under mixed evidence and unit constraints

Tell. Two labs compare energy efficiency results of a physical system where measurements use different rigs and units, and some evidence is missing.

Show (failure without CG‑Spec). The team averages an ordinal safety rating, mixes units (“kWh” vs “MJ”), and silently treats missing lanes as zeros. Cross-lab reuse also leaves any differences in measurement meaning and their effects unexplained.

Show (repair with CG‑Spec). A conformant CG‑Spec:

  • pins the lawful comparator(s) (e.g., unit-aligned ratio comparisons only; ordinal comparisons are order-only),
  • declares the MinimalEvidence lanes and carriers for each characteristic, together with the freshness windows used in this lab comparison,
  • declares explicit failure behavior wiring (tri-state semantics delegated to G.Core),
  • exposes Bridge and bounded-use pins when reuse projects between different local meanings under A.19.CN/F.9; unit conversion within the declared comparison basis follows CN-Spec and SCP,
  • publishes the pinned editions so parity/refresh can detect drift.

G.0:5.2 - Archetype 2: Epistemic comparability for selected-set publication across traditions

Tell. A team selects an R&D set using multiple evaluation traditions: safety assurance, cost models, and readiness heuristics.

Show (failure without CG‑Spec). The team collapses partial orders into a single score, hides the threshold policy in code, and cannot explain why cross-tradition penalties changed between runs.

Show (repair with CG‑Spec). A conformant CG‑Spec:

  • defines a comparator bundle (e.g., Pareto dominance + explicit lexicographic tiebreaks where lawful),
  • pins CNSpecRef.edition and the editioned segments (ComparatorSetRef.edition, SCPRef.edition, MinimalEvidenceRef.edition),
  • makes AcceptanceStubs explicit as templates while locating thresholds in CAL (G.4),
  • ensures RSCR triggers are emitted when comparator or policy pins change.