B.4:7 - Conformance Checklist
- CC-B4.1 (Proportional loop integrity): Connect the observed basis to the change and renewed use where they occurred, or to the sufficient answer or unresolved condition returned by the question. A complete phase-by-phase trace is required only when a relying decision, assurance case, audit or replay needs it. Keep proposed phases distinct from actual events.
- CC-B4.2 (Subject identity): Name the subject kind and apply its continuity rule: System continuity or transformation; episteme predecessor, successor, or edition; Method identity, refinement, substitution, or successor; MethodDescription edition; or separate dated Work occurrences.
- CC-B4.3 (Acting-side distinction): Work that observes or changes a subject MUST have an identified performing System distinct from the changed subject in that Work account. Internal adaptation is permitted when
A.12establishes distinct subsystems or parts and their independently obtaining parthood. Every datedU.Workreuses each performer’s A.13 core and is independently admitted under A.15.1; F.6 is added afterward only for assignment-bound attribution. Its short B.4 account may omit an assignment identifier unused by the receiver only when every consumed relation remains recoverable. - CC-B4.4 (Adaptive-specialization anchoring): A bounded task-family specialization claim MUST identify its bearer, declared
TaskFamilyorTaskSignature, work target, claimed result and grounds. When aC.22.1adaptation signature is selected, retain its threshold target,timeToThreshold,budgetToThresholdandpriorExposureDeclaration, including a not-reached or unresolved result when the history warrants it. - CC-B4.5 (Adaptive-specialization boundary): Claimed transfer, retention, post-threshold efficiency, corridor entry and downside MUST retain the targets, baselines, windows and evidence required by the claim or receiving comparison.
C.22.1defines the selected adaptation-signature meanings;G.5andG.9retain their selector and parity rules when consuming that result. - CC-B4.6 (Phase and transition separation): Each claimed phase and transition MUST retain its question, result and conditions from B.4:4.3. Evidence can be used across phases, and cue preservation or routing can contribute within Observe without requiring another phase.
- CC-B4.7 (No success inference): Deployment or publication establishes neither acceptance nor successful renewed use. Record failure, reopening, fallback, or another iteration when that is what occurred.