E.18.3 - Constraint-Governed Transformation-Flow Unfolding Structure

Type: E.18 transformation-flow specialization of A.22.CGUS Status: Stable Normativity: Normative unless explicitly marked informative

E.18.3:0 - 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, condition, dependency, crossing, or connection changes the continuation question for the thing being transformed. E.18.3 membership requires the A.22 identity, CGUS locus bindings and potential topology, and one of the three E.18 substrate cases with its flow positions, bindings, and obtaining occurrences. The current continuation result is evaluated separately. Description loss, C.33 notes for a declared architecture use, publication, and stronger neighboring claims are added only for uses that need them.

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 A.22 identity, CGUS locus bindings and potential continuation rows, the E.18 or E.18.NET positions and bindings, obtaining relations, applied constraints, and current continuation judgements. Add replay fields, C.33 loss notes for a declared architecture use, publication material, or downstream assurance only when that named use needs them. Here move is Plain wording for the current action, not a universal kind or relation; a proposal, selection result, or formalized description does not establish that the proposed action was performed.

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.

E.18.3:1 - 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-position bindings. A.22.CGUS supplies the broader constraint-governed structure. E.18.3 answers the narrow question: when does that CGUS use one E.18 substrate’s positions, bindings, and obtaining occurrences in its potential continuation topology? Current continuation results and neighboring stronger claims remain separately testable.

E.18.3:2 - 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 A.22-selected structure, its CGUS-local loci and potential topology, the correct E.18 or E.18.NET case, typed transformation subjects, flow-position mappings, and obtaining occurrences. The case- and time-indexed continuation result separately cites each candidate, its applicable test or obtaining-relation basis, case inputs, facts or evidence, dependent occurrences, window, and outcome. Description adequacy and stronger uses are separate decisions.

E.18.3:3 - Forces

E.18.3:4 - 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[]:
  admittedCGUSLocusBindingRef
  flowPositionRef
  exactPositionBindingRef
continuationJudgementResultRefs[]              # one result per candidate, case, and window
currentContinuationSetResultRef                # enabled, disabled, unknown, and error sets
appliedConstraintClaimRefs[]?                  # each condition basis retains its test, applicability, case inputs, and facts
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-basis branches remain different objects. An applied condition claim keeps its predicate or test, applicability, case inputs, and facts. An E.18 guard-failure event keeps its gate-assignment facts. A relation reference resolves only an independently obtaining relation occurrence. Each candidate’s ContinuationJudgementResult cites the branch it actually uses and records enabled, disabled, unknown, or error; the current-set result aggregates those candidate results without changing structure membership.

Paths and demonstrations remain different. PathId, PathSliceId, FlowValuation, and FlowPositionRef stay with one E.18 TFS. A post-qualification demonstrative slice is a separate C.2.1 episteme about the CGUS. Before qualification, a card or explanation remains about the actual subject, question, or proposed continuation set and need not be materialized as an episteme unless persistence or replay requires it.

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. State captured, expected-but-uncaptured, lost and hidden structure for the declared use. Use exact C.33 epistemes for this account when carrier loss affects a declared architecture use. 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.

E.18.3:4.0 - 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 use must assert E.18.3 qualification, compare or publish the structure, or support a stronger downstream claim. It preserves the membership and current-result distinctions; 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 judging a candidate. Keep an applied condition claim with its test, applicability, case inputs, and facts; keep a GuardFail as an E.18 event with its E.18/A.21 assignment facts; and use a relation-reference episteme only for an independently defined obtaining relation occurrence. For each candidate, record the dependent selected occurrences, window, outcome, and reason in a ContinuationJudgementResult, then derive the current continuation set. Carry a relation signature only when declaration-level replay needs it.
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 the ordinary stop and reconsideration conditions. For a post-qualification description or demonstration, state preserved or omitted structure and add C.33 only when carrier loss affects a declared architecture use. Choose exactly one complete locator family for a one-TFS or network demonstration, or neither for a generic slice.
7. If an A.22 discriminator, CGUS locus binding or potential-continuation row, E.18 flow binding, or direct relation is missing, do not claim E.18.3 membership. If only a fact or test result for the current case is missing, keep the structure and return that candidate as unknown. If only a description-loss or stronger-use value is missing, narrow that use rather than demoting the structure.

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.

E.18.3:4.0a - 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
  exactSupportingUseClaimOrRelationRef?: exact separately current claim or relation that uses this occurrence
  supportingUseKindOrPredicateRef?: exact kind or predicate for that claim or relation
  receivingUseRef?: only when it distinguishes the selected use
  networkEndpointBindingSets[]?:
    networkCrossFlowRelationRowRef: exact E.18.NET NetworkCrossFlowRelationRowRef
    endpointRows[]:
      relationParticipantPositionRef
      endpointMemberRef
      endpointLeafTFSRef
      endpointFlowPositionRef

