#Constraint-Governed Transformation-Flow Unfolding Structure

E.18.3 · Stable · E.18 transformation-flow specialization of A.22.CGUS · Normative unless explicitly marked informative · Part E - The FPF Constitution and Authoring Guides

#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: E.18 transformation-flow specialization of A.22.CGUS Status: Stable Normativity: Normative unless explicitly marked informative

Use this pattern when a team is planning, reviewing, or explaining a transformation and a route-like flow card is useful, but branches, joins, guards, or connections to independently identified neighboring values or neighboring claims already shown to obtain determine what can follow. The practical need is to recover those transformation-flow relations without treating displayed order as performed-work order, evidence, decision, or authorization.

#Relations

#Content

#Use This When

Use this pattern when a team is planning, reviewing, or explaining a transformation and a route-like flow card is useful, but branches, joins, guards, or connections to independently identified neighboring values or neighboring claims already shown to obtain determine what can follow. The practical need is to recover those transformation-flow relations without treating displayed order as performed-work order, evidence, decision, or authorization.

The admitted object is the same selected U.Structure already identified under A.22 and qualified as a CGUS by exact constituents, selected obtaining relation occurrences, applied constraints, and one named selection-use frame. E.18.3 recognizes that object under an additional transformation-flow unfolding condition; it does not manufacture a generic CGUS plus a reciprocal narrower structure. That condition uses one independently identified E.18 substrate branch: one TFS, one parent-relative internal SubflowRef within a TFS, or one selected E.18.NET network. The A.22-selected CGUS uses exact substrate positions, bindings, and already-obtaining occurrences; the substrate ref does not resolve to selectedCGUSRef and is not a second CGUS.

Do not use this pattern merely because a visible record or description is a route, path, graph, process map, chain, loop, or swimlane. First ask whether a branch, join, guard, dependency, crossing, or connection changes the continuation question for the concrete thing being transformed. If it does not, keep the artifact as an ordinary route description. When the current use claims E.18.3 qualification, typed transformation positions, exact crossings and guards, the correct one-TFS, internal-subflow or network case, preserved transformation structures, relevant C.33 adequacy notes, explicit stronger neighboring claims with their concrete contributions, and stop or reconsideration conditions become admission criteria rather than first-entry paperwork.

The first useful move is small and ordinary: name the concrete thing being transformed, mark two recognizable places or states on the flow card in domain language, state the proposed connection or guard, and ask which continuation depends on it. A useful result can be a provisional explanation that names the missing relation, fact, or constraint. It need not yet be asserted as a C.2.1 episteme, E.18 position mapping, or selected A.22 structure. If that explanation answers the current use, stop there.

Only when the team must assert E.18.3 qualification, compare or publish the selected structure, or support a stronger downstream claim should it recover the exact A.22-selected structure, transformation subjects and kinds, E.18 or E.18.NET positions and bindings, already-obtaining relation occurrences, constraints, C.33 notes, and replay fields. Here move is Plain wording for the current use action, not a universal kind or relation; proposing, selecting, or formalizing it performs no Work.

What changes in practice. The practitioner stops asking whether a diagram “looks like a flow” and first names the concrete transformation subject, two recognizable places or states, the proposed relation or guard, and the smallest honest continuation question. Exact structure identity, E.18 or E.18.NET bindings, already-obtaining relations, and replay fields are added only when qualification, comparison, publication, or stronger reliance makes them material. A provisional explanation or later demonstration can guide attention without becoming the structure, a MethodDescription, a WorkPlan, or performed Work.

#Problem Frame

E.18 already gives FPF a rich language for transformation-flow structure: transfers, dependencies, paths, crossings, guards, valuations, publication faces, comparability, slice-local refresh, and structure-positioned slot fillings. A.22.CGUS gives the broader A.22 specialization of U.Structure for constraint-governed unfolding structures. A practitioner needs the narrow bridge between them: when is an unfolding structure a transformation-flow unfolding structure, and which independently identified neighboring values or neighboring claims already shown to obtain connect to its positions? When replay or a stronger claim needs the basis, keep any cited definition, constraint, predicate, test, evidence rule, or assurance rule distinct from the current facts or evidence that satisfy it. A Method instead contributes a reusable way of doing and its applicability or bounds; a MethodDescription may state that content, but neither supplies a truth, evidence, or assurance criterion merely by being cited.

#Problem

Transformation-flow artifacts are easy to overread. A path diagram becomes a workflow. A flow card becomes performed work. A P2W chain becomes work authorization. A graph expression becomes the whole structure. A gate, evidence path, architecture decision, or publication face becomes part of the transformation-flow ontology by visual adjacency.

The repair cannot be lexical. E.18.3 qualification depends on one exact A.22-selected structure, the correct E.18 or E.18.NET case, independently identified and typed transformation subjects, admitted position mappings, exact already-obtaining relation occurrences, exact relation references and separately supported subject-use classifications when needed, preserved structures, C.33 adequacy notes, and distinct ordinary stop and reconsideration conditions.

#Forces

#Solution

E.18.3 is a membership-and-use profile for one exact selected A.22.CGUS U.Structure. The selected structure keeps the four A.22 identity discriminators. Its applicable E.18 substrate is independently identified as one TFS, one parent-relative internal SubflowRef, or one E.18.NET network. E.18.3 asks whether the selected CGUS uses exact positions, bindings, and already-obtaining occurrences from that substrate, together with its current constraints and use frame, to satisfy the transformation-flow unfolding conditions below.

Use this compact display only as a recovery aid; it is neither another record kind nor structure identity:

selectedCGUSRef
flowCase: oneTFS | internalSubflow | network        # Plain choice for this use
transformationSubjectRows[]:
  subjectRef
  subjectKindRef
transformationPositionMappingRows[]:
  admittedCGUSPositionLocator
  flowPositionRef
  exactPositionBindingRef
