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 head noun is package; do not turn the modifier functional into U.Function. For this use, recover this concrete result:

exactGovernedObjectOrClaim: A.6.M ModuleInterfaceClaim content naming BrakeControllerPackage, VehicleControlSystem, Release-2026Q2, VP.ModuleInterface, BrakeControlBoundary, and an interfaceSpecificationRef that resolves BrakeControlInterfaceSpec-v5; its direct-relation disposition is noDirectRelationClaimed;
selectedClaimBearingEpistemeUse: BrakeArchitectureNote_v3 : U.Episteme under C.2.1 carries that content and has BrakeControllerPackage as its exact EntityOfConcern;
directRelationPredicateUse, relationalAssertionUse, and obtainingRelationOccurrenceUse: 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-9 is not established by TestArticleSystemRole or TestArticleAssignment-7. Until a direct passive-test-participation predicate supplies participant order and identity, return A.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-17 needs a direct motor-drive-functioning predicate. Assignment, torque capability, and pumping Work remain separate; without that predicate return A.6.RCD missing-governor[direct motor-drive-functioning relation].
Hammer-3 supports PaperStack-9 during Interval-P needs a direct artifact-support predicate. Do not replace that exact claim with an interchangeable list of use, load, support, or function kinds; without the predicate return A.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, the repair can be recorded as:

FunctionUseRepair:
phrase: "functional architecture"
functionLikeReadingUnderRepair: functionalArchitecture
exactGovernedObjectOrClaim: the `ArchitectureOf@Context` claim record and its one selected functional `U.Structure`
selectedClaimBearingEpistemeUse: the exact `ArchitectureStructuralView` episteme whose `EntityOfConcern` is that structure, plus any exact C.2.1 `FunctionalElementClaim` epistemes cited by the use
subjectPatternApplicationRefs: C.30; C.30.ASV
blockedLocalOverreadRefs: the source claim "the functional architecture is the user journey"
nextAdmissibleUse: when the view changes action, use `FunctionalStructureViewUse` to cite the view, exact claim epistemes, and only separately established bearer, capability, port, allocation, or correspondence values
stopCondition: ordinary phrasing remains Plain when no architecture claim is made; requirement-only material remains a claim; an actual transformation appears only on an independent A.3.4 basis

Functionality as quality. A product note says, “new functionality improves adequacy.” The repair separates the exact added-capability or required-effect claim from the quality claim. Capability or effect wording may stay as recognition, but the adequacy claim goes to C.25, C.16, C.16.Q, or the admitted characteristic or measurement pattern that states its bearer and criterion. A.6.F stops once those exact claims and subject patterns are clear; it adds no reusable declaration, view, or representation apparatus unless the receiving use actually needs it.

Mathematical function or loss. A model note says, “the loss function explains the holon purpose.” The repair keeps the mathematical function under C.29 lens discipline: domain, codomain or relation domain, preserved and lost structure, lens-use admissibility value, and stop condition. The loss may inform a reasoning move; it does not become holon purpose, evidence sufficiency, causal proof, assurance, or project decision by itself.

Pump-station functional dependency. A maintenance note says, “the backup pump function is degraded.” A.6.F first separates the required effect, the qualified ability claim about the holder System, the physical module allocation, the performed maintenance work, the evidence relation, and the quality claim. The functional wording may open a FunctionalStructure view under C.30.ASV or go to the capability pattern; it does not by itself prove the pump was tested, authorize operation, or make the backup module compatible with the main line.

Product-platform allocation. A hardware team says, “thermal management functionality moved to the chassis.” The repair separates required heat-removal effect, module allocation, interface constraints, signature constraints, architecture structural view, and any evidence or gate claim. A.6.F keeps the function-like wording useful for architecture work while sending module-interface and evidence claims to their subject patterns.