#Transformation Ontic Precision Restoration

A.3.4.P · Stable · A.3.4 precision-restoration child pattern · Normative unless a section is explicitly informative · Part A - Kernel Architecture Cluster

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: A.3.4 precision-restoration child pattern Status: Stable Normativity: Normative unless a section is explicitly informative

Plain-name. Transformation wording repair.

Intent. Restore precision when wording about a situation of change hides whether the current FPF object is one bounded U.Transformation, its exact changed referent, a system claimed to act through an exact performed-work attribution or another direct actor-side relation, a distinct influence source kept under its exact kind and current relation, a method, method description, mechanism, work plan, dated work, functioning relation, transformation-flow structure, mathematical description, dynamics episteme, temporal aspect, evidence relation, publication relation, gate, decision, result, or source label.

Use this when. Use A.3.4.P when source or FPF-governed wording such as "pipeline", "dataflow", "flow", "network", "circuit", "path", "slice", "workflow", "process", "operation", "transformation", or "change" seems to name the thing under concern, but the text has not yet recovered what kind of FPF value is actually current.

First useful restoration output. Fill a compact TransformationWordingRepair note: encountered wording, working concern, exact recovered EntityOfConcern, actual-transformation basis or non-transformation disposition, any acting-system claim with its exact governor or unresolved disposition, every influence source's exact kind and current relation, exact neighboring claims, retained use, blocked overread, and remaining reader use. Then rewrite only the wording that depends on the recovered objects.

What goes wrong if missed. The text silently creates a local ontology from a convenient source label: "process" becomes method in one paragraph, dated work in another, and transformation-flow structure in a third; "path" becomes evidence sufficiency, assurance, gate passage, deontic permission, work authorization, or release authorization; "function" becomes behavior, bearer, mathematical function, and software routine at once.

What this buys. The reader gets one small restoration use that keeps bounded transformations, compound transformation-flow structures, formal descriptions, methods, mechanisms, work, evidence, publications, and functional structures in their governing places before any wording is changed.

Not this pattern when.

• If one bounded transformation is already identified and only its ordinary use continues, apply A.3.4 directly.
• If the current claim is already a selected transformation-flow structure, use E.18.
• If the current claim is a graph, morphism, category, algebra, path, circuit expression, network expression, or other mathematical description, use E.18.2 and C.29.
• If the current claim is only a semantic way of doing, method description, mechanism, work plan, dated work, evidence relation, publication relation, gate, decision, assurance, result, or temporal claim, use the direct governing pattern.
• If the word is quoted source wording with no FPF-governed use, keep it quote-only.

People talk about change with convenient source labels. A manufacturing line has a process, an ML paper has an architecture pipeline, a refrigerator has a cycle, a plant model has a flow graph, a team has a workflow, and a proof has a construction path. Those labels often help recognition, but they do not say which FPF object is current.

#Relations

#Content

#Problem frame

People talk about change with convenient source labels. A manufacturing line has a process, an ML paper has an architecture pipeline, a refrigerator has a cycle, a plant model has a flow graph, a team has a workflow, and a proof has a construction path. Those labels often help recognition, but they do not say which FPF object is current.

The recurring defect is a second ontology by convenience. The same text may treat "process" as method, work occurrence, transformation-flow structure, mechanism, result evidence, and publication diagram. A graph path may become an action route. A network label may become a durable head beside TransformationFlowStructure. A function word may collapse functioning, mathematical function, software routine, module allocation, a system merely named as actor, and a differently typed influence source whose direct relation has not been recovered.

This pattern restores the current U.Transformation ontic first, then assigns linked values to their governing patterns. It is not a word ban and not a synonym table.

#Problem

Without this repair:

1. Source label becomes kind. "Pipeline", "workflow", "network", "circuit", or "process" is treated as the recovered FPF kind.
2. Selected structure becomes one actual transformation. A flow, path, network, or circuit expression is treated as one actual U.Transformation or as proof of transformation composition without the exact changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis. Identifying one occurrence at the resolution needed by the current use establishes neither finer transformation parts nor partlessness.
3. Method, mechanism, and work collapse. A method description, law-governed mechanism, work plan, dated work, or source diagram is selected by vocabulary rather than by current claim.
4. Functional wording overreaches. A system, module, port, interface, signature, or function label is treated as the transformation or as proof of functioning.
5. Mathematical expression becomes world-side ontology. A graph, morphism, algebra, category, path, network, or circuit expression is treated as the project-world change.
6. Description or evidence becomes transformation. A publication, dashboard, source span, proof, or evidence path is treated as the changed object or the change itself.

