C.19:7 - Conformance Checklist
-
C19-1 When a C.18 generation or archive record relies on a named C.19
EmitterPolicy, it SHALL cite that profile inemitterPolicyRef?. If the active insertion policy is not inherited, record it ininsertionPolicyRef?. If the deduplication threshold is not inherited, record scalardedupThreshold?together with itsdeduplicationBasisRef?anddeduplicationUnit?; never encode that scalar as a reference. These fields are not required without that policy dependence. -
C19-2 The characteristic set and indicators used for dominance MUST be declared and eligibility conditions applied first. If use-value participates in current
Q, the record cites the C.16.QQS.UseValueobjective head in that Q; otherwise it states that the criterion remains outside Q. (References to C.18 generator operators are descriptive only; LOG exports no Γ.) -
C19-3 If a lens is used, its id MUST be recorded; do not label scalarized top-1 as “frontier”.
-
C19-4 Promotion of
SurpriseorIlluminationinto dominance MUST be explicit in policy. -
C19-5 A pool-policy record creates no
SystemRoleAssignmentStateRelation, system-role assignment, permission, plan, budget or Work occurrence. For each such claim needed when implementation follows, establish its context, scope and independent basis under the applicable subject rule. Precise role, assignment or assignment-state claims need their respective grounds; ordinary implementation wording does not require asserting all of them. -
C19-6 When a pool-treatment lens uses dominance or tie-breakers, it MUST document or cite the applicable
Eligibility → Dominance → Tie-breakerscomparison. Eligibility is for the affected use. Continuation and retention without that comparison follow §4’s contribution, commitment, and opportunity-cost basis; exploitation readiness is separate. For every tie-breaker used, cite a constituted result with the compatible basis required above; unused optional tie-breakers need no result. Any promotion of Surprise or Illumination into the dominance set MUST be named by lens or policy id and recorded in provenance. -
C19-7 (pattern-change boundary). A project-local choice or revision of an
EmitterPolicy,DescriptorMap,DistanceDef, sampler, quota, orδ_familythreshold stays under C.19 and the decision or result that consumes it; it does not invoke E.15 merely because a profile changed. When the definition is changed in an existing FPF pattern edition, use E.15 to compare the exact predecessor and candidate, classify the effect, and repair dependent consumers. Compare materially plausible candidate definitions when the question requires it. Use C.18 for their generation/archive account, C.40 for missing construction and C.19 only when their live-pool policy is the question. No default heterogeneity quota or sampler is defined here. Keep the policy and card ids in the existing decision, change, or SCR result that needs them; create no separate authoring trace. -
C19-8 When a heterogeneity-first profile is used, provenance MUST name each admitted heterogeneity constraint and its governing policy id. If a family or subfamily quota applies, record the exact quota vector and family-definition id; if sampling applies, record the sampler class, seed when relevant, and sampler-policy id.
-
C19-9 A
PoolPolicyResultMUST identifylivePool,governingLens,changeTrigger, and exactly onecurrentTreatmenttoken fromwiden | keep_frontier | narrow_to_subset | sunset_line;lensand space-separated treatment spellings are not alternate record fields or values. -
C19-10 If the question under repair is local option choice, an enactment-facing plan, selector-facing result declaration, or publication availability,
C.19MUST name the applicable pattern rather than restate it:C.11, the applicable A.15 pattern (C.24only for tool or service call planning after the action is fixed),G.5,E.17, orE.24.PUB. -
C19-11 If goal- or task-space expansion, autotelic pressure, or capability-discovery support is used, the record MUST cite
goalSpaceExpansionPolicyRefonly when one independently declared policy governs the treatment; retain each supporting result or claim under its native direct-owner reference, kind, identity, claim episteme when applicable, and subject-pattern locator; adda10RelianceRefwhen the needed evidence or source basis requires a replayable A.10 account; and usecompetenceModelRefonly for one exact model episteme. None of these inputs becomes a generic signal or cue, default dominance coordinate, probe choice, or selector result merely by supporting the treatment; any dominance promotion still requires the explicit lens or policy rule and provenance required above. -
C19-12 If exploration collects data for a causal claim, learns or evaluates a causal policy, or treats counterfactual replay as support,
PoolPolicyResult.causalUseSpec?MUST carry the target rung, claim kind, available support-component refs, supported use, unsupported use, and the C.28 support-result ref when one is consumed. -
C19-13 A pool-policy record for live loop-engineering candidates—for example, loops, agent harnesses, workflows, or DPF seeds—names the pool, governing lens, current treatment, and change trigger. Fresh generation, archive work, or front recomputation uses
C.18as the pool-policy pass specifies. Any other next-result question uses the transfer inC.19:4.4; C.19 does not absorb improvement, declaration or publication, choice, Work, or refresh. -
C19-15 Graduation, scaling, or widening an already supported use MUST cite its direct
graduationConditionRef. If that judgement relies on assurance,assuranceResultRef?cites the exact B.3 result andchangeTriggernames the satisfied condition and bounded supported scope. Widening exploration, continuing a line, retaining it without new probing, or sunsetting it MUST follow the stated continuation basis, including its contribution, feasible commitments and opportunity cost. Failure to graduate alone supplies neither a retirement decision nor a reason for indefinite continuation. A policy threshold or label does not create an assurance result.