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 21:55:20 UTC

A.3 - Transformer Quartet: Distinguish Work, Performer, Method and Method Description

Status: Stable

A.3:1 - Intent

Use this pattern to distinguish a performed Work occurrence from its performer, enacted Method and any relied-on MethodDescription. Recover each performer’s A.13 basis, then admit the dated Work independently through A.15.1 with its enacted Method. Use F.6 when the account also needs precise assignment-bound attribution. Add MethodDescription, capability, work-to-change, evidence or aggregation claims only when the receiving use relies on them.

The Transformer Quartet keeps those object families distinct; it does not require every change claim or Work assertion to name all four. A.3.4 independently identifies an actual bounded change. That result alone establishes no acting System, agency, assignment, Method or Work. A.2, A.15.1 and C.2.1 define the neighboring objects; A.7 preserves their distinctions and A.10 governs evidence use.

A.3:2 - Context

  • Holonic substrate. FPF distinguishes what things are (Holon → {System, Episteme, …}) from a System’s classification under local system-role kinds and its obtaining assignments of those kinds (A.2/A.2.1). Only systems can be holders of these assignments, enact methods, and perform Work occurrences admitted under U.Work; epistemes do not act. This work-facing rule does not imply that every actual change has an acting-system side.
  • Local kind, assignment, Method, description, and occurrence stay distinct. A local system-role kind classifies Systems by its criterion; an obtaining assignment of that kind is a separate relation (A.2/A.2.1). U.Method is a run-independent semantic way of doing, U.MethodDescription is an episteme that may describe that Method, and each individual admitted under U.Work is the dated performed occurrence that enacts it.
  • Run-independent semantics vs dated occurrence. A Method and any episteme that describes it are not the occurrence. Add F.6 assignment-bound attribution, affected-referent, binding, or resource-use relations only when they independently obtain and the receiving use relies on them. When actual change is also claimed, identify it independently under A.3.4 and use a separately governed work-to-change relation.
  • Occurrence, assertion, evidence, and carrier. One Work individual is the world-side occurrence. A separate U.Episteme may assert or describe it and designate the exact occurrence and obtaining relations. Logs, observations, evidence items, and publications have their own carriers and direct relations; neither a carrier nor a record becomes Work by referring to it.

A.3:3 - Problem

Shorthand such as “actor,” “process” or “blueprint” can hide these different questions:

  1. Missing acting-side basis: a self-configuration claim depends on a performer or distinct acting and changed positions that its account has not established.
  2. Plan = event: blueprint/algorithm reported as if execution happened.
  3. Capability or Method = Work: having a capability or a Method is taken to establish that Work occurred.
  4. Episteme as doer: documents/models treated as actors.
  5. Occurrence-description confusion: a Method, plan, log, ticket or carrier is treated as the dated Work occurrence, leaving the actual occurrence and the basis required by the receiving claim unresolved.

A.3:4 - Forces

ForceTension
Identity vs behaviourKeep holon identity stable while roles/behaviours change.
Simplicity vs precisionOne process box can hide the distinctions among MethodDescription, Method and Work that a receiving use needs.
Universality vs idiomsAccounts of physical and epistemic Work need the common distinctions while preserving domain terms.
Reusable semantics vs dated occurrenceKeep Method, any MethodDescription edition, and Work distinct; make each relied-on connection explicit.
Evidence vs mereologyProvenance edges (EPV‑DAG) must never turn into part‑whole edges.

A.3:5 - Solution — The Transformer Quartet

For work enactment, A.3 distinguishes four objects: the performer System with its needed assignment basis, a MethodDescription edition when the use relies on one, the enacted Method, and the dated Work. Another independently grounded actor-side claim uses only the participants and relations required by its direct governing pattern. These distinctions qualify that acting-side claim; they are not occurrence conditions for every U.Transformation.

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

  1. 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.

  2. 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.

  3. 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.

  4. 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 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.
  • 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.

A.3:6 - Illustrative scenarios (substrate‑neutral)

A.3:6.1 - Physical system — Cooling loop

The world-side occurrence run-2025-08-08-T14:03 is independently admitted under U.Work through A.13/A.15.1 with PumpUnit#3 as performer and an actual enactsMethod relation to CirculateCoolingFluid@CoolingLoop. If the receiving use also needs attribution under the same U.SystemRoleAssignment occurrence, cite its obtaining F.6 performedUnderAssignment relation. Cite centrifugal_pump_curve.ld when this Work claim relies on its content. Treat its claim-bearing episteme as a U.MethodDescription only if A.3.2 establishes that its EntityOfConcern is CirculateCoolingFluid@CoolingLoop and that it makes a substantive claim about that Method as a way of doing. A separately obtaining resource-use relation connects the Work individual to the 3.6 kWh use; the measured ΔT=6 K and any actual fluid change remain separately governed measurement, transformation, and work-to-change claims.

