A.3.4.P:4 - Solution
Restore the change situation in this order.
- Name the working concern. State what the text is trying to do: identify a change, describe a flow, choose a method, claim evidence, compare architectures, describe functioning, or use a publication.
- Test for one actual
U.Transformation. Recover the exact changed referent; exact temporal extent or exact ordering boundary in a declared formal substrate; boundary conditions; actual characteristic-state and obtaining direct-relation facts before, during, and after that boundary; and the continuity or reidentification rule that makes this one occurrence at the resolution required by the current use. Possible, intended, planned, modelled, predicted, or merely asserted change remains claim content and identifies no actual transformation until this subject-side basis obtains. - Separate an acting-System claim from influence. For performed Work, recover each precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 afterward only when precise assignment-bound attribution is current. Then recover separately the realization, causal, production, or other Work-to-change relation required by the current use. For a non-Work functional or physical actor-side claim, recover the System and the participant, operation-application, functioning, causal, or other direct actor-side relation supplied by its subject pattern; otherwise leave the actor claim unresolved. Each manufacturing organization, certification organization, design organization, toolchain, communication System, selected structure, Method, Method family, or other possible influence source first keeps its kind—a Method or Method family is not a holon by label—and receives only the architecture, Work, communication, constraint, or candidate-synthesis relation current for the claim.
- Test neighboring claims. Decide whether the wording points to a method, method description, mechanism, work plan, dated work, functioning relation, transformation-flow structure, mathematical description, dynamics episteme, temporal aspect, evidence, source, publication, gate, decision, assurance, result, refresh, reopen relation, or another direct subject claim.
- Use the exact governing relation for each neighboring value. A neighboring object keeps its own kind and governor; state its current relation to the transformation, changed referent, work, architecture candidate, or receiving use instead of placing it inside a transformation record.
- Rewrite only after kind and relation recovery. Keep ordinary wording when it is not FPF-governed, write quote-only source wording when no current use is admitted, or rewrite into the recovered FPF kind and exact relation named by value. Use F.19 for the resulting precise-plain-language rewrite.
- Name the reader’s next action. The repaired text must say what the reader may do now: use
A.3.4, useE.18, useC.29, use a method, work, mechanism, architecture, or evidence pattern, keep a quote-only cue, or block the stronger claim.
A.3.4.P:4.1 - TransformationWordingRepair note
Use this note only when wording is doing FPF-governed work and a receiving use needs its repair to remain inspectable. An ordinary wording repair requires no separate note.
TransformationWordingRepair:
EncounteredWording:
WorkingConcern:
RecoveredEntityOfConcern:
ActualTransformationDisposition:
TransformationOccurrenceBasis:
ActingSystemDisposition:
ArchitectureInfluenceDisposition:
NeighboringClaimAndExactRelation:
GoverningPattern:
RetainedUse:
StopOrReturnCondition:
BlockedOverread?:
RemainingReaderUse:
ActualTransformationDisposition is one of: actual bounded transformation recovered, not a transformation, not recovered, not current for this claim, quote-only source wording, or blocking missing value.
TransformationWordingRepair is a temporary wording-use restoration aid. Its retained output is the wording to keep or rewrite, the stop or return condition, and the next subject-pattern application. RetainedUse records which use of the encountered wording is kept; RemainingReaderUse names the practitioner’s next action with the recovered object or claim. BlockedOverread?, also named GroundedBlockedOverread?, is one optional explanatory value under F.19:4’s plausible-reader test. ActingSystemDisposition and ArchitectureInfluenceDisposition are temporary note fields, not FPF kinds or universal relations. An actual transformation occurrence is grounded only through its subject-side occurrence basis.
For a performed-Work actor claim, recover each precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 afterward only when precise assignment-bound attribution is current. Separately establish the realization, causal, production, or other Work-to-change relation required by the use. For a non-Work actor-side claim, use a participant, operation-application, functioning, causal, or other direct relation supplied by its subject pattern. If no such relation is recoverable, keep the actor claim unresolved. Every influence source retains its kind and only its current architecture, Work, communication, constraint, or candidate-synthesis relation; leave any unrecovered influence claim unresolved.
If an episteme asserts possible, intended, planned, modelled, predicted, or actual change, identify that episteme separately through C.2.1 when the assertion is current. Empirical grounding remains optional and, when current, uses its own exact relation; neither the assertion nor its grounding relation substitutes for the actual transformation basis. Use the governing subject pattern’s requirements when creating a project record, gate decision, work plan, or work occurrence.
A.3.4.P:4.2 - Subject pattern selection
| If recovery shows… | Use this subject pattern | Keep this boundary |
|---|---|---|
| one actual bounded change under conditions | A.3.4 | A source label identifies no transformation until the exact changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis are recoverable. |
| selected structure over transformation loci and adjacent governed values | E.18 | TransformationFlowStructure positions, relates, or locates those loci and values. Selection or common structure membership establishes neither an actual transformation occurrence nor transformation composition, parthood, or partlessness. |
| mathematical expression over a selected structure or formal object | E.18.2, C.29, A.6.0, or the direct formal pattern | Recover project-world work separately under A.15.1 when the current use also claims it. |
| semantic way of doing | A.3.1 | Recover the semantic way of doing under A.3.1; identify dated work, mechanism, evidence, or transformation claims separately when current. |
| episteme describing a way of doing | A.3.2 | For example, code, a protocol, a solver model, a proof script, a process model, or a diagram may describe a method. |
| law-governed operation algebra, laws, admissibility predicates, transport, audit, or mechanism-governing-definition assignment | A.6.1 and E.20 | Recover the mechanism’s defining content under A.6.1 and E.20. |
| planned or dated work | A.15.2 or A.15.1 | Identify the plan or dated occurrence under its governing pattern; recover any Method, MethodDescription, transformation-flow structure, or evidence claim separately. |
| pattern-use recommendation, work-entry readiness, language-state move, architecture candidate use, or call-planning next action | E.10.MOVE first, then E.11.PUR, A.15.5, A.16, C.30, C.24, or the subject pattern | Move-like wording is not transformation wording unless a bounded U.Transformation or selected TransformationFlowStructure is actually current. |
| function-like wording inside a change situation | A.3.4.P only to distinguish the actual transformation, selected TransformationFlowStructure, a System claimed to act under an exact actor-side relation, a differently typed influence source under its exact relation, boundary binding, or FunctioningRef?; use A.6.F for detailed function-kind discrimination | For an actual-transformation claim, recover its occurrence basis; for an actor claim, use the performed-Work or non-Work basis in 4.4. |
| state-space and transition-law episteme | A.3.3 | Dynamics can model possible or claimed change; recover any claimed actual occurrence independently under A.3.4. |
| time window, cadence, duration, latency, freshness, currentness, trajectory, inertia, or effort | C.27.TA; use C.27 for temporal-claim adequacy | C.27.TA supplies positive temporal subject matter; C.27 governs temporal-claim adequacy. Recover transformation identity under A.3.4 when that separate claim is current. |
| evidence, provenance, source, publication, dashboard, view, gate, decision, assurance, result, or release claim | the direct governing evidence, source, publication, gate, decision, assurance, result, or release pattern | A visible record or path does not establish evidence sufficiency, assurance, gate passage, deontic permission, work authorization, release authorization, performed work, or acceptance by itself. |
A.3.4.P:4.3 - Common source-label settlements
| Source label | First recovery question | Typical admissible outcomes |
|---|---|---|
pipeline or dataflow | Is the current object one transformation, a compound transformation-flow structure, a method description, a work plan, or a publication diagram? | A.3.4, E.18, A.3.2, A.15.2, C.2.P.DR, or quote-only source wording. |
flow | Is flow the selected structure, a mathematical expression, an actual material, energy, signal, or information flow, or an ordinary source label? | E.18, E.18.2, C.29, direct subject pattern, or quote-only source wording. |
network or circuit | Is it a structure form, topology label, mathematical-expression family, functional structure, architecture-selected structure, or subject-domain system? | E.18, E.18.2, C.29, C.30.ASV, A.6.F, or direct subject pattern. |
path or slice | Is it graph path, PathSlice, evidence path, carrier path, mathematical path, source quote, or action-route metaphor? | E.18, A.10, C.29, C.2.P.DR, carrier wording, source wording, or an explicit stop when no exact current claim is recovered. |
workflow or process | Is it method, method description, work plan, dated work, transformation-flow structure, mechanism, or source label? | A.3.1, A.3.2, A.15.2, A.15.1, E.18, A.6.1 with E.20, or quote-only source wording. |
algorithm, program, solver, or proof | Is it method, method description, formal substrate, mathematical lens, mechanism, work occurrence, evidence, or proof publication? | A.3.1, A.3.2, A.6.0, C.29, A.6.1 with E.20, A.15.1, A.10, C.2.1, or the governing publication pattern. |
function, functional, or functioning | Is the current claim about an actual U.Transformation, selected TransformationFlowStructure, a performed-work or non-work actor under an exact direct governor, a separately typed influence source, boundary binding, or FunctioningRef?; or is the word asking for function-kind discrimination? | Use A.3.4 or E.18 for transformation-side recovery. For performed Work, recover each precise performer’s A.13 core and independently admit the Work under A.15.1; add F.6 only when precise assignment-bound attribution is current, and state the separate Work-to-change relation. For non-Work action, use another exact participant, operation-application, functioning, causal, or direct actor-side relation. Keep every influence source under its own kind and exact relation; use A.6.F for function-kind discrimination. |
A.3.4.P:4.4 - Functional change-situation settlement
When change-situation wording includes function, functional, functioning, transforms, or implements, use this pattern only to recover the exact current claims:
- Is one actual bounded
U.Transformationestablished by changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification? - Is a selected
TransformationFlowStructurecurrent without being treated as the acting system or the change occurrence? - Is performed Work being attributed to a System? Recover each precise performer’s A.13 core and independently admit the Work under A.15.1. Add F.6 only when precise assignment-bound attribution is current, then state separately the realization, causal, production, or other Work-to-change relation required by the claim. An assignment occurrence, Work record, common timestamp, or generic transformation-participant fact does not prove performance.
- Is a non-work functional or physical actor-side claim current? Recover the exact system and the participant, operation-application, functioning, causal, or other direct actor-side relation supplied by its governor. If no actor-side governor is recoverable, leave the actor claim unresolved.
- Is a distinct influence source current? First recover its exact kind. A manufacturing, certification, or design organization may be a System under its direct admission pattern; a toolchain or communication System needs its own admitted kind; a selected structure remains a structure; and a Method or Method family is not a holon by label. State only the exact architecture, Work, communication, constraint, or candidate-synthesis relation current for that value. Influence alone establishes no local system-role kind, separate System-classification judgment, assignment occurrence, Work, acting fact, or transformation participation.
- Are exact participant, port, operation-application, relation-signature, or functioning relations current at the boundary? Keep them under their direct governors; a transformation input or output requires its own direct relation.
Do not introduce a TransformerHolon kind, a generic transformer role, or a universal architecture-influence relation to bridge these claims. After recovery, apply A.6.F when the question is which function-like kind or relation is being claimed. A.3.4.P selects the direct governor for each recovered claim.
A.3.4.P:4.5 - Description, publication, and evidence boundary
A diagram or report, for example, may describe a transformation, state a claim about it, provide evidence for that claim, or help compare transformations. When an actual transformation is claimed, recover its subject-side occurrence basis separately. If the description, assertion, or publication is current, use the episteme, publication, source, or declarative-representation pattern; C.2.1 empirical grounding remains an optional separate relation when the use requires it. If the actual transformation is current, keep every description, assertion, publication, and evidence use as an exact neighboring claim.