Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:25:20 UTC

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 positionManufacturingScientific peer review
Local system-role kindWeldingRobotSystemRolePeerReviewerSystemRole
Holder systemABB_Robot_Model_IRB_6700, designating one particular robot U.System in this hypothetical case; IRB 6700 is its model designationDr_Alice_Smith, modeled as an admitted U.System
Direct assignment species and occurrenceFactoryWeldingAssignment with the robot and WeldingRobotSystemRole; include another participant, for example a factory line or work order, only if that species predicate depends on itJournalReviewAssignment with Alice and PeerReviewerSystemRole; a commission-sensitive appointment species also carries the review commission
Separate semantic sources when usedFactoryProductionSystemRoles-2026 and Factory-Line-B-Scheme may be used as sources for classification or interpretation claims under the applicable source and evidence relationsPhysicsPeerReviewSystemRoles-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 currentCited by the receiving factory interpretation claim, never inserted as a participant of every assignment speciesCited by the receiving journal interpretation claim, never inserted as a participant of every assignment species
U.MethodDescription epistemeThe procedure episteme available through Welding_Procedure_WP-28A.pdf, with admitted WeldingMethod as EntityOfConcern and substantive way-of-doing claimsThe guideline episteme available through Peer_Review_Guidelines_v3.docx, with admitted PeerReviewMethod as EntityOfConcern and substantive way-of-doing claims
Holder capability, when relied onability to execute a 3F welding seam within a declared envelope and current windowability to evaluate a quantum-optics manuscript within a declared envelope and current window
Work occurrenceWeld_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 WeldingMethodReview_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.