A.3:6.2 - Epistemic change — Proof revision

The world-side occurrence lemma-42-check-2025-08-08 is independently admitted under U.Work through A.13/A.15.1 with LeanServer as performer and an actual enactsMethod relation to CheckAndReviseLeanProof@Lean. If the receiving use also needs attribution under the same U.SystemRoleAssignment occurrence, cite its obtaining F.6 performedUnderAssignment relation. proof_tactic.lean, any exact MethodDescription edition, the theorem episteme, carrier or episteme change, and the check log remain separately governed. An exact evidence-use relation may use the log to support a receiving claim; production by the performer does not itself confer evidence status or support.

A.3:6.3 - Reflexive maintenance — “calibrates itself”

When the calibration controller and sensor suite are independently grounded as distinct internal positions, split into Regulator (acting position) and Regulated (changed position), cite the exact interaction and independently obtaining relations involving any claimed Work occurrence, and cite the evidence-use relation supporting each relied-on claim.

A.3:6.4 - Joint or non-separable physical participation

A tide-related change of seawater can be one independently grounded A.3.4 transformation. Moon–Earth–ocean gravitational coupling, joint dynamics, and causal participation are recovered through their direct relation, dynamics, interaction, and causality owners. Coupling or a minimal physical-agentivity reading alone does not make the Moon a holder of TransformerRole@Context and does not create U.Work. Use C.26 only if a residual probe-, frame-, order-, incompatible-read-, or no-faithful-export lens issue remains.

A.3:6.5 - Reflexive work — scratching oneself

For a work-on-oneself claim, the containing holon is the person, the acting position is the grounded neural-control/right-arm subsystem, and the changed position is the grounded left-hand tissue or state. The exact U.SystemRoleAssignment, applicable method, dated work, work-to-change facts, and A.3.4 occurrence remain separate. Selecting these already grounded subholons uses A.14/C.13; it is not an MHT unless the person as a whole is reidentified under B.2.

A.3:7 - Conformance Checklist (normative)

CC‑A3‑0 - Performer basis and conditional assignment-bound attribution. For actual Work, each performer System MUST have the A.13 core, including classification under a local agential system-role kind and an obtaining assignment of that kind. A.15.1 admits the Work independently. The assignment’s declared U.SystemRoleAssignment species determines its predicate, holder, assigned-kind domain, any additional participants, and occurrence identity under A.2.1. State the currently known extent separately as assignmentInterval when needed; taxonomy, scheme, and context references are not generic participants.

If the receiving use also claims under which assignment the Work was performed, that attribution MUST pass F.6 performedUnderAssignment(W, RA) with the same assignment; an unresolved attribution leaves the admitted Work intact. A conforming assertion or description designates the Work and the basis its claim uses. For a non-Work actor-side claim, use its direct governor and introduce a work-facing assignment only when that relation is independently current.

CC‑A3‑1 - Acting-side distinction. When an asymmetric actor-side claim is current, its directly governed acting and changed positions MUST be distinct for that claim. When performed Work is current, recover each actual performer and its obtaining assignment through A.13; add F.6 attribution through that same assignment only when the receiving use needs it. In reflexive Work the acting and changed positions MAY be grounded subholons or positions inside one containing holon; the containing holon need not be reidentified. Do not force this split or a role assignment onto a natural, joint, relational, non-separable, or formal change merely to satisfy A.3. This preserves acting-side externalization without fictive actors.

CC‑A3‑2 - Method-description-Work-assertion separation. U.MethodDescription is a description episteme, U.Method is a run-independent semantic way of doing, and a Work individual admitted under U.Work is a world-side dated performed occurrence. A Work assertion or description is another U.Episteme; a log, ticket, or carrier may express or support it but is not the occurrence. Neither Method nor MethodDescription is a run-time occurrence. A changed description edition and performed Work are separate facts, and a claim that Work occurred remains admissible without a MethodDescription reference when no receiving use relies on an exact description edition.

CC‑A3‑3 - Boundary-crossing evidence. A conforming actor-side or work-to-change assertion MUST designate the exact direct participation, interaction, flow, causality, or work-to-change facts on which it relies; an A.3.4 occurrence alone supplies none of them. Conservation-class effects, when claimed, MUST satisfy the applicable B-invariants.

CC‑A3‑4 - Method and conditional description traceability. Every Work individual admitted under U.Work stands in an exact actual enactsMethod relation to the U.Method it enacts; the assertion or description used by a receiving claim MUST designate both sides and that relation. Cite an exact U.MethodDescription edition only when the receiving claim depends on that edition to identify, constrain, or justify the Method. If actual enactment departs from a cited description, state the description-selection, override, exception, or deviation claim under its direct owner and apply the Work continuity policy to the actual occurrence facts. Absence of a description reliance claim is not silent drift.

