A.6.F:4 - Solution
A.6.F is an A.6.P RPR specialization for function-like wording. It does not mint U.Function. It assigns the use under repair to an entity, value, claim, or claim-bearing episteme and its subject pattern, then stops unless another claim remains current. It does not package direct relations, declaration-local SlotSpecs, assertions, specifications, views, and representation elements as peer records.
A.6.F:4.1 - Trigger rule
When function-like wording remains ambiguous, distinguish the readings below. They are possible meanings to inspect, not a U.* kind, claim kind, relation kind, or admission result:
One phrase may combine several readings or transfer metonymically between them. Recover the claim it makes and retain every distinction that changes its use.
- architecture or functional architecture;
- capability, effect, externally promised behavior, or user-visible functionality;
- method wording, work occurrence, or work result;
- a system-role kind or assignment, participation, actual functioning, or responsibility;
- mathematical function, mapping, relation, loss, objective, or value functional;
- quality, fitness, characteristic, score, or proxy wording;
- module allocation, interface, signature, port, API, protocol, flow, or mechanism relation;
- another independently established claim named by value, such as evidence, assurance, gate, decision, or release.
If none of those readings carries a current FPF claim, the wording may remain ordinary Plain prose.
A.6.F:4.2 - FunctionUseRepair
FunctionUseRepair is an optional pattern-local repair note for a receiving use that needs inspectable detail. Its functionLikeReadingUnderRepair value only helps a reader recognize and dispatch a possible reading; neither that value nor the three scan groups below is a U.* kind, claim kind, relation kind, or admission result. The recovered result belongs in exactGovernedObjectOrClaim under its subject pattern. The note carries no project-publication, evidence, decision, or U.Function authority. FunctionalStructure is an ArchitectureStructureKindRef value under C.30.ASV, not a kernel Function kind.
FunctionUseRepair ::= {
phrase,
functionLikeReadingUnderRepair: {
directObjectOrValueReading?:
systemCapability |
methodDescription |
mechanismRealization |
workPlan |
workOccurrence |
workResult |
mathematicalFunction,
claimOrConditionReading?:
requiredTransformation |
requiredEffect |
inputCondition |
outputCondition |
systemRoleKindOrAssignmentCue |
participationOrFunctioningCue |
responsibilityCue |
qualityExpression |
characteristicExpression |
functionalArchitecture |
evidenceClaim |
assuranceClaim |
gateClaim |
decisionClaim |
publicationClaim,
relationParticipantOrLocusReading?:
functionalElementLocus |
transformerSideFiller |
candidateBearer |
functionalPort |
methodPosition |
mathematicalRelation |
moduleAllocation |
interfaceRelation |
signatureRelation,
otherDeclared?
},
exactGovernedObjectOrClaim: oneOrMoreOf {
exactEntityOrValueRef?,
exactClaimOrClaimContent?,
exactClaimBearingEpistemeRef?
},
directRelationPredicateUse?: {
admittedDirectRelationKindRef,
relationKindToken?,
semanticPredicate,
actualParticipantRefs,
directRelationPatternRef
},
relationalAssertionUse?: {
relationalAssertionEpistemeRef,
assertedClaimContent,
assertedSemanticPredicate,
polarityOrModality,
actualParticipantRefs,
directRelationPatternRef
},
obtainingRelationOccurrenceUse?: {
individuatedRelationOccurrenceRef,
obtainingSemanticPredicate,
actualParticipantRefs,
occurrenceIdentityRuleRef,
directRelationPatternRef
},
reusableDeclarationUse?: {
relationSignatureRef,
declarationLocalSlotSpecRefs
},
selectedClaimBearingEpistemeUse?: {
assertionSpecificationOrViewEpistemeRef,
selectedClaimOrDesignation
},
representationUse?: {
representationElementRefs,
interpretationOrCorrespondence,
representedObjectOrClaimRef
},
sourceCueText?,
subjectPatternApplicationRefs?,
blockedLocalOverreadRefs?,
admissibleUse,
nonAdmissibleUse?,
nextAdmissibleUse,
stopCondition
}
The repair is complete when a practitioner can name the object or claim, apply its subject pattern, and state the remaining action. When a note is needed, at least one entity or value, claim or claim content, or claim-bearing episteme is required in exactGovernedObjectOrClaim. A source cue stays in sourceCueText; it is not a recovered value.
When a direct relation is current, first name its admitted kind, semantic predicate, and actual participants in directRelationPredicateUse. Add relationalAssertionUse only when one C.2.1 episteme affirms, denies, or otherwise modalizes that predicate. Add obtainingRelationOccurrenceUse only when the receiving use needs one separately individuated obtaining occurrence under the subject pattern’s identity rule, applied through A.6.REL; a predicate or assertion never supplies occurrence identity.
Add a reusable RelationSignature and declaration-local SlotSpecs only for reusable typed use; add another selected assertion, specification, or view episteme only when it is a separate claim-bearing object; add a representation and its interpretation or correspondence only when that representation matters, using C.29 when a separate mathematical-representation, transfer or inference question remains. If the text still hides a function, capability, work, method, system-role kind or assignment, participation, functioning, responsibility, module, evidence, gate, or mathematical-function collapse, the repair is incomplete.
Preserve the subject’s necessary applicability and stop conditions in the repaired claim. Add blockedLocalOverreadRefs or nonAdmissibleUse as an explanatory guard only under F.19:4’s full independent-ground, plausible-reader, contribution, and smallest-clear-correction test. An unused guard may be omitted without an absence entry.
A.6.F:4.3 - Repair assignments
When a function-like phrase is claim-bearing, recover the object or claim under concern before lowering or rewriting the phrase. C.30.ASV does not define a world-side or view-local FunctionalElement individual. Its FunctionalStructureView is the same ArchitectureStructuralView episteme about one selected functional U.Structure; a FunctionalStructureViewUse may cite FunctionalElementClaim epistemes and other values needed by the use. Required or desired effects, actual transformations, candidate bearers, capabilities, ports, allocations, and correspondences remain separately established claims or values.
If a distinct functional-element individual is needed, first define its predicate and identity in a subject pattern; otherwise stop at the smaller requirement, behavior or effect claim, capability, participant, condition, port declaration, or other directly defined object. A field name or source cue is not a substitute for that object.
Method-description guard. A procedure, code file, solver model, recipe, protocol, or algorithm is only a clue. First identify the knowledge object and the method it is about. Then point to at least one claim that says how that method is done, such as its transformation or enactment concern, applicability, precondition, intended effect or preserved condition, bound, generic participant meaning, or internal method composition. Only then classify that already identified U.Episteme as U.MethodDescription under A.3.2.
A title, author, citation, approval, file form, or runnable artifact alone is a near-miss. If no admitted U.Method is its EntityOfConcern, or no way-of-doing claim is present, do not use U.MethodDescription: keep the actual plan, work, result, formal substrate, mechanism declaration, representation, publication occurrence or form, or carrier with its subject pattern. A different code, text, diagram, or publication form does not decide membership.
If claim content, method, or effective reference scheme changes, C.2.1 first identifies the resulting episteme; then apply A.3.2 to that individual.
| Function wording use | Recovered object or claim and subject pattern | Boundary |
|---|---|---|
| required or desired functional behavior, transformation, or effect | Keep the requirement or other claim about the required or desired behavior or effect with its requirement, architecture, capability-gap, functional-view, method, or other claim-bearing pattern. Use U.Transformation only for one independently grounded actual bounded change under A.3.4. Use TransformationFlowStructure only for an independently selected structure over explicitly named loci, not for the required effect itself. | Requirement wording establishes neither an occurrence nor a filled FunctionalElementClaim. Stop at the claim pattern unless the changed referent, boundary, conditions, actual before/during/after facts, and continuity or reidentification rule are grounded. A functional view may cite the required claim, selected structure, bearer candidate, capability, and allocation without saying that the change occurred. |
| functional element in a view | Under C.30.ASV, use one ArchitectureStructuralView episteme whose EntityOfConcern is one selected functional U.Structure. When needed, add a FunctionalStructureViewUse that cites C.2.1 FunctionalElementClaim epistemes and only separately established behavior or effect, bearer, capability, port, allocation, or correspondence values. | This is a claim-and-view interface, not a FunctionalElement individual, loose table row, or module. If no bearer or candidate allocation is current, keep the requirement, required-behavior claim, required-effect claim, capability gap, functional-behavior slot, or candidate-allocation question with its subject pattern. |
| transformer-side filler and candidate bearer | For a design-only candidate, keep the candidate transformer-side system locus or candidate U.System reference without asserting an assignment or performed Work. If the local kind TransformerSystemRole is current, name that kind; add a separate judgment classifying a System under it only when that judgment obtains. If an assignment is independently current, recover its directly declared species and its obtaining occurrence with actual participant values, holder, applicability, and extent under A.2.1. If performed Work is independently current, point to its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. Coordinate the selected locus with A.3.4 TransformerRef?, A.7, A.15, A.15.1, and A.15.2 only for the claims that are current. | A FunctionalElementClaim may cite an independently established candidate-bearer locus, but that citation is not the whole transformer ontology. A kind, classification judgment, assignment species, assignment occurrence, and dated Work are independent facts; none manufactures another. |
| input condition, output condition, and functional ports | A.3.4 InputConditionRefs?, OutputConditionRefs?, and FunctionalPortRefs?; U.Signature discipline through A.6.0 and A.6.5 when accepted or produced states, media, flows, signals, information, work products, formal objects, or functional port signatures matter | A functional port is not automatically a module interface. Use A.6.M only when module-interface or substitution compatibility is the claim. |
| capability of a System | the qualified ability claim about an identified System under A.2.2 | Does not imply that a method, module, work occurrence, or successful transformation exists. |
| method or algorithm wording | U.Method only when the claim concerns a reusable semantic way of doing; U.MethodDescription only for an already identified U.Episteme that passes the A.3.2 guard above: one admitted U.Method is its EntityOfConcern and at least one claim says how that method is done | Procedure, code, solver, recipe, protocol, and algorithm forms are clues only; they establish neither membership, execution, nor evidence. |
| mechanism wording | U.Mechanism through A.6.1 and E.20 when a law-governed realization or operation structure is the claim | Does not become a method, Work occurrence, capability, selected functional structure, or functional-view claim by label. |
| work plan, work occurrence, or work result | Recover the U.WorkPlan under A.15.2, one dated W : U.Work on its A.13 basis with independent A.15.1 admission and F.6 only for precise assignment-bound attribution, or the separately identified result entity or episteme together with the predicate that relates it to the current Work or application. Use A.15.PROD when production, entity inception, or production completion is current, and A.6.RCD only when the needed direct result relation has no current governor. | A plan, Work occurrence, and result are different objects. None implies reusable function ontology or completed functioning, and a result is not part of Work identity. |
| system-role or responsibility wording | VP.AllocationResponsibility is a recognition cue. A positive responsibility claim needs an applicable domain predicate and supporting facts about its participants and conditions; add explicit occurrence identity only when the use needs it. An absent predicate leaves an A.6.RCD missing governor, missing case facts leave the claim unknown, and contrary facts refute it. Establish any assignment independently under A.2.1. For actual Work use A.13 first, independent A.15.1 admission second, and F.6 only for precise assignment-bound attribution. | A system-role kind, classification judgment, assignment, function phrase, commitment, position, authority label, or Work attribution establishes no responsibility relation by form. Responsibility may obtain with or without a commitment; each relation keeps its own predicate and identity. |
| participation or actual functioning | Name the domain predicate, participants, conditions and case facts supporting the claim. Add explicit occurrence identity when the receiving use needs it. If no rule governs the needed predicate, return that A.6.RCD missing governor; if only case facts are missing, leave the claim unknown. | Assignment, capability, allocation, nearby Work, or a function label does not make participation or actual functioning obtain. |
| mathematical function or relation | Use its mathematical definition and applicable rule. When the use needs a separate C.29 lens account, state domain, codomain or relation domain, preserved and lost structure, admissible use and stop condition. | Mathematical form alone establishes no architecture, evidence, causal, assurance or decision claim. |
| quality or fitness expression | C.25, C.16, C.16.Q, A.17, A.18, or an admitted characteristic or measurement subject pattern according to the claim being made | Does not let “functionality” carry a quality claim without bearer and subject pattern. |
| module allocation | Recover the allocation or correspondence claim or relation under its subject pattern. When a functional view cites it, use FunctionalStructureViewUse with its ArchitectureStructuralView and the claim or relation reference; use A.6.M when a module-interface claim is being made. | Does not make function and module one FPF kind. One selected functional structure may have allocation claims involving several modules, one module may occur in claims about several functional structures, and a module may have no current functional-view claim. |
| interface relation, module-interface relation, or signature relation | Use A.6.RSIR first when bare interface, API, port, protocol, or service-access wording could point to several direct EoCs; then use A.6.M for the module-interface boundary and A.6.0 and A.6.5 for signature discipline, with A.6.B, A.6.C, or A.6.P:4.11a only when that boundary, interface condition, API, protocol, service, promise, or duty claim is being made | Does not turn a functional link, port label, API name, or signature into implemented compatibility. |
| evidence, result, assurance, gate, decision, or publication claim | the direct evidence, result, assurance, gate, decision, publication, or source pattern named by value | Function wording can point to these claims, but it does not authorize or prove them by itself. |
| functional architecture | ArchitectureOf@Context whose structureKindRefs includes FunctionalStructure, one selected functional U.Structure, and the ArchitectureStructuralView episteme about that structure. Use FunctionalStructureViewUse only when citations to FunctionalElementClaim epistemes or other separately established values change action. | Not a peer architecture ontology, functional-element individual, selected transformation-flow structure, or mathematical graph description by itself. |
Required-versus-actual check. “The cooling loop shall reduce outlet temperature by 8 °C within 60 seconds” remains a requirement or functional-view claim; by itself it identifies no U.Transformation. If a later run changes the loop state, identify that cooling occurrence separately under A.3.4 from the changed loop, boundary and conditions, actual before/during/after facts, and continuity or reidentification rule. Requirement-only material is the countercase and stop: it cannot admit an actual transformation, observed functioning, or evidence of success.
A.6.F:4.4 - Functional architecture boundary
Functional architecture is the FunctionalStructure case of ArchitectureOf@Context: the declared organization used to relate one selected functional structure to independently established claims about required behavior or effects, capabilities, functional dependencies, and constraints that a holon is to realize, before or alongside allocation to modules, local system-role kinds or assignments, work, evidence, control relations, selected transformation-flow structures, or mathematical descriptions of those structures. Under C.30.ASV, the view is an ArchitectureStructuralView episteme whose EntityOfConcern is that selected structure; it does not define a functional-element individual. A FunctionalStructureViewUse may cite FunctionalElementClaim epistemes and other separately established values needed by the use.
Functional architecture shorthand:
open the `ArchitectureOf@Context` form in the current C.30 edition;
name the described holon and select one functional `U.Structure`;
use the `ArchitectureStructuralView` episteme whose `EntityOfConcern` is that structure and whose viewpoint conformance obtains;
add `FunctionalStructureViewUse` only when `FunctionalElementClaim` epistemes or other separately established values change action;
require an independent A.3.4 basis for every actual-transformation reference;
fill every other C.30 field required by this architecture use.
The view keeps requirement, required-behavior/effect, capability, dependency, and constraint claims with their subject patterns; their wording does not turn them into SelectedStructureReference values or actual transformations. An actual-transformation reference is admissible only after A.3.4 independently grounds the occurrence. A selected TransformationFlowStructure, path slice, crossing, flow valuation, or mathematical description may be related to functional structure through C.30.TFS-REL, E.18, or E.18.2, but it is neither the required effect nor the functional architecture itself unless the positive selected-structure co-reference check succeeds.
A.6.F:4.5 - Function-flow-module alignment note
Recover the local alignment when functional wording touches flow or module allocation but does not yet require a full structural view or A.6.M module-relation repair. Use this note only when the receiving use needs an inspectable alignment record; otherwise state the recovered alignment and boundary in the repaired wording.
FunctionFlowModuleAlignmentNote:
required function or effect:
flow path or dependency:
proposed module allocation:
separateNeighborClaims:
known mismatch:
subjectPatternApplicationRefs:
admissible use:
non-admissible use?:
The note records only the local function-flow-module alignment and boundary. Its explanatory non-admissible-use guard is optional under the full F.19:4 test and needs no absence entry when unused. Functional architecture, module relation, implemented-interface, evidence-sufficiency, and architecture-decision claims remain with their subject patterns.
A.6.F:4.6 - Common kind and relation separations
| Confusion | Repair |
|---|---|
| function = module | Keep VP.Functional and VP.ModuleInterface distinct; connect them through declared correspondence, allocation, retargeting, or A.6.M module-relation repair. |
| function = capability | Capability is the qualified ability of a System under A.2.2. Keep a required or desired behavior/effect as claim content under its requirement, architecture, capability-gap, functional-view, method, or other subject pattern; neither that claim nor the capability establishes an actual transformation. |
| function = work | One W : U.Work is a dated world-side occurrence. Its result or output is a separately identified entity or episteme. Connect it only through the subject-specific direct result or production relation that obtains, or use one local A.15.PROD claim for the current production-work, inception, or completion question. Use A.6.RCD only when a needed relation has no current governor. Function wording remains design-side or description-side content unless a work-facing claim is current. |
| function = method | Method is a reusable way of doing. A method claim may state an intended effect, but that effect is neither the method nor an actual U.Transformation; apply A.3.4 only when the actual change occurrence is independently grounded. |
| function = system-role kind, assignment, participation, functioning, or responsibility | Recover only the branch the sentence asserts. A system-role kind is a local ...SystemRole kind; an assignment is one occurrence and its declared U.SystemRoleAssignment species; actual Work requires A.13 and independent A.15.1 admission, with F.6 only for precise assignment-bound attribution; participation, functioning, and responsibility each need their domain predicate and supporting case facts; a missing rule, unknown fact and refuted claim have different outcomes. |
| mathematical function = holon purpose | Recover the intended connection to purpose. Use C.29 when it requires a mathematical representation or inference account, including preserved and lost structure and limits of use; an ordinary mathematical function needs no such account merely to remain a function. |
| functional diagram = evidence | Distinguish the diagram, the claim-bearing episteme it expresses and any publication. The content may support a named claim under that claim’s direct rule; diagram presence alone does not. Use A.10 when the source-to-use account is implicit or must remain replayable, and G.6 when the receiving use needs an addressable provenance path. |
| functionality = quality | Recover the quality bearer and subject pattern through C.25, C.16, or C.16.Q before using the wording as an adequacy claim. |
A.6.F:4.7 - Composability and compositionality
Composability and quality compositionality are separate claims. If the text says parts can be assembled, keep that as a structure or use claim. If it says a quality of the whole follows from parts, assign the quality-composition claim to C.25 and the direct characteristic, measurement, or quality pattern governing that claim:
Composability:
exactGovernedObjectOrClaim: the A.6.M `ModuleInterfaceClaim` content for "A and B can be assembled under interface X"
selectedClaimBearingEpistemeUse: the C.2.1 episteme carrying that claim content
directRelationPredicateUse?: only a domain predicate independently admitted for a direct module-allocation or module-interface relation, with its actual participants
relationalAssertionUse?: the C.2.1 episteme that affirms, denies, or modalizes that admitted predicate, only when such a predicate is current
obtainingRelationOccurrenceUse?: only when that admitted relation has a same-versus-new-occurrence rule and the receiving use needs explicit identity to distinguish, reidentify or refer to one obtaining occurrence, or to use it as a participant through A.6.REL
reusableDeclarationUse?: one compatible RelationSignature and its declaration-local SlotSpecs, only when the receiving typed use needs them
subjectPatternApplicationRefs: A.6.M for `ModuleInterfaceClaim`; C.2.1 for its claim-bearing episteme; A.6.RCD when a reusable direct relation is needed but absent; A.6.REL only after the direct relation is admitted and the receiving use needs explicit occurrence identity; A.6.0 and A.6.5 only for the reusable declaration
Quality compositionality:
exactGovernedObjectOrClaim: the affected Q-Bundle and the structural-characteristic, causal-hypothesis, or evidence-relation claim that this use relies on
directRelationPredicateUse?: the predicate supplied by the applicable subject pattern and its actual participants, only when that relation is current
relationalAssertionUse?: the C.2.1 episteme and its affirmative, negative, or modal quality or evidence claim when that assertion is current
subjectPatternApplicationRefs: C.25; A.17 and A.18 for Characteristic and Scale questions; C.16 for measurement; C.16.Q for unresolved quality wording; A.10 when the source-to-use account is implicit or must remain replayable
Non-admissible:
successful assembly is not quality propagation
Compositional formalisms may express composition structures and view or model relations. They do not make safety, latency, reliability, or another quality propagate automatically.
A.6.F defines no separate quality-composition record. Use the claim form supplied by the applicable subject pattern. A composite family uses the C.25 Q-Bundle with its bearer and declared measures. Include scope, a qualification window, mechanisms, status, or evidence when that value changes the quality claim or receiving action. A single Characteristic and its Scale follow A.17 and A.18; use C.16 for a measurement question and C.16.Q when quality wording still needs repair. Keep a causal inference with its causal pattern. Use A.10 when the source-to-use account is implicit or must remain replayable. If a required value cannot be established, keep the dependent quality-composition claim unresolved rather than filling an A.6.F-only schema.
A.6.F:4.8 - Worked slices
Function-like module claim; no direct relation. A release note says, “The brake-control functional package is in the vehicle-control system.” The receiving question asks what interface BrakeControllerPackage presents in Release-2026Q2 under BrakeControlInterfaceSpec-v5. That question selects the module-interface claim; the adjective functional alone selects neither that claim nor a new U.Function kind. Recover:
exactGovernedObjectOrClaim: A.6.MModuleInterfaceClaimcontent namingBrakeControllerPackage,VehicleControlSystem,Release-2026Q2,VP.ModuleInterface,BrakeControlBoundary, and aninterfaceSpecificationRefthat resolvesBrakeControlInterfaceSpec-v5; its direct-relation disposition isnoDirectRelationClaimed;selectedClaimBearingEpistemeUse:BrakeArchitectureNote_v3 : U.Epistemeunder C.2.1 carries that content and hasBrakeControllerPackageas itsEntityOfConcern;directRelationPredicateUse,relationalAssertionUse, andobtainingRelationOccurrenceUse:not used, because no domain rule has admitted a direct module relation predicate or an obtaining occurrence for this case;- remaining action: apply A.6.M to the declared interface and admissibility conditions; do not infer a function allocation, direct relation, or implemented compatibility from the source phrase.
Interrupted assignment; occurrence identity needed. A maintenance log says, “Robot-7 resumed its inspection function after a documented period with no inspection assignment.” Treat function as a cue. Recover InspectorSystemRole and one declared direct species CellInspectorAssignment <: U.SystemRoleAssignment; then test its direct predicate for Robot-7 : U.System and the species-specific cell and interval participants. Keep Robot7AssignmentLog_42 as the separate C.2.1 episteme that states the interval facts. A.2.1 says that the demonstrated non-assignment period ends the first assignment occurrence and the later resumption begins another. When the maintenance history must distinguish them, apply A.6.REL with that identity rule to keep InspectorAssignment_PreGap and InspectorAssignment_PostGap distinct. A taxonomy or scheme is not an assignment participant, and neither assignment implies inspection Work.
Neighbor claims that need their own relation.
TestArticle-7 participates passively in TestWork-9 during TestInterval-9is not established byTestArticleSystemRoleorTestArticleAssignment-7. Until a direct passive-test-participation predicate supplies participant order and identity, returnA.6.RCD missing-governor[direct passive-test-participation relation]; the tester’s Work and F.6 attribution remain usable.Motor-M1 drives PumpAssembly-A during PumpRun-17needs a direct motor-drive-functioning predicate. Assignment, torque capability, and pumping Work remain separate; without that predicate returnA.6.RCD missing-governor[direct motor-drive-functioning relation].Hammer-3 supports PaperStack-9 during Interval-Pneeds a direct artifact-support predicate. Do not replace that claim with an interchangeable list of use, load, support, or function kinds; without the predicate returnA.6.RCD missing-governor[direct artifact-support relation].
Functional architecture phrase. A team says, “the functional architecture is the user journey.” A.6.F does not let the phrase create a separate architecture kind. For a receiving use that needs inspectable detail, th