appliedConstraintClaimRefs[]?                 # each resolves to its predicate or test and current fact basis
e18GuardEventRefs[]?                         # GuardFail events emitted by E.18 guards, never relation occurrences
guardGateAssignmentFactRefs[]?               # required with cited E.18 guard events under E.18/A.21
relationReferenceEpistemeRefs[]              # EntityOfConcern is an exact already-obtaining relation occurrence only
neighboringValueUseRows[]
transformationFlowStructureRef?             # independently identified one-TFS substrate; never selectedCGUSRef
subflowRef?                                  # parent-relative internal substrate in one TFS; never selectedCGUSRef
transformationFlowStructureNetworkRef?      # independently identified E.18.NET substrate; never selectedCGUSRef
pathIds[]?
pathSliceIds[]?
flowValuationRef?
preservedTransformationStructureRefs[]
structureInformationAdequacyNoteRefs[]?
stopCondition
reconsiderationConditions[]:
  conditionClaimRef
  affectedStructureRef
  nextQuestion
  relevantPatternRef?: cite only when it locates a needed definition, constraint, predicate, test, evidence or assurance rule, or a Method's way of doing and applicability

The first four A.22 discriminators, not this display, identify the selected CGUS. The mutually exclusive substrate fields identify independently current E.18 objects used by that CGUS; none is another identity field and none resolves to selectedCGUSRef. flowCase and the remaining rows show why that one CGUS qualifies and let the current use replay its substrate, subject kinds, relation predicate definitions, position bindings, and reconsideration boundaries. No ambient context, transformed-subject label, path, valuation, tag, record edition, demonstration, or profile field becomes another identity discriminator.

The three continuation-condition branches remain different objects. appliedConstraintClaimRefs[] resolves claims with their predicate or test and current facts. e18GuardEventRefs[] resolves E.18 guard-failure events together with guardGateAssignmentFactRefs[]; neither field denotes a relation. relationReferenceEpistemeRefs[] resolves only epistemes whose EntityOfConcern is an exact already-obtaining relation occurrence. These optional fields are a recovery aid, not a new record or condition kind.

Paths and demonstrations remain different. PathId, PathSliceId, FlowValuation and the complete FlowPositionRef identity stay with one exact E.18 TFS. A post-admission A.22 demonstrative slice is a separate ordinary C.2.1 episteme whose EntityOfConcern is the admitted CGUS. Before admission, a flow card, worked example, or explanation may remain an ordinary explanation about the actual subject, question, or proposed continuation set. Constitute it as a C.2.1 provisional episteme only when the current use needs a persistent or replayable claim; a linear slice may teach one traversal while the selected structure branches, joins, cycles, or keeps alternatives live.

A pattern-selection flow, selected-pattern-application flow and downstream-subject-work flow keep different EntitiesOfConcern, changes, Work occurrences, results, applicable definitions and tests, constraints and reconsideration conditions. If all relevant positions and internal U.Transfer occurrences resolve to one TFS, use its exact positions and, when current, one complete top-level demonstration locator <transformationFlowStructureRef, pathSliceId, DesignRunTag>. A detailed internal portion remains one parent-relative SubflowRef. If independently identified TFS or nested-network members cross, use E.18.NET to recover the network membership and exact cross-member occurrence requirements, including the applicable predicates and current facts showing that the membership and occurrences obtain; the mutually exclusive A.22 network locator applies and the top-level one-TFS triple is absent.

A result, tool, context, constraint, shared label or displayed arrow neither merges network members nor supplies their relation. Every member keeps its boundary, Work, actual transformations, valuations and leaf-local position state. Nested pattern-selection content is present only while its exact source or selection-provenance relation is current for the declared demonstration use. When present, it contributes its own candidate, fit finding or recommendation rather than borrowing a later application result.

Preserved transformation structure is carried by exact U.Structure refs. Captured, expected-but-uncaptured, lost and hidden structure for the declared use remains in exact C.33 epistemes. A stop or reconsideration condition is an ordinary use boundary unless an exact relation occurrence is independently defined and shown to obtain by its applicability conditions and current facts. G.11 supplies the source-currentness and decay tests; E.18 supplies one-TFS slice-local refresh.

There is no generic method-to-work linkage here. When one named use relies on a Method-to-Work claim, cite the exact already-obtaining relation or result and the concrete definition, test or rule that supports it; keep Method, qualifying MethodDescription, WorkPlan, readiness and dated Work separate. A pattern ref, intended realization, selected continuation, imperative sentence or displayed sequence does not admit any episteme as U.MethodDescription. A.3.2 supplies the membership test: one already identified C.2.1 episteme whose exact EntityOfConcern is one admitted U.Method and whose ClaimContent makes at least one substantive way-of-doing claim. Each exact Method, qualifying MethodDescription, WorkPlan, work-entry result, dated Work, actual Transformation, production/inception/completion, evidence, evaluation, or source-use object must first be independently identified; any membership, occurrence, evidence, evaluation, or source-use claim obtains only when current facts or evidence satisfy the applicable definition, test, predicate, or rule. Only current objects and already-obtaining relations may enter the structure.

#Ordinary start and conditional formal recovery

Begin with the ordinary branch: name the concrete thing being transformed, mark two recognizable places or states, state the proposed connection or guard in domain language, and ask which continuation depends on it. Return a provisional explanation that either answers the question or names the missing relation, fact, or constraint. If that is sufficient, stop; neither the explanation nor the flow card must first be constituted as an episteme, position mapping, or selected structure.

Use the numbered recovery branch below only when the current use must assert E.18.3 qualification, compare or publish the structure, or support a stronger downstream claim. The branch preserves the exact admission criteria; it is not a prerequisite for understanding or correcting an ordinary route-like card.