CC‑A3‑5 - Episteme as object-under-change. When Work on an episteme or its carrier is claimed, the performer is a System; episteme identity, carrier continuity, edition succession, publication, and any actual carrier change remain under their direct owners. Do not infer a performer from the episteme change itself. See C.2.1, E.24.PUB, A.14’s mereology firewalls, and direct epistemic aggregation owners when current.

CC‑A3‑6 - Units and measures for performed resource use. Every performed resource-use fact relied on for a claim about Work MUST state its measure and units. A percentage that enters a resource aggregation must be grounded in the exact PortionOf measure needed by that use. Totals, allocation, overlap handling, deduplication, and optional Gamma_work notation belong to a separately recovered B.1.6 aggregation, not to Work identity.

CC‑A3‑7 - Authority, justification, and provenance boundary. Authority, justification and provenance are not generic constitutive fields of a SystemRoleAssignment or Work occurrence. When a receiving use relies on one of them, identify the exact episteme and direct authority, justification, source, evidence or provenance relation and connect it to the assignment occurrence, Work individual, assertion or description. The assignment must obtain under its species predicate; the Work occurrence must meet the A.15.1 admission conditions.

CC‑A3‑8 - Agentic policy, planning, Work, and outcome separation. An agentic case does not license a generic pipeline from policy, through a planned action, to an action. Recover each exact policy, objective, selection or decision, WorkPlan, SystemRoleAssignment, dated Work, actual change, and outcome claim under its direct owner when that claim is current. A policy does not create a plan or Work; a plan does not prove Work; and Work does not prove an outcome.

CC‑A3‑9 - Local interpretation and exact crossings. When interpretation depends on a taxonomy episteme or effective ReferenceScheme, identify that reference in the assertion about the SystemRoleAssignment occurrence. Test compatibility through the exact rule current for that assignment use. Similar labels across localities establish neither equivalence nor conflict. When a receiving use needs exact local-sense correspondence, use F.9 only for the exact SenseCell correspondence and its admitted use; local system-role-kind, policy, criterion, verdict, or other mappings retain their direct owners.

CC‑A3‑10 - Use-driven aggregation boundary. When a receiving use needs order-sensitive Method composition, recover B.1.5 and optional Gamma_method; when it needs a temporal aggregate over exact Work intervals, recover B.1.4 and optional Gamma_time; when it needs a resource ledger, recover B.1.6 and optional Gamma_work. A system-boundary or epistemic aggregation likewise uses its exact direct owner. Each aggregation has its own EntityOfConcern, policy, evidence, and admissible use; none is a universal field or identity condition of MethodDescription, SystemRoleAssignment, or Work.

A.3:8 - Consequences

Benefits

  • Recoverable Work basis. A conforming assertion about performed Work designates the world-side occurrence, each performer System’s A.13 basis, enacted Method, and any obtaining F.6 attribution or neighboring description, capability, work-to-change, evidence, or aggregation claim on which the current use relies; actual-change identity remains separately inspectable under A.3.4.
  • Keep system parts distinct from method and edition claims. A Method, local system-role kind, or description does not become a part of a System by describing its operation; edition succession is also distinct from a part-whole relation. Method-to-Method parts remain governed by A.3.1 and B.1.5.
  • Composable analytics without hidden ownership. Exact Work intervals and performed resource-use facts can feed separately recovered B.1.4 or B.1.6 aggregations; the selected policy, evidence, and result remain inspectable at that direct owner.
  • Local plurality without whole-context bridges. Exact role taxonomies, ReferenceSchemes, compatibility rules, and use-specific mappings let local practices differ without treating a shared label or one bridge as wholesale equivalence.

Trade‑offs

  • More explicit separation when reliance needs it. Start with the smallest grounded performer-assignment, Method, and Work claims; add MethodDescription, capability, policy, plan, change, evidence, and aggregation relations only when a named use depends on them.
  • Discipline for reflexive work. Modellers must ground distinct acting and changed positions before using a controller–plant or other reflexive split; this adds only the relation claims the use needs and avoids an ungrounded performer or arbitrary decomposition.

A.3:9 - Rationale and Source Comparisons