#Forces

#Solution

Restore the change situation in this order.

1. 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.
2. 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.
3. Separate an acting-system claim from influence. For performed work, recover one exact dated Work occurrence admitted under U.Work, the exact covering U.RoleAssignment, and direct performedBy(WorkOccurrenceSlot, RoleAssignmentSlot); then recover separately the realization, causal, production, or other exact work-to-change relation required by the current use. Role assignment alone and generic transformation participation prove no action. For a non-work functional or physical actor-side claim, recover the exact system and the participant, operation-application, functioning, causal, or other direct actor-side relation supplied by its governor; 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 exact kind—a method or method family is not a holon by label—and receives only the exact architecture, work, communication, constraint, or candidate-synthesis relation current for the claim.
4. 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.
5. 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.
6. 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.
7. Leave one reader use. The repaired text must say what the reader may do now: use A.3.4, use E.18, use C.29, use a method, work, mechanism, architecture, or evidence pattern, keep a quote-only cue, or block the stronger claim.

#TransformationWordingRepair note

Use this note only when wording is doing FPF-governed work.

TransformationWordingRepair:
  EncounteredWording:
  WorkingConcern:
  RecoveredEntityOfConcern:
  ActualTransformationDisposition:
  TransformationOccurrenceBasis:
  ActingSystemDisposition:
  ArchitectureInfluenceDisposition:
  NeighboringClaimAndExactRelation:
  GoverningPattern:
  RetainedUse:
  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 blocked overread, and the next governing-pattern application. 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 performed work, an acting-system claim needs one exact dated Work occurrence admitted under U.Work, the exact covering U.RoleAssignment, direct performedBy(WorkOccurrenceSlot, RoleAssignmentSlot), and the separately governed realization, causal, production, or other work-to-change relation required by the use. For a non-work actor-side claim, use an exact participant, operation-application, functioning, causal, or other direct relation supplied by its governor. If no such relation is recoverable, keep the actor claim unresolved. Every influence source retains its exact kind and only its current architecture, work, communication, constraint, or candidate-synthesis relation; influence establishes no acting fact by itself.

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. Project records, gate decisions, work plans, and work occurrences are created only by their direct governing patterns.

#Direct governing-pattern selection

#Common source-label settlements

#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.Transformation established by changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification?
• Is a selected TransformationFlowStructure current without being treated as the acting system or the change occurrence?
• Is performed work being attributed to a system? Recover the exact dated Work occurrence admitted under U.Work, exact covering U.RoleAssignment, and direct performedBy(WorkOccurrenceSlot, RoleAssignmentSlot). Then state separately the realization, causal, production, or other exact work-to-change relation required by the claim. A role assignment, 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. A changed referent, resource, port-bound object, module, or other participant is not an actor merely because it participates. 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 governor; 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 role, work, actor status, or transformation participation.
• Are exact participant, port, operation-application, relation-signature, or functioning relations current at the boundary? Use their direct governors; do not turn them into generic transformation inputs or outputs.

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; it does not infer mathematical function, software routine, capability, quality, work, method, architecture allocation, evidence, assurance, gate, or decision from functional wording.

#Description, publication, and evidence boundary

A diagram, model, dashboard, report, source span, proof, graph, or publication may describe, assert, evidence, or help compare a transformation. It is not the transformation and does not supply its subject-side occurrence basis. 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.

#Archetypal Grounding

#Refrigerator functional diagram

Source wording says: "The refrigeration circuit moves heat through the cycle."

Repair: recover whether the current claim is a refrigerator subsystem transformation, a TransformationFlowStructure over compressor, condenser, expansion, and evaporator transformations, a thermodynamic mechanism, a functional architecture view, or a schematic publication. The circuit label may stay as ordinary domain wording, but FPF use names the selected structure, mechanism, or publication relation.

#Neural-network block

Source wording says: "The attention block transforms activations in the model pipeline."