1. Recover one selected A.22.CGUS and its four exact identity discriminators; do not create a reciprocal E.18.3 structure.
2. Name the current transformation subject or subjects, their kinds and the exact E.18 positions and bindings used by the question.
3. Classify the independently identified E.18 substrate used by selectedCGUSRef as one TFS with its valuations, one parent-relative internal SubflowRef, or one E.18.NET network of independent members and exact crossings; do not resolve the substrate ref to the selected CGUS.
4. Discriminate every continuation basis before citing it. Keep an applied constraint or condition claim in appliedConstraintClaimRefs[] with its predicate or test and current facts; keep a GuardFail emitted by USM.CompareGuard or USM.LaunchGuard as an E.18 event with its E.18/A.21 gate-assignment facts; and use a relation-reference episteme only for an independently defined exact relation occurrence. Cite every selected internal U.Transfer, dependency relation, or cross-member relation occurrence and its predicate-definition source; a condition informally called a guard enters this relation branch only when its relation kind and obtaining occurrence independently exist. Carry a relation signature only when replay needs the exact declaration.
5. For each neighboringValueUseRows[] entry, recover the independently identified neighboring value through its exact kind and ref and one already-obtaining supporting relation. If the row makes a stronger claim, state in ordinary content-bearing language what the neighboring content contributes; a bare label such as test or method is not enough. A definition, constraint, predicate, test, evidence rule, or assurance rule may supply the applicable criterion, with current facts or evidence showing that the claim obtains. A Method contributes a reusable way of doing and its applicability or bounds, and a MethodDescription may state that content; any claim that its use produces, supports, evaluates, evidences, or assures a result still needs a separate applicable rule and current basis. Require an exact claim-bearing episteme, ClaimGraph, edition, or other content identity only when that identity changes the selected stronger use, and reuse an existing exact ref when available. Cite a relevant pattern only when it locates that content. A result label, return arrow, or comparison layout is not the relation.
6. Name preserved structures, relevant C.33 adequacy notes, an ordinary stop and the exact reconsideration conditions. For a post-admission demonstration, choose exactly one complete A.22 locator family: top-level one-TFS, network, or neither for a generic slice.
7. If any A.22 discriminator, position binding, direct relation, network row, or required loss or reconsideration value is missing, keep the artifact as an ordinary provisional explanation and state the exact blocker. Constitute a C.2.1 provisional episteme only when persistence or replay of that narrower claim is current.

The ordinary branch and conditional recovery sequence guide use of the pattern. They are not a local mantra, U.Method, U.MethodDescription, WorkPlan, or performed Work; completing the rows admits nothing by itself.

#Exact relation references

When another person or later use must replay how one selected relation occurrence participates in the selected transformation-flow structure or supports a separately current subject use, materialize one ordinary C.2.1 episteme. Its exact EntityOfConcern is the already-obtaining relation occurrence, its ClaimContent contains only the current reference use below, and its effective ReferenceScheme governs every designation. Transformation-flow relation reference is Plain wording for this use, not a local U-kind. Its edition and currentness remain ordinary C.2.1 and G.11 concerns; they do not add an identity field or ambient context.

transformationFlowRelationReferenceClaimContent:
  selectedCGUSRef
  exactRelationOccurrenceRef
  exactRelationKindRef
  predicateDefinitionRef: exact source that defines the obtaining predicate and participant meanings
  exactParticipantRefsInPredicateOrder[]
  currentFactOrEvidenceRefs[]
  relationSignatureRef?: exact declaration ref only when the replay needs it
  subjectUse?: evidence | assurance | architecture | narrative | publication
  exactSubjectUseClaimOrRelationRef?: required when subjectUse is present
  networkEndpointBindingSets[]?:
    networkCrossFlowRelationRowRef: exact E.18.NET NetworkCrossFlowRelationRowRef
    endpointRows[]:
      relationParticipantPositionRef
      endpointMemberRef
      endpointFlowPositionRef: FlowPositionRef | ExposedFlowPositionRef
      endpointPositionBindingRef

The exact relation kind, predicate definition, ordered participants, current basis, and any network endpoint bindings carry the transformation-flow role; E.18.3 adds no separate structural-function classifier. An internal transfer is cited only as an exact U.Transfer occurrence whose positions resolve inside one TFS. A dependency is recoverable only when the exact predicate truth conditions make one admitted continuation, state, or value depend on another and the participant order preserves that direction. A cross-member connection is recoverable only from an exact obtaining relation whose ordered endpoints bind admitted positions in different selected E.18.NET members. These conditions are distinguishable by value and none relabels or substitutes for the exact relation kind or predicate. An E.18 GateCrossing is a structure-local transition, not a U.Relation occurrence, and never enters this relation-reference field. A domain condition informally called a guard enters a relation reference only when an independently defined relation kind and exact obtaining occurrence exist. An applied constraint or condition claim is not the EntityOfConcern of this relation-reference episteme; keep it in appliedConstraintClaimRefs[] with its test and current facts. A GuardFail emitted by USM.CompareGuard or USM.LaunchGuard is an E.18 event, not a relation occurrence; recover the event and GuardOwnerGateId aggregation-assignment facts under E.18/A.21 instead. The word guard alone admits neither branch.

subjectUse records a separately current use only when the cited exact evidence, assurance, architecture, narrative, or publication claim or relation is already shown to obtain: the cited rule supplies the applicable criterion and current facts or evidence satisfy it. The classifier alone makes none of those uses obtain. One selected relation occurrence may also support a separate use without becoming two occurrences. For example, one exact cross-member relation may support an evidence use only when the cited evidence rule and current facts support the exact use claim; its transformation-flow participation and subjectUse=evidence neither duplicate the occurrence nor make the evidence claim obtain.

For a selected network mapping, resolve NetworkCrossFlowRelationRowRef to exactly one row in its named current record edition. Then require that row, the relation-reference episteme and the direct occurrence to agree on exact occurrence, kind, predicate-definition source, optional signature, participant order, endpoint members, positions and bindings. The endpoint set adds no relation and makes none obtain; it preserves how the already-obtaining occurrence reaches admitted transformation positions.

A pattern identifier or reference is not a U.MethodDescription. A relation signature is carried only when the exact declaration exists and the replay needs it; citation does not make every use signature-dependent.

#Connections to independently identified neighboring values

E.18.3 mints no universal neighboring-value relation. A neighboring Method, plan, Work, evidence, assurance, gate, decision, architecture, narrative, publication, evaluation, or currentness value must be independently identified. A claim about its kind, current status, or use obtains only when current facts or evidence satisfy the criterion supplied by the applicable definition, constraint, predicate, test, evidence rule, or assurance rule. A Method contributes its reusable way of doing and applicability or bounds; a MethodDescription may state that content, but any truth, result, evidence, assurance, or Work claim about using it still needs its separate applicable rule and current basis. A positive connection exists only through an exact already-obtaining relation. A stronger neighboring claim states its concrete contribution in ordinary content-bearing language; an exact content identity is added only when that identity changes the selected use.

Use this display row when a reader must recover the connection:

neighboringValueUseRow:
  admittedTransformationPositionLocator: exact CGUSPositionLocator already used by this E.18.3-qualified structure
  neighboringValueKindRef
  neighboringValueRef
  connectionQuestion: exact stated question
  exactSupportingRelationOccurrenceRef
  supportingRelationReferenceEpistemeRef?: ordinary C.2.1 episteme from 4.0a
  connectionRationaleClaimRef
  concreteContribution?: ordinary content-bearing statement of what the neighboring content contributes; never a bare category label
  relevantPatternRef?: only when it locates that content