The exact relation kind, predicate definition, ordered participants, current basis, and any network endpoint bindings carry the transformation-flow meaning; 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.

The optional supporting-use fields appear only when an independently current exact claim or relation says how the cited occurrence is used. That claim or relation keeps its own kind or predicate, current basis, and receiving use when the receiving use distinguishes it. No broad evidence, assurance, architecture, narrative, publication, gate, decision, comparison, currentness, or other use label makes the stronger use obtain. One selected relation occurrence may support several separately established uses without becoming several occurrences; cite each exact claim or relation that matters rather than extending a classifier.

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.

E.18.3:4.1 - 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:
  admittedCGUSLocusBindingRef: CGUSLocusBinding already mapped by this E.18.3-qualified structure
  neighboringValueKindRef
  neighboringValueRef
  connectionQuestion: exact stated question
  exactSupportingRelationOccurrenceRef
  supportingRelationReferenceEpistemeRef?: ordinary C.2.1 episteme from 4.0a
  connectionRationaleClaimRef
  exactStrongerUseClaimOrRelationRef?: only when a separately governed stronger use is current
  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 use is current, exactStrongerUseClaimOrRelationRef points to the independently governed claim or relation that establishes it; no broad use category substitutes for that ref. concreteContribution then says what the neighboring 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 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. None of these fields 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 rule can state or test the claim for the exact participants and question; otherwise distinguish missing facts or bindings (missing-information) from a positive test that fails on a sufficient case basis (factually unsupported). A failed positive test alone does not establish the negative. Recommendation, intended realization, rationale text, common EntityOfConcern and graph adjacency are not substitutes.

E.18.3:4.2 - 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. Use the explanation or episteme to guide discovery; any claim that the proposed structure, position, or relation occurrence exists still needs its own identity basis and applicable test.

After qualification, a separate ordinary C.2.1 demonstrative-slice episteme may teach one enabled traversal. Its EntityOfConcern is the same selected CGUS recognized by E.18.3. Its ClaimContent cites established CGUSLocusBinding values, the relevant current continuation judgements, relation-reference epistemes or obtaining occurrence refs, any omissions that matter to this carrier (under C.33 for a declared architecture use), alternatives, presentation claims, admissible and forbidden uses, and the return condition. The slice creates none of those values.

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-qualification card can still help discover candidate CGUS loci and proposed E.18 positions. Name the subject-domain object or question, the proposed flow position and binding, and the missing A.22, CGUS, or E.18.3 membership value. Once those values are established, qualify the structure first and constitute a separate slice only if that presentation must persist. Missing current facts instead produce an unknown candidate result; missing description-loss material narrows only the description.

E.18.3:4.2a - 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 E.18.3 slice add its network demonstration mapping rows; those rows supply no missing member, position, relation, constraint, or admission.

For each selectedNetworkPositionMappingRows[] entry, resolve the finite member path to its leaf TFS. A FlowPositionRef names that TFS; an ExposedFlowPositionRef also repeats this network and the complete path. includedLocusBindingRef must be the same CGUSLocusBinding already present in the E.18.3 mapping and the slice’s includedLocusBindingRefs[]. The network ref maps that binding to a flow position; it creates no copied position or constituent binding.

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 architecture-influence and transformed-architecture correspondence row after its direct 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 established leaf position, maps it to the same included CGUS locus binding, cites an 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 bindings, assigns one tag to the network, or cites a row without endpoint bindings; keep that demonstration provisional or return the missing member, relation, position, or binding.

E.18.3:4.3 - 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.

When a continuation is intended to perform work, apply A.22.CGUS:4.1.1 to its relevant constituent and encompassing conditions. The arrangement may need capabilities and shared resources that no single flow position reveals. Recover Method and Work parthood independently through B.1.5.EW; nested transformation-flow positions and temporal arcs retain their own meanings. Local completion supports the whole result only under the required coordination and result-use conditions. A description that omits those conditions answers a narrower question than whether the whole can be performed.

E.18.3:4.4 - Replay and change localization

Replay A.22 identity, CGUS membership, and E.18.3 membership separately. The first uses the four A.22 discriminators; the second uses local locus bindings and potential continuation topology; the third maps those bindings to one E.18 substrate case and its positions, bindings, and obtaining occurrences. Replay the current set from each candidate’s condition or relation basis, applicability, case inputs, facts or evidence, dependent occurrences, window, outcome, and reason. Description loss and every stronger neighboring claim remain separate uses.

