A.12 - Acting-Side Externalization and Reflexive Split: Identify Who Acts on What
Type: Part A architectural ontology pattern Status: Stable Normativity: Normative unless a section is explicitly informative
A.12:0 - Use This When
Use this pattern when self-action or passive wording hides the acting participant or the subject claimed to change, or when interaction is mistaken for parthood.
Typical moments:
- “the robot calibrates itself”;
- “the model updates itself”;
- “the document refreshes its own cross-references”;
- “the organization corrected itself”;
- “the system verifies that its own change succeeded”;
- “the lathe makes the workpiece, therefore the workpiece is part of the lathe during manufacturing”.
First useful move. Name the proposed acting participant and the subject claimed to change, then state the relation between them that matters to your question. For the robot below, the calibration controller acts on the sensor suite. Keep ordinary wording when those participants and their relation are already clear. Use §4.1 when their identities or a System, change, Work or evidence claim need the precise account.
What goes wrong if missed. A controller and controlled part can collapse into one object, an automated publication update can hide its performer, and the performer’s output can be mistaken for sufficient evidence of success. Changing another holon can also be mistaken for containing it.
What this buys. You can locate the acting participant, trace the claimed change, and ask separately what establishes the change or its success. When both participants are distinct parts of one holon, Reflexive Split exposes their internal relation.
Not this pattern when.
- If the current question is whether a bounded change occurred, use
A.3.4. - If the current question is whether work was performed or succeeded, use
A.15andA.15.1. - If the current question is an assignment occurrence, use
A.2.1; if it is a relation among exact local system-role kinds, useA.2.7. For another participation relation, use the pattern that defines that relation. - If the current question is evidence independence or source use, use
A.10and the evidence-use or source-use patterns. - If the current question is part-whole admission, use
A.1,A.14, andC.13.
A.12:1 - Problem Frame
Separate the acting and changed participants before deciding whether the claimed change, Work or evidence obtains. Their participation, System recognition and part-whole relations are separate questions. A self-action sentence may describe internal regulation; §4.2 gives the conditions for that reading.
A.12:2 - Problem
- Self-action hides the acting side. “The system changed itself” leaves unclear who acts, what changes, and which participation relation is asserted.
- Transformation and work collapse. A bounded transformation, a method, a work occurrence, and evidence of success are treated as the same claim.
- Epistemes become agents. An episteme is treated as the acting participant because its carrier or an executing System is described as updating, deciding or verifying.
- Reflexive systems become single blocks. A regulator and regulated part are hidden inside one block, so failure analysis and architecture work lose the internal relation that mattered.
- Transformation becomes containment. A system changing another holon is treated as that holon’s containing whole.
- Evidence becomes self-certifying. The acting system’s own output is treated as sufficient evidence for the success or safety of its work.
A.12:3 - Forces
| Force | Tension |
|---|---|
| Causal clarity vs convenient speech | Everyday speech compresses “self-repair” and “automatic update”; engineering use needs the acting side and changed object. |
| Internal regulation vs object collapse | A larger holon may contain both regulator and regulated parts; that does not make the regulator and regulated position identical for the current claim. |
| Automation vs accountability | Automated action may require distinct System, role, Method, Work and evidence claims; include each only when the explanation needs it and its basis holds. |
| Episteme use vs episteme agency | A carrier update, another episteme edition and a changed publication relation need different identity tests (§4.3). A Work performer or U.SystemRoleAssignment holder must be an admitted U.System. |
| Boundary crossing vs parthood | When a boundary-crossing relation independently satisfies the predicate, applicability, and identity rules that define it, it does not thereby make the acting system a part of the changed holon or the larger whole containing it. Without those rules, keep the crossing claim open rather than inferring either crossing or parthood. |
A.12:4 - Solution
Separate the acting participant from the subject claimed to change. Add the precise claims needed to explain the case.
A.12:4.1 - Acting-Side Externalization
Either of the two optional A.12 outlines can organize the participants and independently governed claims of a precise change-bearing account. Their fields are prompts for the explanation. Fill a neighboring-claim position only when that claim is needed and its own admission conditions hold:
ActingSideExternalization@Context:
changedSubjectRef: one exact continuing referent identified by the identity rule that defines that referent
actingEntityRef: exact U.Entity proposed for the acting side
actingSystemRef?: U.System, fill only after actingEntityRef satisfies the complete A.1 U.System criterion
actingSystemA13CoreRef?: A.13 performer basis, required when an actual Work performer is claimed
a1RecognitionDispositionOrBlockerRef?: required when this account needs an A.1 recognition result and actingSystemRef is unfilled
actingSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment, only when one exact obtaining work-facing assignment is current
actingSideParticipationRef?: one exact obtaining relation occurrence satisfying the predicate and participant meanings that define the participation, causal, or interaction claim
transformationRef?: U.Transformation, fill only when A.3.4 identifies a bounded change of changedSubjectRef
methodRef?
methodDescriptionRef?
workPlanRef?
workOccurrenceRef?
holonBoundaryCrossingRelationRef?: one exact obtaining relation occurrence satisfying the predicate, applicability, and identity rules that define the crossing relation
evidenceRelationRefs?
Identify actingEntityRef and changedSubjectRef as distinct participants in the claim. changedSubjectRef is a question-local position, not a U-kind or union ValueKind: its value retains its independently admitted kind and identity rule. A presentation carrier does not become a U.Holon by filling it. Fill transformationRef only when A.3.4 establishes a bounded change of that same continuing referent.
Use the complete A.1 criterion or an applicable established A.1 result before classifying the acting entity as a U.System. When this account needs recognition and it is not established, retain the entity and its recognized | rejected | unknown disposition or blocker. Leave actingSystemRef unfilled until recognition is established; once recognized, it names the same entity under U.System. Tight coupling or membership in a larger holon does not merge the acting and changed positions.
In these two A.12 outlines, @Context denotes a short case label: the examples use RobotInternals, RobotCalibration, DocumentBuild and Machining. Each stated claim keeps its own participants and defining or testing rule. Make the grounds needed by the present use recoverable with that claim, through an existing reference or an ordinary explanation. Neither A.12 outline has a generic context, scope or qualifier position. Ask what the proposed qualifier changes:
- If claim content, EntityOfConcern or the effective reference scheme changes, C.2.1 identifies another episteme.
- If the question is whether a
U.ContextSlicebelongs to a claim’s set-valued applicability boundary, use A.2.6’sU.ClaimScopeand membership evaluation. - Select A.1.1’s
BoundedModelUseStructureonly when the decision depends jointly on one model edition’s applicability, actual use in assigned Work, fixed-content expression coherence, applied constraints and complete selection-use frame.
For another condition, state the condition or relation and apply its defining or testing rule. A pattern citation is usually enough to locate that rule. Recover its identity-bearing defining or constraining ClaimGraph only when the graph’s identity changes interpretation, comparison, migration, conflict, publication or reuse. A claim phrase or nearby participant does not fill an A.12 field unless it satisfies that field’s meaning.
Use:
A.3.4whentransformationRefbecomes current;A.3.1for Method identity,A.3.2for MethodDescription admission,A.15.2for a WorkPlan, andA.15.1for a dated Work claim;A.15connects these distinct claims, and a Work occurrence follows the performer/admission/attribution order below;A.2.1when an exact assignment occurrence becomes current, andA.2.7only when a relation among exact local system-role kinds becomes current;A.10when evidence or source independence becomes current;A.1,A.14, andC.13when holon identity, part-whole, or constructive grounding becomes current.
For a dated Work claim, first establish each actual performer’s A.13 core: an admitted System, a local agential system-role kind and criterion it satisfies, an obtaining assignment, and the scope, situation and window the use needs, supported by evidence. Add an agency-characteristic profile only for a consumed Grade/autonomy/profile claim, a characteristic-dependent local criterion, or an assurance use that requires it.
Then admit the occurrence independently under A.15.1 from its performance history, enacted Method, temporal extent and obtaining containing-System relation.
Only if precise assignment-bound attribution is also claimed does F.6 relate that admitted Work to the same obtaining assignment. A Work-only account stops after admission.
When the receiving question also asks how that Work changed the subject, use A.3.4:4.2.4. Recover the action performed within the Work, the property changed and the subject grounds connecting them. A.6.RCD permits an ordinary compound claim when its base facts and constructor semantics suffice.
A physical account may need the interacting participants, an applicable response law and preparation under A.3.3.TR; a boundary-exchange question additionally selects the quantity, boundary and interval under C.29.BB. Develop only the connection the receiving question consumes. Section 5.3 shows a local contribution claim and the separate question of a durable crossing reference.
A.12:4.2 - Reflexive Split
Use Reflexive Split when the acting and changed participants are two distinct entity parts or subsystems of one containing holon, with an independently obtaining part relation for each. Establish those premises before using this frame; the word “self-” alone does not establish them. If the source supports another reading, keep that acting-side or relation account and leave any unsupported internal-parts claim open.
ReflexiveSplit@Context:
containingHolonRef: exact U.Holon
actingPartOrSubsystemRef: exact U.Entity
changedPartOrSubsystemRef: exact U.Entity
holonDelimitationRelationRefs?: exact obtaining parthood relations to containingHolonRef
holonBoundaryCrossingRelationRef?: one exact obtaining relation satisfying the predicate, applicability, and identity rules that define the crossing relation
actingSystemRoleAssignmentRef?: U.RelationRef constrained to U.SystemRoleAssignment, only when one exact obtaining work-facing assignment is current
transformationRef?
methodRef?
workOccurrenceRef?
evidenceRelationRefs?
ReflexiveSplit@Context carries no system-recognition position. Its two part-or-subsystem fields identify exact entities, not phases, assignments, relation occurrences, or generic structures. Each filled entity position needs an independently obtaining parthood or subsystem relation to containingHolonRef under A.14 and the direct part-relation specialization.
When the acting-position entity must also be evaluated as a system, state its A.1 recognition result or blocker alongside the part relations. An optional companion ActingSideExternalization@Context can carry that result or blocker: its actingEntityRef identifies that U.Entity; its disposition or blocker remains explicit before recognition; and its optional actingSystemRef may identify the same entity only after A.1 recognition. Do not insert actingSystemRef or an A.1 disposition into ReflexiveSplit@Context.
A temporal phase, system-role assignment, parthood occurrence, software-module description, or selected structure remains a separate object under the identity and relation rules that define it. A software component fills a part-or-subsystem field only when it is itself the exact entity and its direct part relation obtains. If a source supplies only unlike positions such as phases or assignments, state those direct relations and do not force them into this frame.
The minimal rule is:
actingPartOrSubsystemRef != changedPartOrSubsystemRef
for the current change-bearing claim.
For controlled self-change, this split supplies the internal acting and changed participants. Connect their action to the rule or intended result that selects the intervention, its effect on later operation and the consequences used to revise it. C.43:4.1.2 develops that account.
An updater installing a poor setting can satisfy Reflexive Split; whether the update is suitably controlled and improves the result are further questions. If only roles or successive states are established, retain the supported acting-side account without inventing internal entity parts.
A.12:4.3 - Episteme And Publication Cases
If a source says “the document updates itself”, identify the acting participant and decide which changed-object reading the claim needs:
- Carrier-change reading. One exact publication file, representation carrier, or source-record carrier continues through a separately grounded change under its direct carrier identity rule. It may fill
changedSubjectRefas that exact carrier, not as aU.Holonmerely by carrier form; use A.3.4 only when the bounded change of that same referent is independently admitted. - Episteme-edition reading. Changed claim content identifies another episteme, with the predecessor, successor, and exact edition relation governed separately. Do not call it transformation of one unchanged episteme.
- Relation-occurrence reading. One exact episteme-related direct relation—for example constitution, empirical grounding, edition, reference, or publication use—obtains when its actual participants satisfy its direct predicate. Its direct identity and change rules determine whether that occurrence continues, ceases, or is replaced. Use C.2.1 for episteme identity and edition distinctions and E.17 or E.24.PUB for publication use. The relation’s obtaining or replacement does not by itself establish a bounded change of one continuing referent. If a change is claimed, identify its continuing subject under its own identity rule and establish the A.3.4 facts before claiming that transformation.
Choose the reading before filling a singular field; carriers, epistemes and relation occurrences are not interchangeable values. Call the acting entity a U.System only after A.1 recognition, and fill a work-facing assignment only when that U.SystemRoleAssignment obtains. Use C.2.1 for episteme identity, E.24.PUB for publication relations and publication-form or carrier identity, and E.17 when the account needs a reader-facing publication form.
A.12:4.4 - No Containing-Whole Inference From Interaction
Treat the interaction and part-whole claims separately. A system changing another holon does not thereby become its part or the larger whole containing it.
For a part-whole claim, use A.14 or the rule defining the part-whole predicate to test parthood independently of the interaction claim.
A.12:4.5 - No Self-Evidence Shortcut
A producer’s output does not automatically establish a claim of success, safety, adequacy or authorization. State the claim you need to support, then use A.10 to identify its evidence and provenance. The producer’s output may contribute when that evidence relation supports the claim.
Use B.3 when a separate assurance conclusion is requested. Introduce an observer, measurement setup or independent source only when its contribution matters to the evidence account.
A.12:5 - Archetypal Grounding (Worked Cases)
A.12:5.1 - Robot Self-Calibration
Source wording: “the robot calibrates itself.”
CalibrationController-R17 acts on SensorSuite-R17; both are parts of Robot-R17. The precise account below takes their A.1 recognition and two independently obtaining A.14 ComponentOf relations as premises, then distinguishes performer admission, Work, attribution and change:
ReflexiveSplit@RobotInternals:
containingHolonRef: Robot-R17
actingPartOrSubsystemRef: CalibrationController-R17
changedPartOrSubsystemRef: SensorSuite-R17
holonDelimitationRelationRefs: ComponentOf(CalibrationController-R17, Robot-R17); ComponentOf(SensorSuite-R17, Robot-R17), each independently obtaining under A.14
ActingSideExternalization@RobotCalibration:
changedSubjectRef: SensorSuite-R17, the exact continuing U.Holon identified under A.1 for this claim
actingEntityRef: CalibrationController-R17
actingSystemRef: CalibrationController-R17, the same entity after it satisfies the complete A.1 U.System criterion
actingSystemA13CoreRef: A.13 core for CalibrationController-R17 as precise performer in this action, including CalibrationAssignment-R17 as the same obtaining assignment
actingSystemRoleAssignmentRef: CalibrationAssignment-R17, one obtaining work-facing U.SystemRoleAssignment held by CalibrationController-R17
transformationRef: SensorCalibrationTransformation-R17, independently admitted under A.3.4 as a bounded change of SensorSuite-R17
workOccurrenceRef: CalibrationWork-R17, independently admitted under A.15.1 from its performance history, enacted Method, temporal extent, and containing-System relation; because this case claims exact assignment-bound attribution, F.6 afterward relates the already admitted Work to CalibrationAssignment-R17
Robot-R17 remains the containing holon. CalibrationWork-R17 and SensorCalibrationTransformation-R17 are separate admitted objects. The A.13 core includes CalibrationAssignment-R17; after independent A.15.1 Work admission, this case’s additional F.6 attribution uses that same obtaining assignment. The references name the admissions used by the example; each admission still needs its stated basis.
A.12:5.2 - Document Cross-Reference Update
Source wording: “the document updates its cross-references.”
BuildRunner-4 updates the cross-references in PublicationFile-17. BuildScriptEpisteme-9 has the already admitted CrossReferenceUpdateMethod-3 as its exact EntityOfConcern and describes how that Method updates links, satisfying A.3.2. The script is its MethodDescription; BuildRunner-4 is the acting participant. This case follows the publication carrier through the update.
The bounded case-local continuity rule treats PublicationFile-17 as the same carrier only if the file object opened for the build still exists when the build closes, every write asserted to update PublicationFile-17 targets that same open object, and the build neither deletes and recreates that file, atomically replaces it, nor substitutes another carrier. E.24.PUB states which independently identified expression the carrier’s actual state yields; it does not supply this case-local identity rule.
If a continuity fact fails, identify the replacement carrier rather than asserting a transformation of one continuing file. If carrier identity is unresolved, stop before asserting that change. A changed C.2.1 episteme discriminator selects the separate episteme-edition reading.
ActingSideExternalization@DocumentBuild:
changedSubjectRef: PublicationFile-17, the exact continuing digital U.Entity reidentified by the bounded case-local continuity rule stated above
actingEntityRef: BuildRunner-4
actingSystemRef: BuildRunner-4, the same entity after it satisfies the complete A.1 U.System criterion
actingSystemA13CoreRef: A.13 core for BuildRunner-4 as precise performer in this action, including CrossReferenceUpdateAssignment-27 as the same obtaining assignment
methodRef: CrossReferenceUpdateMethod-3, admitted under A.3.1
methodDescriptionRef: BuildScriptEpisteme-9, admitted under A.3.2 as a description of CrossReferenceUpdateMethod-3
actingSystemRoleAssignmentRef: CrossReferenceUpdateAssignment-27, one obtaining work-facing U.SystemRoleAssignment held by BuildRunner-4
transformationRef: PublicationCarrierChange-27, independently admitted under A.3.4 from the build boundary, the before/during/after carrier-state facts below, and the bounded case-local continuity rule
workOccurrenceRef: DocumentBuildWork-27, independently admitted under A.15.1 from its performance history, enacted CrossReferenceUpdateMethod-3, temporal extent, and containing-System relation; because this case claims exact assignment-bound attribution, F.6 afterward relates the already admitted Work to CrossReferenceUpdateAssignment-27
A.10 governs source recovery and bounded reliance on the build log for the following carrier-history claims; A.7 keeps the carrier distinct from the episteme it presents.
Before the boundary, PublicationExpressionBearingRelation(PublicationFile-17, CrossReferenceExpression-26) obtains. CrossReferenceExpression-26 is the independently identified ordered text containing the stale link addresses. During the boundary, the same open file object remains in place while its link-address state is rewritten; the build log records no replacement event. After the boundary, PublicationExpressionBearingRelation(PublicationFile-17, CrossReferenceExpression-27) obtains; the changed address strings identify another ordered-text expression.
Both expressions can conform to the same reusable CrossReferencePublicationForm, so PublicationFormBearingRelation(PublicationFile-17, CrossReferencePublicationForm) can remain continuously true through the update when a conforming expression remains recoverable.
Those facts, the build-open/build-close boundary, and the case-local continuity rule ground PublicationCarrierChange-27 under A.3.4. They do not decide episteme identity: if claim content, EntityOfConcern, or the effective reference scheme changed, C.2.1 identifies another episteme and any historical continuation needs a separately governed edition relation.
An episteme-edition case instead identifies predecessor and successor epistemes plus their edition relation. A reference-relation case identifies one relation occurrence and its defining rule. Keep those accounts separate from the carrier-change case; they are not alternative values for its singular fields.
A.12:5.3 - Lathe And Workpiece
Source wording: “the lathe makes the workpiece, so the workpiece belongs to the lathe during manufacturing.”
Lathe-3 is the acting participant; Workpiece-8 is the changed subject. That distinction does not establish that Workpiece-8 is part of Lathe-3. Test any such parthood claim independently under A.14 or its defining part-whole rule. The precise account separates the admitted Work and change:
ActingSideExternalization@Machining:
changedSubjectRef: Workpiece-8, the exact continuing U.Holon identified under A.1 for this claim
actingEntityRef: Lathe-3
actingSystemRef: Lathe-3, the same entity after it satisfies the complete A.1 U.System criterion
actingSystemA13CoreRef: A.13 core for Lathe-3 as precise performer in this action, including MachiningAssignment-8 as the same obtaining assignment
actingSystemRoleAssignmentRef: MachiningAssignment-8, one obtaining work-facing U.SystemRoleAssignment held by Lathe-3
transformationRef: MachiningTransformation-8, independently admitted under A.3.4 as a bounded change of Workpiece-8
workOccurrenceRef: MachiningWork-8, independently admitted under A.15.1 from its performance history, enacted Method, temporal extent, and containing-System relation; because this case claims exact assignment-bound attribution, F.6 afterward relates the already admitted Work to MachiningAssignment-8
MachiningWork-8 and MachiningTransformation-8 are independently identified. To explain their connection, extend this constructed case with the following supplied facts. During the named Work, Lathe-3 performed TurningApplication-8 with CuttingTool-3 on the continuing Workpiece-8. The operation history identifies the actual engaged cutting pass, its tool and workpiece bindings, and its start/end interval. The supplied material-removal account establishes that this pass removed the outer layer of the selected cylindrical surface, reducing its radius from 10 mm to 9.5 mm. Before/after measurements under the same dimensional reference conditions identify the corresponding diameter change from 20 mm to 19 mm as MachiningTransformation-8.
The useful result is the local assertion MachiningContribution-8: this Work included the actual cutting application whose material removal produced this diameter change. Under A.6.RCD disposition 2, its conjunction has these named base facts and their common workpiece and interval; it holds when all those facts hold for the same application and transformation. This supplies one C.2.1 compound claim.
If the history records only a commanded feed and actual engagement is unknown, the connecting claim has missing-information; the independently observed diameter change remains available. Selecting a different physical regime reopens the material-removal account that the connection consumes.
For an ordinary boundary explanation, select the tool-workpiece contact surface and interval. The contact force is the rate of the tool’s momentum transfer to the workpiece across that surface; C.29.BB locates that contribution in a momentum balance. Predicting the workpiece’s motion also needs the other consequential forces and applicable response conditions.
This explanatory claim does not supply an occurrence identity for holonBoundaryCrossingRelationRef. If a further use needs that exact reference, it still needs the crossing predicate, applicability and occurrence-identity rule; their absence is the A.6.RCD missing-governor for that reference. The local contribution and boundary explanation remain usable, and parthood keeps its separate A.14 test.
A.12:5.4 - Bias-Annotation
| Bias risk | Failure | Mitigation |
|---|---|---|
| Self-action convenience | “The system changed itself” hides the acting side and exact continuing changed subject. | Recover that changed subject by the identity rule that defines it, identify the acting-side entity, and then state each direct relation used by the claim. |
| Episteme agency | A document, model, report or source record is treated as acting. | Identify the acting entity; apply A.1 if Systemhood is claimed and §4.1’s admission order if Work is claimed. Keep C.2.1 episteme identity and E.17/E.24.PUB publication claims separate. |
| Containing-whole inference from interaction | A system that changes another holon is treated as that holon’s containing whole. | Test parthood independently under A.14 or C.13. §5.3 supplies a local contribution and boundary explanation while keeping a durable crossing-reference question separate. |
| Self-evidence shortcut | The acting system’s output is treated as sufficient evidence by default. | Apply §4.5’s claim-first evidence question; add B.3 only for an assurance conclusion. |
A.12:6 - Conformance Checklist
| Check | Requirement |
|---|---|
CC-A12-1 | A self-action or passive change account names the proposed acting participant and changed subject separately. When the precise frame is used, it identifies one exact continuing changedSubjectRef by that referent’s identity rule and requires actingEntityRef. Fill the optional actingSystemRef only after complete A.1 recognition; it identifies the same entity under U.System. When this account needs an A.1 recognition result and recognition is not established, keep the exact disposition or blocker. A filled transformationRef identifies an A.3.4 bounded change of that same changedSubjectRef. ReflexiveSplit@Context has no system-recognition position; state any needed A.1 recognition result or blocker separately, using a companion acting-side outline if useful. |
CC-A12-2 | A Reflexive Split case identifies distinct exact entity parts or subsystems inside one containing holon, and each position has its independently obtaining direct part relation. Temporal phases keep their phase identity rules; assignments use A.2.1; parthood uses A.14 or the exact part-relation rule; descriptions use C.2.1; selected structures use A.22. None fills an A.12 part position merely by being nearby. |
CC-A12-3 | An acting-side account uses the existing entities and relations it requires. A proposal for a new durable kind, including a transformer, boundary or interaction kind, needs the separate A.11 and E.24.UK admission process. |
CC-A12-4 | Bounded transformation claims require A.3.4; Method identity uses A.3.1, MethodDescription admission uses A.3.2, and a WorkPlan uses A.15.2. For a Work claim, establish each performer’s A.13 core before independent A.15.1 occurrence admission. The profile is conditional as stated in §4.1. |
CC-A12-5 | A system-role-assignment field is filled only by one exact obtaining work-facing U.SystemRoleAssignment; any claim that exact Work was performed under it uses F.6. System-role-kind relation claims require A.2.7. |
CC-A12-6 | Evidence and source-use claims use A.10’s direct relations; a separately current assurance conclusion uses B.3. |
CC-A12-7 | Episteme and publication cases do not assign agency to the episteme or publication form. |
CC-A12-8 | Changing another holon does not make it a part of the acting system. A filled singular crossing reference resolves one exact obtaining relation and its defining rule. If that rule is absent, leave the field unfilled and state the A.6.RCD missing-governor problem: the participants, needed sentence and receiving use. An ordinary explanation is enough; no additional record is required. Any containing-whole claim requires a separately admitted exact part-whole relation. |
A.12:7 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Symptom | Repair |
|---|---|---|
| Self-action literalism | “The system fixed itself” is accepted as one undivided claim. | Identify the acting and changed participants. Use ReflexiveSplit@Context only when §4.2’s two-entity-part and one-holon conditions hold. |
| Transformer kind inflation | The acting side is modeled as U.Transformer, as a special system kind, or as a provisional phrase placed in a U.System slot. | When System recognition is needed, retain the U.Entity and A.1 disposition or blocker until actingSystemRef can identify that same entity as a System. Add a local TransformerSystemRole classification only after A.2/C.3 establishes the system-role kind from its system-candidate domain, work-facing membership distinction, member/non-member boundary and continuity rule. Add participation or assignment only when that relation is claimed. |
| Boundary as object by word | Boundary or interaction words become durable root objects. | Identify the relation actually claimed: holon delimitation, boundary crossing, transformation, signaling, evidence, source use or publication use. Apply its defining or testing rule; §4.1 gives the condition for recovering an identity-bearing ClaimGraph. |
| Work success by action | Because a system acted, the work is treated as successful. | Use A.15.1 and evidence-use patterns for performed work and success. |
| Evidence by producer | The acting system’s own output is accepted as enough evidence. | Use §4.5 to identify which claim the output supports under A.10. |
| Manufacturing as containment | A tool or teacher changing another holon is treated as its containing whole. | Keep transformation and part-whole claims separate. |
A.12:8 - Consequences
Positive consequences:
- Self-action claims become inspectable without denying real internal regulation.
- Transformation, Work, assignment and evidence claims can be tested separately.
- An automated publication update identifies its performer separately from the script and changed content.
- Internal control loops and automated changes can be traced through their acting and changed participants.
- Interaction cases retain a separate parthood question.
Costs:
- When the acting/changed distinction matters, a compact “self-” sentence needs unpacking.
- Some diagrams need one more internal distinction between acting and changed positions.
- Supporting a success or safety claim can require evidence beyond the producer’s success message.
A.12:9 - Rationale
The acting/changed distinction helps trace an internal control loop, locate the performer of an automated update and separate a produced result from the evidence supporting a claim about it. Those questions can require different admissions; §4.1 gives their conditional routes.
A.12:10 - SoTA-Echoing
| Source or practice | Contribution to the distinction | FPF use |
|---|---|---|
| Control practice | Distinguishing controller, controlled object, feedback and plant structure helps inspect regulation. | Use Reflexive Split for internal regulation when the two-entity-part and one-holon conditions hold. |
| Constructor theory: introductory account | A substrate undergoes a specified possible task; a constructor retains the capacity to perform the task again. | Keep the changed substrate and proposed acting entity distinct. FPF separately requires A.1 for a System claim and A.3.4 for a bounded change claim. |
| Assurance and evidence practice | A produced result and evidence supporting a claim about it are different objects. | Use A.10 for the claim’s evidence and provenance; use B.3 when an assurance conclusion is requested. |
| Software and automation practice | An automated-update sentence can hide the distinction between the executing entity, script and changed object. | Identify the acting entity and apply A.1 before calling it a System. Apply A.3.2 before treating the script as a MethodDescription; keep change, Work and evidence claims separate. |
A.12:11 - Relations
- Builds on:
A.1for holon and System admission,A.2.1for a directly declared assignment species and its obtaining occurrence,A.2.7for relations among exact local system-role kinds, andA.3.4for bounded transformation. - Coordinates with:
A.10for evidence,A.14andC.13for part-whole claims;A.3.1,A.3.2,A.15.2,A.15.1and the integratingA.15for Method, MethodDescription, WorkPlan and Work;C.2.1andE.17for episteme and publication cases; andB.2.5for supervisor-subholon feedback. - Does not own: transformation occurrence evidence, work success, evidence independence, part-whole admission, MHT declaration, or the architecture of the larger holon.