connectionQuestion is one exact free-text question, not a code, kind, relation, or closed question-type set. Non-exhaustive examples include questions about basis dependency, a result, a governing constraint, or a comparison. A basis-dependency question creates no obligation. A result question is positive only after the exact result entity or relation and what it is a result of or for are recovered. A governing-constraint question needs the exact current constraint claim or occurrence. A comparison question needs its comparator, participants, scope and exact comparison definition or test; juxtaposition supplies none. Every stated question still requires an exact supporting relation. Direction, participant order, applicability, occurrence identity, dependence and currentness come from its predicate definition, exact declaration when replay needs it, and current facts, not from the question wording. When a stronger neighboring claim is made, concreteContribution states what the content actually does—for example, defines a term, constrains a claim, supplies a predicate or test, describes a Method's way of doing, or supplies an evidence or assurance rule. Those forms are non-exhaustive verbs, not field values; definition, test, or method alone cannot fill the field. relevantPatternRef is only a locator. An exact claim-bearing episteme, ClaimGraph, edition, or other content ref is required only when that identity changes the selected stronger use. Neither field creates a relation.

An ordinary stop uses stopCondition; reconsideration uses reconsiderationConditions[] to name the condition claim, affected structure and next question, with relevantPatternRef only when cited content supplies a needed contribution. Neither creates a receiver or connection relation. If the supporting relation is missing, keep the neighboring values separate and record the attempted question. Use the A.6.RCD missing-governor result only when no applicable relation kind or predicate is available for the exact participants and question; otherwise return unresolved-facts, false-predicate or missing-binding. Recommendation, intended realization, rationale text, common EntityOfConcern and graph adjacency are not substitutes.

#Ordinary provisional explanation and admitted slice

Before the selected A.22 structure passes admission and the E.18.3 membership condition, a path fragment, flow card, worked example, or first-use account may remain an ordinary provisional explanation. It can name the concrete subject, recognizable places or states, proposed relations, possible continuations, and the missing fact or constraint without asserting a structure, position, or relation occurrence.

When replay, comparison, publication, or another current use needs that narrower account to persist as a claim, constitute one ordinary C.2.1 provisional episteme. Its exact EntityOfConcern is the actual transformation subject, current question, or proposed continuation set, never a not-yet-admitted structure. Its ClaimContent may name the visible candidate places, proposed relations, presentation form, unresolved coordinates, and the exact condition that would resolve each one. The explanation or episteme guides discovery but creates no constituent, structure identity, position, relation occurrence, Method, MethodDescription, plan, Work, or Transformation.

After admission, a separate ordinary C.2.1 demonstrative-slice episteme may teach one admissible traversal. Its exact EntityOfConcern is the same selected CGUS recognized by E.18.3. Its ClaimContent cites exact admitted CGUSPositionLocator values, already-admitted relation-reference epistemes or obtaining occurrence refs, relevant C.33 omissions, alternatives, loop-compression and presentation-ordering claims, admissible and forbidden uses, and the slice return condition. A source provisional episteme is cited only through an exact source, derivation, or viewing-construction relation whose predicate definition supplies the applicable criterion and whose current facts satisfy it, so that the exact use obtains; file history is not such a relation.

Do not infer that demonstrated order is project-work order. If ordered Work is current, use A.15.2 for the plan test and A.3.1/A.3.2 for independently identified Method and MethodDescription claims; the demonstration’s imperative or repeated wording admits none. Do not infer that a demonstrated path is the whole topology. When the selected structure branches, joins, cycles, keeps alternatives live or is partially ordered, record what the slice omits or compresses before relying on it for comparison, architecture, evidence or planning.

A pre-admission card can still help slot discovery. Each candidate position names the subject-domain object or question it concerns, the proposed E.18 position and binding, and the exact admission coordinate still unresolved. Once the A.22 identity, flow case, admitted position mappings, exact relations, constraints, preserved/lost structure and use boundaries are recoverable, admit the structure first and constitute a separate slice second. If later inspection invalidates admission, withdraw the slice claim while retaining any still-truthful provisional claim under its narrower use.

#Admit network-aware demonstration mappings

A network-aware demonstrative slice is post-admission only. First select and verify one E.18.NET-conforming network. Then recover the one selected A.22.CGUS, its E.18.3 transformation-position mapping rows, and every required relation-reference episteme. Only then may the slice use A.22.CGUS networkDemonstrationLocator; the locator supplies no missing member, position, relation, constraint or admission.

For each selectedNetworkPositionMappingRows[] entry, resolve the finite member path hop by hop through exact direct members to its leaf TFS. A FlowPositionRef must name that final TFS. An ExposedFlowPositionRef must name this slice’s selected network and repeat the same complete member path and leaf position; a different network, path or leaf leaves the mapping out. admittedIncludedPositionLocator must be the same exact CGUSPositionLocator already present in the E.18.3 position mapping and the slice’s includedPositionLocators[]. The network ref locates that admitted position; it does not create a copied raw-position list.

For each selectedCrossFlowRelationReferenceRows[] entry, require its NetworkCrossFlowRelationRowRef to name a current record edition whose EntityOfConcern is this slice’s selected network, then resolve exactly one row by occurrence and complete ordered endpoint-binding identity. Pair that row with one relation-reference episteme already cited by this E.18.3-qualified structure and with its matching networkEndpointBindingSets[] entry. Verify occurrence, kind, predicate-definition source, optional signature, participant order, endpoint members, flow positions and bindings by value. If the record describes another network, zero or several rows resolve, any field differs, or the relation reference is not already current, omit the mapping and name the exact missing or ambiguous network, row, position, occurrence, predicate definition or binding.

The complete top-level one-TFS locator is absent from a network slice. FlowValuation, PathSliceId and DesignRunTag remain member- or leaf-local; Work, actual transformations, boundaries and currentness also remain with their exact member and applicable definitions or tests. Member paths are finite and membership is acyclic, while exact cross-flow feedback occurrences may cycle when their predicates and constraints admit them.

Every selected cross-flow relation remains the exact occurrence whose predicate-definition source fixes its kind and participant meanings and whose applicability conditions and current facts show that it obtains. Do not substitute universal creates, produces, uses, input, output, result, handoff or transfer edges. One C.32.CONWAY result may contribute one exact transformer-role-system and transformed-holon architecture-correspondence occurrence as one qualified network row after its occurrence and endpoint bindings are recovered; it never constitutes the network.