Localize changes by the value they affect. A changed A.22 discriminator can reidentify the structure. A changed CGUS locus binding or potential row reopens CGUS membership. A changed E.18 substrate, flow position, binding, or selected occurrence reopens E.18.3 membership. A changed test, fact, evidence item, guard event, assignment fact, or window reopens only dependent continuation judgements and the current set unless it also changes one of those membership bases. A changed carrier omission reopens the affected description and, for a declared architecture use, its C.33 episteme; a changed neighboring use reopens its own claim.

A changed demonstration, valuation, path slice, local tag, continuation outcome, or enabled-set cardinality does not by itself create another structure. Reidentify the selected U.Structure only when one of its four A.22 discriminators changes.

E.18.3:5 - 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 network and its E.18.3 mappings are established, a slice follows one finite member path to an established leaf position. The network mapping points to the same included CGUSLocusBinding, and every cross-member row cites a relation-reference episteme with matching participant positions and bindings. The leaf path slice and tag stay in its member-local row. Before those facts are recovered, the graph remains an explanation rather than a network-aware slice.

Complete compact high-reliance case — edition-current comparison basis. This replayable comparison has two potential continuations: recalculate with the admitted edition, or stop and replace the edition. The exact objects and occurrences below have already been identified.

selectedCGUSRef: EditionComparisonUnfolding@Review-2026-08
A22IdentityBasis:
  selectedConstituentRefs[]:
    ReferenceEditionChangeConstituent@Review-2026-08
    ComparisonRecalculationConstituent@Review-2026-08
    RecalculateWithV2Continuation@Review-2026-08
    ReplaceReferenceEditionContinuation@Review-2026-08
  selectedObtainingRelationOccurrenceRefs[]:
    ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2
  appliedConstraintClaimRefs[]:
    UseEditionOnlyWhenCurrent@Review-2026-08
    ReplaceEditionWhenCurrentnessFailsOrIsUnknown@Review-2026-08
  namedSelectionUseFrame:
    questionOrAction: may v2 remain the basis for this comparison?
    admissibleAction: judge whether to recalculate with v2 or replace the reference edition for CandidateSetComparisonBasis@Review-2026-08
    stopOrReturnCondition: stop recalculation when the currentness result, dependency occurrence, either flow binding, or source-use occurrence is unavailable; re-evaluate both candidates when the edition or currentness facts change
forbiddenOverread: no displayed order, gate decision, plan, Work, or comparison result follows
constraintGovernedProfileBasis:
  locusBindingRows[]:
    - <EditionComparisonUnfolding@Review-2026-08, edition-change, edition under review, ReferenceEditionChangeConstituent@Review-2026-08>
    - <EditionComparisonUnfolding@Review-2026-08, recalculate, comparison recalculation, ComparisonRecalculationConstituent@Review-2026-08>
  potentialContinuationRows[]:
    - RecalculateWithV2Continuation@Review-2026-08
    - ReplaceReferenceEditionContinuation@Review-2026-08
flowCase: oneTFS
transformationFlowStructureRef: CandidateSetRepairTFS@Review-2026-08
transformationSubjectRows[]:
  - subjectRef: CandidateSetComparisonBasis@Review-2026-08
    subjectKindRef: U.Episteme
transformationPositionMappingRows[]:
  - admittedCGUSLocusBindingRef: EditionComparisonUnfolding@Review-2026-08 / edition-change / ReferenceEditionChangeConstituent@Review-2026-08
    flowPositionRef: CandidateSetRepairTFS@Review-2026-08 / ReferenceEditionChangeFlowPosition
    exactPositionBindingRef: ReferenceEditionChangeToEdition-v2Binding@Review-2026-08
  - admittedCGUSLocusBindingRef: EditionComparisonUnfolding@Review-2026-08 / recalculate / ComparisonRecalculationConstituent@Review-2026-08
    flowPositionRef: CandidateSetRepairTFS@Review-2026-08 / ComparisonRecalculationFlowPosition
    exactPositionBindingRef: ComparisonRecalculationToBasisBinding@Review-2026-08
appliedConstraintClaimRefs[]:
  - claimRef: ReferenceEditionCurrentForComparison@ReferencePublicationEdition-v2
    predicateOrTestRef: G11-ReferencePublicationEditionCurrentTest@Review-2026-08
    applicabilityResult: applicable to the selected comparison basis and ReviewWindow-2026-08
    caseInputRefs[]: [ReferencePublicationEdition@v2, CandidateSetComparisonBasis@Review-2026-08]
    currentFactOrEvidenceRefs[]: [ReferencePublicationEdition-v2-IsAdmitted, ReferencePublicationEdition-v2-IsNotDeprecated]
