Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:05:04 UTC

A.15:7 - Conformance Checklist

IDCheckWhy
CC-A15-1Keep local system-role kind, U.SystemRoleAssignment, U.Method, U.MethodDescription, qualified holder-ability claim, U.WorkPlan, U.Work, and every record or result distinct.Prevents one alignment frame from becoming one object.
CC-A15-1aTreat a dated Work individual as world-side; keep assertions, descriptions, logs, tickets, and performed-work records as separate epistemes. Actual performer, Method, temporal, locally declared containing-system, affected-referent, binding, and resource-use relations obtain independently and are not stored fields of the occurrence.Blocks record fields from constituting Work.
CC-A15-2Keep the reusable Method, its description, intended Work, and performed Work distinct. Operational events do not mutate a MethodDescription or WorkPlan.Prevents recipe, schedule, and execution collapse.
CC-A15-3For a precise actual performer, reuse the A.13 core and independently admit dated Work through A.15.1. Only when the receiving use expressly consumes precise assignment-bound attribution, relate that Work through the same obtaining occurrence of a directly declared species under U.SystemRoleAssignment; confirm that RA.HolderSystemSlot equals the already recovered performer and that the assignment predicate covers the Work interval. Require a characteristic profile only when conditionally consumed.Preserves the independently recovered performer and Work while adding only the conditional attribution; F.6 discovers neither and no universal assignment signature is invented.
CC-A15-4For precise assignment-bound attribution, trace the A.13-qualified H through the same obtaining assignment RA, then W -performedUnderAssignment-> RA, RA.HolderSystemSlot -> H, and W -enactsMethod-> M. Cite characteristic profile, MethodDescription, plan, capability, source, and evidence separately only when relied on.Preserves one inspectable A.13→A.15.1→F.6 chain without turning interpretation metadata into participants.
CC-A15-5Keep system-role kinds, capabilities, fit predicates, Methods, and evidence or assurance records out of partOf hierarchies unless another direct pattern admits a structural relation.Blocks classification, evidence, and assurance as parts.
CC-A15-6Attribute resource use to dated Work through obtaining relations, not to a MethodDescription, WorkPlan, capability, assignment, or fit predicate.Keeps costs with performance.
CC-A15-7Use U.WorkPlan for intended Work and identify actual Work independently.Stops schedule-as-performance drift.
CC-A15-8Resolve ambiguous process, workflow, activity, schedule or role wording through F.19 and the applicable E.10 rule. Retain ordinary wording whose meaning is already clear.A cue prompts inspection rather than automatic formalization.
CC-A15-9State enactsMethod and performedUnderAssignment separately. Only the admitted holder System with its A.13 core performs Work; a profile is conditional. A capability or algorithm-possession phrase proves neither performance nor MethodDescription membership. Spontaneous physical evolution without this alignment is not Work. Use A.3.4 to identify an actual bounded change, and A.3.3 when a U.Dynamics episteme describing its state space and transition law is needed.Prevents kind, assignment, capability, Method, description, plan, dynamics, and records from becoming actors.
CC-A15-10Treat a speech act that institutes an assignment, authorization, or gate-relevant effect as its own Work occurrence only when A.15.1 admission and the effect relation obtain.Keeps the communicative Work distinct from later operational Work.
CC-A15-11Recover the assignment’s direct species, local assigned-kind domain, participants, predicate, and occurrence. Taxonomy, scheme, signature, context, and source are cited separately when the receiving claim uses them. An approver or deployer label neither creates a Work subkind nor proves performance.Prevents a permissive assignment record and kind-by-label.
CC-A15-12For causal intervention or sampling, state the Method, description, plan, dated Work, assignment attribution or enactment claims the use needs, under their own rules. Use C.28 for the causal-use question, rung, estimand, separate support components, support result and admissible-use boundary.Keeps work alignment from becoming causal authority or a compulsory full claim set.
CC-A15-13Use A.15.4 when a visible item is relied on by appearance; retain only the system-role–Method–Work separation here.Keeps reliance repair out of the alignment kernel.
CC-A15-14Keep an E.18.1 P2W structure, its publication, selected Method, WorkPlan, Work, result record, and measurement distinct.Publication alone establishes none of the project-side values.