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: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 wordingGoverning repair application
componentFirst 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.
moduleRecover 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 elementKeep 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 boundaryRecover 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 placementRecover 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.
interfaceFor 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.
signatureKeep as A.6.0 declaration. It is not an implemented interface, mechanism, gate, evidence row, or substitution policy.
port or endpointRecover 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 linkKeep 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 pathKeep under E.18 and C.30.TFS-REL; it may inform an architecture-to-transformation-flow relation, but it is not an interface specification.
platformRecover 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 labelApply 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 architectureRecover 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

  1. Name the phrase and the practical situation.
  2. Recover the meaning using §4.3 when needed; a clear meaning needs no additional classification.
  3. For a module-interface claim, identify the whole and candidate module holons. Keep any other claim with its governing pattern.
  4. State the boundary and the declared interface specification or explicit interface-specification gap.
  5. 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.
  6. Apply the subject pattern for any remaining non-module claim; §12 identifies the relevant boundaries.
  7. 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.