Constructor theory. Constructor theory informs the distinction between possible and impossible tasks and the conditions on substrates and constructors. A.3 adopts that modal discipline without equating a constructor-theory constructor with an FPF performer or TransformerRole holder. In the performed-Work branch, an independently grounded System may be the holder of an exact SystemRoleAssignment, and a Work occurrence performed under that assignment may enact an exact Method; natural, spontaneous, joint, formal, or otherwise non-agentive transformation remains possible without that actor-side factorization. A task description qualifies as a MethodDescription only under A.3.2; it is neither the constructor nor the Work. (Royal Society Publishing, arXiv, Constructor Theory)

Active inference & free‑energy mechanics (2017→). When an agentic claim is current, active-inference and free-energy work motivates keeping policy, objective, observation, selection, planning, performed Work, and evidence distinctions visible under their direct owners. It does not supply a universal action pipeline, make agentivity a Work occurrence, or make one policy, plan, or posterior prove another. (MIT Press Direct, PubMed, arXiv)

Provenance and FAIR packaging (2016→). FAIR, RO-Crate, OpenLineage, and ML Metadata motivate exact, machine-actionable provenance and evidence links when a receiving use relies on lineage, editions, runs, or jobs. A.3 therefore preserves those links as separately governed relations rather than making {authority, justification, provenance} constitutive fields of SystemRoleAssignment or Work. (Nature, researchobject.org, SAGE Journals, openlineage.io, GitHub, arXiv)

The source contributions above inform A.3’s design. Its performer basis comes from A.13, Work admission from A.15.1, Method and MethodDescription distinctions from A.3.1/A.3.2, and conditional assignment-bound attribution from F.6. A.3.4 separately governs actual change, including cases without a performer.

A.3:10 - Relations

A.7 Strict Distinction. A.3 keeps the target EntityOfConcern, MethodDescription, Method, local system-role kind, SystemRoleAssignment occurrence, dated Work occurrence, Work assertion or description, actual change, log or observation, and evidence relation distinct. A recipe or log is not part of the target merely by describing or recording work on it, and a record about Work is not the Work occurrence.

A.12 Acting-Side Externalization and Reflexive Split: Identify Who Acts on What. A.3’s CC-A3-1 uses A.12 only when an actor-side or reflexive-work claim is current. The split keeps grounded acting and changed positions distinct for that claim; it neither invents an actor for non-separable change nor turns ordinary descent to already grounded parts into an MHT.

A.13 Agential Role. When an agency claim is current, A.13 governs agenthood and the domain profile, while A.17, A.18, A.19, C.16, and A.10 govern its measurement and evidence as applicable. A.3 keeps identity, role assignment, method, plan, work, transformation, and evidence separate. Scale-free or minimal physical agentivity, observerhood, self-evidencing, or causal participation does not by itself establish an obtaining U.SystemRoleAssignment, TransformerRole@Context, method enactment, or dated Work.

A.3.4 Actual Bounded Change Under Conditions. A.3.4 independently identifies one actual bounded transformation from the changed referent and subject-side occurrence facts. A.3 opens only when an actor-side enactment claim is additionally grounded. Natural, spontaneous, formal, relational, and joint-dynamics changes therefore need no fictive performer.

A.3.3, direct relation, interaction, and causality owners. These patterns govern claims about participation and causal structure. Use an asymmetric actor-target factorization only when that result is independently grounded; retain a joint or non-separable account otherwise. C.26 may test a residual probe, frame, order, incompatible-read, or no-faithful-export lens issue.

A.15 Role-Method-Work Alignment. A.3 relies on A.15’s separation of local system-role kind, System-classification claim, exact world-side SystemRoleAssignment occurrence, run-independent Method, conditional MethodDescription reliance, intended WorkPlan episteme, world-side dated Work occurrence, and any assertion, description, log, or evidence about that occurrence. The Work stands in an actual enactsMethod relation; use F.6 with the same A.13 assignment only when precise assignment-bound attribution is claimed. A MethodDescription may describe the Method; neither the description, plan, nor record proves that Work or actual change occurred.

A.14 Mereology. A.3 consumes A.14/C.13 only for independently grounded part or structure relations and forbids inferring System-part membership from a local system-role kind or recipe. Selecting grounded internal positions for a reflexive claim is not an MHT; B.2 opens only when the containing whole is reidentified.

B-cluster (Gamma sections). A.3 supplies grounded actor-side facts and exact Work occurrences that receiving assertions may designate. B.1.5 governs order-sensitive Method composition and optional Gamma_method; B.1.4 governs a selected temporal aggregation and optional Gamma_time; B.1.6 governs a selected Work-resource aggregation and optional Gamma_work. System-boundary and epistemic aggregations use their exact direct patterns when current. Every such result has its own EntityOfConcern, policy, evidence, and admissible use rather than becoming a field or identity condition of MethodDescription, SystemRoleAssignment, or Work.

A.3:End

Referenced in the corpus

48 literal mentions in other sections. Read their context to establish the relation.