A source phrase or graph enters only through an exact source-to-use claim or relation. A separately identified BoundedModelUseStructure participates only when the current assertion or use selects it and its organization changes interpretation of that claim; shared wording, adjacency, or a crossing display is evidence of neither model-use qualification nor crossing.

Positive case. A four-level build-the-builder demonstration follows one finite member path to an already admitted leaf position, maps it to the same included CGUS/E.18.3 locator, cites one exact admitted cross-flow relation-reference episteme, and keeps path slice and tag in one leaf-local row. Near miss. A graph supplies raw positions or an edge label, mixes locator families, duplicates positions, assigns one tag to the network or cites a row without exact bindings; keep it provisional or return the exact missing member, relation, position or binding.

#Boundary

E.18.3 recognizes one selected A.22.CGUS U.Structure; it is not a second transformation ontology or reciprocal narrower structure. That selected CGUS uses one independently identified E.18 substrate branch and its exact positions, bindings, and already-obtaining occurrences; the substrate is not the selected CGUS. The selected structure is not a workflow, Method, MethodDescription, WorkPlan, performed Work, actual Transformation, mathematical graph, publication, evidence relation, gate decision, architecture decision, or architecture description. It organizes independently identified constituents, already-obtaining relations, and constraints for one transformation-flow unfolding use.

A graph, record, filled table, demonstration, imperative, selected continuation, recommendation, or intended realization is evidence of neither the A.22 identity nor the E.18.3 condition. It admits no MethodDescription or Work. A.3.2, A.15.1, A.3.4 and A.15.PROD supply the applicable membership or occurrence tests; every relation claim still needs its exact predicate definition, applicability conditions and current facts.

#Replay and change localization

Replay one use from the selected CGUS's exact four A.22 identity discriminators, the independently identified E.18 substrate branch and ref, transformation subjects, admitted position mappings, exact selected relation occurrences and relation-reference epistemes, applied constraint claims with their tests and current facts, any E.18 guard events with their gate-assignment facts, exact supporting relations to neighboring values, one-TFS path or valuation refs when current, any post-admission network mappings, preserved structures, C.33 adequacy notes, and ordinary stop and reconsideration conditions. For each continuation, recover the actual condition branch rather than inferring its type from a guard label. For every stronger neighboring claim, state in ordinary language what the neighboring content actually contributes: a definition, constraint, predicate, test, evidence rule, or assurance rule may supply its criterion, while a Method contributes a reusable way of doing and applicability or bounds and leaves every stronger result or support claim to a separate rule and current basis. Record exact content identity only when that identity changes the selected use.

Localize changes by the object they affect. A changed relation occurrence, predicate definition, participant, or current fact reopens its relation-reference episteme and dependent continuations. A changed applied-condition test or fact reopens that claim and its dependent continuations. A changed E.18 guard event or aggregation-assignment fact reopens that event branch and its E.18/A.21 gate account. A changed neighboring value, concrete contribution, or supporting relation reopens only that use row. A changed path or valuation reopens only dependent one-TFS slices and demonstrations. A changed network member, path, exposure, row, or endpoint binding returns first to the E.18.NET membership and mapping tests and then to dependent mappings. Changed omitted structure reopens its C.33 episteme. Source edition, source-use, freshness, telemetry, and decay use the G.11 currentness tests; E.18 supplies only one-TFS slice-local refresh.

Re-evaluate E.18.3 qualification when its flow case, position mapping or use claim changes. Reidentify the selected U.Structure only when one of the four A.22 discriminators changes; a changed description, demonstration, valuation, path slice, local tag or E.18.3 qualification result does not by itself create another structure.

#Archetypal Grounding — Worked Slices

Ordinary first use — heat-treatment card. A practitioner reviewing the flow card for GearBlank@Lot-14 marks “soak complete” and “quench candidate,” writes “quench remains an admissible continuation only when the measured soak state is within the allowed range,” and asks whether the card may show that continuation or which fact or constraint is missing. If the measured-state fact or range rule is unavailable, the useful result is a provisional explanation naming that gap. The team may use it to correct or discuss the card and stop; it authorizes no Work and asserts no C.2.1 episteme, A.22 structure, E.18 position, applied constraint claim, E.18 guard event, or relation occurrence. Continue to formal recovery only when the team must qualify, compare, publish, or rely more strongly on the structure.

Candidate-set replay entry. When the team must compare or publish the candidate-set repair structure, name one proposed selected-structure use, CandidateSetComparisonBasis@Review-2026-07 and its kind, then describe candidate ReferenceEditionChangePosition and ComparisonRecalculationPosition plus the proposed dependency ComparisonDependsOnAdmittedEdition. Because this use needs a replayable claim, constitute an ordinary C.2.1 provisional episteme whose EntityOfConcern is that comparison-basis question. Its ClaimContent names the G.11 currentness test and A.19.CPM comparison rule as needed contributions and states that the A.22 identity, exact E.18 bindings, and dependency occurrence remain unresolved. This prevents a stale-edition comparison from looking current without asserting a structure, typed position, or relation prematurely.

P2W carry-through. Accepted problem-side records may name distinctions, constraints and unresolved relation positions that guide later Method selection, planning, Work, interpretation and reconsideration. E.18.3 may organize independently current objects only after the selected A.22 structure, E.18 position bindings and direct relations are recovered. It does not authorize launch or performed Work, does not admit any MethodDescription from intended use, and does not replace E.18.1 carry-through.

Recursive build-the-builder demonstration. After a four-level network is selected and verified under E.18.NET and the relevant E.18.3 position mappings and relation-reference epistemes are current, a demonstrative slice follows one finite member path to an already admitted leaf position. The network mapping points to the same included CGUSPositionLocator, and every cross-member row cites an already-current relation-reference episteme with matching participant positions and bindings. The leaf path slice and tag stay in its member-local row. The cross-member relation is recovered from its exact ordered endpoint bindings in different selected network members; an E.18 GateCrossing would remain outside the relation reference. Before those facts are recovered, the same graph remains a provisional episteme rather than a network-aware slice.

Complete compact high-reliance case — edition-current comparison basis. Suppose the following exact objects, facts, and occurrences have already been identified for one replayable comparison use. The condition branch is one applied claim; no E.18 guard event or independently defined guard relation is asserted.

