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:15:20 UTC

A.6.M:7 - Conformance Checklist

IDCheck
CC-A6M-1The repaired claim makes recoverable the whole holon, candidate module holon, effective reference scheme, claim coverage when it matters, and module-interface viewpoint episteme when used; already clear wording needs no further repair. No context suffix or optional model-use structure supplies those objects.
CC-A6M-2The repair states whether the phrase is a module relation, component relation, function allocation, procedural or work-package relation, system-role-assignment occurrence, direct responsibility relation, deployment or placement structure, interface specification, signature, port or endpoint, transformation-flow crossing, mechanism realization, platform grammar, control relation, autonomy-like operation claim, C.30.STRAT source-label case, or open-architecture claim.
CC-A6M-3No root kind is created for module, interface, platform, or open architecture, and ModuleInterfaceClaim is not treated as an independently admitted direct relation. The four direct-relation dispositions remain distinct; an admitted predicate may be affirmed, denied or left factually unresolved without an obtaining occurrence. A needed missing rule uses A.6.RCD; occurrence identity uses A.6.REL only after that relation is admitted and obtains.
CC-A6M-4The independently identified InterfaceSpecification episteme, its C.2.1 identity, and an interfaceSpecificationRef that resolves it are recoverable when interface compatibility, substitutability, or conformance is claimed. A missing specification remains an explicit gap.
CC-A6M-5Substitution or change policy is declared when replaceability, alternate supplier, upgrade, or platform extension is being claimed. Substitutability not established by the repair is marked as not established, not implied by wording.
CC-A6M-6Function, transformation-flow, control, work, evidence, assurance, gate, decision, causal, and mechanism claims use their subject patterns.
CC-A6M-7A failed check gives a repair action or subject-pattern application, not only a rejection.
CC-A6M-9Normative wording makes clear who must do what, or which condition an object must satisfy. A module may be required to meet an interface constraint without being treated as an agent with a duty.
CC-A6M-10Reopen only uses affected by a change in their whole, module, boundary, specification, policy, platform grammar, conformance expectation, relied-on basis or correspondence. Retain unaffected claims; lower only a dependent claim whose required basis is unavailable.