A.3:5 - Solution — The Transformer Quartet

For work-enactment, A.3 keeps four neighboring anchors visible: the performer-side assignment, a MethodDescription edition when the receiving use relies on one, the enacted Method, and the dated Work. For another independently grounded asymmetric actor-side claim, apply only the anchors required by its direct governor. These anchors qualify the actor-side claim; they are not occurrence conditions for every U.Transformation.

A.3:5.1 - The four anchors (terms & types)

Acting side: for actual Work, use A.13 to recover each performer System and its obtaining assignment, then let A.15.1 admit the dated occurrence independently. If the current use also claims under which assignment the Work was performed, use F.6 performedUnderAssignment(W, RA) with that same assignment and its holder System. For another actor-side claim, its direct owner grounds the participants and decides whether a work-facing role assignment is current. Canonical phrase when that assignment is grounded: system assigned to the locally defined TransformerRole@Context kind. Local shorthand: after explicit binding in the same subsection, you MAY write Transformer for that same system; re-bind on context change and do not use the shorthand where the domain already has a conflicting transformer term. The shorthand neither identifies an actual transformation nor upgrades causal participation or broad physical agentivity into Work.
MethodDescription (description episteme, when relied on): an SOP, program, protocol, script, diagram, or other source is a U.MethodDescription only when it meets A.3.2 membership for the exact Method. Its exact edition is cited only when the receiving claim about Work, assurance, gate, audit, or another use depends on that description.
Method (run-independent semantic way of doing): the exact U.Method that Work may enact. It is neither an occurrence nor a MethodDescription, role assignment, or holder capability. Order-sensitive composition belongs to B.1.5 only when that composition claim is current.
Work (world-side dated occurrence holon): U.Work is the admitted kind; one Work individual is admitted under A.15.1 from independently grounded performance history, each performer System’s A.13 basis, actual enactsMethod relations, its temporal extent, and at least one obtaining locally declared Work-to-System relation whose stated boundary contains the complete occurrence. Add F.6 performedUnderAssignment, affected-referent, binding, and resource-use relations only when their own facts obtain and the current use relies on them. A U.Episteme may assert or describe those facts and designate the occurrence; a ticket, log row, record, or carrier is not the Work. The occurrence neither requires one universal MethodDescription edition nor establishes an actual change, result, production, delivery, acceptance, or aggregate merely by occurring.

Memory line: A MethodDescription may describe a Method; one dated world-side Work occurrence may enact that Method; a Work assertion may designate that occurrence. The description, occurrence, and assertion are different holons, and none of these relations alone establishes actual change or result. A local system-role kind and an obtaining assignment are distinct (A.2/A.2.1); a Method is a reusable way of doing; a Work individual is the performed behaviour occurrence.

A.3:5.2 - System-role assignment (`U.SystemRoleAssignment`) for actor-side enactment

When a performed-work claim relies on an assignment, identify its directly declared species under U.SystemRoleAssignment, the participant meanings and predicate that species defines, and the actual participant values that satisfy that predicate. Preserve the holder System, the assigned local system-role kind, and any real additional participant, such as a commission or position, required by that species. Use A.2.1 for its declaration and occurrence identity.

An assignment assertion or occurrence description may state assignmentInterval for the currently known temporal extent. That description does not make the predicate obtain or add a generic assignment participant.
Cite a taxonomy episteme and effective ReferenceScheme when they matter to interpretation. They, a generic U.BoundedContext, and a selected BoundedModelUseStructure are not generic assignment participants. When a receiving claim about Work depends on a selected interpretation structure, designate it through that receiving use’s relation.
The same System may hold several assignments to local system-role kinds when their direct compatibility rules admit them; labels or shared context wording do not decide compatibility.
When work on an episteme or carrier is claimed, the acting performer remains a System; episteme identity, carrier change, Work, publication, and evidence retain separate governors.
An independently grounded A.3.4 occurrence supplies none of the assignment participants or temporal facts by itself.

A.3:5.3 - Boundary & externality

A.3.4 first identifies the actual bounded change from its changed referent and subject-side occurrence facts. Add an asymmetric acting side and target side only when a direct participation, interaction, causality, or work owner independently grounds that factorization. If an exact interaction relation obtains, cite its direct governing pattern; A.3 does not create one from the word “transformation.”

Natural, spontaneous, and formal transformations can therefore remain actual without an invented performer. Joint dynamics, relational change, or a non-separable or frame-dependent participation case also remains under its direct dynamics, relation, interaction, or causality owner until an asymmetric actor–target split is justified. Ordinary coupling and scale-free or minimal physical agentivity alone establish neither TransformerRole@Context, U.Method, nor a dated Work occurrence admitted under U.Work.

For work on oneself, use the A.12 reflexive split only after two distinct internal positions are grounded for the current claim. The acting and changed positions may be subholons inside one containing holon; selecting those already grounded parts is an A.14/C.13 structure move, not a Meta-Holon Transition. Use B.2 only if the whole itself is reidentified.

A.3:5.4 - Align the temporal claims of descriptions, Methods and Work

A U.MethodDescription is a separately identified episteme; cite its exact edition only when the receiving use relies on what that edition says, using C.2.1 for any claimed edition relation.
A U.Method is run-independent and may be enacted by many dated Work occurrences.
One Work individual admitted under U.Work has its own governed temporal extent and performer basis under A.13/A.15.1. Use F.6 with the same obtaining assignment only when precise assignment-bound attribution is claimed; an assertion or description may designate those facts, but is not the occurrence. No universal live StateAssertion is a Work or Method condition.
When a work-to-change claim is current, identify the world-side Work under A.15.1, the actual change under A.3.4, and the exact direct relation between them. A formal ordering boundary or natural change remains under A.3.4 without a work-facing inference.

A.3:5.5 - Evidence Graph Referring

An assertion or description episteme about one Work occurrence makes its performer Systems with their A.13 assignments and enacted Method recoverable. Cite an obtaining F.6 relation for a claimed assignment-bound attribution and a MethodDescription edition only when the receiving use depends on it. Logs, observations, provenance, evidence, and their carriers remain separately related under their direct owners; neither the assertion nor a carrier or output produced by the performer is the Work occurrence or self-certifying evidence for it or its effects.

A.3:5.6 - Didactic dictionary

Process, workflow, SOP, algorithm, protocol, script, or recipe is source wording first. Recover whether the current object is a MethodDescription, Method, WorkPlan, dated Work, method-relation structure, or another directly governed object.
Operation, job, run, or performance is a Work individual admitted under U.Work only when the A.15.1 occurrence basis is recoverable; a log row, ticket, assertion, description, or label does not make it Work.
Function in an equipment specification may describe a Method, a MethodDescription, a capability, an intended effect, or another direct relation; the word alone decides none of them.
Creator becomes local shorthand for a Transformer only when an exact actor-side holder has already been bound as a system through the applicable direct relation and, for performed Work, an obtaining U.SystemRoleAssignment; otherwise recover the actual relation or stop.