selectedCGUSRef: EditionComparisonUnfolding@Review-2026-07
A22IdentityBasis:
  selectedConstituentRefs[]:
    ReferenceEditionChangeConstituent@Review-2026-07
    ComparisonRecalculationConstituent@Review-2026-07
  selectedObtainingRelationOccurrenceRefs[]:
    ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2
  appliedConstraintClaimRefs[]:
    - claimRef: ReferenceEditionCurrentForComparison@ReferencePublicationEdition-v2
      predicateOrTestRef: G11-ReferencePublicationEditionCurrentTest@Review-2026-07
      currentFactOrEvidenceRefs[]:
        ReferencePublicationEdition-v2-IsAdmitted@Review-2026-07
        ReferencePublicationEdition-v2-IsNotDeprecated@Review-2026-07
  namedSelectionUseFrame:
    questionOrAction: may the v2 edition be used as the current comparison basis?
    forbiddenOverread: no displayed order, gate decision, MethodDescription, plan, Work, or comparison result follows
flowCase: oneTFS
transformationFlowStructureRef: CandidateSetRepairTFS@Review-2026-07
transformationSubjectRows[]:
  - subjectRef: CandidateSetComparisonBasis@Review-2026-07
    subjectKindRef: U.Episteme
transformationPositionMappingRows[]:
  - admittedCGUSPositionLocator: EditionComparisonUnfolding@Review-2026-07 / ReferenceEditionChangePosition / ReferenceEditionChangeConstituent@Review-2026-07
    flowPositionRef: CandidateSetRepairTFS@Review-2026-07 / ReferenceEditionChangeFlowPosition
    exactPositionBindingRef: ReferenceEditionChangeToEdition-v2Binding@Review-2026-07
  - admittedCGUSPositionLocator: EditionComparisonUnfolding@Review-2026-07 / ComparisonRecalculationPosition / ComparisonRecalculationConstituent@Review-2026-07
    flowPositionRef: CandidateSetRepairTFS@Review-2026-07 / ComparisonRecalculationFlowPosition
    exactPositionBindingRef: ComparisonRecalculationToBasisBinding@Review-2026-07
continuationConditionBranch: appliedConstraintClaim  # Plain recovery discriminator, not a kind
relationReferenceEpistemeRefs[]:
  - epistemeRef: ComparisonBasisDependsOnEditionReference@Review-2026-07
    entityOfConcernRef: ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2
    effectiveReferenceSchemeRef: CandidateSetRepairReferenceScheme@Review-2026-07
    claimContent:
      selectedCGUSRef: EditionComparisonUnfolding@Review-2026-07
      exactRelationOccurrenceRef: ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2
      exactRelationKindRef: ComparisonBasisDependencyRelationKind@Review-2026-07
      predicateDefinitionRef: ComparisonBasisDependsOnEditionPredicate@Review-2026-07
      exactParticipantRefsInPredicateOrder[]:
        ReferencePublicationEdition@v2
        CandidateSetComparisonBasis@Review-2026-07
      currentFactOrEvidenceRefs[]:
        ReferencePublicationEdition-v2-IsAdmitted@Review-2026-07
        ComparisonBasisPinsReferencePublicationEdition-v2@Review-2026-07
neighboringValueUseRows[]:
  - admittedTransformationPositionLocator: EditionComparisonUnfolding@Review-2026-07 / ComparisonRecalculationPosition / ComparisonRecalculationConstituent@Review-2026-07
    neighboringValueKindRef: U.Episteme
    neighboringValueRef: ReferencePublicationEdition@v2
    connectionQuestion: which admitted edition is used by this comparison basis?
    exactSupportingRelationOccurrenceRef: ComparisonBasisUsesReferencePublicationEdition@v2
    connectionRationaleClaimRef: ComparisonBasisPinsReferencePublicationEdition-v2@Review-2026-07
    supportingRelationKindRef: ComparisonBasisSourceUseRelationKind@Review-2026-07
    predicateDefinitionRef: ComparisonBasisUsesReferencePublicationEditionPredicate@Review-2026-07
    exactParticipantRefsInPredicateOrder[]:
      CandidateSetComparisonBasis@Review-2026-07
      ReferencePublicationEdition@v2
    currentFactOrEvidenceRefs[]:
      ComparisonBasisPinsReferencePublicationEdition-v2@Review-2026-07
preservedTransformationStructureRefs[]:
  EditionToComparisonDependencyStructure@Review-2026-07
stopCondition: stop stronger use if the edition-current claim, dependency occurrence, either binding, or source-use occurrence is not current
reconsiderationConditions[]:
  - conditionClaimRef: ReferencePublicationEditionChangedAfter-v2@Review-2026-07
    affectedStructureRef: EditionComparisonUnfolding@Review-2026-07
    nextQuestion: does the comparison basis still use an admitted current edition?
    relevantPatternRef: G.11, because its currentness test is used

This is complete for the bounded high-reliance question it asks: two admitted positions, one dependency occurrence with one relation-reference episteme, one applied-constraint branch with its test and current facts, one neighboring source-use occurrence anchored at the admitted comparison-recalculation position with its exact rationale claim, and one preserved transformation structure are recoverable by value. ComparisonBasisDependsOnEditionPredicate@Review-2026-07 makes the current comparison basis depend on the admitted edition, and the ordered participants fix the direction from edition to basis; no separate functional label is needed. The neighboring row makes no stronger contribution claim, so it carries no concreteContribution. The applied claim remains a claim. It is not inserted into relationReferenceEpistemeRefs[] and is not redescribed as an E.18 guard event.

Partial candidate-set recovery display. The larger four-position account below preserves the broader teaching slice but intentionally leaves several exact values unresolved. It is a scaffold for recovery, not a worked conformance proof:

selectedCGUSRef: CandidateSetRepairUnfoldingStructure@Review-2026-07
A22IdentityBasis:
  selectedConstituentRefs[]: exact edition, comparison, retained-set and decision-use constituents
  selectedObtainingRelationOccurrenceRefs[]:
    ComparisonDependsOnAdmittedEdition
    CandidateSetUpdateDependsOnComparison
  appliedConstraintClaimRefs[]:
    EditionAdmissionGuard       # applied-constraint branch; legacy label does not make it a relation or event
    ComparisonBasisChangeGuard  # applied-constraint branch; legacy label does not make it a relation or event
  namedSelectionUseFrame:
    questionOrAction: decide which repair continuation remains admissible
    forbiddenOverread: no table order, MethodDescription, plan, Work, gate or decision follows
