Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 10:17:34 UTC · last check 2026-10-03 10:30:16 UTC
C.22.1:15 - Conformance checklist
CC-C22.1-1 An adaptation signature SHALL bind to one declared TaskFamily or TaskSignature, one work target, and one work-measure threshold target rather than one generic improvement story.
CC-C22.1-2 An adaptation signature SHALL publish timeToThreshold, budgetToThreshold, and priorExposureDeclaration; if threshold was not reached, the signature SHALL say so explicitly instead of implying success.
CC-C22.1-3 Any declared transfer, retention, post-threshold-efficiency, downside, corridor-entry, or stepping-stone claim SHALL be explicit by value with the target, baseline, evidence source, or evidence locus named, not left as narrative garnish.
CC-C22.1-4 This pattern may refine specialization timing and reuse claims over the declared C.22 anchor, but it SHALL NOT redefine acceptance-gate thresholds, task-family attachment, or selector/parity law governed by another FPF pattern.
CC-C22.1-5 Downstream selector/parity pattern applications SHALL cite or consume the same published adaptation-signature field set rather than silently redefining threshold, prior-exposure, transfer, retention, downside, or corridor-entry terms.