A.6.M:5 - Archetypal Grounding
A module claim concerns a holon as a structural unit of a larger whole under a boundary, interface specification and applicable conditions. Replacement needs a substitution policy; separate change needs a change policy.
A software package, neural-network block, chiplet, power converter, document template or organizational unit may be a module candidate. Identify the whole, boundary and interface specification, and the policies required by the replacement or separate-change claim. The claim remains distinct from an independently obtaining direct relation.
A port or endpoint label, flow edge or function name may help locate relevant content. Evaluate that content under the applicable interface, correspondence or evidence rule; presence of the label alone establishes no compatibility.
Holon, relation, and episteme: the candidate module and whole retain their admitted holon kinds. A ModuleInterfaceClaim is content in a C.2.1 claim episteme and may concern the module holon, one selected dependency structure, or an independently admitted direct module relation occurrence; it is not that relation. The InterfaceSpecification is another independently identified episteme, and interfaceSpecificationRef only resolves it.
Framework and module-description epistemes, authoring Work, publication occurrence, publication form, carrier, effective reference scheme, ClaimScope, and optional model-use structure retain separate identities and direct relations. Method descriptions enter as epistemes; method values enter through their Method pattern. Stratification and architecture-operation labels named by C.30.STRAT remain source labels unless C.30.STRAT recovers module-interface claim content that A.6.M can repair.