flowCase: oneTFS
transformationFlowStructureRef: CandidateSetRepairTFS  # independently identified E.18 substrate; not selectedCGUSRef
transformationSubjectRows[]:
  CandidateSetComparisonBasis@Review-2026-07, U.Episteme
transformationPositionMappingRows[]:
  ReferenceEditionChangeLocator -> unresolved exact CandidateSetRepairTFS FlowPositionRef and binding
  ComparisonRecalculationLocator -> unresolved exact CandidateSetRepairTFS FlowPositionRef and binding
  CandidateSetUpdateLocator -> unresolved exact CandidateSetRepairTFS FlowPositionRef and binding
  DecisionRepairLocator -> unresolved exact CandidateSetRepairTFS FlowPositionRef and binding
continuationConditionBranches[]:
  EditionAdmissionGuard: appliedConstraintClaim
  ComparisonBasisChangeGuard: appliedConstraintClaim
relationReferenceEpistemeRefs[]:
  ComparisonDependsOnAdmittedEditionReference@Review-2026-07
  CandidateSetUpdateDependsOnComparisonReference@Review-2026-07
neighboringValueUseRows[]: unresolved exact G.2 source-use, G.11 currentness, A.19.CPM comparison, C.18 retained-set, and C.32.PAD repair rows
pathIds[]: CandidateSetRepairFlow
pathSliceIds[]: EditionChangeToDecisionRepairSlice
preservedTransformationStructureRefs[]:
  EditionToComparisonDependencyStructure
  ComparisonToCandidateSetDependencyStructure
structureInformationAdequacyNoteRefs[]:
  CandidateSetRepairTeachingOmissionNote under C.33
stopCondition: stop stronger use when an A.22 discriminator, position binding or selected relation is not current
reconsiderationConditions[]:
  - conditionClaimRef: exact claim that the admitted reference-publication edition changed
    affectedStructureRef: CandidateSetRepairUnfoldingStructure@Review-2026-07
    nextQuestion: does the A.19.CPM comparison basis or retained set change?
    relevantPatternRef?: G.11, because it supplies the currentness test
  - conditionClaimRef: exact claim that the retained candidate set changed
    affectedStructureRef: CandidateSetRepairUnfoldingStructure@Review-2026-07
    nextQuestion: does the C.32.PAD repair decision need reconsideration?
    relevantPatternRef?: C.18, because it defines retained-set stewardship
demonstrativeSliceRef:
  separate post-admission C.2.1 episteme for CandidateSetRepairTeaching

The unresolved position refs and bindings, the full ClaimContents and current bases of both dependency references, the tests and current facts for both applied claims, and every neighboring-value row must be recovered before this larger account can pass the checklist. Neither applied claim belongs in relationReferenceEpistemeRefs[]. After those values and the C.33 omission and reconsideration conditions are recoverable, the demonstration ref may name a separate episteme about the same selected structure.

Local edition-relation repair. [G.11](/generated/patterns/G.11) admits ReferencePublicationEdition@v2 while ComparisonDependsOnAdmittedEdition still references v1. Keep independently unchanged constituents, positions, path and path-slice identifiers, preserved structures, and reconsideration conditions. Re-evaluate the relation under its predicate definition and current facts, replace the selected occurrence only if the v2 predicate obtains, and then re-evaluate EditionAdmissionGuard explicitly as an applied constraint claim under its test and current facts. Reopen the A.19.CPM comparison use only if its basis changed, C.18 only if the comparison result changed, and C.32.PAD only if that retained-set change affects the current decision. If the selected occurrence changes, the A.22 relation discriminator changes and the selected structure must be reidentified; mere publication wording or a new relation-reference episteme does not do so.

Connected-box proxy failure. A team reports that every flow-card box is connected and adds low-value edges until path coverage reaches its target. The relation count rises, condition labels no longer distinguish applied claims, E.18 guard events, and actual relation occurrences, stale dependencies remain unrepaired, and unsupported neighboring connections increase. Edge count, labels, and path coverage describe the expression only. Remove edges without exact occurrences and predicate definitions, recover each continuation's actual condition branch, evaluate whether practitioners select the correct continuation and smallest repair, and use [E.13](/generated/patterns/E.13) when display coverage substitutes for those outcomes.

Architecture P2S projection. A P2S flow card includes architecture-relevant problem pressure, unknown or selected structures, synthesis positions and actual-structure feedback. If one selected CGUS satisfies E.18.3, cite its exact E.18 positions and relations. [C.32.P2S](/generated/patterns/C.32.P2S) defines and constrains selected and expected epistemic structures and their exact use; realization Work and actual world-side structures remain separate. C.30.TFS-REL supplies the architecture-use rule and [C.32.PAD](/generated/patterns/C.32.PAD) supplies the architecture-decision test. One exact [C.32.CONWAY](/generated/patterns/C.32.CONWAY) correspondence may be one qualified E.18.NET row, never the whole network.

Physical workpiece transformation. A heat-treatment unfolding use concerns GearBlank@Lot-14, independently admitted as a project U.Holon, and selects exact E.18 positions for load, soak, quench, and hardness evaluation. QuenchAdmittedAfterSoakRange is an applied condition claim only when its range test and current measured-state facts are recoverable; it is not thereby a relation occurrence or E.18 guard event. If an exact USM.CompareGuard or USM.LaunchGuard failure is current, recover that event and its gate-assignment facts separately. Furnace loading and quenching must pass the applicable A.15 plan or dated-Work test; each actual heat-treatment change must pass A.3.4; production, inception, or completion uses the A.15.PROD tests; hardness uses the applicable measurement, evaluation, and evidence rules. A flow card can expose alternatives before execution without claiming that Work occurred.

Clinical transformation planning. A treatment-adjustment unfolding use concerns Patient@Case-17, independently admitted as a U.System, and selects assessment, intervention-candidate, contraindication, observed-state, and reconsideration positions. A contraindication condition remains an applied clinical claim with its test and current facts; a cited E.18 guard failure remains an event with its gate-assignment facts; and the one exact observed-state relation changes admissibility only when its independently defined kind and occurrence obtain. The selected structure does not authorize treatment, show that evidence is sufficient, replace clinical judgement, admit a MethodDescription, or show that an intervention occurred; those claims require the applicable clinical DPF, permission, Work, evidence, and gate definitions or tests plus the current facts or evidence that satisfy them.

