A.6.M - Module and Interface Claim Repair
Type: Architectural pattern Status: Stable Normativity: Normative unless explicitly marked informative
A.6.M:1 - Problem frame
Use this pattern when module, component, interface, port, platform or open-architecture wording leaves a module-interface claim unresolved. The question is whether a holon is claimed as a replaceable, reusable or separately changed structural unit of a larger holon, under VP.ModuleInterface when that viewpoint matters. Keep already clear wording. Use C.30.STRAT first only when a covered stratification or architecture-operation label still hides the claim; return here if that recovery selects module-interface content. The claim does not itself make a direct module relation obtain.
The first useful output is a sufficient account of the recovered claim or question; an ordinary sentence can be complete. Use ModuleRelationRepairNote when its structure helps the receiving use, including policy, blocked-interpretation and neighboring-claim details only when they change that use:
ModuleRelationRepairNote:
wholeHolonRef:
candidateModuleHolonRef:
effectiveReferenceScheme: EpistemeInterpretationScheme, byValue
claimScope?: U.ClaimScope, byValue
modelUseStructureRef?: only when one selected model-use structure changes module meaning
moduleInterfaceViewpointRef?: VP.ModuleInterface
selectedDependencyStructureRef?: SelectedStructureReference
boundaryRef:
interfaceSpecificationRef?: U.EpistemeRef constrained to InterfaceSpecification
interfaceSpecificationGap?: missing-specification result
admissibilityConditions:
substitutabilityPolicyRef?:
changePolicyRef?:
directModuleRelationDisposition:
noDirectRelationClaimed | admittedPredicateClaim | admittedRelationAndOccurrence | missingGovernor
admittedRelationKindOrDeclarationRef?:
relationParticipantRefs?:
relationClaimContent?:
obtainingRelationOccurrenceRef?: U.RelationRef
missingRelationParticipantRefs?:
proposedPredicate?:
affectedUse?:
futureDefinitionNeed?:
definingPatternLocator?: PatternID used only as a locator
claimBoundary:
unsupportedModuleInference?:
governedNonModuleClaimPatternRefs?:
stopCondition:
In this note and the fuller form below, effectiveReferenceScheme carries a rule collection by value with the C.2.1:4.1.2 range EpistemeInterpretationScheme. It must supply the designation and interpretation rules used in the module-interface claim, including its holons, boundary, interface conditions and any asserted substitution or change policy.
Exactly one of interfaceSpecificationRef and interfaceSpecificationGap is current.
noDirectRelationClaimed leaves the direct-relation fields empty. admittedPredicateClaim names an already governed predicate, its participants and the affirmative, negative, modal or unresolved claim being made; it requires no invented obtaining occurrence. admittedRelationAndOccurrence additionally identifies one independently obtaining occurrence when its identity matters. missingGovernor names the participants, proposed predicate, affected use and missing rule.
Missing case facts under an available rule leave a factual question, not a missing governor. A PatternID may locate the rule but cannot substitute for its predicate, participants or facts.
Ordinary use stops when the whole, candidate module, boundary, interface specification or explicit gap, relation disposition, and conditions needed by the selected claim are clear enough to choose the next architecture move. Recover substitution or change policy when replacement or separate change is claimed, and a neighboring subject pattern when another claim remains current. Use the fuller ModuleInterfaceClaim record only when substitutability, conformance, publication, evidence, assurance, change policy, repeated reuse, or cross-team coordination requires durable claim content.
Misreadings to repair: a functional link becomes a module interface; a signature becomes an implemented interface; a port label becomes proof of integration; “open” becomes a decoration; a platform label hides the extension rules; a stratification or architecture-operation source label bypasses C.30.STRAT and mints a false local kind; autonomy-like wording is confused with separate module change policy; and a module diagram starts being used for claims governed elsewhere.
What A.6.M buys in practice: the practitioner can repair one module or interface phrase into usable claim content, distinguish it from an independently admitted direct relation occurrence, see which FPF pattern defines or constrains any remaining non-module claim, and stop before full measurement, evidence, or mechanism-suite records are needed.
Not this pattern when the question under repair is the general architecture claim, selected architecture structure kind, structural view, stratification wording or source-label recovery, function wording, procedural or work-package wording, role or enactor wording, autonomous operation, independent acting, unsupervised decision or action, measurement, modularity characterization, or reusable-structure residue. Use C.30, C.30.ASV, C.30.STRAT, A.6.F, A.15, A.2, E.16, C.31, C.16, or C.31.RSA as appropriate. For any other claim being made, apply the governing FPF pattern and keep A.6.M only for the module-relation and interface-specification portion.
E.10.ARCH relation. A.6.M is the precision-restoration pattern for module-interface relation wording, interface-specification wording, platform-grammar wording, substitutability wording, change-policy wording, and open-architecture module-interface claims. E.10, E.10.ARCH, or C.30.STRAT applies A.6.M only after the recovered result is a module-interface relation, interface specification, platform grammar, substitutability policy, change policy, or open-architecture module-interface claim.
If the source wording is still a stratification or architecture-operation source label covered by C.30.STRAT, apply C.30.STRAT first.
If the claim being made is non-module work, role, evidence, assurance, gate, decision, characteristic, flow, autonomy, component, mechanism, or mathematical-lens use, apply the subject pattern named in A.6.M:12 and keep A.6.M only for the module-interface slice when that module-interface relation remains the claim being made.
A.6.M:2 - Problem
Engineering teams use module language for several different things:
- a component in a part-whole decomposition;
- a replaceable unit under a declared interface;
- a functional element;
- a software package, neural-network block, hardware board, chiplet, subsystem, service, team boundary, or delivery unit;
- a published API, protocol, signature, port, connector, or endpoint;
- a platform extension point;
- a control relation, deployment scope, or stratification or architecture-operation source label that still needs
C.30.STRATrecovery; - an open-architecture claim.
These are useful ordinary words, but they do not establish the same FPF claim. A module claim is not created by a label. A conforming module-interface claim names the candidate U.Holon, larger U.Holon, VP.ModuleInterface viewpoint episteme when needed, boundary, interface specification, admissibility conditions, substitutability policy when replacement is claimed, change policy when separate change is claimed, and any evidence, conformance, or admissible-use claim being made. It remains claim content unless a separate direct relation pattern has admitted a module relation and its obtaining predicate is satisfied.
The practical question is: does this phrase name a module relation, component relation, functional allocation, procedural or work-package relation, system-role-assignment occurrence, direct domain responsibility relation, deployment or placement structure, interface specification, signature declaration, port or endpoint slot, transformation-flow crossing, mechanism realization, platform grammar, control relation, autonomy-like operation claim, source label governed first by C.30.STRAT, or only plain source wording?
A.6.M:3 - Forces
| Force | Tension |
|---|---|
| Engineering convenience vs relation precision | Practitioners need short words such as module and interface, but claim-bearing use must recover both holons, the boundary, interface specification, admissible use, and whether an independently admitted direct relation is current. |
| Module claim vs root or relation kind | A candidate module keeps its direct holon kind. Neither the source word nor a ModuleInterfaceClaim record admits U.Module or a general direct module relation; a reusable relation needs its own A.6.RCD settlement. |
| Interface label vs interface specification | An API name, port label, connector label, or signature may substantiate an interface claim, but it is not by itself substitutability or conformance. |
| Function-flow-module proximity vs false identity | Functions, E.18 flow relations, control relations, mechanisms, and module interfaces often meet at the same artifact, but each has a different subject pattern. |
| Open architecture payoff vs open label overread | MOSA and open-system practice make open interfaces useful only with standards, conformance expectations, replacement or change policy, and data or access constraints when those conditions are part of the claim being made. |
| Team boundary vs module boundary | Conway’s law and mirroring practice make team communication boundaries and delivery-responsibility scopes architecture-relevant, but they do not turn a team boundary, delivery unit, system-role assignment, or responsibility relation into a module interface by identity. Assignment also does not establish responsibility: use its domain predicate and case facts; return an A.6.RCD missing governor only when the needed rule is absent. |
| Parallel decomposition vs serial bottleneck | Amdahl-style reasoning makes serial work, synchronization, communication overhead, and shared resource limits visible; more modules, teams, or parallel transformation-flow paths do not automatically improve throughput or evolvability. |
| Cheap repair vs full evidence pack | Most cases need a sufficient sentence or short repair note. Additional conformance, evidence, assurance, gate or mechanism-suite work depends on the receiving claim. |
A.6.M:4 - Solution
A.6.M specializes A.6.P for module, component, interface, platform, and open-architecture wording when the recovered result is module-interface claim content, an interface specification, platform grammar, substitutability claim, or open-architecture module-interface claim. Stratification or architecture-operation source labels covered by C.30.STRAT are governed by C.30.STRAT until that repair recovers this module-interface content. A.6.M neither mints root kinds from those labels nor admits a direct module relation from record syntax.
A candidate module is a U.Holon used in a claim that treats it as a replaceable, reusable, or separately changed structural unit of a larger U.Holon, ordinarily under the VP.ModuleInterface viewpoint episteme. The claim names its boundary, interface specification, admissibility conditions, substitutability policy when replaceability is claimed, and change policy when separate change is claimed. Effective reference scheme and U.ClaimScope qualify the claim; an optional selected model-use structure appears only when its organization changes module meaning. None replaces the two holons or makes a module relation obtain.
A FunctionalElementClaim is different: it is a claim-bearing episteme cited by a functional structural view under C.30.ASV, not a root kind or a module relation. It binds required behaviour or effect to bearer or candidate bearer, capability, functional ports, and allocation claims when those claims are current; required or desired content is not an actual U.Transformation.
The relation between functional and module claims is separately governed allocation or correspondence, not identity. One module candidate can correspond to many functional elements; many module candidates can correspond to one functional element; a functional element can remain unallocated; and a module candidate can be present in a module-interface view with no current functional behaviour in the functional view.
Functional ports and module interfaces may both use U.Signature discipline, but they govern different claims. A functional port constrains input condition, output condition, accepted-state, and produced-state slots for a functional behavior or transformation. A module interface constrains boundary, substitutability, compatibility, protocol references, schema references, version policy, change policy, and conformance expectations for a module relation. Do not move a functional-port claim into module-interface structure unless a module-interface or substitution claim is being made.
For modular synthesis, A.6.M supplies only the module-interface claim slice. A synthesis action may align required functional claims under VP.Functional, transformation-flow topology under E.18 and C.30.TFS-REL, control structure under C.30.LCA, procedures and work packages under VP.Procedural, and module and interface claims under VP.ModuleInterface.
VP.AllocationResponsibility is only a recognition cue for allocation or responsibility concerns: a positive responsibility claim needs its domain predicate and supporting participant and applicability facts, with explicit occurrence identity when the receiving use needs it. Missing facts leave that claim unknown; only an absent governing rule leaves an A.6.RCD missing governor.
Use A.6.M to repair claims about modules and their interfaces; non-module candidate generation, allocation, responsibility, evidence, assurance, decision, Work, and characteristic claims remain with their direct patterns.
A.6.M:4.1 - ModuleInterfaceClaim record
Use ModuleInterfaceClaim only when the light repair note is not enough and durable claim content is needed. Its Plain reading is claim about a module and its interface in a larger whole.
ModuleInterfaceClaim:
claimEpistemeRef: U.EpistemeRef
entityOfConcernRef:
moduleHolonRef | selectedDependencyStructureRef |
admittedDirectModuleRelationOccurrenceRef
effectiveReferenceScheme: EpistemeInterpretationScheme, byValue
claimScope?: U.ClaimScope, byValue
modelUseStructureRef?: SelectedStructureReference
moduleHolonRef: U.HolonRef
wholeHolonRef: U.HolonRef
viewpointRef?: U.ViewpointRef = VP.ModuleInterface
selectedDependencyStructureRef?: SelectedStructureReference
boundaryRef: BoundaryRef
interfaceSpecificationRef?: U.EpistemeRef constrained to InterfaceSpecification
interfaceSpecificationGap?: missing-specification result
functionalCorrespondenceRelationRefs?: FinSet(U.RelationRef)
transformationFlowStructureRefs?: FinSet(SelectedStructureReference)
transformationFlowRelationOccurrenceRefs?: FinSet(U.RelationRef)
mechanismRefs?: FinSet(U.EntityRef constrained by the selected mechanism pattern)
dependencyRelationOccurrenceRefs?: FinSet(U.RelationRef)
substitutabilityPolicyRef?: U.EpistemeRef
changePolicyRef?: U.EpistemeRef
variabilitySlotRefs?: FinSet(SlotSpecRef)
evidenceOrSourceRelianceRelationRefs?: FinSet(U.RelationRef)
directModuleRelationDisposition:
noDirectRelationClaimed | admittedPredicateClaim | admittedRelationAndOccurrence | missingGovernor
admittedRelationKindOrDeclarationRef?:
relationParticipantRefs?:
relationClaimContent?:
obtainingRelationOccurrenceRef?: U.RelationRef
missingRelationParticipantRefs?:
proposedPredicate?:
affectedUse?:
futureDefinitionNeed?:
definingPatternLocator?: PatternID used only as a locator
admissibleUse
nonAdmissibleUse?
This form is claim content in one C.2.1 episteme. Its identity uses that content, the one entityOfConcernRef, and the effective reference scheme. claimScope qualifies the claim when its coverage matters. modelUseStructureRef is present only when one independently selected model-use structure changes the meaning of module for this claim; it is not a module participant, whole, boundary, or source of relation obtaining. VP.ModuleInterface is a reference to the viewpoint episteme when viewpoint use matters; citing it does not make this claim a U.View.
The interface-specification and direct-relation fields obey the same exclusive branches as ModuleRelationRepairNote. If entityOfConcernRef names an admitted direct module-relation occurrence, the disposition is admittedRelationAndOccurrence and obtainingRelationOccurrenceRef resolves that same occurrence. Under the other dispositions, entityOfConcernRef stays with the module holon or selected dependency structure.
A record, package path, file boundary, graph edge, list position, name or publication does not make a world-side module relation obtain. Its content may supply a claim or grounds; assess those under the applicable rule. A.6.M admits no general direct module relation kind. If the receiving use needs a predicate that no subject rule supplies, use A.6.RCD to settle participant meanings, obtaining conditions, applicability and any needed recurrence or identity rule. Use A.6.REL when explicit identity is needed to distinguish, reidentify or refer to an obtaining occurrence, or to use it as a participant. A separately constituted RelationSignature may declare reusable SlotSpecs; neither declaration nor claim creates the occurrence.
For an already defined domain predicate p(M, W, B) over module M, whole W and boundary B, a practitioner may report that its truth is unknown because required protocol facts are missing. If established facts violate its rule, the practitioner may instead assert that p(M, W, B) does not hold. Both use admittedPredicateClaim, preserving the predicate, participants and grounds without positing an obtaining occurrence. A positive claim may also use that branch when explicit occurrence identity adds nothing. Use admittedRelationAndOccurrence only when the obtaining occurrence is independently established and its identity is needed.
Well-formedness: the claim names both holons, one EntityOfConcern, an effective reference scheme, one boundary, and exactly one of an interface-specification reference and an explicit interface-specification gap. Its direct-relation disposition has exactly the fields required by the selected branch. Optional structure, relation, evidence, mechanism, policy, conformance, source, and reliance references are used only when those objects and claims are current under their direct rules.
A.6.M:4.2 - Interface specification is not a label
A.6.M calls the independently identified specification episteme an InterfaceSpecification. It is one U.Episteme under C.2.1 whose EntityOfConcern is the boundary named by the module claim. Its identity is <ClaimGraph, that one EntityOfConcern, effective reference scheme>. Its claim content may include:
InterfaceSpecification claim content:
signatureRefs?: FinSet(SignatureRef)
slotSpecSetRefs?: FinSet(SlotSpecSetRef)
portEndpointSpecRefs?: FinSet(PortEndpointSpecRef)
protocolRefs?: FinSet(EpistemeRef)
schemaRefs?: FinSet(EpistemeRef)
admissibilityConditions
semanticConditions
versionPolicyRef?
changePolicyRef?
conformanceExpectationRefs?
evidenceOrSourceRelianceRefs?
nonAdmissibleUse?
interfaceSpecificationRef is one U.EpistemeRef constrained to that specification form. Under the effective reference scheme it resolves one already identified InterfaceSpecification; it carries none of the specification content itself. Two spellings or serialized references may resolve the same unchanged specification. Retargeting the reference selects another already identified specification without changing the previous one. Changing identity-bearing specification content, its EntityOfConcern, or its effective reference scheme yields another episteme. When no complete specification is established, keep an explicit interfaceSpecificationGap rather than a partly filled reference.
A signature declares vocabulary, laws, and applicability. A slot or endpoint record names positions and field structure. A protocol or schema constrains interaction. A mechanism reference can substantiate a realization relation. Evidence relations, source relations, reliance relations, and conformance expectations substantiate reliance only when the corresponding evidence, source-use, assurance, or conformance claim is being made. A referenced specification may contain all the conditions needed for a simple interface; its citation alone does not establish that a candidate satisfies them. Any explanatory nonAdmissibleUse or unsupportedModuleInference is optional: retain it only when an independently grounded, plausible misreading changes truth or use under F.19:4.
A.6.M:4.3 - Repair applications for overloaded words
| Source wording | Governing repair application |
|---|---|
component | First recover the claim 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 U.Holon refs under the VP.ModuleInterface viewpoint episteme when needed. Do not infer a direct relation occurrence; assert that the relation obtains only when its defining rule exists and current facts satisfy its predicate; a negative or unresolved predicate claim does not require an obtaining occurrence. |
functional element | Keep it as a FunctionalElementClaim episteme cited by a functional structural view; use A.6.F to repair wording and connect it to module-interface structure only through an 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 | Recover only the Work, Method, WorkPlan, system-role or responsibility claim made. For deliberately asserted dated Work use A.13, independent A.15.1 admission and F.6 only for precise assignment-bound attribution. An independent system-role kind or classification claim needs no assignment; responsibility needs its own rule and case facts. Relate these to module-interface structure only through the applicable 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 | For the recovered module-interface claim, identify its InterfaceSpecification or the missing specification. If bare interface wording could mean another object, use A.6.RSIR first; a wire, port, API or flow need not be a module interface. |
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 a 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 conformance, evidence, source, or reliance relations only when that stronger reliance claim is being made. |
A.6.M:4.4 - First repair sequence
- Name the phrase and the practical situation.
- Recover the meaning using §4.3 when needed; a clear meaning needs no additional classification.
- For a module-interface claim, identify the whole and candidate module holons. Keep any other claim with its governing pattern.
- State the boundary and the declared interface specification or explicit interface-specification gap.
- State the admissibility conditions needed by the claim. Recover substitution policy when replacement is claimed and change policy when separate change is claimed. Omit an inapplicable policy; keep a required but unestablished policy as an explicit gap.
- Apply the subject pattern for any remaining non-module claim; §12 identifies the relevant boundaries.
- Stop when the claim, direct-relation disposition and next use are clear. Use A.6.RCD only for a needed missing rule, and A.6.REL only when the receiving use needs explicit identity for an independently obtaining relation.
A.6.M:4.5 - Worked slices
Ports line up.
Phrase:
"The ports line up, so the modules are compatible."
ModuleRelationRepairNote:
wholeHolonRef: VehicleControlSystem
candidateModuleHolonRef: BrakeControllerPackage
effectiveReferenceScheme: VehicleControlInterfaceScheme-2026Q2
claimScope: BrakeControllerReleaseUse-2026Q2
directModuleRelationDisposition: noDirectRelationClaimed
boundaryRef: BrakeControlBoundary
interfaceSpecificationGap: endpoint names are present, but protocol and semantic conditions are still missing
admissibilityConditions: not yet declared
claimBoundary: compatibility question; replacement, separate change, evidence and gate use are not assessed here
unsupportedModuleInference: port labels alone do not establish implemented interface compatibility
governedNonModuleClaimPatternRefs: A.6.5 for endpoint slots; A.6.B only if L, A, D, or E boundary-package statement classification is current; A.6.M only if a module-interface or substitution claim remains
stopCondition: endpoint slots and missing interface-spec fields are visible
Open platform claim. A team calls its platform open. Suppose the published ExtensionGuide-v3 specifies AdapterBoundary and AdapterSpec-v3, lists the AdapterSlot, permits an adapter to be replaced after ProtocolTest-P and SchemaTest-S pass, and requires a major interface version for a semantic change. These supplied facts support a bounded claim:
Phrase:
"This is an open platform."
OpenArchitectureClaim:
architectureClaimRef: PlatformArchitecture-v3
platformGrammarRef: ExtensionGuide-v3
interfaceSpecificationRefs: AdapterSpec-v3 at AdapterBoundary
variabilitySlotRefs: AdapterSlot
substitutabilityPolicyRef: ExtensionGuide-v3 replacement rule requiring ProtocolTest-P and SchemaTest-S
changePolicyRef: ExtensionGuide-v3 major-version rule for semantic change
conformanceExpectationRefs: ProtocolTest-P; SchemaTest-S
evidenceOrSourceRelianceRefs?: omitted until a particular adapter test or reliance claim is made
admissibleUse: plan an adapter substitution and identify its required tests
nonAdmissibleUse:
the published rules do not establish that a particular replacement adapter has passed those tests
The first slice makes the missing compatibility basis usable without requiring measurement. The second uses the supplied extension and replacement rules to identify the next action: test a proposed adapter under the two named tests before claiming its conformance. Publication of the rules supports planning; a test result would support a different claim.
Supplier-diversity, procurement suitability, use-context compatibility, business constraint, policy authorization, and provider-selection claims are not module-interface fields. If those claims are being made, A.6.M names only the module-interface slice; non-module selection, procurement, work, role, evidence, assurance, gate, release, and mechanism claims are governed by the patterns named in A.6.M:12.
Team boundary claim.
Phrase:
"The team communication boundary matches the module boundary."
ModuleRelationRepairNote:
wholeHolonRef: PaymentsPlatform
candidateModuleHolonRef: SettlementService
effectiveReferenceScheme: PaymentsPlatformInterfaceScheme-2026Q2
claimScope: SettlementServiceProductLineUse-2026Q2
directModuleRelationDisposition: noDirectRelationClaimed; team/module correspondence remains diagnostic
boundaryRef: SettlementServiceBoundary
interfaceSpecificationGap: the service API exists, but semantic versioning, data schema, and semantic conditions are incomplete
admissibilityConditions: module-interface conditions not yet established; assess team-delivery and on-call responsibility separately under their admitted predicates
claimBoundary: assess any team, Work or procedural claim on its own basis; establish module-interface conditions separately
unsupportedModuleInference: a communication boundary or delivery-responsibility relation alone does not establish module interface, substitutability or compatibility
governedNonModuleClaimPatternRefs: A.2 for system-role claims; A.13 and A.15.1 for actual Work, with F.6 only for assignment-bound attribution; C.29 if the correspondence raises a separate mathematical transfer or inference question; A.6.M for the module-interface claim
stopCondition: use the correspondence to locate an architecture question; it supplies no compatibility result
The third slice uses Conway-like mirroring as a diagnostic prompt. It does not make organization structure, communication relations, a system-role assignment, or delivery responsibility into module-interface structure by identity. Assess any team-delivery or on-call responsibility claim under its own admitted predicate for the actual Systems, scopes and intervals. Retain a supported claim, an adequately grounded negative, or an unresolved factual question as warranted. Return the A.6.RCD missing governor only when a needed defining, applicability or identity rule is absent.
If the repair proposes more modules, more open interfaces or more parallel transformation-flow paths, assess the possible costs before claiming improvement. Synchronization work, communication overhead, conformance work, shared-resource pressure, hidden exception cost, or cross-boundary change cost can become the claim being made. A.6.M repairs only the module-interface relation; speedup, bottleneck, modularity, measurement, work, and quality tradeoffs are governed by C.29, E.18, C.31, C.16, A.15, or the related subject pattern named by value when that related claim is being made.
A.6.M:4.6 - Lowering and Reopen Conditions
Lower only the part of an A.6.M repair that depends on an unavailable required basis, keeping the supported claim or explicit question usable. A missing interface specification can block a compatibility claim; a missing substitution or change policy blocks the replacement or separate-change claim that requires it. A policy not needed by the selected claim is inapplicable, not a reason to lower that claim.
Reopen the repair when any of these change: the whole holon, candidate module holon, boundary, interface specification, explicit interface gap, substitutability policy, change policy, platform grammar, conformance expectation, relied-on evidence relation, relied-on source relation, source-label recovery from C.30.STRAT, team-boundary correspondence, work correspondence, or the subject pattern for a related claim being made.
If the reopened material is no longer a module-interface relation, A.6.M keeps only the previous repair as source context and the claim being made is governed by the pattern named in A.6.M:12.
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.
A.6.M:6 - Bias-Annotation
| Bias risk | A.6.M repair |
|---|---|
| Box bias | Do not treat a diagram box as a module. Recover holon, whole, boundary, and interface specification. |
| Open-label bias | Do not treat “open” as substitutability. Recover standards, conformance expectations, data or access constraints, and change policy when those conditions are part of the claim being made. |
| Component bias | Do not treat every part as a module. Apply A.14 to component wording unless a module-interface relation is being claimed. |
| Interface-label bias | Do not treat API, port, endpoint, or signature labels as implemented compatibility. Recover the independently identified InterfaceSpecification episteme and a governed reference that resolves it, or record a specification gap. |
| Team-boundary bias | A team boundary or responsibility label does not establish a module boundary. Recover only the team, Work, system-role or responsibility claims needed, each under its rule and facts. Then assess the module-interface correspondence and specification. |
| Parallelism bias | Do not treat decomposition into more modules, teams, services, or transformation-flow paths as performance or evolvability improvement. Recover serial work, synchronization, communication overhead, shared resources, and bottleneck claims through E.18, C.30.TFS-REL, C.29, C.31, or neighboring characteristic patterns when those claims are being made. |
| Platform bias | Do not treat a platform name as architecture quality. Recover platform grammar and the claim named by value it can substantiate. |
A.6.M:7 - Conformance Checklist
| ID | Check |
|---|---|
CC-A6M-1 | The 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-2 | The 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-3 | No 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-4 | The 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-5 | Substitution 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-6 | Function, transformation-flow, control, work, evidence, assurance, gate, decision, causal, and mechanism claims use their subject patterns. |
CC-A6M-7 | A failed check gives a repair action or subject-pattern application, not only a rejection. |
CC-A6M-9 | Normative 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-10 | Reopen 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. |
A.6.M:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Symptom | Repair |
|---|---|---|
BoxIsModule | A diagram box, package, or file boundary is treated as a module or as proof that a module relation obtains. | Recover the two holons, claim content, boundary, and interface specification; interpret the box under the diagram’s conventions and assess any claim-bearing content. Use a direct relation occurrence only after its governing predicate obtains. |
SignatureAsInterface | A signature declaration is treated as implemented compatibility. | Keep signature under A.6.0 and add interface-specification fields only when interface compatibility is being claimed. |
PortAsProof | Matching port or endpoint names are treated as integration proof. | Recover slot specs, protocol or schema, semantic conditions, and evidence, conformance, source relation, or reliance relation named by value. |
FunctionalLinkAsInterface | A functional relation is treated as module boundary. | Keep VP.Functional and add correspondence or allocation only when module allocation or correspondence is being claimed. |
OpenByPublicationOnly | Published interface text is treated as open architecture. | Add substitution policy, conformance expectations, change policy, source or evidence relation, and data or access constraints when those conditions are part of the open-architecture claim; non-module selection, procurement, work, evidence, assurance, gate, mechanism, and decision claims are governed by the patterns named in A.6.M:12. |
TeamBoundaryAsModule | A team boundary, responsibility label, communication boundary or delivery unit is treated as a module interface. | Recover the team, Work, system-role or responsibility claim and its basis, without requiring the neighboring claims. Then assess the module-interface relation or correspondence. Use C.29 only when a separate mathematical representation, transfer or inference question remains. |
MoreModulesMeansBetter | More modules, teams, services, threads, or parallel transformation-flow paths are treated as automatic improvement. | Recover serial work, synchronization, communication overhead, shared resources, and bottleneck claims; use C.29 when a mathematical speedup or correspondence claim leaves a representation, transfer or inference question, and characteristic tradeoffs are governed by C.31 and C.16. |
PlatformAsKind | A platform label becomes a root kind or quality claim. | Use PlatformGrammarRef and apply subject patterns for quality, measurement, and decision claims. |
StackAsArchitecture | A stack diagram is treated as the architecture itself or as a module-interface relation by label. | Apply C.30.STRAT first; then use C.30 or C.30.ASV for architecture or structural-view use, A.6.M only for a recovered module-interface relation, or ordinary source-label disposition. |
A.6.M:9 - Consequences
Benefits:
- Module and interface talk becomes usable without minting false root kinds.
- Practitioners get a cheap relation repair before measurement or evidence work.
- MOSA and open-system claims become precise enough to make substitution and change reasoning admissible.
- Functional, flow, control, mechanism, work, evidence, assurance, gate, decision, and causal claims stay with their subject patterns.
Costs:
- Ordinary architecture prose loses the convenience of treating boxes, ports, interfaces, and modules as one kind.
- Interface claims sometimes require additional records before substitutability can be relied on.
- “Open architecture” becomes harder to claim because interface publication alone is not enough.
A.6.M:10 - Rationale
The central decision is to treat module as relation-sensitive claim language over admitted holons, not as a root kind and not as a relation admitted by notation. The same system, organization-as-system, episteme, Work occurrence, discipline, or other admitted holon may be claimed as a component under one direct relation, as a module candidate under one interface-and-change claim, or as a bearer/candidate bearer in functional claim content.
effectiveReferenceScheme and ClaimScope make the claim interpretable and bounded. An independently selected model-use structure may qualify model-local meaning, but it neither becomes a holon nor supplies module membership. Method descriptions and publication-family material enter through their episteme and publication patterns; authoring, description edition, publication occurrence, form, and carrier remain distinct.
A.6.M follows A.6.P: overloaded relation language is repaired by recovering the subjects, claim content, direct-relation disposition, qualifiers, admissible use, and sources. A.6.M is the pattern for the module/interface claim repair. A direct module relation, if later needed, is admitted only by its subject pattern with A.6.RCD’s participant, obtaining, applicability, and identity discipline; A.6.REL handles explicit identity when the receiving use needs it for an obtaining occurrence.
The pattern keeps measurement out of the first move. A module relation can be repaired before anyone knows whether external coupling density, interface standardization share, evidence reuse, or reusable-structure accounting will be needed. When those claims are being made, A.6.M applies C.31, C.31.RSA, and C.16.
A.6.M:11 - SoTA-Echoing
| Source or practice | Role in this account | Adopt | Adapt for FPF | Reject or boundary | Practitioner implication |
|---|---|---|---|---|---|
| DoD OUSD(R&E) MOSA guidance and implementation guidebook (https://www.cto.mil/sea/mosa/; https://www.cto.mil/wp-content/uploads/2025/03/MOSA-Implementation-Guidebook-27Feb2025-Cleared.pdf) | Acquisition and engineering guidance on open modular systems, including the dated 2025 guidebook. | Modular design, interface standards, conformance verification, replacement policy, change policy, and competitive reuse are conformance and substitution expectations. | Recover them as an independently identified InterfaceSpecification episteme plus an interfaceSpecificationRef that resolves it, PlatformGrammarRef, substitutabilityPolicyRef, changePolicyRef, conformance expectation, source relation, and evidence relation only where the recovered claim needs them. Non-module selection, procurement, policy, evidence, assurance, gate, decision, Work, system-role-assignment, responsibility, and mechanism claims keep their own direct patterns; a responsibility claim needs its own predicate and case facts, with A.6.RCD used only for a missing rule. | Do not treat open, interface publication, or modular-looking structure as substitutability, assurance, procurement suitability, supplier-set selection, policy authorization, quality proof, or decision authority. | A practitioner asking whether something is open first repairs the relation and interface specification; other claims remain with the patterns named in A.6.M:12. |
| Conway’s law, the mirroring hypothesis, and Team Topologies and inverse Conway practice (https://www.melconway.com/Home/Committees_Paper.html; https://doi.org/10.1016/j.respol.2012.04.011; https://itrevolution.com/wp-content/uploads/2022/06/TTOP_excerpt.pdf) | Socio-technical conjecture, empirical mirroring research and organization-design practice; used diagnostically. | Team communication structure, boundary placement, and delivery-responsibility relations can create pressure on module and interface boundaries and useful correspondence clues. | Recover the team, system-role, Work or responsibility claims needed under their separate rules and facts. Connect that material to ModuleInterfaceStructure only through declared correspondence, allocation, boundary relation, and preserved and lost structure note. Use C.29 when a separate mathematical representation, transfer or inference question remains. | Do not treat Conway’s law, an org chart, assignment, responsibility label, or delivery unit as proof of module interface, substitutability, modularity quality, evidence, gate passage, or architecture decision. | A practitioner may use team-boundary mismatch as a diagnostic prompt, then repair each relation before deciding what architecture change is warranted. |
| Amdahl’s law and communication and synchronization extensions (https://www.cs.cmu.edu/~18742/papers/Amdahl1967.pdf; https://arxiv.org/abs/1306.3302; https://arxiv.org/abs/2603.20654) | Amdahl’s mathematical result and proposed extensions concerning communication, synchronization and scalable-workload fractions. | Serial work, synchronization, communication overhead, shared resources, and changing scalable workload fractions can limit the payoff of decomposition, parallelization, or specialization. | Keep an adequate mathematical calculation; use C.29 when its representation, transfer or inference conditions remain unresolved. Use E.18 for transformation-flow structure, C.30.TFS-REL when the module claim uses an architecture-to-transformation-flow relation, and C.31 and C.16 for modularity and characteristic tradeoffs. | Do not treat module count, team count, service count, transformation-flow path count, or accelerator count as improvement, scalability, throughput, or evolvability by itself. | A practitioner considering a module split names the serial part, shared bottleneck, synchronization or communication overhead, and characteristic tradeoff before claiming improvement. |
| SEI Views and Beyond, ISO/IEC/IEEE 42010:2022, and multi-view architecture practice | Architecture-description and viewpoint discipline; not a source of module-quality judgments. | Module and component-and-connector views are distinct architecture descriptions. | Use ModuleInterfaceStructure and RuntimeInteractionStructure as structure-kind signals under C.30.ASV. | Do not reduce architecture to a module diagram. | Module repair stays one architecture-structure concern, not the whole architecture ontology. |
| Platform and product-line engineering practice (https://tag-app-delivery.cncf.io/fr/whitepapers/platform-eng-maturity-model/; https://www.sei.cmu.edu/library/variability-in-software-product-lines/; https://arxiv.org/abs/2605.21353) | Product-line variability, platform-engineering and review sources used for variability slots and extension rules. | Variation slots and extension rules matter for reuse and substitution. | Use PlatformGrammarRef, variabilitySlotRefs, and change policy instead of a platform root kind. | Do not treat platform name as architecture quality, architecture scale-preference evidence, procurement suitability, supplier-set selection, or decision authority. | The next module-repair action is to identify extension rules and substitution conditions; non-module quality, scale-preference, procurement, supplier-set, and decision claims are governed by the patterns named in A.6.M:12 when those claims are being made. |
| Architecture-operation language, with neural-network and software-system intakes as source examples | Practitioner-language examples used for recognition. | C.30.STRAT source labels, including source examples such as block, layer, expert, router, cache, and state, are useful recognition prompts. | Keep them as source labels until the recovered FPF kind, relation, claim-use, or source-use disposition is known; use A.6.M only for module-interface relation, interface specification, platform grammar, substitutability, or open-architecture module-interface claims. | Do not import source-context labels as module kinds or evidence of adequacy. | The same repair works for neural-network block replacement, hardware module substitution, organizational module repair, and episteme-module repair without making any source context the ontology. |
A.6.M:12 - Relations
| Pattern | Relation |
|---|---|
A.6.P | A.6.M is an RPR specialization for module-interface claim and interface-specification language; its record forms do not create a direct relation occurrence. |
A.6.RSIR | Bare interface-like wording is recovered before A.6.M is applied; A.6.M governs only recovered module-interface claim content, interface specification, platform grammar, substitutability policy, change policy, or open-architecture slice. |
A.6.RCD and A.6.REL | A needed reusable direct module relation requires its subject pattern and A.6.RCD for participants, obtaining, applicability, recurrence, and identity. A.6.REL applies after admission when the receiving use needs explicit identity for an obtaining occurrence. |
C.2.1, A.2.6, and A.22 | Govern the ModuleInterfaceClaim episteme, the separate InterfaceSpecification episteme, effective reference scheme, ClaimScope, and any independently selected dependency or model-use structure. None creates a module relation. |
C.30.STRAT | Recovers stratification and architecture-operation source labels before A.6.M governs only recovered module-interface relation cases. |
E.16 | Governs autonomy-budget, autonomous operation, independent acting, unsupervised decision or action, and freedom-of-action claims when those description or view uses are being made; A.6.M keeps only the module-interface relation, boundary, interface specification, and substitution or change-policy slice. |
A.14 | Component and part-whole wording uses A.14 first unless a module-interface relation is being claimed. |
A.6.0 and A.6.5 | Signatures, slots, ports, endpoints, and field structure remain governed by signature and slot discipline. |
A.6.B, A.6.C, and A.6.P:4.11a | Boundary, interface-specification, API, protocol, service, promise, and duty wording uses A.6.M only when the claim is module-interface relation, interface specification, substitutability, change policy, platform grammar, or open-architecture module-interface claim. |
C.30 and C.30.ASV | Architecture claims and module-interface structural views stay architecture-governed. |
C.33, C.34, and C.35 | Use these only when a module carrier, interface carrier, view, source label, generated map, or discovered structure needs architecture-specific captured-structure adequacy, lost-structure adequacy, preservation adequacy, or generated-carrier admission support. Use A.6.M for module-interface relation, interface specification, substitutability, change-policy, and platform-grammar claims. |
A.6.F | Function and functional wording stays distinct from module allocation. |
A.15 and A.2 | Method, WorkPlan, performed Work, system-role-kind and assignment claims, team-boundary wording, and delivery-unit wording keep their own defining or constraining patterns. Responsibility claims require their domain predicate and case facts; A.6.RCD addresses a missing rule, not unknown facts; VP.AllocationResponsibility is only a recognition cue. Use A.6.M only for a recovered module-interface relation or correspondence. |
E.18 and C.30.TFS-REL | E.18 transformation-flow relations, path slices, crossings, and flow valuations are not interface specifications. |
C.31 | Modularity and reusable-structure characteristics are governed by C.31 after relation repair when characteristic or measurement use is being made. |
C.31.RSA | Reusable-structure accounting is governed by C.31.RSA when reusable loci, bespoke residue, or report-only share claims are being made. |
A.17, A.18, C.16, C.16.P, and A.19.CPM | Use A.17 for the Characteristic, A.18 for scale-operation legality, C.16 for measurement, C.16.P while measurement wording is ambiguous, and A.19.CPM for comparison. An evidence stub remains an optional locator into A.10/G.6 provenance. |
A.10, B.3, A.20, A.21, C.28, E.20, G.5, C.11 | Evidence, assurance, gates, causal use, mechanism suites, set-return selection, and local decisions use their subject patterns; they are not A.6.M claims. |