Repair: the block may be an architecture locus or module allocation, but that fact alone establishes no actor. If dated inference work is claimed, recover its exact Work occurrence admitted under U.Work, covering U.RoleAssignment, direct performedBy, and the separately governed work-to-activation relation required by the use. If a non-work block action is claimed, recover the exact operation-application, functioning, causal, or other direct actor-side relation; otherwise leave action unresolved. A design organization, method or method family, toolchain, or communication system that shaped the block first keeps its exact kind and then only its exact architecture, work, communication, constraint, or candidate-synthesis relation. Activation and tensor-shape claims use exact participant, port, operation-application, or signature relations; attention may be a method description or mathematical lens; the pipeline may be a transformation-flow structure. Benchmarks or ablations are evidence or evaluation relations only when their governing patterns are current.

#CRISPR editing workflow

Source wording says: "The guide-selection workflow changes the target gene."

Repair: the target-gene edit is only a candidate U.Transformation until the exact biological referent, edit boundary, boundary conditions, actual sequence and direct-relation facts, and reidentification rule establish one occurrence. Guide selection may be method, method description, work plan, evidence-facing table, or performed lab work according to the current claim. A table rank or workflow diagram establishes neither actual edit, gate passage, deontic permission, work authorization, release authorization, nor performed lab work.

#Evidence path near a plant change

Source wording says: "The evidence path lets the valve-change flow proceed."

Repair: an evidence path may be a legitimate A.10 provenance relation for a named claim. The valve change still needs its exact changed referent, boundary, boundary conditions, actual subject facts, and continuity or reidentification basis; work plan, dated work, gate, assurance, result, and receiving use remain exact neighboring relations when current. The path establishes no work authorization, release authorization, gate passage, performed work, or actual transformation by shape or name.

#Filled minimal repair note

TransformationWordingRepair:
  EncounteredWording: "the refrigeration circuit moves heat through the cycle"
  WorkingConcern: recover whether the sentence is about one bounded heat-transfer change, a selected compound transformation-flow structure, a thermodynamic mechanism, a functional architecture view, or a schematic publication.
  RecoveredEntityOfConcern: `RefrigeratorHeatTransferFlowStructure-1`, the exact selected `TransformationFlowStructure` over the compressor, condenser, expansion, and evaporator transformation loci.
  ActualTransformationDisposition: no actual bounded transformation is recovered; `RefrigeratorHeatTransferFlowStructure-1` is the exact current object, and its selection establishes neither transformation composition nor partlessness.
  TransformationOccurrenceBasis: no component transformation occurrence is asserted; each remains unresolved until its exact changed referent, boundary, boundary conditions, actual subject facts, and continuity or reidentification basis are recovered.
  ActingSystemDisposition: unresolved and not asserted; the circuit wording supplies no exact dated Work occurrence admitted under `U.Work`, `performedBy` relation, work-to-change relation, or non-work direct actor-side relation.
  ArchitectureInfluenceDisposition: no influence claim is current and no influence source is selected; any later source must first keep its exact kind and then receive only its exact architecture, work, communication, constraint, or candidate-synthesis relation.
  NeighboringClaimAndExactRelation: the four named transformation loci are positions in `RefrigeratorHeatTransferFlowStructure-1`; their exact transformation occurrences and structure-membership relations remain to be recovered under `E.18` and `A.3.4`. Thermodynamic-law material, functional view, and schematic publication remain unselected neighboring candidates.
  GoverningPattern: `E.18` governs `RefrigeratorHeatTransferFlowStructure-1`; `A.3.4` governs each component transformation only after its occurrence basis is recovered; mechanism, architecture-view, and publication patterns open only if one of those candidate objects becomes current.
  RetainedUse: "circuit" may remain ordinary domain wording for `RefrigeratorHeatTransferFlowStructure-1` after that exact selected structure is named.
  BlockedOverread: `RefrigeratorHeatTransferFlowStructure-1` is not proof of functioning, an actor, dated work, a gate decision, one actual transformation, or transformation composition; its component loci do not establish component occurrences, parthood, or partlessness.
  RemainingReaderUse: use `E.18` for `RefrigeratorHeatTransferFlowStructure-1`; open `A.3.4` only for a component whose exact occurrence basis is recovered, or the direct mechanism, architecture-view, or publication pattern only when that separate object becomes current.