Formal flow-expression boundary. A team expresses the candidate-set repair use as a directed graph or DCR model to ask whether DecisionRepairPosition is reachable after EditionAdmissionGuard. The expression may preserve the dependency topology and a condition label plus the queried path, but it does not decide whether that condition is an applied claim, an E.18 guard event, or an independently defined relation occurrence. It also loses neighboring claims already shown to obtain, their concrete contributions, C.33 omissions, and currentness semantics unless those are separately mapped. Use [E.18.2](/generated/patterns/E.18.2) for the mathematical description and [C.29](/generated/patterns/C.29) for its declared use, preserved/lost structure, and stop. Positive reachability alone shows neither the condition's ontic type, currentness, retained-set validity, decision repair, Work order, nor selected-structure identity.

Reference-currentness repair. A one-TFS path slice may depend on an admitted publication edition, a [G.2](/generated/patterns/G.2) source-use relation, a source pack or a telemetry window. E.18 supplies slice-local flow refresh. G.11 supplies the tests for source currentness, decay, edition shift, deprecation, reship and no-change claims. Connect these values only through exact obtaining occurrences and their predicate definitions, and reopen the smallest dependent use; do not create a combined currentness-refresh value.

#Bias-Annotation

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them — Repairs

#Consequences

This profile lets E.18 keep its strength without swallowing every route-shaped pattern. P2W, P2S, agent-loop, gate, evidence, architecture, and currentness cases may use the same selected A.22 structure and exact transformation-flow relations. Each stronger neighboring claim obtains only when current facts or evidence satisfy its applicable definition, constraint, predicate, test, evidence rule, or assurance rule. A Method may contribute a reusable way of doing and its applicability or bounds, but any claim that using it produces, supports, evaluates, evidences, or assures a result remains separately testable under its own rule and current basis.

The cost is explicit recovery only when the current use claims E.18.3 qualification, comparison, publication, or stronger reliance. A selected CGUS qualifies for E.18.3 only when its E.18 or E.18.NET case, subject rows, admitted position mappings, exact selected occurrences, and any applied-claim, E.18-event, or independently defined relation condition branches are discriminated and recoverable together with preserved/lost structure, concrete neighboring contributions, and reconsideration conditions. Before that, the visible card or explanation remains provisional; constitute a C.2.1 episteme only when its narrower claim must persist or be replayed, and constitute a separate demonstrative episteme only after admission.

The benefit is change locality. A changed demonstration, valuation, path slice or tag usually changes only that use; it does not reidentify the selected structure. A changed selected constituent, occurrence, applied constraint or named selection-use frame changes an A.22 discriminator and therefore requires a different structure selection.

#Rationale

The design follows the same principle as E.18: transformation-flow structure is structure, not the whole work process. Constraint-governed unfolding adds a next-use concern—how one selected structure exposes admissible continuations while protecting the differences among structure, description, Method, MethodDescription, plan, Work, transformation, production, evidence, gate, decision, architecture, publication, E.18 slice-local refresh and G.11 currentness.

E.18.3 stays deliberately thin. It does not create a reciprocal specialization object or universal connection relation. It recognizes one A.22-selected U.Structure when that CGUS uses exact positions, bindings, and already-obtaining occurrences from one independently identified E.18 substrate branch and its current transformation-flow constraints support the unfolding use. It uses ordinary C.2.1 epistemes only to make that qualification and its demonstrations replayable.

#SoTA-Echoing

As of 2026-07-11, OCPQ is the current research comparator for typed multi-object constraint structure, while Modelica 3.7 and Dyad 3.1.0 are current engineering comparators for relation-first models separated from analyses and execution. The older CMMN, Declare, DCR, and artifact-centric rows supply lineage. These source decisions changed 4.0 by requiring exact typed relations before continuation, 4.1 by keeping independently identified neighboring values and separately supported claims explicit, 4.2 by preserving graph-shaped alternatives behind a linear demonstration, and the physical case by separating structure from work and analysis. Reopen the adoptions when object-centric constraint methods change object-relation treatment, model languages change model-analysis separation, or use evidence shows that these distinctions no longer prevent workflow, query-result, or execution-artifact overread.

#Relations

Specializes: the A.22.CGUS use of one selected U.Structure when the same exact constituents, selected obtaining relation occurrences, applied constraints, and named selection-use frame use exact positions, bindings, and obtaining occurrences from one independently identified E.18 substrate branch and satisfy the transformation-flow unfolding condition. E.18.3 creates no second structure or ambient context identity, and no substrate ref resolves to selectedCGUSRef.

Builds on: E.18 for independently identified one-TFS substrates, positions, internal U.Transfer occurrences, valuations, paths, slices, and parent-relative SubflowRef; E.18.NET for independently identified network substrates, finite member paths, exposed positions, and exact obtaining cross-member occurrences; A.22.CGUS for the separate selected-CGUS identity, position locators, provisional/description/demonstrative episteme separation, and mutually exclusive post-admission locator families; A.3.4, A.22, and E.17 for transformation, structure, and publication discipline.

Coordinates with: E.18.1, C.32.P2S, C.30.TFS-REL, C.32.CONWAY, E.23, C.18, C.19, G.5, A.15, A.15.PROD, A.10, B.3, A.20, A.21, A.6.3.NAR, exact source-use patterns and G.11. A network demonstration consumes only already-current E.18.3 position mappings and relation-reference epistemes; one C.32.CONWAY occurrence can fill at most one qualified network row.

Does not replace: the definitions, constraints, predicates, membership or occurrence tests, evidence rules, and assurance rules governing Method, MethodDescription, Work, transformation, production, evidence, assurance, gate, architecture, decision, publication, mathematical-lens, source-use, E.18 slice-local refresh, or G.11 currentness claims. Nor does it replace a Method's reusable way of doing and applicability or bounds. A Method or MethodDescription supplies no truth, result, evidence, or assurance criterion merely by being cited; any such stronger claim retains its separate applicable rule and current basis. A pattern ref only locates content, and a contribution-form label does not state that content; exact content identity is required only when it changes the selected use. Pattern refs, selected continuations, imperative wording, graph adjacency and intended realization admit none of those objects.

#E.18.3:End

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