E.18.1 - P2W Problem-to-Work Carry-Through
Tech-name:
ProblemToWorkCarryThroughPlain-name: problem-to-work carry-through Type: Architectural pattern (E) Status: Stable Normativity: Normative unless marked informative Placement: Part E -> E.18 child pattern Builds on:E.18Transformation Flow Structure,C.22.2ProblemCard@Context,A.6.0U.Signature,A.6.1U.Mechanism,A.3.1U.Method,A.3.2U.MethodDescriptionmembership,A.3.4actual bounded change, the A.15 work family,A.15.PRODlocal production-claim recovery,A.6.RCDblocker boundary and local-claim dispositions,A.6.RELrelation-occurrence and receiving-use discipline,A.6.Prelational precision restoration,A.6.P.WMRwording-to-relation recovery,C.29,C.16,A.19.CPM,A.19.SelectorMechanism,C.18,C.19,F.8,F.18,F.17,F.9,G.5,G.9,G.11,A.20, andA.21. Purpose: preserve selected distinctions from an accepted problem-side record as method selection, planning, performed work, result interpretation, and return become current.
E.18.1:1 - Problem frame
Use this pattern when an accepted ProblemCard@Context can guide work, but the next FPF use is unsettled. Ask which accepted distinction should shape the next question, which relation and participants that question asserts, and what result or stop is needed before the next action.
Method selection, planning, dated work, actual change, result interpretation, and return remain separate continuations. For each current question, apply the pattern that answers it and carry the result it returns or the reason work on that question must stop.
Distinguish the accepted ProblemCard, the subjects of the questions answered by the cited patterns, and the materials that describe those claims. The accepted ProblemCard is the EntityOfConcern of a materialized P2W note. The note is identified under C.2.1 by its ClaimGraph, the accepted card, and its effective reference scheme; its ClaimGraph names the receiving use and designates a separately identified viewpoint or model-use structure only when the claim uses that object and its organization changes how the receiving claim is interpreted.
Each cited PatternID locates the Solution passage needed for the question about its subject EntityOfConcern. A practitioner or another capable system applies that guidance to the project entity or relation—for example, a System, episteme, Method, Work occurrence, or direct relation. When source wording says role, apply E.10.ROLE before treating it as a local system-role kind, separate System-classification judgment, assignment occurrence, participation or functioning relation, ordinary non-use, or missing-governor case.
The compact note, diagram, plan, trace, and publication are epistemes or publication-side values that describe, constrain, or make those claims inspectable. Later method enactment or dated work can change or preserve a subject EntityOfConcern; improving a P2W note or completing its fields does not establish that subject change, work occurrence, evidence, acceptance, or result.
When P2W helps. Use P2W only when keeping the accepted distinction changes which relation you assert, what result you write, or whether you continue, split, stop, or return. If the relation and result are already settled and another P2W note would add nothing to the decision, apply the pattern whose Solution answers the current question.
E.11.PUA covers a smaller use and may begin without ProblemCard@Context: use one selected pattern for one current practical question. Obtain the smallest useful result that answers the question or state why work on it must stop. That ordinary use may stop there; name a receiving use only when the enclosing P2W continuation or another later use is current.
E.18.1 begins only when the wider work-facing continuation depends on preserving accepted problem-side material. PUA may support one pattern inspection inside a P2W flow, but it does not replace the accepted-problem carry-through.
E.18.1:1.1 - Use this when
- an accepted
ProblemCard@Contextnames a working problem and the team needs a way to choose its next use of FPF toward method, planning, performed work, or result interpretation; - an invariant,
U.Signature(profile=FormalSubstrate),PrincipleFrame, mechanism-position, method-position,A.15.2 U.WorkPlanor plan-item wording cue, performed-work, result-record, or source-currentness cue is present, but the FPF kind or relation to use next is still unsettled; - a transformation-flow structure, mathematical path relation in a graph-shaped description, flow diagram, principle scheme, scenario, functional description, or source publication helps the team think, while the next FPF use still lacks an FPF kind or relation named by value;
- a result artifact, telemetry line, acceptance record, quality-evaluation record, done-state update, feedback pin, or integration claim needs to be unpacked before it can guide the next FPF use.
E.18.1:1.2 - What goes wrong if missed
The team jumps from a convincing problem-side formulation into downstream language without naming the FPF relation being used. The work then looks responsive to the accepted problem, but the next record is unclear, the result phrase becomes too broad, and the team has no basis for deciding which earlier uses to reopen when a measurement or source currentness changes.
E.18.1:1.3 - What this buys
The practitioner gets one concrete next move: keep the accepted claim in view, state the question and participants, apply the pattern that answers it, and use the result it returns. Split several relation claims before applying their patterns. If the relation or needed facts are missing, keep the cue and stop. If a relied-on result changes, reopen only the continuation that used it.
Add the compact note only when another person or later action must replay that path. The accepted problem-side distinction remains useful without becoming hidden permission to start work.
E.18.1:1.4 - Not this pattern when
- there is no accepted problem-side record; use
C.22.2or the problem-side pattern named by value first; - the FPF kind under repair, relation, and record to write are already settled; use the applicable pattern directly;
- the requested output is a local project procedure, schedule, or work-management method; use the relevant work, planning, method, gate, or operational-management pattern;
- the requested record or claim is an evidence case, assurance case, gate record, decision record, architecture description, publication-use claim, or wording-use repair; recover the relation and apply the pattern whose Solution answers that evidence, assurance, gate, decision, description, publication-use, or wording question.
E.18.1:2 - Problem
An accepted problem-side distinction becomes useful when it is ready to guide downstream work or work-planning use. The accepted problem card may expose an invariant, mathematical lens, unresolved functional role cue, mechanism-position candidate, method candidate family, planning constraint, result cue, or changed measurement assumption.
Route unresolved role wording through E.10.ROLE before it affects a continuation; the recovered local system-role kind, classification, assignment occurrence, direct participation or functioning relation, ordinary non-use, or missing governor remains with its own pattern. Without P2W, the team either reduces the accepted problem-side distinction to “we have a solution” or scatters it across several related FPF patterns before preserving it.
First say which accepted claim must affect which decision or use. Then write one ordinary relation-specific question, name its participants, apply the pattern that answers it, and keep that pattern’s result or stop. Add a compact note only when another person or later action must replay the path.
P2W succeeds when the accepted claim, receiving use, concrete question, applicable pattern contribution, and result remain inspectable without turning their use-specific connection into a relation kind or treating a note, diagram, plan, trace, or publication as the subject entity or as proof that work occurred.
E.18.1:3 - Forces
| Force | P2W-preserved content | Pressure to manage |
|---|---|---|
| Problem-side usefulness | An accepted problem-side distinction may guide method, planning, work, or result interpretation. | The team may treat the distinction as a completed downstream claim. |
| Relation-kind precision | The reader states one concrete relation question and uses the pattern whose Solution answers it; P2W adds no relation species. | A diagram, source phrase, or filled note can look like the relation already obtains. |
| Practical readability | First use needs one recognizable claim, concrete question, the pattern contribution that answers it, result, and next move or stop. | Too much boundary prose or mandatory record apparatus can hide the working P2W application. |
| Non-linear use | P2W may skip, branch, split, stop, or reopen continuations in the carry-through structure. | A readable diagram or graph-shaped expression can be mistaken for a prescribed project sequence. |
| Result usefulness | Result phrases often point to artifacts, telemetry, acceptance, measurement, refresh, or unresolved role enactability wording that must pass through E.10.ROLE before use. | One broad result word can hide several different records or relations. |
| Neighboring-content economy | Each cited pattern keeps the definition, test, and result it contributes. | Repeating those patterns’ non-use rules in P2W leaves the same guidance in several places. |
E.18.1:4 - Solution
Local P2W mantra. Use this wording to recall the question behind one working decision. Which P2W continuation, if any, is justified now?
Carry the accepted distinction — ask one relation question — apply the pattern for that relation — keep its result or stop — reopen only the dependent continuation.
| Phrase in the mantra | Identified value |
|---|---|
| Carry the accepted distinction | one accepted ProblemCard claim and the receiving decision or use that would change if the claim changed |
| ask one relation question | one ordinary question with its participants; several independent claims are split |
| apply the pattern for that relation | the pattern whose Solution answers that relation or object question, not a P2W-created relation or a presumed U.MethodDescription |
| keep its result or stop | the result, reduced-use cue or blocker that pattern returned; no generic result token |
| reopen only the dependent continuation | the smallest continuation that relied on a changed problem claim, measurement, source-use/currentness relation or other returned value |
Filled cooling use. ProblemCard@Context PC-FAB-042 says that method comparison must preserve the conserved heat-flow structure. The current decision is whether a mathematical-lens continuation is justified. Ask which structure the proposed lens preserves, which it loses, and where its use stops; apply C.29; keep the returned lens-use result.
If the lens subject, declared use, preservation/loss account or stop is unresolved, keep that C.29 question open and do not advance by wording to method selection, planning or Work.
The wording helps a practitioner recall which question to ask. A claim about a Method, MethodDescription, plan, dated Work, Transformation, CGUS or P2W relation requires identification of that object under its own rule. The five rows below display conditional continuations. The applicable relation determines which one to take.
| Shown continuation | Applicable pattern contribution | Solution use | Expected result | Current condition |
|---|---|---|---|---|
| Carry one accepted distinction. | E.18.1 | Cite the accepted problem-side record, state the one distinction that matters, and say which decision or use needs it. | The accepted distinction and the decision or use it will inform. | The problem-side record is accepted and that decision or use would change if the distinction changed. |
| Ask and recover. | E.18.1 | State the unsettled practical question, name its participants and relation, and locate the pattern that answers it. | One concrete question, relation, participants, and applicable pattern contribution. | A diagram, source phrase, or familiar label has not yet answered the question. |
| Apply the pattern that answers the question. | The pattern recovered in the preceding row. | Apply its Solution while keeping the accepted distinction visible in the concrete method-selection, planning, dated U.Work, actual-change, interpretation, or other claim being made. | The result that answers the question, or that pattern’s stop. | The relation, participants, applicable pattern, and contribution used are recoverable. |
| Continue, branch, or stop. | E.18.1 | Keep one returned result, split results that answer different relation questions, or retain the cue and stop. | One continuation per answered question, or one explicit stop. | One question, several independent questions, or no answerable relation remains. |
| Return locally after change. | The guidance recorded for the earlier use, coordinated through E.18.1. | Reapply that guidance, use the basis it supplied or located with current facts to reassess the earlier claim or result about the independently identified changed value, and return only to the smallest earlier P2W continuation affected by the changed assumption. | A local return with what still carries and what no longer carries stated. | Measurement, source currentness, problem-side content, or another relied-on assumption changed. |
If a selected CGUS already exists, an A.22 demonstrative slice may include this display in its ClaimContent for a declared use. The table itself admits no structure, continuation-row kind, relation occurrence, MethodDescription, plan or Work.
Here and elsewhere in this pattern, move is Plain wording for the current use action or continuation: stating a question, applying the pattern that answers it, keeping its returned result, stopping, splitting, or reopening. In another case it may instead refer to an independently defined recommendation, PlanItem, enabled continuation of a qualified CGUS, dated Work, or actual Transformation. No universal Move object or shared identity connects proposed, chosen, and performed work.
The decision aid below helps the practitioner choose which relation question to answer now. Fill a compact carry-through or replay episteme only when another person or later action must recover the path. The aid shows the accepted claim, concrete question, relation and participants, pattern contribution that answers it, returned result or stop, and the smallest continuation to reopen after a relied-on result changes.
Choose the first of these three levels that lets the current reader act and, when later use requires replay, lets that reader recover the path to the result or stop:
- Ordinary conversational use. State one concrete relation question and its participants, apply the pattern that answers it, use its result or stop, and finish. Write no P2W note when feedback is fast, the use is local, and nobody later needs to replay the path.
- Reliance-bearing use. Add the compact episteme in
4.1when transfer, audit, delayed feedback, expensive reversal, automation, or durable reuse depends on recovering the accepted claim and direct continuation. - Structure-bearing use. Add the selected structure defined and tested by
E.18.3, A.22.CGUS and, for independent members, E.18.NET in4.0bwhen a named use needs that structure’s identification or qualification, or relies on it for comparison, publication or a stronger downstream claim. Section4.0bexplains when an ordinary account of branches and conditions already suffices.
Choose a higher level only when its transfer, audit, delayed-feedback, costly-reversal, automation, durable-reuse or explicit-structure need is present.
Choose only the extension the receiving use needs.
| Material | Modularity status | Boundary |
|---|---|---|
| Accepted claim -> receiving use -> concrete question -> applicable pattern contribution -> result or stop -> split/local return | Stable P2W core | Sections 4.0, 4.0a, and 4.2-4.7 state this interface without copying the cited pattern’s procedure. |
| Compact positive, stop, or replay episteme | Conditional reliance extension | Open only for transfer, audit, delayed feedback, costly reversal, automation, or durable reuse; it records the core result and adds no prerequisite to conversational use. |
| Explicit transformation-flow unfolding structure | Conditional structure extension through A.22.CGUS, E.18.3 and, when applicable, E.18.NET | Open when a named use needs the selected structure’s identification or qualification, or relies on that structure for comparison, publication or a stronger downstream claim; P2W supplies no hybrid or shortened structure schema. |
| Development-loop and DPF didactic branches | Conditional didactic extension | Open only when cheap generation or a fast DPF seed raises one of the concrete questions in 4.1a or 4.1b. Apply the unchanged core to that question and use the Relations map once for an exceptional object; this extension is not a lifecycle, workflow, authority record, or second relation-selection map. |
| Practice naming and publication | Conditional publication extension through F.8, F.18, and F.17 | Open only when a public document, training material, or tool interface must cite the settled E.18.1 practice. Naming adds no core field or result and does not admit MethodDescription membership. |
| Relation obtaining, occurrence identity, reusable signatures, admission, production, evidence, gates, decisions, and other neighbouring doctrine | Handled outside P2W by the pattern whose Solution answers the claim | That pattern returns the applicable result or blocker. P2W cites it and never copies the occurrence, derivation, admission, production, publication, or assurance method. |
No conditional extension may add a mandatory input to ordinary P2W use, change the kind or identity of a result returned by the cited pattern, or mutate the stable core. Omit unused extensions, including their fields.
Assurance scope by use. For a materialized positive episteme, check the accepted ProblemCard edition, carried ClaimGraph slice, decision or use that relies on the result, effective ReferenceScheme, returned result kind and ref, the cited pattern contribution used, and carry-through rationale. Check a separately identified U.Viewpoint episteme or BoundedModelUseStructure only when the claim designates that object and its organization changes how the receiving claim is interpreted.
For a stop use, check that no result was fabricated and that the cue and stop are stated. In both positive and stopped uses, the episteme is about the accepted ProblemCard under C.2.1, not a P2W relation occurrence or RelationSignature.
For practitioner guidance or conformance, verify that a practitioner applying the guidance can obtain the required result or the reason to stop. None of these checks adds Work, transformation, evidence, gate, MethodDescription membership or downstream subject facts.
E.18.1:4.0 - P2W result without a new relation species
An ordinary P2W application is a practitioner move: preserve one accepted problem-side claim, name the receiving decision or use, ask one concrete question per independent relation, and keep only the result or stop returned by the pattern whose Solution answers that question.
Start with the part of the accepted ProblemCard that can change the answer needed for the next decision or action. State what the reader must preserve and why it matters there. Retain the claim’s status and the scope and conditions on which its use depends. For example, an accepted problem formulation can carry a causal hypothesis that needs testing.
Choose the next question from the work that needs the answer. Say what answering it would enable and what would count as enough for that use. If the present need is to choose guidance, an explained selection and its applicability boundary can suffice.
If the next action needs a subject result, such as a plan or a measurement, apply the supplying method to the case and obtain that result or identify the exact gap. Use an adequate existing way directly. If the way itself is missing, use C.39 to find or develop it; E.4.CM guides that construction when it must become a maintained framework contribution. When the next decision depends jointly on how a suitable method becomes available, how a performer gains access or capability, and how the job is supplied, C.32.MWA:4 connects those contributions. For a readiness decision alone, use A.15.5 for the intended job.
Bring the answer back to the receiving decision or action. Explain how the carried claim constrained the question, choice or interpretation of the answer. If the local answer leaves a connection required by the larger task unresolved, keep that connection as unfinished work. A stop can settle the present inquiry while leaving the receiving task dependent on further facts or a still-missing way.
For example, C.22.2:20.1a supplies an accepted ProblemCard about two support-policy clauses that use “complete” for different events. Carry that difference and the policy edition into the question of which event the policy means by completion. Resolve the question through the applicable declaration or interface rule; if that rule is unavailable, retain that gap. The observed difference supports clarification, while the proposed causal connection with reopened cases remains a hypothesis. If both clauses are later shown to mean the same event, return to the problem formulation because that comparison no longer supports the ambiguity claim.
This move introduces no ProblemToWorkCarryThroughRelation@Context, reusable predicate definition, RelationSignature, or P2W relation occurrence.
When transfer, audit, delayed feedback, costly reversal, automation, or durable reuse requires the claim to be retraced, use the C.2.1 episteme in 4.1. Its identity is its ClaimGraph, the accepted ProblemCard@Context as EntityOfConcern, and the effective reference scheme.
The ClaimGraph records the accepted card edition and carried claim slice, decision or use relying on the result, concrete question, applicable pattern reference, contribution used, returned result kind and ref or stop, and why the carried content remains relevant. It designates a separately identified U.Viewpoint episteme or BoundedModelUseStructure only when the claim uses that object and its organization changes how the receiving claim is interpreted; neither becomes another identity discriminator.
These are use-specific claim contents, not SlotSpecs of another relation species; the returned result retains its own kind, relation semantics when applicable, identity, and subject-specific basis.
In each case, participants need a grounded claim and a way to retrace how they reached it. Conversation can supply both on the spot. Transfer, audit, delayed feedback, automation or durable reuse may require someone to retrace it later. None of these uses asks whether repeated P2W relation occurrences are the same individual.
The conversational move, optional positive note, and stop description therefore close those uses without a relation-kind candidate. A.6.RCD, E.24, E.24.UK, A.6.0, and relation-species naming do not open.
If a later use asks whether a P2W relation occurrence persists, recurs, ceases, or participates in another relation, reopen A.6.RCD and obtain the direct subject settlement and admission before declaring or instantiating such a kind.
A positive use closes only when the accepted card and carried slice remain current for the receiving use, the cited pattern has returned its result for that use, and the rationale remains a truthful claim in the note or is directly recoverable in conversation. A preceding P2W note may be cited for replay, but it supplies neither occurrence continuity nor a supporting relation; use each relation’s defining predicate and identity rule. If these conditions fail, correct the value-kind pair, apply the pattern that answers the question, split the claims, or retain a reduced-use cue and stop.
E.18.1:4.0a - P2W Declarative Carry-Through Structure
Use P2W as a declarative interface from one accepted ProblemCard@Context claim to results or stops obtained by applying the patterns that answer its continuation questions. P2W preserves the carried claim and receiving use, states the concrete relation-specific question and its participants when relation-like, cites the applicable pattern, and keeps each result or stated stop on a separate continuation. It defines none of the selected relations or results. Refer to the neighbouring guidance without restating it.
Use the following questions to carry the result or blocker returned by the applicable pattern.
| P2W-local question | Required interface result | P2W disposition |
|---|---|---|
| What accepted problem-side content matters now? | The accepted card edition, carried ClaimGraph slice, and decision or use that will rely on the answer. | Carry only that content. |
| What practical question remains unsettled? | One ordinary relation-specific question that does not presuppose its answer or a new relation kind. | Name the participants, then locate the pattern whose Solution answers it. |
| Which pattern answers that question? | One applicable pattern per independently stated claim. | Keep the question distinct from the pattern. Apply its Solution; split when several claims are current. |
| What did the cited pattern return? | The result it defines, a reduced-use cue, or a blocker. | Carry that result, keep the cue, or stop; do not copy that pattern’s method into P2W. |
| Which continuations remain current? | One or more separate results from the patterns that answered their questions, or no continuation. | Keep one continuation per answered question; display order and chronology add no relation. |
| What changed later? | The changed relied-on value or relation and the smallest dependent continuation. | Reapply the guidance recorded for the earlier use, use the basis it supplied or located with current facts to reassess the earlier claim or result about the independently identified value or relation, and reopen only that continuation. |
When the conditional structure extension opens, recover one admitted A.22-selected CGUS and, under E.18.3, the independently identified E.18 substrate positions, bindings, already-obtaining occurrences, and any relation-reference epistemes needed for replay.
The condition basis—an applied claim with its test and current facts, an E.18 GuardFail event with its gate-assignment facts, or an independently defined obtaining guard-relation occurrence—supports an ordinary stop or reconsideration question; no return relation follows from the pattern reference.
P2W keeps only its accepted claim, current use, one returned result or stated stop, split, and the dependent continuations; it adds no structure field. Plain actions such as carry, recover, write, split, stop, and return guide this P2W use. They are not P2W relation kinds, commitments, permissions, gates, or substitutes for the cited pattern’s rules.
E.18.1:4.0b - Conditional structure extension through E.18.3
First explain which continuations are available, blocked or unknown, using their conditions and the facts of the case under A.22.CGUS:4.1. E.18.3:0 permits a sufficient ordinary explanation of the transformation-flow connections. Stop at that explanation when it answers the receiving question.
Open this structure extension when a named use needs the selected structure’s identification or qualification, or relies on that structure for comparison, publication or a stronger downstream claim.
Identify one U.Structure under A.22.CGUS by its independently identified constituents, selected obtaining relation occurrences, applied constraints, and named selection-use frame. E.18.3 qualifies that selected CGUS only when it uses positions, bindings, and already-obtaining occurrences from one independently identified E.18 one-TFS, parent-relative internal-SubflowRef, or E.18.NET substrate. E.18.1 declares no P2W subset schema, wrapper relation, or hybrid record.
| P2W need in the structure-bearing use | Representation recovered from the direct interface | P2W boundary |
|---|---|---|
Cite the accepted starting ProblemCard@Context | Select that already identified C.22.2 episteme as one constituent only when the admitted A.22/E.18.3 structure and current use include it. | The accepted card remains a record; selection, a field or adjacency does not make it the structure, a position, a relation occurrence, MethodDescription or Work. |
| Expose transformation-flow topology or positions | Use the positions and bindings from the independently identified E.18 substrate plus separately admitted relation-reference epistemes or obtaining occurrence refs needed by the stated decision or use. | Each value and relation keeps its own identity and obtaining basis; citing E.18.3 or a neighboring pattern neither identifies nor routes it, and P2W neither shortens the interfaces nor turns display order into project-work order. |
| Preserve the carried claim and why the decision or use needs it | Use conversational P2W content or the compact C.2.1 episteme in 4.1; cite an exact source, derivation, or current-use relation only when its direct predicate and current facts show that it obtains. | P2W adds no carried-claim field to structure identity, and file history or shared wording creates no source-use relation. |
| State a stop or reconsideration question | Use the admitted structure’s named selection-use frame and the condition basis: an applied claim with its test and current facts, an E.18 GuardFail event with its gate-assignment facts, or an independently defined obtaining guard-relation occurrence. Then state the ordinary stop or reconsideration question; add a neighboring relation only when its occurrence obtains. | P2W contributes only the local continuation that stops or reopens; a boundary sentence creates no relation, gate, permission, or Work. |
Before choosing the structure branch, distinguish three cases. Several FlowValuation values remain valuations of one TFS only while its A.22-selected O/R/C/F remain the same under E.18. A detailed internal portion remains one parent-relative SubflowRef when its positions and selected relation occurrences resolve in that parent, with every required participant retained.
Two or more independently identified TFS or nested-network values connected across their boundaries by already-obtaining relations require one E.18.NET TransformationFlowStructureNetwork; do not flatten them into one giant TFS. Each member retains its boundary. Work, actual transformations, valuations, position bindings and any DesignRunTag stay with the leaf TFS where they occur or apply.
Each nested boundary reference resolves through one finite acyclic memberPath[] to an ExposedFlowPositionRef; each selected cross-boundary claim cites its obtaining occurrence and complete ordered endpoint bindings through one resolvable NetworkCrossFlowRelationRowRef. Membership is acyclic; a feedback relation may cycle only when its predicate and occurrence facts permit that cycle.
If explicit structure is not required, use the stable conversational core. If replay but not structure is required, use 4.1.
If the next question is work-facing, apply the A.15 family before claiming a plan, readiness, launch or dated U.Work. Use A.3.4 for each actual transformation and A.15.PROD only for the exact production-work, identity-inception or completion claim currently made.
G.11 handles source currentness; E.18:5.13 covers all dependent uses through the needed PathSlices; E.18.NET retains independent members and cross-member occurrences. P2W reopens each affected application and dependent continuation, preserving independent uses.
E.18.1:4.1 - Compact carry-through episteme (conditional reliance extension)
Open this extension only when transfer, audit, delayed feedback, expensive reversal, automation, or durable reuse requires someone to replay the stable P2W core. Materialize one ordinary C.2.1 episteme whose EntityOfConcern is the accepted ProblemCard@Context, whose ClaimContent is the current positive or stopped carry-through account, and whose effective ReferenceScheme governs its designations. Carry-through note and stop description are Plain use labels for those two ClaimContent shapes, not local U-kinds or relation species.
carryThroughClaimContent:
acceptedProblemCardEditionRef
carriedProblemCardClaimSlice
receivingDecisionOrUse
nextPracticalQuestion
applicablePatternRef: pattern whose Solution answers nextPracticalQuestion
contributionUsed: definition, admission, selection, method, decision rule, publication rule, returned result, or other concrete contribution used in this case
returnedResultKindRef?: kind returned by that pattern
returnedResultRef?: positive result, relation occurrence, assertion or description
honestStop?: blocker or reduced-use cue returned by that pattern
carryThroughRationale
localNonOverread?
precedingCarryThroughEpistemeRef?: replay/source pointer only, with an exact relation when continuity or derivation is claimed
continuationDescriptions[]: one question or use, applicable pattern reference, and contribution used per continuation
returnCondition?
A positive use fills the returned result and leaves honestStop absent. A stopped use fills the returned blocker or reduced-use cue and fabricates no positive result.
When the claim uses a separately identified U.Viewpoint episteme or BoundedModelUseStructure and that object’s organization changes how the receiving claim is interpreted, the ClaimContent designates it; otherwise no surrogate field is filled. Citing a PatternID does not by itself admit a U.MethodDescription. The episteme, its claim and its predecessor pointer are neither a reusable predicate definition nor a P2W relation kind or occurrence.
A positive use is well formed only when the named result kind is one that the cited pattern returns for the stated question, the carried ClaimGraph content remains relevant to the receiving use, and every independent continuation stays separate. When the result is a relation occurrence, assertion, or description, cite that exact object; keep its obtaining or claim basis, occurrence-identity rule, and any receiver-conditioned reusable declaration or typed SlotSpecs with that returned object under the pattern content that defined or tested it. A predecessor pointer supports replay only and establishes neither episteme continuity nor another occurrence.
For first-minute use, state the question, apply the pattern that answers it, and continue with its result or stop without materializing this episteme. Materialize it only when replay is required.
Each continuation names one applicable pattern reference and one question or use that its result answers. Do not combine value kind and relation signature, method and mechanism, evidence and assurance, plan and dated Work, actual Transformation and production, or refresh and residual triage in one field.
| Compact ClaimContent field | Filled cooling-fixture example |
|---|---|
| Accepted problem card reference | ProblemCard@Context PC-FAB-042, accepted for a cooling-fixture deformation problem. |
| Carried problem-card claim | The deformation is not one more tuning defect; the downstream comparison use relies on preserving the conserved heat-flow structure identified by the problem card. |
| Receiving use | Decide which mathematical-lens result is needed before formal-substrate declaration and method comparison. |
| Next practical question | Which structure is preserved, which is lost, and where does the heat-flow lens stop? |
| Applicable pattern | C.29 Mathematical Lens Use. |
| Result written and use it answers | The C.29 local lens-use result: target phenomenon, candidate mathematical object, preserved structure, lost structure, payoff, declared use, and stop condition. |
| Local non-overread | This positive C.29 continuation selects no Method, MethodDescription, WorkPlan, dated Work, evidence verdict or gate result. Method comparison remains a separate continuation and waits until its comparator, measurement basis and candidate-set relation are current. |
| Return condition | When a measurement, reference plane, or source-currentness relation changes, reapply the pattern for that value and reopen only the dependent P2W continuation. |
The use closes positively when the cited pattern has returned its positive result and the carried problem-card claim remains visible in that result or its stated basis. It closes by bounded stop when the cited pattern returns a blocker or reduced-use cue and no positive continuation can be stated.
E.18.1:4.1a - Conditional development-loop relation-selection extension
Open this didactic extension only when cheap generation, open-ended search, or evolutionary-engineering work has produced many variants before the project has a stable problem, comparison basis, selected set, work entry, or currentness relation. Apply the unchanged P2W core to the one question that changes the next action. Use the four rows to distinguish these cases. Once you have stated the question, use the single map in Relations.
If the current question is still problem formulation or opportunity, return first to C.22.2 to accept or revise the ProblemCard@Context and its carried claim. That is an upstream return, not another downstream P2W result.
| Source cue | Ask this concrete question | Continue or stop |
|---|---|---|
| “We generated many variants.” | Which variants are retained, and under which descriptor or front? | Carry the returned archive/front value. If no retained-set relation is current, keep only the candidate-set cue. |
| “This is the best set.” | Is the current claim comparison, selector application, local choice, selected-set result declaration, or actual publication? | Split those claims. Apply only the branch being asserted; a score or front supplies none of the others. |
| “The candidate is ready.” | Is the team planning work, checking entry readiness, reporting a dated U.Work occurrence, claiming a gate or permission result, or asserting acceptance for one named use? | Name one question and use the Relations map once. For acceptance, name the predicate and its participants; stop if ready or accepted is the only basis. |
| “We trust the generator.” | Does the sentence name an autonomy declaration or boundary—what the generator may do or spend, and when it must stop—or is it about evidence, assurance-sensitive confidence, permitted action, or merely a project label? | For a declared autonomy limit, apply E.16 and carry its declaration or boundary result; that result supplies no evidence, assurance, or permission. Otherwise apply A.10, B.3, or A.2.8.PER only to the claim made. If the phrase is only a label, retain it and make no action claim. |
Cheap variant generation shifts effort toward problem production, characterization, archive stewardship, fair comparison, explicit choice, autonomy boundaries, evidence, assurance, performed work, effect measurement, currentness, and repair. P2W preserves the accepted problem-side claim while one of those relations becomes current; an archive, front, selected set, confidence phrase, or choice rule supplies neither an A.2.8.PER permission result nor performed work.
Source wording such as trust budget, problem factory, solution factory, or factory of factories remains a project label until the evidence, assurance, autonomy, work-organization, or other direct relation is named.
E.18.1:4.1b - Conditional development-for-developed first-minute extension
Open this didactic extension only for a fast DPF seed, and keep the source-use and hardening continuations distinct. An accepted problem-side record may cite a G.2 source-use relation, selected source U.Episteme, exact EpistemePublicationRelation occurrence reference when availability is material, source-pack cue or return, and provisional framework purpose.
If choosing a DPF, an access-only route, or stop must settle a downstream-used framework boundary, use E.4.PFAD to profile that framework-specific content in one E.9 DRR; a cheap seed or route that settles no such boundary stops without that DRR.
State each material initial pattern relation with the predicate that defines it, and use E.4.PFR only when a named maintenance use needs relation records. Using the E.4.PFAD profile adds no second decision or decision record.
If the receiving use needs a way that the sources do not yet supply, develop it through C.39; for a framework contribution, use E.4.CM to develop the connected Methods and their explanation before allocating them to patterns. An adequate supplied way can be used directly.
Use E.8 for pattern authoring, E.21 for evaluation, E.23 for improvement, and G.11 for currentness or refresh. Keep the source result, selected answer and DRR, direct relation assertions or optional records, authored patterns, quality results, and currentness results separate.
When the receiving question is which guidance to use next, an explained selection can close that question. When the receiving work needs the subject result, keep the carried claim through application of the selected guidance to the result or stop.
Cooling-module example. ProblemCard@Context PC-DEV-041 states that cheap generation produces many cooling-module layouts while fair problem framing and comparison remain weak. The carried claim is that the current candidate set retains maintainable low-energy variants until energy use, service access, manufacturability, thermal margin, and test cost are represented in the current characteristic and comparison relations.
A C.18 archive and front are current. A.19 defines the characteristic space and its comparability boundary; A.19.CPM comparison becomes current only when that characteristic space and comparator are current. The G.5 selected-set result declaration remains stopped until that comparison and front are current; actual audience availability is a separate later question that uses E.17 for a source-backed publication face and return to source and E.24.PUB for the publication occurrence, form, carrier, audience, bounded use, and availability.
An E.16 generator boundary may separately bound search and test spending. Recover the prototype observations and their support for the receiving claim. Use A.10 when that source-to-use account is implicit or must remain replayable; use B.3 for assurance-sensitive confidence use.
A C.30 architecture-candidate relation appears only for retained layouts that change selected structure. No U.WorkPlan has yet been produced under A.15.2, and no dated U.Work occurrence has yet been admitted under A.15.1.
Thermal and serviceability measurements can feed but cannot create three separate results: applying A.15.5 may return WorkEntryReadiness@Context for one named intended-work concern; applying A.21 may return a GateDecision only for one current OperationalGate(profile) and its declared checks; applying A.2.8.PER may return one named non-prohibition, granted-permission, permission-exercise, non-violation, or permission-conflict result with its required participants and basis.
An actual release action is an A.15.1 U.Work occurrence; a further claim that a subject was released needs its named subject predicate and participants. No predicate definition or occurrence rule for that release relation is current in this example, so an approved, authorized, or released cue stops as missing-governor for that attempted use rather than inheriting the measurement, readiness, or gate result.
When descriptors, tests, competitor information, or cited publication editions change, reopen the currentness-dependent continuations under G.11.
Which retained layouts belong in the current front? Apply C.18 to obtain its current front record. Architecture comparison, selected-set result declaration, actual publication, planning, and work are possible later continuations, not alternative fillers of one field.
E.18.1:4.1c - Conditional naming and publication extension
Ordinary P2W use skips this extension. Open it only when a pattern author, publisher, trainer, or tool builder must cite the already defined practice outside its local use. The header’s Tech/Plain pair identifies this pattern for readers: ProblemToWorkCarryThrough / problem-to-work carry-through. It does not classify a U.Method, U.MethodDescription, relation, Work or result. If the use requires MethodDescription membership, first identify one C.2.1 episteme, require one independently admitted U.Method as its EntityOfConcern, and apply the A.3.2 substantive way-of-doing claim threshold.
The compact positive, stop and replay shapes in 4.1 and 4.8 are local ClaimContent uses of ordinary C.2.1 epistemes. Their field labels are local phrases, not reusable U-kinds, NameCards or term rows.
Cite the settled Tech/Plain designation directly when its existing meaning serves the receiving use. Use F.8 for an unsettled or stronger naming need; apply F.18 for the durable designation and F.17 for a public scheme-local row when those uses require them. F.9 opens only if two independently identified scheme-sense cells require an exact Bridge. No Bridge is current merely because two readers use similar P2W wording.
Keep the practice, pattern episteme, any admitted Method, any qualifying MethodDescription episteme, local carry-through episteme, publication occurrence, publication form and presentation carrier separate. Naming or publication admits none of them and adds no stable-core field.
Reopen only what the change affects: a changed practice or practitioner use reopens E.18.1; changed wording reopens F.18; changed public reader use reopens F.17; changed source basis reopens its exact source-use relation. For a changed publication, use E.17 for the source-backed face and return to source and E.24.PUB for the occurrence, form, carrier, audience, bounded use, and availability. A source phrase or remembered title supplies no source-to-use relation, authority, evidence, result or performed Work.
E.18.1:4.2 - Positive carry-through: one executable first use
Use the first three rows for an ordinary case. Open the fourth only when the source sentence contains the additional claim. Other relation families use the same branch rule in 4.6; consult the single relation-selection map in Relations only for the relation being asserted.
| What the reader has | Do now | Result or stop |
|---|---|---|
Accepted ProblemCard@Context PC-FAB-042: the cooling-fixture deformation is not one more tuning defect because method comparison must preserve a heat-flow invariant. | Carry that distinction into the question: “Which structure does the proposed mathematical lens preserve, which does it lose, and where does its use stop?” | One recognizable receiving question; no method, declaration, plan, or work claim yet. |
| That question names one mathematical-lens relation. | In the Relations map, select C.29 once and apply its Solution to the cooling-fixture subject and comparison use. | CoolingFixtureHeatFlowLensUse-042: preserved structure, lost deformation factors, payoff for method comparison, declared use, and stop. |
The C.29 result still carries the accepted heat-flow distinction. | Continue with that value; stop before method comparison until its comparator, candidate set, and measurement basis are current. | A useful positive P2W continuation. No compact note is needed unless another user must replay it. |
The same source also shows a FormalSubstrate signature. | Split the signature claim from the lens-use claim. Apply A.6.0 only if its defined subject, ranged value, and selected profile can be named. | A separate declaration result, or a stopped declaration cue. The signature neither replaces the C.29 result nor selects a method. |
In this example the ordinary route uses one carried distinction, one concrete question, one map lookup, one result from the pattern that answers the question, and one visible stop.
A case with several claims splits before any pattern is applied; a case with only a cue stops under 4.6.
E.18.1:4.3 - Direct-relation distinctions that change the branch
P2W carries the value or stop returned by the neighboring pattern. Apply that pattern’s test there, without restating it in P2W. Keep a local distinction here only when it changes which question the reader asks:
- Lens or declaration? Ask whether the current use judges a mathematical representation or declares a signature. Split the claims when both are present; the first-use case in
4.2shows the difference. - Mechanism or method? Ask whether the claim concerns a law-governed operation application or a reusable way of doing. A shared noun supplies neither; split the questions and use the Relations map once for each current claim.
- Change or timing? Ask whether the claim concerns an actual bounded change, a temporal aspect such as an interval or cadence, or the adequacy of a temporal claim for one use.
- Work, change, or their connection? Identify the dated
U.Workoccurrence and actualU.Transformationseparately, then ask whether a work-to-change claim is current. Apply the pattern that defines or tests that claim, or the applicable A.6.RCD route, and carry only its positive or negative result or blocker. Shared timing does not answer the question. The BuildOps and Pump 14 slices in5.1show a positive result; Pump 14 also preserves an earliermissing-governorstop without copying the result’s proof. - Approved, ready, released, or permitted? State which result is being sought: a gate decision, permission result, work-entry-readiness result, release
U.Workoccurrence, or subject-release relation. Apply the pattern that answers that question and carry its result or blocker;authorizationis not a result type. - Result or production? Let
A.6.P.WMRseparate the concrete result questions. OpenA.15.PRODonly for a production-work, entity-inception, or production-completion question; its returned claim or blocker stays separate from work, change, delivery, acceptance, and release.
For every other exceptional object, state the relation-specific question and consult the canonical map in Relations.
E.18.1:4.4 - Boundary and relation discipline
A neighboring pattern’s detail appears outside Relations only when one local discriminator in 4.3 or one worked case needs it to choose, split, or stop. Use the branch rule in 4.6 and the single question-to-pattern map in Relations. Neither place restates a neighbour’s occurrence basis, recovery algorithm, production criterion, derivation method, or admission law.
A local P2W application closes positively when a practitioner or another capable system has obtained or amended the result by applying the cited guidance and the carried distinction remains visible in that result or its stated basis.
It closes by bounded stop when no continuing relation can be recovered and the reduced-use cue plus stop condition are stated. A following method selection, planning act, work occurrence, evaluation, or other use of neighboring pattern content is not unfinished P2W work.
A wider P2W carry-through slice remains current only while a named downstream receiving use relies on the accepted problem-side distinction. It closes when no remaining receiving use relies on that distinction and no return condition is current. A later changed assumption opens a local return to each application that depends on it, continuing through dependent branches and joins. Earlier applications with independent grounds remain closed.
E.18.1:4.5 - Return and refresh rule
Reopen the relation that supplied the changed value, then only the continuation that relied on it. Do not replay the whole carry-through.
| What changed | First return | Smallest P2W reopen |
|---|---|---|
| A measurement, unit, reference plane, normalization, comparator, selected set, criterion, or other result used by the continuation | Reapply the guidance recorded for the earlier use and use the basis it supplied or located with current facts to reassess the earlier claim or result about the independently identified value. | Reopen only the continuation whose answer used it. |
| A source publication, source-use relation, freshness/currentness line, or appearance on which the use relied | Apply the currentness or reliance repair for that source relation, then reapply the pattern for the affected relation. | Only continuations that relied on the stale or misleading source value. |
| A result artifact, telemetry line, acceptance label, done-state, or similar record | First state the relation that the record is claimed to report; the record’s appearance alone is not a changed world fact. | Reopen a dependent continuation only if the result returned for that question changed. |
| The accepted ProblemCard claim itself | Amend or replace the problem-side result under its direct problem pattern. | Every continuation that relied on the changed distinction, and no others. |
A dated occurrence already admitted as U.Work remains the same world-side occurrence. Return may change a later interpretation or plan; it does not rewrite that occurrence retrospectively.
E.18.1:4.6 - Plain relation-selection branch
Put the unsettled question into one ordinary sentence: “Did this work change that pressure here?”, “Does this grant let this technician do this work now?”, or the equally concrete sentence for the current case. Name the participants and relation, then use the matching row. Do not scan every pattern first.
| What you can truthfully state | Do next | Close this P2W move with |
|---|---|---|
| One relation-specific question and its participants. | Use the Relations map once, apply the pattern whose Solution answers that question, and keep the accepted problem distinction visible. | The result or stop defined by that pattern. |
| Two or more relation-specific questions. | Write one question per claim and apply the pattern that answers each question separately. | One result or blocker per question; no omnibus result. |
Only a cue such as result, approved, ready, a diagram arrow, or a familiar noun. | State the stronger claim the cue seems to suggest. If its relation and participants still cannot be named, preserve the cue and stop. | The cue plus the unanswered relation-specific question; no guessed answer. |
| The cited pattern returns a lower-use result or blocker. | Keep that result intact. | The returned stop or bounded continuation, not a P2W substitute. |
| A relied-on value later changes. | Use 4.5: reapply the guidance recorded for its earlier use, use the basis it supplied or located with current facts to reassess the earlier claim or result about the independently identified value, and reopen only the dependent continuation. | What still carries, what no longer carries, and the one next question. |
The ordinary case closes after the first row. The Relations map is for locating that one pattern or checking an exceptional branch; it is not a checklist to traverse.
E.18.1:4.7 - Lowering and reopen block
Lower only the claim that cannot be made. Keep any independently grounded value and preserve the practical question that would reopen the branch.
| Nearest failure | P2W action | Result |
|---|---|---|
| No accepted problem-side record exists. | Stop before P2W; apply the problem-side pattern that answers the missing formulation or acceptance question. | The source phrase remains a cue, not a carried distinction. |
| A cue suggests one relation, but its subject, other participants, or deciding rule cannot be named. | Preserve the cue and the attempted question; use the Relations map only to locate the pattern that can answer it. | Stop without a positive relation. |
| One sentence blurs several relations—for example lens plus declaration, plan plus Work, or Work plus change. | Split the sentence into separately answerable questions and apply 4.6 to each. | Independent values or blockers; no sequence is inferred. |
A cited pattern returns missing-governor, factually unsupported, missing-information, a reduced-use result, or another blocker. | Carry that result unchanged and stop only the dependent claim. | The blocker with its affected participants or use; independently grounded values remain. |
| A relied-on value changed after a prior positive use. | Apply 4.5. | Reopen only the smallest dependent continuation. |
E.18.1:4.8 - Conditional reliance replay after a relied-on value changes
Open this extension only when transfer, audit, delayed feedback, costly reversal, automation, or durable reuse requires a durable account of what still follows after source-currentness repair, appearance-based reliance repair, changed measurement, changed problem-side record, FPF pattern change, or a use-found defect. For an ordinary local return, use 4.5 without creating a replay episteme.
Materialize one ordinary C.2.1 episteme whose EntityOfConcern is the accepted ProblemCard carried by the original carry-through episteme, whose ClaimContent is the replay account below, and whose effective ReferenceScheme governs its designations. Replay note is Plain wording for this use, not a local U-kind, refresh process, change log or authority record.
replayClaimContent:
originalCarryThroughEpistemeRef
changedValueRef
changedValueKindRef
changedValuePatternRef: pattern containing the guidance applied in the earlier use of changedValueRef
changedValueContributionUsed: exact Solution passage applied in that earlier use
stillCarriedClaimSlice
noLongerCarriedClaimSlice?
smallestReopenedContinuation
refreshCurrentnessLineRef?: exact current G.11 episteme or relation
nextApplicablePatternRef: pattern whose Solution answers the reopened question
Reapply the guidance recorded for the earlier use before filling the replay episteme, then use the basis it supplied or located with current facts to reassess the earlier claim or result about the independently identified changed value.
If the changed object is a relation, that reassessment first judges whether the relation obtains; apply A.6.REL afterward only when relation-occurrence identity is current. The earlier result keeps its participants, obtaining or claim basis, occurrence-identity rule and any reusable RelationSignature or typed SlotSpecs.
The replay account records only what still follows, what no longer follows and which P2W continuation reopens. Citing a PatternID does not admit a MethodDescription.
P2W may cite a readable relation assertion, an explicitly individuated occurrence, or a typed assertion or description, but it cites the independently identified object that served as the earlier result together with its obtaining or claim basis. Citation does not make relation use signature-dependent; a receiving episteme carries a signature reference only when the defining content for that claim requires one.
The changed object may instead be a source edition, measurement, unit, reference plane, Method set, comparator, module-interface relation, publication-use relation, problem record, or FPF pattern publication.
Whatever changed keeps its own kind. If the reopened use depends on maintenance, responsibility, or authority, name the direct relation and its participants; an owner-shaped label is not enough. Reapply the guidance used for the earlier result. Add a G.11 line only when one exists.
The practitioner or another capable system applies the guidance to the reopened question and decides whether to continue, stop, split, retain a reduced-use cue, or return upstream.
E.18.1:5 - Archetypal Grounding
E.18.1:5.0 - Seal-failure carry-through
A maintenance team has an accepted ProblemCard@Context for recurrent seal failure. It records the operating conditions, the distinction between thermal deformation and material degradation, and the observations that would challenge that distinction. The team uses E.18.1 because diagnostic-method selection, repair planning, dated repair work, interpretation of the post-repair measurements, and return after a changed diagnosis all depend on preserving these accepted problem-side distinctions.
E.11.PUA may help the team inspect and apply one diagnostic-pattern candidate inside this flow. Its result might be one fit finding or one diagnostic method-selection input. That smaller result does not replace the accepted problem material, the repair plan, the repair work, or the later interpretation and return relations.
In System-facing work, an accepted problem-side record may lead toward method choice, planning, performed work, result records, and result measurement. In Episteme-facing work, the same record may lead toward a U.Signature(profile=FormalSubstrate) declaration, mathematical-lens use, description, publication, evidence, or gate-related claims. Both uses ask the same P2W question: which FPF kind or relation can carry the next claim being made?
| Archetype | System-side grounding | Episteme-side grounding |
|---|---|---|
| Working situation | A manufacturing team accepts a problem card showing that a fabrication issue is caused by a missing functional constraint. | A research team accepts a problem card showing that two descriptions may be almost the same only under a declared U.Signature(profile=FormalSubstrate). |
| Failure | The team treats the principle scheme as method selection, work plan, performed work, and acceptance evidence at once. | The team treats mathematical equivalence as real-world identity, measurement validation, evidence, and decision claim. |
| Repaired use | The team carries one accepted claim and separates method comparison from one exact A.15.2 U.WorkPlan. That WorkPlan’s declaration-local planned-filling content may carry the Method, window, intended performer and kind conditions, evidence-reference pins, freshness requests, and planned constraints; a needed row is cited only through the exact WorkPlan edition and its local-content locator. The team separately records references to dated U.Work occurrences while keeping those records as separate epistemes, and unpacks result relations; it writes a compact note only when replay matters. | The team separates mathematical-lens use, U.Signature(profile=FormalSubstrate), bridge, measurement, evidence, and provenance relations, and keeps equivalence bounded by the declared formal relation. |
E.18.1:5.1 - Worked slices
Each slice shows only the P2W contribution: the carried distinction, current question, pattern that answers it, independently obtained result or blocker, and next continuation or stop.
-
Thin first-principles start. The accepted card says that a conserved structure, not one more tuning defect, matters to the next decision. The current question is a mathematical-lens question, so the practitioner applies
C.29and carries its lens-use result or stop. A separate declaration question goes toA.6.0; method selection waits for its own question and participants. -
Planning from a selected-enough method. The carried distinction constrains planning and the current question asks for a plan. The practitioner applies
A.15.2and carries the plan result returned there. Any compact P2W note cites that result and the problem-side claim it preserves; the plan keeps its own content and authority. -
Performed work and a positive store-change connection. The carried claim makes actual population of the artifact-store partition material to the next release question. The current question asks whether
ReleaseBinary12_BuildWork_2026-07-21T0900_0912is connected toArtifactStorePopulationTransformation_12.A.15.1andA.3.4identify those two participants, and applying the BuildOps work-to-change predicate yields positive assertionBuildWorkPopulatedStore-12. P2W carries that assertion and continues to the separate release question; if the defining pattern instead yields a blocker, P2W stops there. It does not recreate the predicate test, performed-application proof, or negative-claim rule. -
Result interpretation without a generic result. The sentence the work result proves the approach worked leaves the result question unresolved. Apply
A.6.P.WMR; carry each concrete returned claim or blocker on its own continuation. No returned item becomes a generic result or production value merely because the source used the word result. -
Functional explanatory order. A source diagram places formal declaration, principle framing, mechanism, normalization, method selection, planning, performed work, and measurement in one readable order. Treat each as a possible question, apply its defining pattern only when that question is current, and carry the separate returned values or stops. Display order supplies no project sequence or authority.
-
Interface split before P2W use. A source says a port-throughput limit makes a solution feasible after integration. Ask the module-interface question through
A.6.Mand the selected transformation-flow question throughE.18. Planning, work, evidence, gate, function, and architecture cues remain stopped until their own questions are stated. P2W carries only the result or stop that matters to the current decision. -
Measurement returns to planning. A source says one work occurrence produced telemetry and an artifact.
A.6.P.WMRfirst returns the distinct artifact, telemetry, production, or unsupported results needed by the case; P2W keeps separate continuations. If a laterC.16result andG.11currentness result change the reference plane used by planning, reopen only the planning, method-comparison, or problem-side continuation that relied on it. The earlier dated Work occurrence is not rewritten. -
Pump 14 pressure adjustment; positive continuation after an earlier stop. The carried distinction makes the relation between
W-P14-ADJUST-1010-1020andT-P14-PRESSURE-RISEmaterial. In the earlier case record, no current predicate could state that connection, so applying the defining work-to-change pattern yieldedmissing-governorand P2W stopped.In the current record, each precise performer has an independently established A.13 core and A.15.1 has independently admitted the Work. Because this record also carries exact assignment-bound attribution, F.6 afterward establishes that relation through the same obtaining assignment. That basis and the
P14-REL-2026application support the positiveAdjustmentWorkCausesPressureRiseresult; P2W carries the result without reconstructing the agency, Work-admission, assignment-attribution, transformation, or causation proof.The separate claim that
PC-P14-PRESSUREguidedWP-P14-2026-07-15still has its ownmissing-governorresult and stays stopped. Later measurement and decision questions remain separate.
E.18.1:5.2 - Additional worked situations
| Situation | P2W application | What changes |
|---|---|---|
| First-minute use | A practitioner has an accepted ProblemCard@Context and the sentence “the cooling fixture violates the heat-flow invariant.” State the accepted card, carried claim, decision or use needing the answer, and next practical question in conversation. Add a compact note only when another person or later action must replay the path. Then name the pattern whose Solution answers the question and the result it must return, or state the stop. | Apply C.29 to the preserved structure, lost structure, payoff, declared use, and stop condition. A later formal-substrate declaration under A.6.0 is separate; neither continuation selects a method or writes evidence. |
| Diagram and approval note in the same source publication or source-use record | The same source publication contains a diagram, a test photo, and a manager note saying “approved.” Keep P2W focused on the claim carried from the accepted problem card. | Diagram cue, evidence-looking cue, and gate-looking cue are separated by relation recovery; conversational use or the compact note keeps only the carried claim and current direct relation. |
| Principle story without accepted problem-side record | A source has an inspiring principle story but no accepted ProblemCard@Context. | P2W stops before it begins; the source remains a reduced-use cue until C.22.2 or the problem-side pattern named by value accepts a problem-side record. |
| Acceptance claim with and without a current acceptance rule | For Fixture-42, the project-local predicate-definition episteme ThermalTestAcceptanceRelations defines when a named fixture is accepted under a named criterion set for a named campaign. Its ClaimContent says that Fixture-42 is accepted under CriterionSet-T7 for Campaign-T7. CriterionSet-T7 requires leak rate at most 0.5 mL/min and mounting offset at most 0.2 mm; current measurements are 0.3 mL/min and 0.1 mm, so the stated acceptance relation obtains and P2W carries the positive claim. In the earlier dashboard record, only a green accepted label exists, the offset was measured from the wrong reference plane, and no current rule defining acceptance can be recovered. | Apply that acceptance rule in the positive case. In the earlier case, return A.6.RCD missing-governor because no current pattern or project-local rule defines the claimed acceptance relation. Independently repair the measurement: if the correctly referenced measurement is unavailable, return missing-information; once current facts support applying the rule, carry its positive or negative result. The label establishes no acceptance, and C.25 does not define a universal acceptance rule. Any ownership, maintenance, responsibility, or authority claim remains separate and needs its own obtaining relation. |
| Changed unit after source-currentness repair | Later source-currentness repair changes only the unit and reference plane used by the planning constraint. | P2W reopens all applications dependent on that unit or reference plane, including their dependent joins; the earlier dated U.Work occurrence is cited, not rewritten. |
| Clinical differential carried into care planning | An accepted problem card distinguishes an adverse treatment effect from progression of the underlying condition. Diagnostic-method choice, care planning, performed clinical work, and outcome interpretation all depend on retaining that distinction. | The practitioner applies the clinical DPF and direct work, evidence, and measurement patterns. The problem-side claim does not grant permission to treat; a changed observation reopens the diagnostic continuation before any dependent plan, permission, or work-entry relation. |
| Learning difficulty carried into teaching and assessment | An accepted problem card distinguishes missing recall from a wrong conceptual model. Teaching-method selection, session planning, performed teaching work, and later assessment depend on that distinction. | The selected educational method and A.15 work relations keep their own values. A lesson plan or completed session does not prove changed learner capability; an assessment that challenges the distinction reopens the smallest method or problem continuation. |
| Near-sameness under a formal declaration | A mathematical near-sameness claim preserves heat-flow structure but loses deformation factors outside the model. | The practitioner applies C.29 for mathematical-lens use. Apply A.6.0 separately only when the signature’s subject, ranged value, and FormalSubstrate profile can be named; otherwise keep the signature wording as a stopped cue. P2W preserves the accepted claim across those continuations without settling empirical truth or granting permission to start work. |
| FPF relation rule changes after a P2W use | Reapply the guidance recorded for the earlier use and re-evaluate the independently identified relation result under its own predicate or test and current facts. When relation-occurrence identity is current, apply A.6.REL only after that judgement. If the result changed and a later continuation relied on it, record the changed result, what still follows, what no longer follows, and the smallest continuation to reopen. | Age alone does not validate the earlier use. Replay it with the current facts; only the changed relation and dependent continuation reopen. |
| Relation selection would over-select from one phrase | A source says “the new port contract proves integration readiness.” P2W splits module-interface relation, E.18 transformation-flow relation, a dated U.Work occurrence, evidence cue, gate cue, and architecture-description cue. | Only the relation that changes the P2W application being made is written; the remaining readings stop as named cues until their relations and participants are stated. |
| Formal claim loses payoff | A U.Signature(profile=FormalSubstrate) declaration preserves a neat invariant, but no practical payoff or downstream stop condition can be stated for the accepted problem-side record. | The mathematical phrase lowers to a reduced-use cue; P2W does not justify method selection, evidence, gate, or A.15.2 planning from mathematical prestige alone. |
| Result source-use relation becomes stale | A result-looking source-use relation or publication cue is later replaced by a fresher source-use relation with a different artifact reference and measurement reference. | The practitioner applies A.15.4 appearance-based reliance repair before continuing P2W; stale result wording cannot continue as evidence, acceptance, or quality evaluation. |
E.18.1:5.3 - Pilot examples for transformation-flow structures and networks
Distinguish three cases in the examples: several valuations or path slices of one TFS; one parent-relative internal SubflowRef; or an E.18.NET network of independently identified TFS or nested-network members connected by already-obtaining cross-boundary relations. A diagram, common product, display order, shared Work or source wording decides none of them.
For one TFS, every valuation uses E.18:5.2’s resolved connection/cut domain while retaining the same A.22 selection O/R/C/F. A new actual application or selected relation occurrence first reopens that identity.
In a network, each member retains its boundary. Keep Work, actual transformations, valuations, position bindings and any DesignRunTag at their respective leaf TFSs. Cross-flow occurrences retain their defining predicates, signatures, participant order and endpoint bindings. Membership is acyclic; feedback relations may cycle when their own rules permit it.
Use a pilot to check the carried object’s exact member-local position, the direct relation that crosses a boundary when one exists, and every dependent member or continuation. When two branches use the same changed calibration, the pilot covers both branches and their join; the first detected slice is only an address into that work.
| Pilot | P2W use being made | What it tests |
|---|---|---|
| Coffee service TFS | Accepted ProblemCard@Context PC-COFFEE-SERVICE-17 keeps the service-temperature and throughput problem visible while each next claim opens separately: C.29 returns CoffeeHeatMassBalanceLensUse-17; A.6.0 returns CoffeeFormalSubstrateSignature-v3 only for its declared subject and ranged value; A.6.1 returns CoffeeBrewHeatTransferMechanism-v2 and exact application bindings; A.19.UNM returns CoffeeTemperatureNormalization-v4; A.3.1 returns CoffeeBrewMethod-v5; A.15.2 returns CoffeeShiftPlan-17; A.15.1 returns dated CoffeeBrewWork-17-0815; C.16 returns the temperature and throughput measurements; and G.11 reopens only a continuation relying on the changed source, normalization, Method or measurement. Treat them as positions or continuations of one TFS only while every use resolves to that same selected structure and its selected internal relation occurrences, resolved through their E.18 connection positions. | A signature supplies no mechanism or Method; a plan supplies no Work; telemetry supplies no measurement result until C.16 applies it; another valuation or slice does not mint another TFS; refresh changes only the relation that relied on the changed value. |
| Compiler design and run | Compiler preparation/build, later compiler use, release assurance and product operation retain independently identified TFS values when their boundaries, Work or change cadence differ. Release-assurance use, launch-gate use, reproducible-build currentness and G.11 source-currentness remain separate claims. Select an E.18.NET network only after the source-use, production/inception, operation-application, evaluation or other cross-member occurrences and endpoint bindings independently obtain. | No collapse of build, run and product Work; no giant flow; no universal produces/uses edge; local DesignRunTag; and no transformation, production, gate or currentness result from a build arrow or intended realization. |
| TAMP and MPC robotics | Method selection and A.15.2 planning may be revised under a declared progress or budget condition before performed Work. That planning/replanning cycle may be one TFS valuation or path-slice family when the structure identity is shared; separately selected development, controller-execution and evaluation flows require E.18.NET and cross-member relations. | Branching and cycles without a fixed work procedure; a prospective launch decision remains distinct from later dated Work; and feedback cycles do not make membership cyclic. |
| AutoML and QD | Method selection retains alternatives from a declared front or archive as a Shortlist, or as a RankedShortlist under an admissible order (G.5:4.4b–4.4e). The result preserves the source reference, comparison basis and ordering, with comparator and descriptor editions pinned. If generation, evaluation and deployment are independently selected flows, relate them only through direct occurrences in E.18.NET. A changed descriptor, comparator or retained-set relation reopens only the dependent selection or publication continuation. | Set-return discipline, comparator currentness, no hidden scalarization, retained-set refresh, and no evaluation label used as a universal edge. |
| Freshness or physical-transport case | Work planning and performed Work depend on freshness windows, transport relations, units, reference planes and source-currentness. A detailed internal route remains a SubflowRef; independent transport and use flows require a network. | No implicit latest, no unbridged unit or plane comparison, exact member boundary, and the full dependency closure, retaining independent uses. |
| Integration under module-interface constraints | After assembly, a result phrase may say role enactability under module-interface constraints or may point to evidence, a gate, architecture, function-like wording, or a Work relation. | Treat role enactability as unresolved wording and apply E.10.ROLE; then recover the local system-role kind and classification, assignment occurrence, direct participation or functioning relation, ordinary non-use, or exact missing governor that the current claim needs. Recover module-interface, evidence, gate, architecture, and Work claims separately under their own patterns; route claim-bearing function-like wording through A.6.F. |
| Tool-product-use network | One member contains dated tool-building Work, actual substrate changes, and only the local A.15.PROD production-work, inception, or completion claims that are current; another member uses the admitted tool through an operation-application or subject-use occurrence. In the concrete chain, a later member may use that tool to make a chair and another may use the chair as context for writing a text. Every current A.15.PROD claim and every direct tool-use or context relation must pass the test defined for it. | The same carried object may occupy a run-result, design-side input, tool, context, or constraint position in different members without changing kind. Source and use relations, together with the local A.15.PROD claims, connect members; a design tag, result label, or adjacency does not. |
| FPF pattern development and use network | One member carries exact drafting or repair Work and episteme-edition changes; quality evaluation, publication projection, admitted publication, later application to another EntityOfConcern and use-found evaluation remain separately identified values or members when independently selected. An evaluation member may return a defect through exact source-use, evaluation and change relations to the dependent development continuations. | Development, publication, application and evaluation remain separate; evidence stays outside practitioner prose; repair identifies the exact development object and applies the pattern for its change, rather than treating the publication as acting or every edit as production. |
E.18.1:5.4 - Filled P2W carry-through notes
These examples show how to fill and replay the compact note in 4.1.
Cooling-loop mathematical-lens continuation.
| Compact note field | Filled value |
|---|---|
| Accepted problem card reference | ProblemCard@Context PC-COOL-017, accepted for a cooling-loop stabilization problem. |
| Carried problem-card claim | The observed deformation is not one more tuning defect; the later method-comparison use relies on preserving the conserved heat-flow structure. |
| Receiving use | Determine the mathematical-lens result needed before any formal-substrate declaration or method comparison. |
| Next practical question | Which structure is preserved, which is lost, and where does the heat-flow lens stop? |
| Applicable pattern | C.29 Mathematical Lens Use. |
| Result written and use it answers | A C.29 local lens-use result naming target phenomenon, candidate mathematical object, preserved structure, lost structure, payoff, declared use, and stop condition. |
| Local non-overread | Method comparison waits until comparator, measurement, and candidate-set relations are named. A later A.6.0 signature declaration is a separate continuation. |
Port-throughput continuation split.
| Compact note field | Filled value |
|---|---|
| Accepted problem card reference | ProblemCard@Context PC-PORT-008, accepted for an integration-throughput problem. |
| Carried problem-card claim | The port-throughput constraint affects integration, but the source phrase does not decide which module-interface, transformation-flow, planning, work, evidence, gate, or architecture relation is current. |
| Receiving use | Make the current module-interface relation and selected transformation-flow structure inspectable without inferring readiness. |
| Next practical question | Which relation are you stating now? |
| Continuation 1 | Apply A.6.M and write the exact module-interface relation for the port contract. |
| Continuation 2 | Apply E.18 and identify the selected transformation-flow structure and the exact interface-bearing position or binding used by the current question. |
| Stopped cues | Apply A.15.2 only if a planning constraint is being stated. Evidence, gate, and architecture cues remain stopped until their direct relations are current. |
| Local stop | No readiness result, granted permission, performed-work claim, evidence verdict, or gate decision follows from the port phrase by itself. |
E.18.1:6 - Bias-Annotation
These five lenses were tested: Gov, Arch, Ontological and epistemic, Prag, Did. Scope: accepted problem-side record plus carried distinction moving toward FPF applications.
- Governance bias (Gov): permission, gate, release, assurance, and decision cues remain local cues until the relation and participants are stated: an
A.2.8.PERpermission result,A.21 GateDecision,A.15.1releaseU.Workoccurrence plus any required named subject release predicate,B.3assurance result, or direct decision result. The wordauthorizationsupplies none of them. - Architectural bias (Arch): diagrams, selected structures, and module-interface language help formulate the next relation question; they do not replace the accepted claim, receiving use, separately identified viewpoint or model-use participant, applicable pattern contribution, or returned result.
- Ontological and epistemic bias: a source publication, diagram, compact note, or formal declaration remains separate from the subject EntityOfConcern and from the relation or result claimed through the pattern contribution used for the current question.
- Pragmatic bias (Prag): the carry-through structure is useful for action without becoming a prescribed project procedure.
- Didactic bias (Did): the local P2W mantra and positive carry-through structure show how to use P2W before the reader needs the more detailed relation aids.
E.18.1:7 - Conformance Checklist
CC-E18.1-1The P2W use starts from an acceptedProblemCard@Contextor stops before P2W begins.CC-E18.1-1aThe accepted ProblemCard as the note’s EntityOfConcern, the note’s ClaimGraph and effective ReferenceScheme, any separately identifiedU.ViewpointorBoundedModelUseStructuredesignated by that ClaimGraph, each cited pattern’s subject EntityOfConcern, and every supporting compact note, diagram, plan, trace, or publication remain distinct. Note completeness does not prove a P2W relation occurrence, subject change, performed work, evidence, acceptance, or result.CC-E18.1-1bEvery materialized carry-through episteme identifies one accepted ProblemCard as EntityOfConcern, carries one ClaimContent for the receiving use, names its effective ReferenceScheme, and designates a separately identifiedU.Viewpointepisteme orBoundedModelUseStructureonly when the claim uses that object and its organization changes how the receiving claim is interpreted. It cites the carried ProblemCard slice,applicablePatternRef, returned value kind and ref or a justified stop, and rationale. It introduces no reusable P2W predicate,RelationSignature, relation kind, local note kind or occurrence.CC-E18.1-1cWhen external naming or publication is current, F.8/F.18/F.17 apply only to the already identified value and receiving use. The pattern label and local positive/stop/replay phrases create no NameCard, U-kind, relation, Method or MethodDescription. Any MethodDescription claim separately passes the A.3.2 EntityOfConcern and substantive-claim threshold.CC-E18.1-2A positive carry-through ClaimContent cites one returned result and one or more separate continuation descriptions. A stopped ClaimContent instead states the reduced-use cue or blocker and stop without fabricating a relation. Local non-overread and return conditions appear when relied on; absent fields are not filled by generic unions.CC-E18.1-3The stable core works without a separate carry-through episteme or explicit structure: accepted claim, receiving use, concrete question, applicable pattern contribution, returned result or a justified stop, split, and smallest local return. When explicit structure is needed, A.22.CGUS and E.18.3 select the exact structure; E.18 keeps several valuations or one internalSubflowRefon one TFS; E.18.NET keeps independently selected flows or nested networks and exact cross-member occurrences. E.18.1 adds no hybrid schema.CC-E18.1-4One wording span from an admitted source may split into several FPF applications; the record does not compress them into one generic token.CC-E18.1-5Result wording is unpacked into concrete result-related relations; a genericWorkResultkind is not admitted.CC-E18.1-6PrincipleFramereferences keep postulates and CHR observability distinct from units, planes, comparators, thresholds, ontology editions, CHR editions, plans, work, evidence, and gates.CC-E18.1-7Measurement,G.11source-currentness relation, reference-plane, method-set, comparator, or problem-side changes return to every application, branch and join that depends on the change.CC-E18.1-8The stable P2W core contains only accepted claim, receiving use and concrete question, applicable pattern contribution, returned result or a justified stop, split, and local return. Reliance notes, explicit E.18.3 structure, development examples, and naming or publication are optional extensions. No extension may add a core input or change a returned result. Relation obtaining and identity, occurrence declarations, admission, production, evidence, gates, decisions, and other neighbouring algorithms remain in the patterns whose Solutions answer those questions.CC-E18.1-9Local boundary wording remains only where it names a near-miss that changes the next P2W application.CC-E18.1-10The pattern leaves one usable next move: apply the pattern that answers the question and use its result, write a compact note when another person or later action needs replay, split independent claims, keep a cue and stop, or reopen only the continuation affected by a changed relation.CC-E18.1-11For a structure-bearing conformance or authoring use, replay at least one pilot from5.3and classify it as several valuations of one TFS, one parent-relative internalSubflowRef, or one E.18.NET network of independently selected members and cross-boundary occurrences. Preserve each member’s boundary. Keep Work, actual transformations, valuations, position bindings andDesignRunTagvalues at their respective leaf TFSs. The self-evolving-spec case keeps use-found evidence outside practitioner-facing prose. Ordinary P2W use does not open this extension.CC-E18.1-12Every carried claim family can be lowered, stopped, split, or reopened throughE.18.1:4.7; a cue from a wording span in an admitted source or from a source-pack cue that cannot name the recovered FPF kind or relation remains a reduced-use cue.CC-E18.1-13Every materialized replay identifies the changed value, occurrence, assertion, or description; its kind andchangedValuePatternRef; what still carries and what no longer carries; the smallest reopened continuation; any currentG.11currentness line; andnextApplicablePatternRef. If the changed object is relation-bearing, the cited result—not a P2W copy—retains its kind, participants, obtaining or claim basis, occurrence-identity rule, and any receiver-conditionedRelationSignatureor typed SlotSpecs.CC-E18.1-14When a generated DPF seed or cheap framework seed enters P2W, the record names theG.2source-use record, selected sourceU.Epistemereference, exactEpistemePublicationRelationoccurrence reference when availability is material, source-pack cue, or source-pack return when that source use is current; the problem-side cue when that is current; the next concrete claim or relation-specific question, including its participants when a relation is asserted; the next applicable pattern selected from the canonical Relations map; and the stop condition that prevents the seed from becoming public authority by generation alone.CC-E18.1-15An actual-transformation continuation carries only a current value or blocker returned byA.3.4; E.18.1 does not reconstruct the occurrence basis or infer actuality or composition from a method, plan, model, description, flow position, adjacency, shared work, or common referent.CC-E18.1-16A work-to-change continuation cites the positive or negative claim or blocker already returned by the named subject predicate’s defining pattern or the applicableA.6.RCDroute. It keeps the actualU.WorkandU.Transformationreferences when they are part of that result, but does not reconstruct occurrence proof, predicate tests, failure classification, or negative-claim closure. The BuildOps and Pump 14 slices show positive carry-through; Pump 14 also preserves the earliermissing-governorstop. A production continuation likewise carries only the result or blocker returned byA.15.PROD.CC-E18.1-17A PatternID reference, selected or recommended continuation, imperative wording, intended realization, plan seed, graph or filled table admits noU.MethodDescription. Membership exists only for an independently identified C.2.1 episteme whose EntityOfConcern is one admittedU.Methodand whose ClaimContent contains at least one substantive way-of-doing claim.CC-E18.1-18Move remains Plain wording for the exact current object or use action. Proposed or chosen work remains distinct from dated performed Work; no universal Move kind, record or relation is introduced.CC-E18.1-19The wording of the local mantra in §4 recalls one decision. Each phrase refers to an independently identified value, as illustrated in the cooling case. The practitioner stops when the applicable neighboring pattern supplies its answer or identifies the missing basis. The five-row table displays the possible continuations.
E.18.1:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| Boundary fanout. The pattern repeats neighboring algorithms or builds a second relation-selection catalogue. | Keep 4.6 as the plain one/several/no-claim branch, Relations as the only question-to-pattern map, and include neighboring-pattern details elsewhere only when a local discriminator or worked case changes the reader’s action. |
| Carry-through-as-procedure. A carry-through structure, diagram, or graph-shaped expression is read as a prescribed project sequence. | Treat it as a way to keep one accepted claim visible across separately answered relation questions. Stop, split, and return guide use of E.18.1; they are not P2W relation kinds or a project-work order. |
| ProblemCard-as-solution. The accepted problem card is treated as method, plan, Work, evidence, or result. | State the carried distinction and next question in conversation; add a compact note only when another person or later action needs replay, then apply the pattern that answers the question. |
Math-as-authority. A U.Signature(profile=FormalSubstrate) declaration, mathematical lens, or near-sameness does all downstream work. | Apply C.29 to the preserved structure, lost structure, payoff, declared use, and stop condition. Continue only through the resulting relation; add a P2W note only when another person or later action needs replay. |
| Generic result token. The word result is treated as one kind, or P2W repeats the whole recovery method. | Ask what you can assert. Apply A.6.P.WMR, then carry only the direct subject claim, A.6.1 application binding, local A.15.PROD or A.6.RCD claim, or bounded non-assertability result it returns. Keep factually unsupported, missing-information, and missing-governor distinct; only missing-governor says that no current predicate definition or occurrence rule can state the claim for the named participants and use. |
Choice-as-commitment. A C.11 choice result is treated as an individual duty, recommendation-as-duty, prohibition, or obtaining commitment. | Keep the option set, comparison basis, choice rule, and choice result under C.11, and apply A.2.8 separately. A generic prescription remains an episteme without an individual commitment. Carry a U.Commitment only when the applicable institution rule and current facts establish its bearer, modality, referents, scope, validity interval, prescription, and instituting basis. Carry the rule’s non-obtaining result when the available facts make its test fail. Return unknown or the pattern’s missing-information result when a required fact is unavailable, and missing-governor[individual commitment institution] only when no current rule can state the commitment. |
| Plan, path, or proximity as actual change. A desired state, model, method, plan, flow arrow, adjacent work occurrence, or common affected referent is treated as an actual or composite transformation. | Apply A.3.4 to the change and the direct work-to-change or A.15.PROD pattern to its separate claim. Carry only the results or blockers they return; shared timing or proximity opens no composition or production claim. |
| Intended realization as MethodDescription. A selected continuation, recommendation, plan seed, imperative sentence or pattern ref is said to describe the Method it may realize. | First identify one C.2.1 episteme and one admitted U.Method; apply A.3.2 only when that Method is the episteme’s EntityOfConcern and the ClaimContent contains a substantive way-of-doing claim. |
| One giant transformation flow. Independently selected development, production, use or evaluation flows are flattened because a diagram or common product connects them. | Keep same-TFS valuations and internal SubflowRef cases in E.18; select E.18.NET only from independently identified members and cross-boundary occurrences. |
| Treating a reminder as evidence of execution. A practitioner infers a plan or performed step from the repeated words or the five-row display. | Use the mantra to recall the decision and the table to locate a possible continuation. Apply the governing pattern to establish which action was planned or performed. |
| Interface shortcut. Interface, port, protocol, connection, resource, or integration wording selects function, method, work, evidence, gate, or architecture by itself. | Recover the module-interface, signature-slot, function, architecture, work, evidence, or gate relation before continuing. |
E.18.1:9 - Consequences
| Consequence | Benefit | Cost or mitigation |
|---|---|---|
| A compact carry-through note can be materialized when another person or later action needs replay. | A practitioner can recover how the accepted problem-side claim led to the applicable pattern contribution and its result. | Ordinary conversation adds no record; transfer, audit, delayed feedback, costly reversal, automation, or durable reuse pays for the note. |
| Positive carry-through structure comes before boundary. | First use is readable before the heavier relation aid. | Boundary checks remain available in one section. |
| The reader can identify what a result claim means. | Artifacts, telemetry, acceptance, measurement, and refresh can be handled by their own records; unresolved role enactability wording goes through E.10.ROLE and then to the pattern for the recovered object or relation. | More than one application may be needed for one wording span from an admitted source. |
| P2W stays non-procedural. | The pattern can be used in many project situations without prescribing one local procedure. | A work procedure comes from method material or A.15.2 planning material outside P2W. |
| Related patterns keep their authority. | P2W avoids duplicating evidence, gate, decision, architecture, publication, mechanism, and work-family doctrine. | Users consult the pattern named by the recovered relation when that relation is being made. |
E.18.1:10 - Rationale
E.18.1 is a child of E.18 because a P2W use may need transformation-flow structure when the accepted claim spans several slices, typed positions, or returns. It does not define graph semantics or prescribe performed-work order.
It helps a practitioner keep the accepted claim visible while selecting the pattern whose Solution answers the next question. P2W preserves the carried claim; the practitioner or another capable system obtains or amends the downstream result by applying the neighbouring guidance.
E.18.1:11 - SoTA-Echoing
The table identifies the comparators for specific P2W moves in the assessment dated 7 August 2026. Each row states the adopted contribution and its use limit.
The synthesis that combines these moves into one P2W carry-through discipline is an FPF-scoped architectural hypothesis, not established SoTA.
The sources support the problem-first, relation-separated, replayable moves named in their rows; they do not establish that P2W is a universal workflow or that one carry-through claim is sufficient for every downstream claim.
The hypothesis is limited to one accepted problem-card claim, one stated decision or use that needs it, and one result or stop from the pattern that answers the question. Outside that boundary, apply the pattern whose Solution answers the claim, split independent claims, or stop.
| Source and currentness role | Move adopted in P2W | Overread rejected and practical effect |
|---|---|---|
| Roger Jiao, Towards rigorous problem formulation for engineering design research: from motivations to measurable claims via metric-measure-method, Journal of Engineering Design 37, 2026. Current engineering-design research comparator for problem-first coherence and method-first failure. | Keep the accepted problem-side claim, characteristic meaning, measurement relation, method, and validation use connected. Select the method only after the practical question and relevant characteristic or measurement relation are recoverable. | Its Metric-Measure-Method vocabulary is not imported as FPF ontology: FPF keeps each characteristic, scale, measurement, and U.Method question with the pattern whose Solution answers it and carries only the returned result. Tool availability, fashionable AI, or a ready dataset cannot choose the problem or method. |
| Jenny Zhang et al., Darwin Godel Machine: Open-Ended Evolution of Self-Improving Agents, 2025; Nico Pelleriti et al., What Do Evolutionary Coding Agents Evolve?, 2026. A recent open-ended agent-evolution system paper paired with the current diagnostic limitation study. | Preserve generated variants and stepping stones in exact C.18 or C.19 structures; preserve the evaluator, edit history, comparison basis, and replay relation before interpreting a higher score. | Archive membership or best benchmark score does not establish new algorithmic structure, method superiority, performed work outside the run, or subject improvement. Pelleriti et al. show why replay and intervention on search traces are needed to distinguish structural novelty, retuning, recombination, and evaluator overfit. |
| Yoichi Ishibashi, Taro Yano, and Masafumi Oyamada, Effective Harness Engineering for Algorithm Discovery with Coding Agents, 2026. Current harness-design study under fixed budget with explicit evaluation-hack and parallel-execution concerns. | Keep generation method, harness, evaluator, budget, safety boundary, comparison, selected result, and later work as separate questions, using the definitions or tests that answer each one. | A score produced by an exploitable evaluator or unsafe execution harness cannot carry method selection, evidence, gate passage, or work-entry use. More generated candidates do not substitute for an admissible comparison basis. |
| Haoxiang Qin et al., A survey on Quality-Diversity optimization: Approaches, applications, and challenges, Swarm and Evolutionary Computation 100, 2026. Current peer-reviewed QD survey comparator. | Keep descriptor space, diversity relation, archive or front, comparator, selected-set result declaration, and actual publication distinct. | A front or archive is a structured retained set, not a scalar winner, method choice, decision, WorkPlan, or permission to start work. Descriptor or distance change reopens only dependent comparison and selection continuations. |
| Sarah Malik and Antonios Kontsos, A Digital Thread Approach for Real-Time Defect Correction in Polymer Additive Manufacturing, 2026; Sastry Veluri and Kannan Gopala Krishnan, Agentic Digital Thread for Managing the Non-Conformities in Manufacturing of Aerospace Products, 2026. Current manufacturing feedback and proposed agentic digital-thread cases. | Connect sensed defects, process state, design or process correction, quality use, and return through exact relations; preserve the dated work occurrence and reopen only the dependent design, method, planning, or decision continuation. | Data continuity, report generation, confidence prediction, or a named digital thread does not itself establish evidence sufficiency, approval, decision, permission to act, or completed correction. The aerospace architecture is one proposed domain implementation, not universal P2W ontology. |
| JuliaHub, Dyad changelog, component syntax, and analysis documentation, 2026. Bounded relation-first multi-domain modeling comparison using the cited component and analysis documentation. Modelica 3.7 is retained only as historical acausal-modeling lineage, not as the SoTA basis. | Keep reusable model components and relations, analysis definitions, model compilation, solver or simulation work, and analysis results separate by applying the definitions or tests for each claim. The component, analysis and compilation distinctions inform the diagram and model-use boundary; this analogy does not establish an E.18.3 qualification. | Acausal model structure or an agent-authored model does not become one execution order, performed simulation, empirical evidence, accepted method, or physical result. A model representation can expose a continuation without supplying its downstream authority; historical Modelica lineage supplies no such authority. |
The Jiao article, QD survey, manufacturing digital-thread papers, historical Modelica 3.7 specification, and cited Dyad component and analysis documentation are publication or practice anchors. The Dyad comparison concerns separation of component models, analysis definitions and execution; Modelica remains historical lineage only. At the time of that assessment, the DGM paper provided a recent system result. The 2026 EvoTrace and harness papers were then preprints, with the uncertainty that status carried. Reopen these adoptions when stronger studies change problem-first method selection, distinguish generated structural novelty differently, revise evaluator-hack controls, alter QD archive semantics, or show that digital-thread continuity warrants a stronger use than the exact direct relation currently supports.
E.18.1:12 - Relations
-
Apply
A.22.CGUSwhen P2W identifies one A.22 structure whose local loci, selected relations, applied constraints, and at least two potential continuations are recoverable. Judge enabled, disabled, unknown, and error outcomes for the present case separately from structure identity and membership. -
E.18.3qualifies that A.22-selected CGUS through positions, bindings, and already-obtaining occurrences from one independently identified E.18 substrate. E.18 defines the one-TFS and parent-relative internal-SubflowRefinterfaces; E.18.NET defines independently identified network members and obtaining cross-member relations. P2W cites those values, adds no subset, reciprocal record, or hybrid structure schema, and neither reidentifies nor routes them. -
Before hardening a source-derived DPF seed, recover the needed source contribution and its limits through the sufficient source route in
E.4.DPF:4. UseG.2when that requires a broad, refreshable CG-Frame pack across competing traditions. AddA.10when the source-to-use account is implicit or must remain replayable,G.6for addressable path citation or shared provenance representation,B.3for assurance of a named reliance use, andG.11for currentness and refresh only when that stronger use is current. -
E.4.DPFguides DPF authoring;E.4.CMdevelops the connected Methods and their explanation from the field’s working questions before they are assigned to patterns. When the framework-architecture question is live,E.9records the selected answer andE.4.PFADprofiles its framework-specific content;E.4.PFRhandles an optional framework-relation record only when a named maintenance use needs one. -
E.23defines and tests repeated quality improvement only after the object version and evaluation are recoverable; P2W may carry a seed to that point but does not become the improvement method. -
G.11defines and tests currentness, admitted-source decay, source-use relation change, edition change, and refresh when a changed source publication, source-use relation, or telemetry reopens the P2W applications that depend on that change and their consuming continuations. -
E.18defines and tests the selectedTransformationFlowStructure, its participant positions and resolved connection positions q, flow valuations, crossings and local state bindings. Each q resolves through rho to one selected internal relation occurrence r; establish r under its direct predicate and occurrence-identity rule. ApplyA.20for a current internal constraint-validity claim andA.21for a current gate profile application, check mapping or gate decision; cite those separate results only when the P2W continuation uses them. -
C.22.2defines and tests the accepted problem-side record and problem-side claims related to the carried distinction. -
A.6.Psupplies recovery and readable statement of each direct relation.A.6.RELdefines and tests direct obtaining, occurrence individuation, and receiver-conditioned use of any reusableRelationSignature; P2W cites the occurrence, assertion or description returned there without repeating its defining rules in ClaimContent. UseA.6.RCD,E.24, andE.24.UKfor any later P2W relation-kind candidate and admission, whileA.6.0declares aRelationSignatureonly after that settlement. F.8/F.18/F.17 open only when an external naming or publication use is current; the header’s Tech/Plain pattern label and local note-field phrases create no NameCard, term row, U-kind, relation or MethodDescription.
Canonical question-to-pattern map. Read each row independently. The row order is not a declaration or work sequence, and each pattern keeps the definition, test, and basis of the result it returns.
| Current object or question | Pattern to apply; P2W keeps only its result or stop |
|---|---|
Mathematical-lens use; FormalSubstrate or PrincipleFrame declaration; ontology or admission | Mathematical-lens use -> C.29; profile-specific signature declaration -> A.6.0; residual relation-kind settlement -> A.6.RCD; admission of the settled candidate -> E.24 or E.24.UK. These are separate questions. |
| UTS publication; semantic Bridge; characteristic space; measurement; subject-specific evaluation; normalization; comparison; parity | UTS publication -> F.17; Bridge -> F.9; characteristic-space construction -> A.19; measurement -> C.16; evaluation -> the pattern that defines the subject-specific criterion and test; normalization -> A.19.UNM; comparison -> A.19.CPM; parity -> G.9. A measurement or evidence result is not an evaluation, permission, readiness, gate, or decision result. |
| Mechanism; mechanism-method stabilization; Method identity or development | Mechanism declaration -> A.6.1; stabilization of its method connection -> E.20; reusable way of doing -> A.3.1; finding or developing a needed way -> C.39; its connected framework contribution -> E.4.CM. |
| Transformation; temporal aspect; temporal-claim adequacy; dynamics | Actual bounded transformation -> A.3.4; temporal aspect -> C.27.TA; adequacy of a temporal claim for use -> C.27; dynamics episteme -> A.3.3. |
| Archive or front; retained exploration value; live pool; selector; parity; selected-set declaration; publication | Archive or front -> C.18; still-live pool -> C.19; selector -> A.19.SelectorMechanism; parity -> G.9; selected-set declaration -> G.5; source-backed publication face -> E.17; publication occurrence, form, carrier, audience, bounded use, and availability -> E.24.PUB. A pool, selected set, and publication are different results. |
| Alignment; dated Work; planning; planned filling; appearance-based reliance; work-entry readiness; work-to-change; production; unresolved result wording | Alignment -> A.15; Work -> A.15.1; planning -> A.15.2; planned filling -> A.15.3; reliance repair -> A.15.4; readiness -> A.15.5; work-to-change -> its named subject predicate or the applicable A.6.RCD route; production -> A.15.PROD; unresolved result, input, or handoff wording -> A.6.P.WMR. P2W cites the returned claim or blocker rather than repeating its proof. |
| Generator autonomy; evidence; assurance; provenance | Generator autonomy -> E.16; evidence -> the applicable subject-support grounds and A.2.4; implicit or required-replayable source-to-use account -> A.10; assurance for a named reliance -> B.3; a needed citable or shared provenance path -> G.6. An autonomy declaration supplies none of evidence, assurance, permission, or performed Work. |
| Acceptance record, label, or claimed acceptance | Name the acceptance question and apply the pattern that defines or tests its predicate. Carry its result or blocker. A record or label does not establish acceptance, and C.25 defines no universal acceptance predicate. |
| Step constraint validity; subject or regulatory conformance; FPF pattern-quality review or admission | E.18 step validity -> A.20; other conformance -> the pattern or regulation that defines its test; FPF pattern-quality review -> E.21; admission, refresh, or return after that review -> E.19. None supplies universal conformance. |
| Gate decision; permission; release; work-entry readiness; local choice; commitment | Gate decision -> A.21; permission, exercise, or conflict -> A.2.8.PER; grant or revocation act -> A.2.9; obligation or prohibition -> A.2.8; release Work -> A.15.1; subject-release relation -> the pattern for its named predicate; readiness -> A.15.5; local choice -> C.11. Ask these separately. |
| Architecture; architecture description; structural view; problem-to-structure architecturing; reusable structure; cross-scope or interlevel residual | Architecture -> C.30; architecture description -> C.30.AD; structural view -> C.30.ASV; problem-to-structure architecturing -> C.32.P2S; reusable structure -> C.31; cross-scope or interlevel residual -> C.30.ILC. |
| Module interface; function-like claim; wording use | Module-interface relation -> A.6.M; function-like claim -> A.6.F; wording-use repair -> E.10. |
| Multi-view publication face or form; publication occurrence and bounded availability; explanation faithfulness; publication Work | Face or form -> E.17; publication occurrence and bounded availability -> E.24.PUB; explanation-faithfulness use -> E.17.EFP; rendering, upload, indexing, or other publication Work -> A.15.1 plus the direct relations current for that Work. Form, carrier, occurrence, Work, access, and reliance remain distinct. |