G.4:4.2 - CAL Pack@CG-Frame surface (kit governed by this pattern)
CAL Pack@CG-Frame is the CG‑Frame’s published CAL Pack. Minimally, it provides:
-
CAL.Charter— identification and assumption basis for this CAL pack:- cites the exact
CGFrameId,EntityOfConcernRef, andReferencePlane, - cites the governance and legality records (
CNSpecRef,CGSpecRef) by edition, - records the assumption envelope on which the acceptance predicates rely without minting another governance or legality record.
- cites the exact
-
TaskMap— the conditional G.4 handoff record toG.5when CAL gates are current; one exact edition names the task, cites the already constituted C.22TaskSignatureRefand exact charter edition, and cites the acceptance-clause, operator, flow, and evidence-profile refs that selection consumes. It does not constitute the TaskSignature or contain threshold values. -
CAL.Operator[]— UTS‑published typed operation declarations governed byA.6.1; a card declares possible arguments, result kinds, and conditions but does not assert that an operation ran:- declared signature over CHR types,
- declared preconditions and postconditions, including references to legality guard macros,
- provenance and evidence hooks identified by ids or pins independently of tool behavior.
-
CAL.Acceptance[]— typed predicate declarations whose use is bounded by the declaredClaimScope, any evaluation window required by the predicate or receiving use, and any separate qualification window that limits use; a clause declares how an actual application is judged but is not itself a verdict:- binds to CHR characteristic ids and to exact A.6.1 argument declarations for admissible C.16 measurement-result epistemes (and, when inducing numeric comparison or aggregation, to
CG‑Spec.characteristicids), - keeps the exact current result episteme in the later application binding rather than in the reusable clause,
- exposes unknown handling and failure behavior via policy pins.
- binds to CHR characteristic ids and to exact A.6.1 argument declarations for admissible C.16 measurement-result epistemes (and, when inducing numeric comparison or aggregation, to
Each resultInputDeclarationRef resolves an A.6.1 ArgumentDeclaration. Its meaning identifies the C.16 measurement-result episteme expected by the clause. The declaration states the ValueKind and binding designation rule and requires a result for the named Characteristic with the admissible shape. A one-off clause may also cite an already existing episteme in fixedResultEpistemeRefs[]?; mark that clause one-off instead of presenting it as reusable.
-
CAL.Flow[]— legality‑checked declarations of possible operator composition; a declared DAG is not performed work:- declares result kind (scalar only when lawful; selected-set / set-result when partial orders remain partial orders),
- records which acceptance clauses gate which flows.
-
CAL.EvidenceProfiles— evidence wiring surface:- lane tags under their declared regime / provenance anchors / policy pins needed for
SCRand audit surfaces, - currentness conditions needed by the receiving use, with freshness-window and decay/Γ_time policy refs pinned only when those mechanisms are used.
- explicit
ReferencePlaneand any used penalty-policy refs (Φ(CL),Ψ(CL^k),Φ_plane); the ProofLedger supplies the receiving quantity, scale, input meanings, assumptions, and derivation or calibration. Monotonicity and boundedness alone do not justify a numerical loss.
- lane tags under their declared regime / provenance anchors / policy pins needed for
-
Optional
CAL.NQD[]— QD/OEE‑related calculus surfaces when declared:
A CAL clause that consumes G.7 calibration states its exact receiving use and premises. A locally justified CL threshold is an additional policy condition; the ProofLedger and named authority must support that condition. It does not replace the bounded-use claim, target classification or reliance result. A policy waiver changes only the authorized policy condition.
-
CAL.ProofLedger— a proof/justification ledger:- links operator/flow/clause ids to their needed legality and soundness results; a numerical support fold includes the B.3/C.2.2 receiving model, compatible scales and inputs, dependence assumptions, and boundary behavior.
-
Publication artifacts:
- UTS Name Cards under F.17/F.18 for all public ids,
- ids for RSCR tests and worked examples,
- deprecation notices and edition bump notes as public-id continuity records.
Boundary discipline (normative):
- No shadow specs: CAL artefacts cite
CN‑Spec/CG‑Specand do not introduce competing “local specs” (delegated; seeCC‑GCORE‑CN‑CG‑1via CC‑G4‑CoreRef). - Shipping boundary:
G.10governs shipping; seeCC-GCORE-SKP-1via CC-G4-CoreRef. - Refresh boundary: CAL publishes pins/payload for refresh;
G.11governs refresh orchestration.
Minimal schema fragments (notation‑independent; fields for citation, not an implementation schema):
CAL.Charter :=
⟨ charterId, charterEdition, cgFrameId, entityOfConcernRef, referencePlaneRef,
CNSpecRef.edition, CGSpecRef.edition, assumptionEnvelope ⟩
CALCharterRef := <charterId, charterEdition>
TaskMap :=
⟨ taskMapId, taskMapEdition, charterRef := CALCharterRef,
taskRef, taskSignatureRef := TaskSignatureRef,
acceptanceClauseRefs[], operatorRefs[], flowRefs[], evidenceProfileRefs[] ⟩
TaskMapRef := <taskMapId, taskMapEdition>
CAL.Pack@CG-Frame :=
⟨ calPackId, charterRef, taskMapRef, operatorIds[], acceptanceClauseIds[], flowIds[],
evidenceProfileIds[], proofLedgerId, nqdIds[]?,
utsRowIds[], workedExampleIds[], rscrTestIds[], publicIdContinuityNoteIds[] ⟩
CAL.Operator :=
⟨ operatorId(UTS), signature(CHR-typed), preconditions[], postconditions[],
evidenceProfileRefs[]?, failureBehaviorRef?, crossingRefs[]? ⟩
CAL.Acceptance :=
⟨ clauseId(UTS), characteristicRefs[], resultInputDeclarationRefs[],
fixedResultEpistemeRefs[]?, // deliberately one-off clause only
cgSpecCharacteristicRefs[]?, predicateRef, claimScopeRef,
evaluationWindow?, qualificationWindow?, unknownHandlingRef,
failureBehaviorRef, evidenceProfileRefs[]?, crossingRefs[]? ⟩
CAL.Flow :=
⟨ flowId(UTS), dag(operatorIds, edges), gateClauses(acceptanceClauseIds),
resultKind, decisionAidPolicyRef? ⟩
CAL.EvidenceProfile :=
⟨ evidenceProfileId(UTS), lanes(declared tags), anchors(A.10)[],
freshnessPolicyPins[]?, penaltyPolicyPins[]?, ΓFoldRef.edition? ⟩
lanes carries the tags and meanings of the declared evidence-lane regime; when a CHR charter supplies that regime, retain its tags and meanings. The assurance claim, receiving use and selected contributions follow B.3/B.3.3. Keep any consumed C.2.2:4.1 tuple, with its exact claim and F, G and R_eff values, separately recoverable from the lane tags.
CALCharterRef and TaskMapRef each resolve one immutable edition. A changed charter, task, TaskSignature edition, clause, operator, flow, evidence profile, or edition-bearing cited list creates a new taskMapEdition; an old TaskMapRef continues to resolve its old values. The C.22 TaskSignature remains a separately constituted episteme. The map relates that exact signature to the CAL declarations used by selection but neither derives the signature nor duplicates their thresholds.
When CAL authoring relies on SoTA coverage, consume G.2’s pack CoverageJudgementRef with its HarvestPolicy basis and receiving question. Preserve the distinction between family coverage and lineage/material-entry plurality. A CAL clause does not turn a combined method/generator count into method-only coverage.