#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: Draft 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, a transformed object, a transformer-side system or holon, 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 move. Fill a compact TransformationWordingRepair note: encountered wording, working concern, recovered transformation or non-transformation object, recovered slot or neighboring pattern, retained use, blocked overread, and remaining reader move. Then rewrite only the wording that depends on the recovered kind.

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 proof or permission; "function" becomes behavior, bearer, mathematical function, and software routine at once.

What this buys. The reader gets one small repair move 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, and the transformer-side system.

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. Compound structure becomes atomic change. A flow, path, network, or circuit expression is treated as one U.Transformation without identity slots.
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 U.Transformation. If one bounded change is current, fill the A.3.4 identity slots: transformed object, bounded context, initial condition, post-state or delta, transformation relation, boundary or admissibility condition, and temporal or ordering reference when relevant.
3. Test for neighboring slots. Decide whether the wording points to a transformer-side system or holon, 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, or reopen relation.
4. Use the governing pattern for each filled value. The slot may belong to the transformation ontic; the filler keeps its own kind and governing pattern.
5. Rewrite only after kind 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 relation named by value.
6. Leave one reader move. 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, or mechanism 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:
  TransformationCoreDisposition:
  RecoveredSlotOrNeighboringValue:
  GoverningPattern:
  RetainedUse:
  BlockedOverread:
  RemainingReaderMove:

TransformationCoreDisposition is one of: 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. Project records, evidence relations, gate decisions, work plans, and work occurrences are created only by the governing pattern selected in the note.

#Direct governing-pattern selection

#Common source-label settlements

#Functional transformer settlement

When change-situation wording includes function, functional, or functioning, use this pattern only for the transformation-side recovery:

• Is one bounded U.Transformation current?
• Is a TransformationFlowStructure current?
• Is the current value a transformer-side filler such as a system, holon, module, bearer, allocation locus, interface, port, or signature-side value?
• Is the current value an input boundary, output boundary, or FunctioningRef? for transformation behavior under conditions?

After that recovery, apply A.6.F when the question is which function-like kind or relation is being claimed. A.3.4.P does not decide mathematical function, software routine, capability, quality, role, work, method, module allocation, evidence use, assurance use, gate use, or decision use except by selecting the governing pattern that owns the recovered value.

#Description, publication, and evidence boundary

A diagram, model, dashboard, report, source span, proof, graph, or publication may describe, evidence, or help compare a transformation. It is not the transformation. If the current object is the description or publication, use the episteme, publication, source, or declarative-representation pattern. If the current object is the transformation, keep the description or publication as a neighboring value and state the evidence use, description use, or comparison use separately.

#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 a system-like architecture locus or module allocation; activations and tensor shapes may fill input and output slots or signature slots; attention may be a method description or mathematical lens; the pipeline may be a transformation-flow structure. Benchmarks or ablations are evidence or result 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 the candidate U.Transformation; 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 does not approve the edit.

#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 the transformation, work plan, dated work, gate, assurance, and result relations when those claims are current. The path does not authorize the change 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 compound transformation-flow structure, a thermodynamic mechanism, a functional architecture view, or a schematic publication.
  RecoveredEntityOfConcern: refrigerator heat-transfer behavior in the bounded cooling context.
  TransformationCoreDisposition: not one atomic transformation yet; compound transformation-flow structure is current.
  RecoveredSlotOrNeighboringValue: compressor, condenser, expansion, and evaporator transformations are candidate component transformations; thermodynamic laws are mechanism-governing material; the diagram is a publication only if the diagram itself is the current object.
  GoverningPattern: `E.18` for selected transformation-flow structure; `A.3.4` for each bounded component transformation when named; `C.30.ASV` for functional architecture view; direct publication pattern when the schematic publication is current.
  RetainedUse: "circuit" may stay as ordinary domain wording after the selected structure is named.
  BlockedOverread: the circuit label is not proof of functioning, not a gate decision, not dated work, and not one atomic transformation.
  RemainingReaderMove: name the selected transformation-flow structure and then open the direct governing pattern for the next claim being made.

#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, proof, permission, 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;
• slot-filler fusion: a method, mechanism, work occurrence, system, or evidence record fills a transformation slot and is then treated as the whole transformation.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

• FPF gains one reusable repair move 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 translated into transformation identity slots and neighboring values.
• 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 change. That compactness only helps if wording repair can return common source labels to the correct object and slot. 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 that ontic, one of its slots, one of its slot fillers, a compound structure, a mathematical description, or a neighboring claim. 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

No new external SoTA claim is introduced here. The pattern inherits the current source decisions already carried by A.3.4, C.2.P.DR, and the governing neighboring patterns; it changes only the reusable restoration move 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, 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.
• 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-06-14 — this section last modified in upstream FPF commit 7c617d5d (github.com/ailev/FPF)