#G.Core:7 - Conformance checklist (normative) — CC‑GCORE
Preface node
heading:g-core-7-conformance-checklist-normative-cc-gcore:135994
#What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
#Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
#Content
The following conformance items retain their stated applicability conditions. Each Part-G pattern cites the items it uses, directly or through its linkage manifest.
| ConformanceId | Statement |
|---|---|
| CC‑GCORE‑DEL‑1 | A conforming G.Core SHALL be delegation-first: if a norm is already governed by A.6.7, A.15.3, A.19, G.0, A.19.CHR, or a relevant Part E pattern, G.Core cites that governing definition rather than duplicating semantics. |
| CC‑GCORE‑CN‑CG‑1 | A Part-G use governed by CN‑Spec or CG‑Spec SHALL cite the applicable specification and edition. No Part-G pattern introduces a shadow specification; apply SuiteObligations.transport_declarative_only and SuiteObligations.cg_spec_cite_required_for_numeric_ops under their governing conditions. |
| CC‑GCORE‑OBL‑1 | A conforming G.Core SHALL treat the obligation vocabulary in A.6.7:4.2 as the canonical naming surface for Part‑G‑wide obligations and SHALL NOT introduce competing obligation names for the same norms. |
| CC‑GCORE‑CROSS‑1 | A Part-G pattern SHALL apply A.6.7's correspondence and visibility obligations only to the actual relations and receiving uses defined there. An F.9 correspondence, C.3.3 kind correspondence and separately governed plane relation keep their own bases; an actual E.18 flow crossing or A.21 gate keeps its required bundle/gate anchors. Changes to crossing-relevant artefacts trigger RSCRTriggerKindId.CrossingBundleEdit and, for a changed edition pin, EditionPinChange under multi-cause discipline. A changed entity, context/plane label or edition alone creates neither Bridge nor crossing. |
| CC‑GCORE‑GUARD‑1 | A Part‑G pattern SHALL treat `GuardDecision := {pass |
| CC‑GCORE‑PEN‑1 | A Part-G pattern SHALL apply A.6.7:4.2(2) to its loss and assurance-penalty claims (SuiteObligations.penalties_route_to_r_eff_only), including that clause's model-bound applicability and separation from legality, invariant and claim-scope judgments. |
| CC‑GCORE‑SET‑1 | A Part‑G pattern SHALL preserve the result type of the admitted operation under a partial order and SHALL prohibit silent scalarization or totalization. A completed A.19.CPM Compare returns a set of relation or poset tokens in ComparisonResultSlot. CompareEligibility returns a separate guard decision. On abstention the comparison has no returned binding. A completed G.5-3 selection returns its candidate set. G.5-6 may declare exact members under an existing inclusion decision. An abstention or handoff has its own grounds. Any scalar summary SHALL remain report-only unless admitted as a comparator for this use (SuiteObligations.no_silent_scalarisation_of_partial_orders, SuiteObligations.no_silent_totalisation). |
| CC‑GCORE‑SKP‑1 | A Part‑G pattern SHALL preserve the suite/kit/pack distinction (A.19.CHR) and SHALL keep shipping concerns governed by their canonical governing patterns (e.g., G.10) rather than embedding shipping semantics into unrelated kits or core invariants. |
| CC‑GCORE‑P2W‑1 | When a Part-G use adopts an edition/reference baseline as planned work, identify its A.15.2 WorkPlan and local content locator. A.15.3 typed planned filling applies only to an independently declared argument or relation position, with its own meaning and binding rule. Final launch values and actual bindings remain enactment claims; gate decisions keep their own governor. Ordinary source or edition citation alone does not assert planned work. |
| CC‑GCORE‑LINK‑1 | Each G.x makes its applicable core obligations, pins, defaults and trigger kinds recoverable under G.Core:4.2, through direct references or a GCoreLinkageManifest. Nil-elision for ∅ does not waive an applicable obligation. |
| CC‑GCORE‑LINK‑2 | A CC‑Gx‑CoreRef, when used, delegates to the effective core obligations and their conditions, including referenced profile expansions. Equivalent direct delegation is sufficient. |
| CC‑GCORE‑UTS‑1 | If a Part‑G pattern mints, deprecates, or evolves any public identifier, it SHALL publish/update the corresponding UTS entries and cite them via UTSRowId pins, delegating UTS semantics (Tech and applicable Plain designations, alias/deprecation discipline, edition pins) to its canonical governing definition F.17 (UTS). |
| CC‑GCORE‑ID‑1 | When deduplicating, existing public CC ids in G.x SHALL NOT be deleted/renamed; they SHALL become delegation items to relevant CC‑GCORE‑… items. |
| CC‑GCORE‑ID‑2 | Publications SHALL preserve non-CC public ids, including UTSRowId and RSCRTriggerAliasId tokens (e.g., T0…T7). Express changes through aliases, deprecation notices and new editions. An old id SHALL NOT be reused or redefined. When downstream behaviour can change, the change SHALL emit a canonical RSCRTriggerKindId (e.g., TokenizationOrNameChange, EditionPinChange). |
| CC‑GCORE‑TRIG‑1 | A conforming G.Core SHALL define the canonical RSCRTriggerKindId catalogue and SHALL be its single writer. |
| CC‑GCORE‑TRIG‑2 | Any G.x that uses local trigger tokens SHALL provide (or cite) a TriggerAliasMap mapping each alias to canonical RSCRTriggerKindId. |
| CC‑GCORE‑TRIG‑3 | Any artefact that records RSCR/SCR/refresh reasons SHALL record canonical RSCRTriggerKindId (aliases may be recorded as labels only). |
| CC‑GCORE‑TRIG‑4 | A conforming G.Core SHALL keep TriggerAliasMap.* consistent with the governing patterns’ deprecated trigger alias catalogues (e.g., G.11:T*). Any change to an alias mapping SHALL be treated as refresh‑sensitive; at minimum it SHALL be recorded/emitted as RSCRTriggerKindId.TokenizationOrNameChange (and, if the mapped trigger kinds change, the corresponding canonical kinds apply as well). |
| CC‑GCORE‑DEF‑1 | A conforming G.Core SHALL maintain a Default Governing Definition Index for Part‑G defaults, ensuring each DefaultId.* names exactly one governing definition (a CC item, policy id or TaskSignature rule). All other patterns SHALL cite the governing definition and SHALL NOT state competing defaults. Any governing-definition change MUST be recorded as RSCRTriggerKindId.DefaultGoverningDefinitionChange. |
Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)