| CC‑G2‑CoreRef | A conforming G.2 artefact MUST satisfy the effective core obligations declared by the GCoreLinkageManifest in G.2:4.1 (per G.Core Expansion rule). | Keeps core invariants governed by G.Core. |
| CC-G2-Pluralism-1 | A conforming pack MUST include at least two Tradition lineages and at least three materially distinct entries, each identified by its source edition and claim region, with its EntityOfConcern, evidence norm, and comparison limits visible. | Prevents a single lineage or one renamed source cut from masquerading as synthesis. |
| CC‑G2‑Ledger‑1 | A conforming pack MUST include G.2a CorpusLedger with inclusion/triage status and explicit rationale hooks per entry. | Makes discovery/triage auditable. |
| CC‑G2‑FlowRecord‑1 | A conforming pack MUST include G.2h FlowRecord that traces identification → screening → eligibility → included at a minimum granularity sufficient to reproduce the corpus boundary. | Prevents “mystery inclusion” and supports refresh. |
| CC-G2-ClaimSheets-1 | For each included Tradition, the pack MUST include a ClaimSheetId naming exact sources and editions, claim regions, effective schemes where meaning matters, EntitiesOfConcern, comparison bases, evidence anchors, freshness notes, and intended use; it MUST NOT fuse cross-Tradition claims by default. | Keeps plurality and provenance explicit without a Context container. |
| CC‑G2‑Palette‑1 | A conforming pack MUST export SoTA_Set@CG‑Frame and SoTAPaletteDescription as citable views (via SoTA_SetId, SoTAPaletteDescriptionId) and ensure both are reconstructible from pack components by id (no hidden extra structure). | Prevents downstream scraping of prose; keeps “M2 output” explicit. |
| CC‑G2‑Palette‑2 | If the pack exports one derived tradition view such as TraditionFront or TraditionArchive, it MUST keep SoTAPaletteDescription explicit as the default base palette, keep that derivation recoverable, and cite the declared Q or reachability/coverage rule that disciplined that view. Derived tradition views MUST NOT silently replace the palette’s default meaning. | Keeps non-default tradition views recoverable without redefining palette-first semantics. |
| CC‑G2‑AtlasInterpretation‑1 | If the pack exports TraditionAtlasView, it MUST satisfy §4.7 and the cited A.19 interpretive-view declaration by value, including the reason a thinner view is insufficient. | Keeps atlas use conditional and its interpretation recoverable. |
| CC‑G2‑entityOfConcernMap‑1 | A conforming pack MUST include G.2g entityOfConcern Map, mapping (at minimum) each load‑bearing claim family and each minted/evolved public id to entityOfConcern := ⟨GroundingHolon, ReferencePlane⟩, and citing the relevant ClaimSheetId and evidence anchors (A.10 and/or G.6 paths when used). | Keeps plane/holon boundaries explicit and citable. |
| CC‑G2‑Alignment‑1 | Cross‑Tradition consolidation SHALL present either disjoint parallel claims with explicit divergence or an explicitly justified alignment proof. Reuse MUST cite the exact basis for every sense, kind or plane relation actually used and disclose its preservation and losses. Bundle/gate anchors MUST be supplied when an E.18 flow crossing or A.21 gate independently requires them, per CC‑GCORE‑CROSS‑1. | A kind correspondence alone requires neither an F.9 sense Bridge nor a flow-crossing bundle. |
| CC‑G2‑GammaSynth‑1 | If the pack asserts fusion or substitution across sources or across Tradition records (not merely “parallel divergent claims”), it MUST emit GammaEpistSynthId records satisfying G.2:Ext.GammaEpistSynthesis (provenance union + explicit alignment refs + assurance tuple refs). If no fusion or substitution is asserted, the pack SHALL state so explicitly. | Keeps the synthesis record (alias: G.2‑F) citable under its governing definitions. |
| CC‑G2‑Inventory‑1 | A conforming pack MUST include G.2c OperatorAndObjectInventory, sufficient for downstream CHR/CAL authoring to begin without re‑harvesting terms. | Ensures the pack is actionable. |
| CC‑G2‑Inventory‑2 | G.2c OperatorAndObjectInventory entries MUST be treated as stubs for downstream authoring: they MUST NOT embed acceptance thresholds or claim legality decisions locally. If an entry is not a citation of an already governed CHR/CAL artefact, it MUST be explicitly marked as stub (typing/lawfulness TBD) and MUST NOT be used as if lawful. Legality/threshold semantics are governed by G.3 for CHR and G.4 for CAL via explicit ids/pins. | Prevents “shadow CHR/CAL” and preserves lawfulness discipline without redefining it locally. |
| CC‑G2‑MeasurementLawful‑1 | If any inventory entry is presented as non‑stub (i.e., already lawful/typed), the pack MUST cite the governing lawfulness discipline (e.g., A.17–A.19/C.16 as applicable) and provide the minimal evidence anchors needed to justify that typing claim. | Prevents “quietly lawful” measurement claims inside the harvester pack. |
| CC-G2-MicroExamples-1 | For every load-bearing claim family, a conforming pack MUST include at least two worked micro-examples on heterogeneous substrates. Each names the source and edition, claim region, EntityOfConcern, comparison basis, and intended use; cites its evidence carrier or A.10 evidence-provenance path; and gives an applicable assurance tag. | Makes the synthesis teachable and inspectable; the example form supplies no meaning or authority. |
| CC‑G2‑UTS‑1 | If the pack proposes or evolves any public ids, it MUST publish UTS proposals (Name Cards + MDS where applicable) and cite them via UTSRowId[], satisfying CC‑GCORE‑UTS‑1 (delegation). | Keeps naming and evolution disciplined. |
| CC‑G2‑Families‑1 | SoS indicators and candidate evaluation constructs SHALL be represented as families/variants (windows/constraints/assumptions) with explicit Acceptance branch structure per variant (branch ids/labels only), not as single unqualified scalars; any scalar summary MAY be included only as report‑only unless explicitly promoted by governing patterns. (Set-return discipline is delegated to CC‑GCORE‑SET‑1.) | Prevents covert scalarization and keeps acceptance governed by downstream patterns. |
| CC‑G2‑HandOff‑1 | A conforming pack MUST emit hand‑off manifests to G.3, G.4, and G.5 that cite pack components by id and identify which families/operators are intended for downstream formalisation or registry entry. | Prevents downstream re‑authoring and drift. |
| CC‑G2‑CoverageGate‑1 | The pack MUST declare FamilyCoverageFloorK and enforce it as a harvesting gate. It MUST either (i) specify k explicitly in an explicit HarvestPolicyRef, or (ii) use the pattern‑local default rule governed by CC‑G2‑CoverageGate‑1. Default threshold (pattern-local): k=3. In both threshold branches, an explicit HarvestPolicyRef MUST fix the receiving question, population/scope, grouping, same-family equivalence and overlap rule before counting. The pack judgement cites that basis, its distinct units and result; all consumers reuse it. Missing basis returns unassessable. Duplicate references add zero, and a threshold override changes neither units nor independent pluralism duties. The independent CC-G2-Pluralism-1 duties remain. If the defined gate fails, the pack MUST (a) record the repair iteration in FlowRecord, and (b) broaden the search radius (new venues/corpora/contexts/traditions) rather than silently weakening the gate; if an exploration policy is used for this broadening, it MUST be pinned as a policy id/ref. | Makes “coverage floor” explicit and prevents “silent narrowing” under failure. |
| CC‑G2‑DistanceGate‑1 | If a diversity‑by‑distance gate is used, the pack MUST pin DistanceDefRef.edition and the declared threshold (δ), and treat edits as RSCR‑relevant per CC‑GCORE‑TRIG‑* (delegation). If no such gate is used, the pack SHALL explicitly state that it is not used. | Avoids implicit distance defaults and improves refreshability. |
| CC‑G2‑RSCR‑1 | A conforming pack MUST emit canonical RSCRTriggerKindId causes (not free text) for edits to evidence surfaces, name/tokenization surfaces (e.g., UTS proposals/aliases), crossings, planes, edition pins, and harvesting policy pins (HarvestPolicyRef), per CC‑GCORE‑TRIG‑1…TRIG‑4 (delegation). | Keeps refresh reason codes stable and typed. |
| CC‑G2‑Ext‑GammaEpist‑1 | If G.2:Ext.GammaEpistSynthesis is used (i.e., any fusion/substitution is asserted), the pack SHALL expose the required pins listed in that extension and SHALL NOT redefine Γ‑fold/Φ/penalty semantics locally (cite governing definitions by delegation). | Keeps synthesis auditable without creating shadow specs. |
| CC‑G2‑Ext‑HarvestProtocols‑1 | If G.2:Ext.HarvestProtocols is used, the pack SHALL expose the required pins/criteria ids listed in that extension and SHALL NOT redefine evidence/quality semantics outside the declared protocol profile. | Keeps protocol variation explicit and separately citable. |
| CC-G2-Ext-DHC-1 | If G.2:Ext.DHCAlignmentHooks is used, expose the DHC method edition, exact compared F.17 cell population, counted obtaining directed F.9 relation refs with their orientation and admitted-use qualifiers, evidence paths, and C.21 Unit obtaining_relations/100_compared_cells. CL labels alone neither change that population nor impose a counting threshold. Cite any separate receiving-use policy under its own authority. | Keeps the quantity identical to the C.21/G.7 definition. |
| CC‑G2‑Ext‑NQD‑1 | If G.2:Ext.NQDAnnex is used, the pack SHALL expose the required pins/editions/policies listed in that extension and SHALL NOT redefine QD semantics locally. | Keeps QD/OEE extension pins replayable and non‑shadowing. |
| CC‑G2‑Ext‑Interop‑1 | If G.2:Ext.InteropForms is used, the pack SHALL expose the required interop pins and SHALL NOT introduce alternative legality/acceptance semantics. | Prevents “foreign gate” shadowing. |