component | First recover the claim actually made under A.14: for example ComponentOf, ConstituentOf, PortionOf, belonging under the collection’s own rule, or PhaseOf. Apply A.6.M only when a module-interface relation is being claimed. |
module | Recover a ModuleInterfaceClaim or ModuleRelationRepairNote over exact U.Holon refs under the exact VP.ModuleInterface viewpoint episteme when needed. Do not infer a direct relation occurrence; use an admitted direct relation only when its defining rule exists and current facts make its predicate obtain. |
functional element | Keep it as FunctionalElementClaim inside a functional structural-view episteme; use A.6.F to repair wording and connect it to module-interface structure only through an exact allocation or correspondence relation. Keep required or desired behaviour as claim content. Cite an actual U.Transformation only when A.3.4 independently supplies its changed referent, boundary, conditions, actual before/during/after facts, and continuity basis. |
work package, delivery unit, or team boundary | Keep Work, Method, WorkPlan, exact system-role kind and assignment, and responsibility claims separate. Use A.15, A.2, and VP.Procedural for their own objects; treat VP.AllocationResponsibility only as a cue, then cite the direct allocation or responsibility predicate or the exact missing governor. Relate those facts to module-interface structure only through a declared correspondence, allocation, or boundary relation. |
deployment scope or placement | Recover a deployment or placement structure under C.30 or C.30.ASV when that deployment or placement structure is being claimed. Relate it to module-interface structure only through declared correspondence or boundary relation. |
interface | Recover the independently identified InterfaceSpecification episteme and an interfaceSpecificationRef that resolves it, not a wire, API label, port label, E.18 transformation-flow relation, or function by itself. |
signature | Keep as A.6.0 declaration. It is not an implemented interface, mechanism, gate, evidence row, or substitution policy. |
port or endpoint | Recover SlotSpec, endpoint field, or interface-specification field when the claim is being made. It is not a module, graph edge, transformation-flow crossing, or proof of integration. |
functional link | Keep it as claim content in a functional structural-view episteme; relate it to module claims only through an exact correspondence, allocation, or retargeting relation. |
E.18 transformation-flow relation or path | Keep under E.18 and C.30.TFS-REL; it may inform an architecture-to-transformation-flow relation, but it is not an interface specification. |
platform | Recover PlatformGrammarRef: extension rules, variability slots, interface specifications, substitution policy, and conformance expectations when platform extension, variation, substitution, or conformance use is being claimed. |
| stratification or architecture-operation source label | Apply C.30.STRAT first. Use A.6.M only when the recovered result is a module-interface relation, interface specification, platform grammar, substitutability policy, change policy, or open-architecture module-interface claim. Otherwise apply C.30.LCA, C.30.ASV, A.6.F, E.18, C.16.P, C.29, C.2.P, or use ordinary source-label disposition when no FPF-governed claim remains. |
open architecture | Recover an OpenArchitectureClaim episteme: published interface specifications, substitution rules, change policy, data-rights or access constraints when those constraints are part of the claim, and exact conformance, evidence, source, or reliance relations only when that stronger reliance claim is being made. |