#Bias-Annotation

Lenses tested: Onto, Arch, Prag, Epist, Gov.

This pattern intentionally biases toward kind recovery before wording repair. It resists:

• source-label ontology: familiar labels such as pipeline, process, network, circuit, or workflow become FPF kinds;
• graph or path overread: graph path, evidence path, and carrier path become action route, evidence sufficiency, assurance, deontic permission, work authorization, release authorization, or work sequence;
• function collapse: functioning, functional element, module allocation, mathematical function, software routine, and everyday purpose collapse into one "function";
• semio displacement: descriptions and publications of transformations replace the transformation under concern;
• neighboring-object fusion: a method, mechanism, work occurrence, system, influence source, or evidence record is inferred from wording and then treated as the transformation, its actor, or a transformation participant; generic participation is also treated as action without exact performedBy, work-to-change, or other direct actor-side relation.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

• FPF gains one reusable restoration pattern for language about change situations without making every subject pattern carry its own cue list.
• A.3.4 becomes easier to use because source labels are tested against the exact subject-side transformation basis and then routed to exact neighboring relations.
• E.18, E.18.2, and C.29 stay distinct: selected compound structure, mathematical expression, and mathematical-lens use do not collapse.
• Architecture, method, work, mechanism, function, evidence, publication, and temporal patterns can point to the transformation ontic without becoming transformation patterns.
• The cost is one small restoration note when wording is FPF-governed and hides several candidate kinds.
• Reopen this pattern at the smallest affected row when A.3.4, E.18, E.18.2, C.29, method, mechanism, work, function, temporal, evidence, publication, or architecture patterns change the governing kind boundary, or when FPF wording repair repeatedly finds a change-situation label that the current settlements cannot recover by value.

#Rationale

The current transformation ontology gives FPF one compact way to speak about bounded actual change. That compactness only helps if wording repair returns common source labels to the exact changed referent, temporal or formal boundary, boundary conditions, actual subject facts, and continuity or reidentification basis. Otherwise source labels reappear as local mini-ontologies: a process ontology here, a graph ontology there, a function ontology elsewhere.

A.3.4.P is placed under A.3.4 because the recurring repair is not about words in general. The repair starts from the U.Transformation ontic and asks whether the current use is an actual occurrence established on that basis, a performed-work actor claim grounded by one exact Work occurrence admitted under U.Work, performedBy, and its required work-to-change relation, a non-work actor claim under another exact direct actor-side governor, a differently typed influence source under its exact relation, a compound structure, a mathematical description, or another neighboring object connected by an exact current relation. E.10 recognizes the wording-use problem; E.10.ARCH:2.2 distributes direct governing, ontic-level restoration, and facet-level restoration; this pattern performs the ontic-level transformation restoration.

#SoTA-Echoing

SoTA use is conservative: this pattern relies on the current FPF settlements already carried by A.3.4, C.2.P.DR, and the governing neighboring patterns; it contributes the reusable restoration use for transformation-situation wording.

#Relations

• Builds on: A.3.4, E.10, E.10.ARCH, E.24, A.6.5, and E.8.
• Coordinates with: E.18 for a selected structure that positions, relates, or locates transformation loci and adjacent governed values without establishing transformation composition, parthood, or partlessness; and with E.18.2, C.29, A.3.1, A.3.2, A.3.3, A.6.0, A.6.1, E.20, A.15.2, A.15.1, A.6.F, A.6.M, C.30.ASV, C.27.TA, C.27, A.10, C.2.P.DR, C.2.1, E.17, and direct gate, decision, assurance, result, source, publication, and release patterns when those claims are current.
• Coordinates with: E.10.MOVE when source wording about a move, next action, pattern-use recommendation, work-entry readiness, language-state transition, architecture candidate use, or call-planning next action is not actually transformation wording.
• Selected by: E.10 recognition row for change-situation wording when FPF wording repair needs transformation-ontic precision restoration.
• Specializes: A.3.4 for wording-use precision restoration around situations of change.

#A.3.4.P:End

Last Updated: 2026-08-04 — upstream FPF commit 8b727cba (github.com/ailev/FPF)