continuationJudgementResults[]:
  - continuationCandidateRef: RecalculateWithV2Continuation@Review-2026-08
    conditionPredicateOrTestRef: G11-ReferencePublicationEditionCurrentTest@Review-2026-08
    applicabilityResult: applicable to CandidateSetComparisonBasis@Review-2026-08 in ReviewWindow-2026-08
    caseInputRefs[]: [ReferencePublicationEdition@v2, CandidateSetComparisonBasis@Review-2026-08]
    currentFactOrEvidenceRefs[]: [ReferencePublicationEdition-v2-IsAdmitted, ReferencePublicationEdition-v2-IsNotDeprecated]
    requiredPolarity: current
    observedOutcome: satisfied
    dependentSelectedRelationOccurrenceRefs[]: [ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2]
    qualificationWindow: ReviewWindow-2026-08
    result: enabled
  - continuationCandidateRef: ReplaceReferenceEditionContinuation@Review-2026-08
    conditionPredicateOrTestRef: ReplaceEditionWhenCurrentnessFailsOrIsUnknown@Review-2026-08
    applicabilityResult: applicable to CandidateSetComparisonBasis@Review-2026-08 in ReviewWindow-2026-08
    caseInputRefs[]: [ReferencePublicationEdition@v2, CandidateSetComparisonBasis@Review-2026-08]
    currentFactOrEvidenceRefs[]: [ReferencePublicationEdition-v2-IsAdmitted, ReferencePublicationEdition-v2-IsNotDeprecated]
    requiredPolarity: currentness failed or unknown
    observedOutcome: notSatisfied
    dependentSelectedRelationOccurrenceRefs[]: [ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2]
    qualificationWindow: ReviewWindow-2026-08
    result: disabled
currentContinuationSetResult: enabled [RecalculateWithV2Continuation]; disabled [ReplaceReferenceEditionContinuation]; unknown []
relationReferenceEpistemeRefs[]:
  - epistemeRef: ComparisonBasisDependsOnEditionReference@Review-2026-08
    entityOfConcernRef: ComparisonBasisDependsOnEdition@ReferencePublicationEdition-v2
    claimContent:
      predicateDefinitionRef: ComparisonBasisDependsOnEditionPredicate@Review-2026-08
      exactParticipantRefsInPredicateOrder[]: [ReferencePublicationEdition@v2, CandidateSetComparisonBasis@Review-2026-08]
      currentFactOrEvidenceRefs[]: [ComparisonBasisPinsReferencePublicationEdition-v2@Review-2026-08]
neighboringValueUseRows[]:
  - admittedCGUSLocusBindingRef: EditionComparisonUnfolding@Review-2026-08 / recalculate / ComparisonRecalculationConstituent@Review-2026-08
    neighboringValueRef: ReferencePublicationEdition@v2
    connectionQuestion: which admitted edition is used by this comparison basis?
    exactSupportingRelationOccurrenceRef: ComparisonBasisUsesReferencePublicationEdition@v2
    connectionRationaleClaimRef: ComparisonBasisPinsReferencePublicationEdition-v2@Review-2026-08
preservedTransformationStructureRefs[]: [EditionToComparisonDependencyStructure@Review-2026-08]
stopCondition: stop recalculation if the currentness result, dependency occurrence, either flow binding, or source-use occurrence is unavailable
reconsiderationCondition: re-evaluate both candidates when the edition or currentness facts change

This case is complete for its bounded question. The structure has two potential candidates, while the present window enables one. The currentness claim remains a condition claim with a test, applicability, inputs, and facts; it is not inserted into relationReferenceEpistemeRefs[]. If those facts disappear, the recalculation candidate becomes unknown and the replacement candidate is judged under its own condition; the topology and structure do not change merely because the enabled set does. 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 when carrier loss affects a declared architecture use
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 omission and reconsideration conditions are recoverable, the demonstration ref may name a separate episteme about the same selected structure. Use C.33 for the omission account when carrier loss affects a declared architecture use.

Local edition-relation repair. After ReferencePublicationEdition@v2 is admitted, use G.11 to record the edition change; 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 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 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 supplies the architecture-decision test. One exact 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, description omissions (including C.33 omissions for a declared architecture use), and currentness semantics unless those are separately mapped. Use E.18.2 for the mathematical description and 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 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.

E.18.3:6 - Bias-Annotation