A.15 - System-Role–Method–Work Alignment
Type: Architectural (A) Status: Stable Normativity: Normative unless marked informative
At a glance. Use this pattern when a team must say which System performed which Work, under which assignment, which Method the Work enacted, and which plan applied without confusing any of those values with a description, capability, record, or result. A precise actual-performer branch first reuses A.13’s core, then A.15.1 independently admits the dated Work, and only afterward F.6 uses the same obtaining assignment when precise assignment-bound attribution is current; an agency characteristic profile remains conditional on its receiving use.
Use this when. Use A.15 when a receiving decision needs to connect classification or assignment, Method, capability, planning and performed Work while keeping the claims distinct. Recover only the values and relations that decision consumes.
Start here when. The team is mixing system classification or assignment with recipe, schedule, capability, or performed Work, often under an ambiguous source word such as role, process, workflow, or activity.
First output. For planning, identify the intended WorkPlan, performer, local system-role kind and Method only as the next decision requires them. For precise actual performance, recover the A.13 core and independently admit dated Work under A.15.1 from its history, Method, extent and containing-System relation. Add F.6 performedUnderAssignment only for precise assignment-bound attribution, using that same obtaining assignment. State that the System performed the Work under the assignment and that the Work enacted the Method only when both relations obtain. Keep descriptions, plans, capability claims, records and results distinct.
Minimum sufficient use. Recover only the values and relations needed by the receiving use. Ordinary orientation can stop at one clear sentence. A reliance-bearing claim may also need occurrence identity and extent, the selected source and its currentness, a capability-fit claim, and the evidence or assurance claim relied on.
Recovered-reference sufficiency condition. Proceed when every value and relation consumed by the claim is recoverable with the meaning, identity and conditions that use needs. Otherwise narrow the claim or recover the missing basis. A bounded reversible probe is one option when its attainable contribution justifies its burden under C.11.DUA. Record a repair or decision request, prospective plan entry or source gap only when the continuation needs it.
Ordinary use. “Robot-7 performed InspectionWork-17 under InspectionAssignment-17, and the Work enacted TurbineInspectionMethod” can be enough when the A.13 core, same obtaining assignment, F.6 link, and enactsMethod relation remain recoverable and the receiving use needs no additional identifiers. A Grade or autonomy profile is not implied.
Reliance-bearing use. Use the fuller frame when assignment identity, assignment state, Method edition, capability fit, plan baseline, approval, evidence, release, or disputed responsibility changes the decision. Responsibility and authority remain separate direct relations; neither follows from a system-role kind or assignment.
Stop condition. Stop when the needed values and relations are clear enough for the supported next use and further separation would not change that use.
Admissible-use examples.
| Admissible project use | Source-finding or reversible probe | Non-admissible use |
|---|---|---|
| A maintenance team identifies the local inspection kind, assignment species and occurrence, Method, and any description or WorkPlan needed by its decision. After inspection, it identifies dated Work independently of the inspection record. | A briefing lacks a source or relation required for its attempted use; use it to locate or recover that basis before making the unsupported claim. | The presence or form of a dashboard, copied approval, generated explanation, label or briefing is treated as proof of assignment, Method, WorkPlan or performed Work. Assess the content’s evidence contribution under the rule for the claim it bears on; use A.10 when that use needs a replayable source-to-use account. |
Alignment frame in plain terms. The system-role kind says what contribution kind is in question. The assignment relates this System to that kind while its predicate obtains. The Method is the way the Work is done. A MethodDescription describes the admitted Method; a WorkPlan states possible future Work. Dated Work is what happened. A log reports it and remains distinct from that occurrence.
What goes wrong if missed. A team collapses classification, assignment, recipe, plan, capability, and performed Work into one fuzzy “process” or “role” label, then mistakes documentation for execution, capability for performance, a schedule for an occurrence, or an assignment for responsibility.
What this buys. A compact trace answers who performed the Work, under which assignment, which Method it enacted, and which separate plan and evidence applied, while leaving each additional claim to its direct pattern.
Not this pattern when. Use A.15.1 for one dated Work occurrence, A.15.2 for planning or schedule baselines, A.15.5 for work-entry readiness, A.16 or A.16.1 for a cue that has not become an alignment question, A.6 or A.6.B for boundary or policy wording, E.10.ROLE when role is still unresolved, and A.15.4 when a visible item is being relied on by appearance.
Related pattern contributions. Use A.2 and C.3 to identify local system-role kinds, A.2.1 for direct U.SystemRoleAssignment species, A.13 for the local agency core and any conditionally consumed profile, F.6 for performed-Work attribution through that same assignment, A.15.1 for dated Work, A.15.2 for WorkPlan epistemes, A.15.3 for declaration-local planned-filling content inside a WorkPlan, A.15.4 for work-relevant reliance by appearance, A.15.5 for work-entry readiness, F.11 to align Method and Work vocabulary across contexts, and F.17 for the human-facing term sheet.
Causal-use work boundary. Causal inquiry can use the Method, plan, performer and Work distinctions when those claims are needed. C.28 separately governs the causal-use question, rung, estimand, identification, estimate, sampling and simulation contributions, and supported or unsupported uses. Alignment alone does not establish causal admissibility.
Related-record mistakes. A cue, publication, plan, record, result, evidence item, or approval can help locate a value without becoming that value. Recover the dated Work under A.15.1. State a subject-specific production or result relation only under its direct pattern; for a production-work, entity-inception, or production-completion question, A.15.PROD may instead return one local claim or blocker. Use A.15.4 only when reliance on an encountered appearance is the problem.
Boundary to coarsened renderings. A briefing, summary, redacted note, or coarsened rendering may orient work. Rely on it for an execution, approval, gate, or evidence question only when the sources and relations required by that use remain explicit and reopenable. Use A.6.3.CSC when coarsening itself changes what may be relied on.
Outside-practice result boundary. When one receiving decision or piece of Work needs a bounded result governed by another practice, use A.15.9 to inspect an already-available result before requesting anything new, ask only for the remaining gap, and preserve supplier Method and authority separately from the receiving decision. A.15 keeps the underlying Method, Work, performer, assignment, communication, result, and record distinctions unchanged.
A.15:1 - Problem frame
When the alignment is already clear and ongoing Work still needs one next action chosen from current facts within an applicable domain Method, use A.15.7. It keeps the domain Method, steering Method, deciding System, intended performer, and any later WorkPlan or performed-action claim separate.
Complex work requires several independent distinctions: what a System is; which local system-role kind classifies it; which assignment occurrence obtains and which declared U.SystemRoleAssignment species it instantiates; how Work is done through U.Method; whether an episteme is a U.MethodDescription; which holder capability is relied on; what U.WorkPlan states; which dated Work happened; and which separate assertions, records, results, and evidence concern that Work.
A.15 brings these already defined values together without creating a new process object or redefining their ontologies:
- A.2 and C.3 identify a local system-role kind and any classification judgment. Classification neither creates an assignment nor proves Work.
- A.2.1 identifies an assignment occurrence and its declared species under
U.SystemRoleAssignment. The species declaresHolderSystemSlot, a declaration-localAssignedSystemRoleKindSlotwith its local system-role-kind domain, its predicate and applicability, any additional participants, and its occurrence-identity rule. The occurrence supplies the actual participants and extent. Taxonomy, scheme, signature, assertion, evidence, and interval may interpret or describe the claim; they are not generic participants. - A.13, A.15.1, and F.6 govern ordered but distinct results. A.13 supplies the System, local agential kind and criterion, classification, obtaining assignment, scope, working situation, window, and adequate core evidence; its characteristic profile is conditional. A.15.1 then independently admits dated Work. Only after admission, and only when the receiving use expressly consumes precise assignment-bound attribution, does F.6 relate that Work to the same assignment through
performedUnderAssignment. Its holder projection is used only to compare holder equality with the actual performer already recovered through A.13; F.6 identifies neither assignment nor performer. Missing F.6 attribution does not revoke Work membership. - A.3.1 and A.3.2 keep
U.Methoddistinct fromU.MethodDescription. - A.15.1 and A.15.2 keep actual dated Work distinct from intended WorkPlan and from every record about either.
- A.2.2, A.10, and neighboring direct patterns keep capability-fit claims, evidence use, source currentness, publication, responsibility, authority, access, results, and assurance outside assignment and Work identity.
When source wording such as process, workflow, action, activity, schedule or role leaves its meaning unresolved, use F.19 and then the applicable E.10, E.10.ARCH or E.10.ROLE rule. Keep ordinary wording when the needed object, relation or action is already clear. Recover the precise FPF value only when the receiving claim depends on it.
A.15:2 - Problem
Without this alignment, several category errors recur:
- System-role-kind as part.
AuditorSystemRoleis placed in structuralpartOfdecomposition although it is a local kind used to classify systems. - Description as execution. A recipe, algorithm, SOP, or MethodDescription is treated as proof that Work occurred.
- Capability as Work. Ability and actual performance are collapsed.
- Incomplete Work basis or attribution. A Work claim lacks its required performer, assignment, or Method basis, or a precise assignment-bound attribution claim lacks its holder-equality check.
- Assignment as responsibility or authority. Holding a system-role assignment is treated as if it established a duty, permission, responsibility, authority, or approval relation.
- Universal assignment record. A permissive root signature hides different direct species and turns taxonomy, scheme, context, or source into generic participants.
- Actor by association. A kind, assignment, capability, Method, description, plan, or record is made to act. Only the admitted holder system performs Work.
- Process soup. One overloaded source word stands for classification, assignment, Method, description, plan, Work, result, and record at once.
A.15:3 - Forces
| Force | Tension |
|---|---|
| Structure and enactment | Stable structural decomposition must remain distinct from system classification, assignment, Method, plan, capability, and dated Work. |
| Simple and specialized assignments | A simple assignment should remain light, while a commission, position, or locus must retain the participant that distinguishes its species and occurrence. |
| Method, plan, and occurrence | A reusable Method, its description, intended Work, and performed Work must stay connected without becoming one record. |
| Clarity and precision | Practitioners need ordinary readable claims, while reliance-bearing use may need occurrence identity, evidence use, source currentness, or assurance. |
| Accountability and proportionality | Auditability may require a full trace, but ordinary orientation should stop at the shortest sufficient relation chain. |
A.15:4 - Solution
Recover the values first, then state only the relations needed by the receiving use. A.15 aligns system-role kind, assignment, Method, MethodDescription, capability, WorkPlan, Work, and separate records; it does not create a universal process object or a universal assignment signature.
When wording about changing, producing, selecting, deriving, controlling or maintaining leaves its object unresolved, use E.10.ARCH. A workflow graph, process calculus, matrix, category, embedding or neural representation may describe or serve as a lens over a Method relation structure; its representation form alone establishes no Method, assignment, WorkPlan or Work occurrence.
A.15:4.1 - Core entities kept distinct
- Local system-role kind. A value such as
InspectorSystemRole : U.Kindis admitted under A.2 with C.3 through itsU.Systemcandidate domain, operative work-facing membership condition, member/non-member boundary, and continuity rule. It is not a system, assignment, relation slot, capability, Method, Work, responsibility, or authority. A system classification judgment and an assignment occurrence are separate claims. U.SystemRoleAssignment. This is the relation family consumed by A.15 and F.6. It has no permissive rootRelationSignature. Each direct species declaresHolderSystemSlot : U.System, a declaration-localAssignedSystemRoleKindSlotwhose ValueKind is one local system-role-kind domain, its predicate and applicability, every additional participant, and its occurrence-identity rule.U.Method. The run-independent semantic way of doing. A Work occurrence can stand inenactsMethod(W, M); the Method does not act.U.MethodDescription. An already identifiedU.EpistemewhoseEntityOfConcernis an admitted Method and whose substantive claims say how that Method is done, as judged by A.3.2. Wording, file form, or publication alone establishes no membership.- Holder capability (A.2.2). The holder’s ability to perform named work under stated conditions and bounds. Its assertion, evidence, currentness assessment and fit to a demand remain separate. Ability establishes neither assignment nor performed Work.
U.WorkPlan. AU.Epistemeabout possible future Work, including intended windows, dependencies, performers, and budgets. It does not bring a future Work occurrence into existence.U.Work. The admitted kind for concrete dated Work occurrences. One Work individual has its own temporal extent, at least one obtaining A.15.1enactsMethodrelation, and at least one obtaining locally declared containing-system relation. It may stand in further enactment, affected-referent, binding, resource-use, production, and result relations when the receiving use needs those independently obtaining facts. Any log, ticket, assertion, description, or performed-work record is a separate episteme.
Work occurrence and record boundary. Recover the affected-referent, transformation, speech-act effect, commitment effect, production, delivery, acceptance, or other relation under its direct pattern. Labels such as operational, communicative and epistemic can remain recognition cues; they do not define Work subkinds by enumeration.
Didactic note for managers: the chef analogy. ChefSystemRole is one local system-role kind. A kitchen-assignment species defines the holder and assigned-kind positions and adds shift, station, or commission only when it changes the assignment. A particular assignment fills those positions with the chef System, the kind, and any additional value. A cookbook can be a MethodDescription; the chef’s skill can be a capability; a WorkPlan can schedule cooking; and making one souffle on Tuesday is dated Work. Its temporal and resource-use relations can state the 25-minute extent, eggs, butter, and consumed gas, while a kitchen log remains a separate episteme. A restaurant vocabulary or scheme can help interpret the claims without becoming a participant in every assignment. The cookbook, skill, plan, assignment, and log do not cook.
A.15:4.2 - Canonical relations
graph TD
subgraph "Direct system-role assignment species"
H["holder H : U.System"] -- "HolderSystemSlot" --> RA["RA : InspectionShiftAssignment<br/><: U.SystemRoleAssignment"]
K["InspectorSystemRole<br/>local kind"] -- "AssignedSystemRoleKindSlot" --> RA
end
subgraph "Method, description, and capability"
M["M : U.Method"]
D["D : U.Episteme<br/>A.3.2 membership: U.MethodDescription<br/>EntityOfConcern = M"]
Cap["Qualified ability claim about H"]
Fit["capability-fit condition"] -- "tests" --> Cap
end
W["W : U.Work"] -- "performedUnderAssignment<br/>holder equality check: RA.Holder = H" --> RA
W -- "enactsMethod" --> M
style K fill:#fff2cc,stroke:#d6b656,stroke-width:2px
style Cap fill:#d5e8d4,stroke:#82b366,stroke-width:2px
style Fit fill:#d5e8d4,stroke:#82b366,stroke-width:2px,stroke-dasharray: 4 4
style M fill:#d5e8d4,stroke:#82b366,stroke-width:2px
style D fill:#f8cecc,stroke:#b85450,stroke-width:2px
style H fill:#e1d5e7,stroke:#9673a6,stroke-width:2px
style RA fill:#dae8fc,stroke:#6c8ebf,stroke-width:3px,stroke-dasharray: 5 5
style W fill:#ffe6cc,stroke:#d79b00,stroke-width:2px,font-weight:bold
The diagram shows a simple direct assignment species. A stronger appointment can declare an additional participant such as a review commission; that specialized occurrence itself is the U.SystemRoleAssignment. Do not create a weaker generic occurrence beside it. The displayed F.6 edge is included because this example claims precise assignment-bound attribution; a Work claim that does not need that attribution omits it.
- Capability fit. A MethodDescription, WorkPlan, or work-admission assertion may require a holder capability threshold. The fit condition compares the holder’s qualified ability claim with the receiving work conditions and bounds and may cite declared measures,
U.Characteristicvalues, Q-Bundle slots, or architecture-characteristic criteria. It is neither an assignment participant nor a second capability kind. - MethodDescription membership.
Dis aU.MethodDescriptiononly when A.3.2 recovers MethodMas its EntityOfConcern and at least one substantive way-of-doing claim. “D describes M” is shorthand for that constitution and membership result, not another binary relation. enactsMethod(W : U.Work, M : U.Method). This relation states which Method the dated Work enacts. A.15.1 defines its participant order, predicate, occurrence identity, and multiplicity. It neither attributes a performer nor turns a description into the Method.performedUnderAssignment(W : U.Work, RA : U.SystemRoleAssignment). F.6 defines this relation. For a precise actual performer,RAis the same obtaining assignment used by A.13 for the action, scope, working situation, and window. It must be an occurrence of a declared assignment species, have the A.13-qualified System as holder, and cover the Work while the species predicate obtains. The assignment is the attribution ground, not the actor. A record may state the relation without constituting it. Read an existingperformedBy(W, RA)claim only through the F.6 compatibility boundary after resolving the holder System; do not author new claims with that spelling.
One assignment occurrence continues through the maximal uninterrupted interval in which its direct species predicate obtains for fixed participants. A declared interval, taxonomy, scheme, KindSignature, assertion, evidence item, or selected model-use structure can describe or interpret the claim but does not create the occurrence or become a generic participant.
For a precise performed occurrence, first recover the A.13 core for the actual performer System and action, then admit W : U.Work under A.15.1 from its independent occurrence, Method, extent, and containment facts. Only afterward trace W to the same RA through F.6 performedUnderAssignment when the receiving use needs precise assignment-bound attribution, and compare RA.HolderSystemSlot with the already recovered performer; F.6 identifies neither. Trace W to M separately through enactsMethod. Cite a characteristic profile only when conditionally consumed; cite a MethodDescription, plan, capability claim, evidence item, taxonomy, or scheme separately only when the receiving use relies on it. The performer System acts; the kind, assignment, capability, Method, description, plan, evidence, and record do not.
A.15:4.3 - Bounded specialization scouting and CheckpointReturn
For a human-plus-AI pair planning tool calls or probing a route, recover only the Systems, assignments, Methods, plans and Work needed by the alignment claim, with their applicable admission grounds. The pair may use four local system-role kinds for this bounded work: OutcomeCriterionHolderSystemRole, AIScoutSystemRole, AISpecialistProbeSystemRole, and CommitAuthoritySystemRole. Claim an assignment only by naming its occurrence and declared species under U.SystemRoleAssignment. The CommitAuthoritySystemRole name does not supply decision authority; any authority relation must obtain independently.
First distinguish the current question. If another probe could change which option survives the OptionSet, return to C.11. If changed live facts or domain-Method limits could change the next action during ongoing Work, return to A.15.7. Use C.24 when an applicable domain prescription or a completed decision has fixed the action or option and tool or service calls must be planned.
Use a sufficient existing CallPlan directly. Otherwise use C.24 to construct the fixed action’s route from available inputs, qualified Method contributions and required intermediate results, then check its feasibility. Select a bounded scout or probe only for a specific unresolved fact that could change the usable route and when the attainable answer justifies the inquiry under the applicable criterion, budget and permission. After actual probing, return what was tested and observed in a CheckpointReturn. Use A.15 for the assignment, Method, plan and Work claims this use needs, and C.24 for planning and checkpoint semantics. When an E.16 autonomy budget governs the scouting, retain its scout budget, probe budget, commit checkpoint and guard or override path.
After a bounded probe, its CheckpointReturn carries the C.24 action basis and:
- the objective or
TaskFamilyand the applicable outcome criterion; - the Methods tested, with approach descriptions when needed;
- the evidence observed for those tests and important failure signals, including progress toward any work-measure threshold used by the decision;
- burned and residual budget;
- the recommended next action, such as a further bounded probe, adoption of an identified
CallPlan, a narrower supported claim, return to the applicable pattern or domain prescription, or stop; and - the commit trigger for considering whether to end the probe and adopt an identified
CallPlan.
The return is evidence about the tested approaches, observed results, budget and proposed continuation. It is not the selected Method, U.WorkPlan or actual Work. Use the trigger, probe evidence, residual budget and any required safety or assurance result to decide whether to adopt the identified plan, probe further or stop. Plan adoption, permission to perform calls and actual Work remain separate. Recover the execution-evidence, provenance or rollout-decision claims consumed by that decision or later rollout under their applicable rules.
A.15:4.4 - Boundary to A.15.4 Work-Relevant Appearance-Based Reliance Repair
Use A.15.4 when an encountered episteme, carrier, display, credential view, generated explanation, copied statement, provenance mark, dashboard tile, schema wording, API wording, or source-relation chain is being relied on by appearance for Work, assignment currentness, assignment state, source currentness, approval, authorization, gate passage, evidence, engineering justification, release, or another reliance-bearing claim.
A.15 itself keeps the local system-role kind, holder system, direct assignment occurrence, Method, MethodDescription, WorkPlan, dated Work occurrence, and every separate episteme distinct. A.15.4 recovers the project-side value and relation that must hold before the visible item can warrant the attempted use.
A principle scheme, functional diagram, scenario, screen, or explanation that exposes an E.18.1 P2W carry-through structure may help a team plan Work or find a source. It does not become the selected Method, plan, Work occurrence, result, evidence, or authority by publication.
A.15:4.4a - Inspecting Method–Work Alignment Across an Unfolding Structure
Do not create a linkage record merely because one unfolding structure mentions several Method- and Work-related values. Keep each direct relation under the pattern that defines it. When a receiving use must preserve an inspectable explanation across those relations, write one bounded C.2.1 episteme whose EntityOfConcern is the selected unfolding U.Structure. Its ClaimGraph may cite, as separate claims, the selected Method and Method-relation structure, MethodDescription epistemes, relevant local system-role kinds and assignment occurrences, the Work that enacts the Method, Work-part relations, independently identified transformations and their direct Work-to-change claims, intended WorkPlans, readiness results, capability-fit conditions, evidence, assurance, and gate decisions. Include only claims needed by that receiving use.
Call this episteme a Method–Work alignment account in ordinary prose. Its identity comes from its EntityOfConcern, ClaimGraph, and effective ReferenceScheme, not from a field bundle. Each claim in the account remains defined or tested by its own pattern: A.3.1 for Method, A.3.2 for MethodDescription, A.15.2 for planning, A.15.5 for readiness, A.15.1 for dated Work and Work relations, B.3 for assurance, A.20 for internal-constraint results, and A.21 for gate decisions. Assess evidence under the rule for the claim it bears on; use A.10 when a replayable source-to-use account is needed. If the useful account would need several unrelated entities of concern, split it instead of using one umbrella record.
Another structure, such as CGUS, P2W, P2S, an improvement-loop slice or a transformation-flow slice, may cite the episteme when its receiving use needs the alignment explanation. Recover the cited claims under their source, identity and applicability conditions; reuse an established result while those grounds remain valid.
A.15:4.5 - Boundary to A.15.5 Work-Entry Readiness
Use A.15.5 when the current question is whether intended Work is ready to enter its boundary. A.15 keeps system-role kind, assignment, Method, plan, and Work distinct; A.15.5 carries WorkEntryReadiness@Context, FullKitCondition, commitment disposition, resource-readiness references, WIP or flow-policy references, planned baselines, and launch-gate references when those values are current.
Readiness is not performed Work, evidence sufficiency, or gate passage. A briefing, dashboard, source bundle, or P2W record may cue A.15.5. Ground the result in the WorkPlan being judged, the PlanItem content the criterion consumes, that criterion and the facts used to evaluate it. State the readiness result, its qualification window, and the applicable stop or degraded-use condition. Identify missing or unknown required inputs; include performed preparation Work or a planned baseline only when the criterion or receiving use consumes it. Address the PlanItem content through that WorkPlan; it is not another readiness target.
A.15:5 - Archetypal Grounding
Use this alignment whenever the live question joins a holder system, local system-role kind, assignment occurrence, Method, plan, capability, or performed Work. Physical engineering, knowledge work, and socio-technical work can use the same distinctions without turning A.15 into a universal process ontology.
Boundary case — possessed algorithm versus enacted Method. Robot-7 : U.System is classified under InspectorSystemRole and is the holder of InspectionAssignment-17, an occurrence of a direct maintenance-assignment species. A capability claim may say that Robot-7 can inspect turbines, and source prose may say it “possesses inspection algorithm A”. Neither claim is dated performance, and neither makes TurbineInspectionProcedure-v3 a U.MethodDescription. If InspectionWork-17 occurs, first recover Robot-7’s full A.13 core through that same obtaining assignment and let A.15.1 independently admit the Work. Then, because this alignment also expressly consumes precise assignment-bound attribution, establish F.6 through InspectionAssignment-17. The already recovered performer performed the Work under that assignment, and the Work enacted TurbineInspection@Maintenance-2026. Use A.3.2 to decide whether the procedure episteme is a MethodDescription. Robot-7 acts; the kind, assignment, capability, algorithm wording, Method, and description do not.
| Alignment position | Manufacturing | Scientific peer review |
|---|---|---|
| Local system-role kind | WeldingRobotSystemRole | PeerReviewerSystemRole |
| Holder system | ABB_Robot_Model_IRB_6700, designating one particular robot U.System in this hypothetical case; IRB 6700 is its model designation | Dr_Alice_Smith, modeled as an admitted U.System |
| Direct assignment species and occurrence | FactoryWeldingAssignment with the robot and WeldingRobotSystemRole; include another participant, for example a factory line or work order, only if that species predicate depends on it | JournalReviewAssignment with Alice and PeerReviewerSystemRole; a commission-sensitive appointment species also carries the review commission |
| Separate semantic sources when used | FactoryProductionSystemRoles-2026 and Factory-Line-B-Scheme may be used as sources for classification or interpretation claims under the applicable source and evidence relations | PhysicsPeerReviewSystemRoles-2026 and PhysicsLetters-A-Review-Scheme may be used as sources for classification or interpretation claims under the applicable source and evidence relations |
| Selected model-use structure, only when current | Cited by the receiving factory interpretation claim, never inserted as a participant of every assignment species | Cited by the receiving journal interpretation claim, never inserted as a participant of every assignment species |
U.MethodDescription episteme | The procedure episteme available through Welding_Procedure_WP-28A.pdf, with admitted WeldingMethod as EntityOfConcern and substantive way-of-doing claims | The guideline episteme available through Peer_Review_Guidelines_v3.docx, with admitted PeerReviewMethod as EntityOfConcern and substantive way-of-doing claims |
| Holder capability, when relied on | ability to execute a 3F welding seam within a declared envelope and current window | ability to evaluate a quantum-optics manuscript within a declared envelope and current window |
| Work occurrence | Weld_Job_#78345, whose temporal relation covers 15:32–15:34 UTC on 2025-08-15; separate resource-use relations connect 1.2 kWh and 5 g Argon, and enactsMethod connects WeldingMethod | Review_of_Manuscript_#PL-2025-018, whose temporal relation ends on 2025-08-15; a separate resource-use relation connects four hours of reviewer time, and enactsMethod connects PeerReviewMethod |
Worked continuation: attribution can remain open after Work is identified. In a constructed inspection, Robot-7 is an admitted System satisfying the local InspectorSystemRole criterion of detecting the specified blade discontinuities from the required images. InspectionAssignment-18 obtains under its direct maintenance-assignment species for Robot-7 in the morning inspection window. The performance history places InspectionWork-18 from 08:10 to 08:25 on Day-D; its independently established enactsMethod relation identifies the admitted TurbineInspection@Maintenance-2026 Method, and the locally declared containing-System relation identifies the independently admitted System MaintenanceCell-1. These facts satisfy the stated A.13 core and the independent A.15.1 admission basis.
The receiving attribution question additionally asks whether InspectionWork-18 was performed under InspectionAssignment-18. The case establishes that Robot-7 accepted the inspection task under InspectionAssignment-18 and carried out InspectionWork-18 as that assigned task. The assignment’s holder is Robot-7 and its obtaining interval is 08:00–09:00. With the declared species and its obtaining conditions also established, these facts satisfy the F.6 constraints and the separate Work–assignment link. Another assignment with the same holder and interval does not inherit that link. If later evidence leaves the assignment’s ending time unresolved, reopen that attribution and every decision relying on it. Preserve the independently established performance history and Method enactment. Retain Work identity where its independent admission grounds still hold, and recheck any admission condition that consumed the disputed premise. Missing F.6 attribution alone establishes neither no Work nor successful inspection; success requires its own result and evidence claim.
Key takeaway. Both cases use an admitted holder System, a local system-role kind, an assignment occurrence and its declared species, a Method, a separate MethodDescription, a capability relied on for the case, and dated Work. Their taxonomies, schemes, commissions, records, and results remain separate values and relations. This common alignment does not erase their different domain ontologies.
A.15:5.1.a - Briefing guides orientation, not execution
Source set. A release team has one deployment method description, one current work plan, one approval or decision record when required, and the evidence records and evidence relations used to decide whether the rollout may proceed. A short rollout briefing is prepared for the daily stand-up.
Briefing slice. For stand-up orientation: the source bundle reports that the rollback procedure passed its named check. Before rollout, recover that result and the deployment Method, WorkPlan and any required authorization and evidence under their applicable conditions.
This briefing may orient the team and cue attention. If the team wants to execute from the briefing alone, use A.15.4 or the evidence, gate, decision, or assurance pattern that defines or tests the claim to recover the missing project-side kind and reference. Inside A.15, keep only the system-role kind, assignment, Method, plan, and Work-occurrence separation.
A.15:5.1.b - P2W principle-scheme publication guides planning, not occurrence
Source set. A team has a principle scheme that shows an E.18.1 P2W carry-through structure for a fabrication task: signature or principle episteme, method-family selection, selected method, U.WorkPlan, an actual Work occurrence admitted under U.Work, a separate work-result record, and result measurement.
Published slice. For the proposed next batch, Method M-2 is selected from the declared family; prepare WorkPlan WP-17 before performing that batch's planned Work.
This publication can guide Method inspection and planning. Keep the selected Method, WorkPlan, any earlier actual Work occurrence, its record and result measurement distinct. For evidence, gate or engineering reliance, recover the required project-side claim under its direct rule. If that basis is missing, retain the supported planning use and state only the gap or continuation the receiver needs.
A.15:5.1.c - Scenario guides method selection, not performed work
Source set. A method-selection scenario says that material X is below threshold T, resource window W is available, and the fabrication cell is under setup condition S. The scenario is admitted source material; a publication form or carrier may expose that source material for choosing between method families but does not become the selected method or plan.
Published slice. Under scenario S, method family MF-2 is admissible for planning; choose the selected method and prepare the work plan before execution.
The scenario can guide Method-family selection and planning. Identify a selected Method or resulting WorkPlan in the account where that result is needed. Ground any later dated Work independently under A.15.1; a record may designate it but is not that occurrence. For evidence, gate or engineering-justification reliance, establish the required claim, relation or decision under its direct rule, such as A.20 for internal-constraint results, A.21 for gate decisions or B.3 for assurance. Use A.10 when that reliance needs a replayable source-to-use account. If a required basis is unavailable, narrow the use and keep the needed gap or continuation in the receiving account.
A.15:6 - Bias-Annotation
Bias lenses: Gov, Arch, Onto and Epist, Prag, Did. Scope: Universal for system-role–Method–Work alignment across engineering, operational, and knowledge-work settings.
| Bias risk | Failure | Repair |
|---|---|---|
| Governance bias | A familiar system-role label, assignment row, approval display, or status is treated as proof that Work happened or responsibility obtains. | Keep classification, assignment, Work, responsibility, authority, and evidence in their direct relations. |
| Architectural bias | A system-role kind, capability, fit condition, Method, or record is placed in structural decomposition. | Keep structure, classification, dependent capability, relations, epistemes, and dated Work distinct. |
| Epistemic bias | A recipe, schedule, roster, or log is treated as its world-side referent. | Recover the Method, assignment, WorkPlan, Work, and obtaining relations; keep the source as an episteme. |
| Pragmatic bias | One overloaded process or role term is retained because it feels shorter. | Use E.10.ARCH or E.10.ROLE, then write the shortest sentence that names the recovered values. |
| Didactic bias | The chef analogy hides direct-species and occurrence requirements. | Recover the concrete assignment species; add F.6 only for precise assignment-bound attribution. An ordinary explanation needs no complete schema. |
A.15:7 - Conformance Checklist
| ID | Check | Why |
|---|---|---|
| CC-A15-1 | Keep local system-role kind, U.SystemRoleAssignment, U.Method, U.MethodDescription, qualified holder-ability claim, U.WorkPlan, U.Work, and every record or result distinct. | Prevents one alignment frame from becoming one object. |
| CC-A15-1a | Treat a dated Work individual as world-side; keep assertions, descriptions, logs, tickets, and performed-work records as separate epistemes. Actual performer, Method, temporal, locally declared containing-system, affected-referent, binding, and resource-use relations obtain independently and are not stored fields of the occurrence. | Blocks record fields from constituting Work. |
| CC-A15-2 | Keep the reusable Method, its description, intended Work, and performed Work distinct. Operational events do not mutate a MethodDescription or WorkPlan. | Prevents recipe, schedule, and execution collapse. |
| CC-A15-3 | For a precise actual performer, reuse the A.13 core and independently admit dated Work through A.15.1. Only when the receiving use expressly consumes precise assignment-bound attribution, relate that Work through the same obtaining occurrence of a directly declared species under U.SystemRoleAssignment; confirm that RA.HolderSystemSlot equals the already recovered performer and that the assignment predicate covers the Work interval. Require a characteristic profile only when conditionally consumed. | Preserves the independently recovered performer and Work while adding only the conditional attribution; F.6 discovers neither and no universal assignment signature is invented. |
| CC-A15-4 | For precise assignment-bound attribution, trace the A.13-qualified H through the same obtaining assignment RA, then W -performedUnderAssignment-> RA, RA.HolderSystemSlot -> H, and W -enactsMethod-> M. Cite characteristic profile, MethodDescription, plan, capability, source, and evidence separately only when relied on. | Preserves one inspectable A.13→A.15.1→F.6 chain without turning interpretation metadata into participants. |
| CC-A15-5 | Keep system-role kinds, capabilities, fit predicates, Methods, and evidence or assurance records out of partOf hierarchies unless another direct pattern admits a structural relation. | Blocks classification, evidence, and assurance as parts. |
| CC-A15-6 | Attribute resource use to dated Work through obtaining relations, not to a MethodDescription, WorkPlan, capability, assignment, or fit predicate. | Keeps costs with performance. |
| CC-A15-7 | Use U.WorkPlan for intended Work and identify actual Work independently. | Stops schedule-as-performance drift. |
| CC-A15-8 | Resolve ambiguous process, workflow, activity, schedule or role wording through F.19 and the applicable E.10 rule. Retain ordinary wording whose meaning is already clear. | A cue prompts inspection rather than automatic formalization. |
| CC-A15-9 | State enactsMethod and performedUnderAssignment separately. Only the admitted holder System with its A.13 core performs Work; a profile is conditional. A capability or algorithm-possession phrase proves neither performance nor MethodDescription membership. Spontaneous physical evolution without this alignment is not Work. Use A.3.4 to identify an actual bounded change, and A.3.3 when a U.Dynamics episteme describing its state space and transition law is needed. | Prevents kind, assignment, capability, Method, description, plan, dynamics, and records from becoming actors. |
| CC-A15-10 | Treat a speech act that institutes an assignment, authorization, or gate-relevant effect as its own Work occurrence only when A.15.1 admission and the effect relation obtain. | Keeps the communicative Work distinct from later operational Work. |
| CC-A15-11 | Recover the assignment’s direct species, local assigned-kind domain, participants, predicate, and occurrence. Taxonomy, scheme, signature, context, and source are cited separately when the receiving claim uses them. An approver or deployer label neither creates a Work subkind nor proves performance. | Prevents a permissive assignment record and kind-by-label. |
| CC-A15-12 | For causal intervention or sampling, state the Method, description, plan, dated Work, assignment attribution or enactment claims the use needs, under their own rules. Use C.28 for the causal-use question, rung, estimand, separate support components, support result and admissible-use boundary. | Keeps work alignment from becoming causal authority or a compulsory full claim set. |
| CC-A15-13 | Use A.15.4 when a visible item is relied on by appearance; retain only the system-role–Method–Work separation here. | Keeps reliance repair out of the alignment kernel. |
| CC-A15-14 | Keep an E.18.1 P2W structure, its publication, selected Method, WorkPlan, Work, result record, and measurement distinct. | Publication alone establishes none of the project-side values. |
A.15:8 - Common Anti-Patterns and How to Avoid Them
- System-role-kind as part. Do not place
InspectorSystemRole, a capability, fit condition, or evidence or assurance record in structural decomposition merely because it appears on an architecture diagram. - Universal assignment signature. Do not give
U.SystemRoleAssignmentone permissive root signature. Recover the direct species and its local assigned-kind domain. - Generic assignment beside an appointment. Let the specialized appointment occurrence itself belong to
U.SystemRoleAssignment; F.6 uses its common holder projection. - Recipe as evidence. A MethodDescription can identify or constrain a Method but does not prove performed Work.
- Plan as performed Work. A schedule or intended-assignment claim remains distinct from dated Work, which is identified independently under A.15.1; use A.15.2 for WorkPlan membership.
- Capability as Work. Ability, a capability statement, or a passing fit condition is not performance.
- Assignment as responsibility or authority. Recover the direct neighboring relation required by the claim, for example responsibility, commitment, permission, authority, access, or gate passage, or return its missing governor.
- Approval collapse. Keep approval or authorization Work and the operational Work it permits as separate occurrences and effect relations.
- Process soup. Resolve ambiguous source wording before relying on it; do not create a generic process object.
- Appearance as execution. Use A.15.4 when a dashboard, credential, copied approval, generated explanation, provenance label, or command-like cue is being relied on by appearance.
- P2W publication as Work. A principle scheme, functional diagram, scenario, screen, or explanation can guide planning without becoming Method, WorkPlan, Work, result, evidence, gate, or justification.
A.15:9 - Consequences
| Gain | Cost or trade-off |
|---|---|
| Teams can ask which System performed which Work, under which assignment and Method, without making a kind or document act. | Reliance-bearing use must recover the assignment occurrence and its declared species rather than stop at a familiar label. |
| Simple assignments stay simple while commission-, position-, or locus-sensitive assignments preserve their participants. | Each bounded vocabulary must admit the direct species and local system-role-kind domain it uses. |
| MethodDescription, WorkPlan, Work, result, and evidence can change independently. A MethodDescription can be revised without rewriting past Work; a holder can be replaced when the replacement satisfies the required classification, assignment, and capability-fit conditions. | A decision-relevant case may need several short direct claims instead of one overloaded record. |
| Responsibility, authority, permission, capability, assignment state, and result stay available without being inferred from assignment. | The receiving use must say which of those additional relations it needs. |
| The chef analogy and ordinary first sentence make the distinction teachable. | Readers still need one concrete direct-species example so the analogy does not hide assignment identity. |
For example, AuditorSystemRole can be the local kind used by an audit-assignment species. A particular assignment names its holder System, but this precise attribution still requires F.6 to relate ApprovalWork-17 to that same assignment and confirm holder equality with the A.13-qualified performer after A.15.1 independently admits the Work. Any decision authority, responsibility, gate effect, Method, capability fit, result, and evidence are separate claims. The kind name and assignment prove none of them.
A.15:10 - Rationale
Teams often store classification, assignment, recipe, plan, capability, execution, result, and evidence in one “process” record, then cannot tell which fact changed. A.15 keeps the values separate and adds only the two alignment relations needed most often: performed-Work attribution and Method enactment.
The separation follows established ontology and practice distinctions among enduring systems, relation occurrences, event-like Work, and epistemes. Process-theory formalisms such as Petri nets and process calculi remain source lineage for dynamic interaction, but their word process is recovered here to Method, MethodDescription, WorkPlan, dated Work, Dynamics, Transformation, or a separate episteme rather than imported as one FPF object. FPF adapts the useful distinctions through local system-role kinds, assignment species and their occurrences, a common holder projection, Methods, WorkPlans, dated Work, and neighboring relations; it does not import a foreign hierarchy.
The distinction is operationally useful. When work fails, a team can ask whether the wrong system was assigned, the assignment did not cover the Work, the Method was unsuitable, the MethodDescription was wrong, the plan was stale, the capability claim was unsupported, or the performed occurrence departed from the Method. Correcting one answer need not rewrite the others.
A.15:11 - SoTA-Echoing: Adopted Invariants and Rejected Shortcuts
| Practice need | Source line and status | FPF adaptation | Rejected shortcut |
|---|---|---|---|
| Keep case, decision, plan, and executed occurrence separable. | OMG CMMN 1.1 (2016) and OMG DMN 1.5 (2024) provide mature modeling lineage; ITIL 4 Change Enablement (2023) provides current practitioner guidance. | Keep MethodDescription, WorkPlan, approval Work, and operational Work separate, with every Work occurrence admitted on its own A.15.1 basis. | One undifferentiated process object. |
| Keep system classification, relation occurrence, and dated Work distinct. | Almeida, Guizzardi, Sales, and Fonseca, gUFO (2026 preprint), is a current foundational-ontology comparator rather than imported hierarchy. | Retain FPF’s local system-role kinds, direct assignment species, holder projection, and Work identity laws. | A foreign role hierarchy or relation model deciding FPF identity. |
| Recover event, performer, qualified association, and records without making a log row the event. | OCEL 2.0 (2024) is current object-centric event-log practice; W3C PROV-O (2013) is representation lineage. | Identify dated Work and the assignment occurrence first; keep logs and provenance as separate epistemes and relations. | Anonymous Work, assignment by label, or record-as-occurrence. |
| Keep authorization acts and the operations they permit distinct. | ITIL 4 Change Enablement (2023) and DMN 1.5 (2024) separate assessment, decision, authorization, scheduling, and realization. | Admit each communicative or operational Work occurrence independently and state its effect relation. | Approval collapsed into later operational Work, or label-defined Work subkinds. |
| Keep bounded exploration separate from committed rollout. | Current agentic tool-use, self-correction, and human-in-the-loop work-control practice extends the ReAct, Toolformer, and Reflexion lines with explicit checkpoints and bounded tool use. | For tool-call planning after the action is fixed, keep the relevant System, assignment, Method, plan and Work claims distinct. Retain an adequate CallPlan; after a needed bounded probe, return the tested Methods, evidence, budget and commit trigger in CheckpointReturn under C.24, with E.16 controls when an autonomy budget applies. | One successful probe silently becomes the selected Method, WorkPlan, or rollout. |
Use the direct FPF identity rules for the alignment claims above. Use C.30.AD for an architecture-description question.
For visible credential, provenance, dashboard, explanation, or composed-source cases that require a project-side value and relation before reliance, use A.15.4.
A.15:12 - Relations
-
A.15.9coordinates one receiving decision or piece of Work with one bounded result governed by another practice. It first tests an already-available result, requests only a remaining gap, and preserves supplier Method and authority separately from receiver decision authority; it creates no new alignment object or result kind. -
A.15.7supplies the situation-responsive steering Method after current Work, its domain Method, and relevant facts are known; it returns the selected action, intended performer, and stop or feedback condition without making the answer into Work. -
Architecture-work boundary: C.32.P2S and C.32.PAD may cite MethodDescriptions, pattern-use references, system-role assignments, separate responsibility or authority relations, readiness exits, and expected structure effects. C.32.ADR may publish those references. A.15 supplies only Method, description, plan, readiness, performed Work, and attribution distinctions.
-
Uses:
A.7for strict distinction among system-role kind, assignment, Method, MethodDescription, plan, Work, and records. -
Builds on:
A.2and C.3 for local system-role kinds and classification;A.2.1for directU.SystemRoleAssignmentspecies; A.13 for the local agency core and conditionally consumed profile;A.2.2for capability;A.2.5forSystemRoleAssignmentStateRelation;A.2.7for relations among system-role kinds;A.6.5for relation-slot discipline; A.3.1/A.3.2/A.3.3/A.3.4 for Method, MethodDescription, Dynamics, and Transformation, respectively;A.15.1for independent Work admission;A.15.2for WorkPlan;A.15.3for declaration-local planned-filling content inside that WorkPlan;A.15.5for readiness; and F.6 for the laterperformedUnderAssignmentrelation and holder-equality projection only when precise assignment-bound attribution is consumed. -
Coordinates with: A.15.4 for work-relevant reliance repair; E.10, E.10.ARCH, and E.10.ROLE for wording recovery; A.6 for boundary and policy claims; A.10 for evidence and provenance; B.3 for assurance; A.20 and A.21 for constraints and gates; C.28 for causal-use admissibility; C.29 for mathematical-lens use; E.18.1 for P2W carry-through; C.32.P2S for architecturing-flow references; and E.17.EFP for generated-explanation faithfulness.
-
Used in: claims that must keep systems, local system-role kinds, assignments, Methods, WorkPlans, Work occurrences, result records, and reliance repairs distinct. A.15 is not a generic process ontology, workflow engine, evidence graph, gate pattern, or publication pattern.
A.15:12a - Coordinated-work evidence and distributed-state relation note
Use A.15 first when the claim concerns which system performed which Work, under which system-role assignment, which Method the Work enacted, and which separate result is claimed. Coordinated Work, routine skill, team alignment, tacit knowledge, and fit among assignment, Method, and Work are not quantum-like by default.
Application choices:
- Name the holder systems, local system-role kinds, assignments, Methods, Work occurrences, and separate results needed by the claim.
- State which Work occurrences and which separate C.2.1 assertions, traces, observations, reports, or metrics make the coordination visible.
- Ask whether ordinary system-role–Method–Work alignment explains the case. If yes, stop in A.15.
- Add a C.26.2 low-recoverability distributed-state reading only after establishing its collective
U.Systembearer and boundary under C.26.2, and only when no participant statement, local component report, single evidence record, dashboard, or exported representation carries the inferred state faithfully enough for its intended use. Without that collective bearer, retain ordinary A.15 alignment of individual performers. - State the weakest evidence-bound reading, its time window, rival explanations, and export loss.
- Use C.26.2:4.11 to select the evidence posture and additional support needed by the intended use. Use A.10 when the selected posture or intended reliance requires a replayable account of evidence provenance and bounded reliance. Obtain a B.3 assurance result for the named target claim and receiving use when an actual assurance claim is current. QLP-3 use or a direct domain requirement for assurance requires that claim and result. Momentary, low-consequence local Work guidance does not by itself require B.3.
The C.26.2 reading is a minimal evidence-bound U.Episteme claim about that collective System. It is not a group mind, performed Work, evidence sufficiency, or assurance by itself.
| Position | Required content |
|---|---|
| Evidence or provenance relation | Work, or a separate assertion, trace, observation, report, or metric about it, connected to the reading through an independently established direct evidence/provenance relation. Use A.10 when a replayable source-to-use account is needed, and G.6 when a trace representation is needed. |
| Time window | The interval for which the reading is supported and any local stop; add decay or refresh conditions when the intended reuse, contest or consequential reliance needs them. |
| Probe or occasion | The question, task, workshop, incident, handover, dashboard, or coordination situation that made the state inferable |
| Weakest claim | The minimal distributed-state reading carried by the sources |
| Rival explanations | For example, routine compliance, policy, command, coincidence, incentive, documentation, or local skill |
| Export loss | What is lost when the reading is summarized into one report, score, or statement |
Useful outputs are an A.15 alignment claim when assignments and Work explain the case; a C.26.2 reading about the declared collective System within its boundary when the evidence survives ordinary rivals; an A.10 account of the evidence relation; a B.3 assurance result for a current named assurance claim, including the claim required by QLP-3 use or a direct domain rule; or no distributed-state reading when the sources, rivals, or time window cannot be named.
A.15:12b - C.29 mathematical-lens use relation
When a mathematical lens helps select a Method, compare Method families, shape a WorkPlan, or diagnose Work, use an adequate domain result directly, retaining the correspondence, application conditions and material limits needed by the claim. Use C.29 when a separate mathematical-representation choice, transfer or reliance question remains. The next concrete value remains under its direct pattern: ChoiceResult or another local choice record when a choice is made, the selected Method when Method selection is claimed, U.WorkPlan for intent, dated Work for execution, a separate result record for a result claim, and A.15.4 when a reliance appearance is being used as the reason before the required relation is known. A mathematical lens may explain why a distinction is useful; it does not make a plan into performed Work or a Method explanation into execution evidence.
A.15:12c - P2W Work-Family Split
When an E.18.1 P2W use reaches work planning or work-entry readiness, keep the selected Method, one U.WorkPlan with any declaration-local SlotFillingsPlanItem content, WorkEntryReadiness@Context, dated Work occurrence, and separate result records distinct. A planned-filling row is addressable only through that WorkPlan and gains no independent identity. A principle scheme, functional diagram or scenario may help identify a Method or planning question and guide its examination. Establish the particular Method, WorkPlan, readiness result or dated Work under its own pattern before asserting or relying on that value.
Work planning may cite evidence and currentness requests for the direct relation under repair. A.15.5 may cite the WorkPlan and designate declaration-local PlanItem content when its readiness criterion uses that content. Name evidence, gate passage, performed Work, result measurement, assurance, or refresh before relying on a planning or readiness record for that stronger claim.
A.15:12d - P2W Performed-Work Relation
When E.18.1 reaches performed Work, keep U.Work as the admitted kind and identify one dated occurrence under it.
A performed-work record is a separate U.Episteme. It may cite a WorkPlan, planned baseline, and Work occurrence. It can state bindings, performed values, substitutions, variance, telemetry, outputs, outcome claims, and result references only through independently obtaining relations; none is stored in or constituted by the Work occurrence. Comparator, transport, PrincipleFrame, formal-substrate signature, evidence, assurance, and gate relations remain separate.
A.15:12e - P2W Integration as System-Role Assignment and Work Feasibility
When E.18.1 uses integration to ask whether an admitted system can hold a local system-role kind and perform Work under interface constraints, name the system-role kind, the direct U.SystemRoleAssignment species and occurrence when assignment is claimed, the Method or MethodDescription, the relevant WorkPlan or Work occurrence, and the interface constraints defined by the architecture or module-interface pattern.
Classification, assignment, capability fit, interface satisfaction, authority, responsibility, Method selection, planning, and performed Work remain separate claims. Other connected values, for example artifacts, telemetry, acceptance records, diagrams, selected structures, checks, gates, evidence, and provenance, also keep their direct relations.
A.15:12f - Lowering, Repair, and Refresh Conditions
Lower an A.15 claim when the holder system, local system-role kind, direct assignment species or occurrence, Method, MethodDescription, WorkPlan, readiness relation, dated Work, or capability fit cannot be named at the granularity needed by the next use. A weaker result can be a separation note, missing-source note, A.15.4 repair request, decision request, prospective WorkPlan entry, or A.15.5 readiness-gap note.
Repair the changed relation or its account and recheck every claim that depends on that change. A corrected assignment or SystemRoleAssignmentStateRelation does not by itself rewrite the Method or historical Work; a changed WorkPlan does not rewrite performed Work. Corrected evidence may change what is justified about an assignment or Work without changing the past occurrence. Preserve independently supported claims and unchanged dependencies.
Refresh before reliance when the local system-role kind or its criterion changes, the assignment species or predicate changes, another assignment occurrence is needed, the Method family or WorkPlan changes, the execution window changes, or a result, evidence, assurance, gate, reliance, or mathematical-lens relation is no longer current. A taxonomy, scheme, KindSignature, or selected model-use structure triggers refresh only when the receiving claim depends on the changed semantic basis. If the remaining question is no longer system-role–Method–Work alignment, use its direct pattern and keep only the A.15 separation still needed.