E.18.1:4 - Solution
Local P2W mantra. Use this Plain recall formula for one working decision: which exact 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.
| Formula term | Identified value |
|---|---|
| Carry the accepted distinction | one exact 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 exact 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 exact result, reduced-use cue or blocker returned by that pattern; 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 formula is neither U.Method, U.MethodDescription, U.WorkPlan, dated U.Work, actual U.Transformation, CGUS nor a P2W relation. Imperative grammar and repetition establish none of those objects. The five rows below are a readable display of conditional continuations, not the mantra itself and not a project-work order.
| 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 honest 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 exact 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 current 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, and wording performs nothing.
The decision aid below helps the practitioner choose the one 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 any later reader replay the path truthfully:
- Ordinary conversational use. Repeat the local P2W mantra, 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 exact selected structure defined and tested by
E.18.3, A.22.CGUS and, for independent members, E.18.NET in4.0bonly when branches, joins, guards, preserved structure, omitted-structure notes, path slices, or neighboring identified positions matter to the receiving use.
Choose a higher level only when its transfer, audit, delayed-feedback, costly-reversal, automation, durable-reuse or explicit-structure need is present. More fields do not improve the subject result and do not substitute for applying the pattern whose Solution answers the question.
What is always needed, and what is optional. The stable P2W core is only: one accepted problem-side claim; one receiving decision or use; one concrete relation-specific question; one pattern contribution per independent claim; the result or honest stop returned by that pattern; a split when several claims are current; and the smallest local return when a relied-on result changes.
| 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 only when branches, joins, guards, paths, preserved structure or stop/return positions matter; 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 | Apply the pattern whose Solution answers the exact claim; this is not a P2W extension | 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. When an extension is not needed, omit it rather than filling its fields with generic placeholders.
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 particular 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. 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 the mantra reaches one result or honest stop without making the episteme, structure, reader or checklist perform work. Pattern authoring or review additionally replays the cases, neighboring-pattern boundaries, checklist, and no-new-kind and non-procedural boundaries. 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. 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 another person or later action to replay the claim, use the C.2.1 episteme in 4.1. Its identity is its ClaimGraph, the accepted ProblemCard@Context as EntityOfConcern, and the effective U.ReferenceScheme. The ClaimGraph records the accepted card edition and carried claim slice, decision or use relying on the result, concrete question, applicable pattern reference, particular contribution used, returned result kind and ref or exact 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.
The conversational, transfer, audit, delayed-feedback, automation, and durable-reuse cases in this pattern need a truthful, replayable claim; none 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 actually 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 honest stop on a separate continuation. It defines none of the selected relations or results; it cites rather than reproduces the neighbouring guidance.
The table below is the complete P2W-local decision aid. It asks only what result or blocker the applicable pattern returned for this use; it does not copy that pattern’s test, derivation, or admission method.
| 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 an exact 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 exact 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 exact 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 honest stop, split, and smallest affected continuation; 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
Open this extension only when the reader must show explicit branches, joins, guards, paths, preserved structures, omitted-structure notes, or distinct stop and reconsideration questions. Identify one exact 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 exact 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 actually 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 exact 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 exact 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 exact 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 that resolve to one exact TransformationFlowStructure remain valuations of that one TFS. A detailed internal portion that resolves only through the same TFS positions and internal U.Transfer occurrences remains one parent-relative SubflowRef. Two or more independently identified TFS or nested-network values connected across their boundaries by exact already-obtaining relations require one E.18.NET TransformationFlowStructureNetwork; do not flatten them into one giant TFS. Every network member retains its own boundary, Work, actual transformations, valuations and leaf-local position binding or DesignRunTag. Each nested boundary reference resolves through one finite acyclic memberPath[] to an exact ExposedFlowPositionRef; each selected cross-boundary claim cites its exact obtaining occurrence and complete ordered endpoint bindings through one resolvable NetworkCrossFlowRelationRowRef. Membership is acyclic; a feedback relation may cycle only when its exact 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 handles one-TFS slice-local refresh; E.18.NET handles independent members and exact cross-member occurrences. P2W reopens only the smallest affected application.
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 exact 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: particular definition, admission, selection, method, decision rule, publication rule, returned result, or other concrete contribution used in this case
returnedResultKindRef?: exact kind returned by that pattern
returnedResultRef?: exact positive result, relation occurrence, assertion or description
honestStop?: exact 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 particular contribution used per continuation
returnCondition?
A positive use fills the exact 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 thereby 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 actually 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. The four rows below are discriminators, not a second relation-selection map; use the single map in Relations only after the question is stated.
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 actually 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 exact 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 one claim actually 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.
Use E.8 for 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. P2W preserves the carried claim only until the next concrete claim or relation-specific question is stated and its applicable pattern is selected.
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 now. 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. Prototype observations enter through A.10; assurance-sensitive confidence use enters through B.3. 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.
The current next question in this example is: which retained layouts belong in the current C.18 front? The next applicable pattern is C.18, and its result is the 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. The selected name keeps the work-facing receiving use visible without implying a generic value endpoint, a linear continuation or path, unchanged preservation, or a principle-only source; it is the widened successor to Principles-to-Work Carry-Through. If MethodDescription membership is actually needed, first identify one C.2.1 episteme, require one independently admitted U.Method as its exact 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. Before any external citation or tool-interface reuse, F.8 decides whether a name is needed; F.18 settles the name only for that exact governed value and use; F.17 publishes the exact scheme-local sense and source basis. 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 actually 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. |
This example exercises the ordinary route: 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 a returned value or stop; it does not restate the neighboring pattern’s internal test. 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. A timestamp or a before-and-after picture supplies none of those answers.
- 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 exact 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. A label, diagram, note, plan, trace, or familiar noun can trigger that question but cannot answer it.
E.18.1:4.4 - Boundary and relation discipline
P2W does not repeat the boundary rules of neighbouring patterns. Its local rule is simple: carry only the accepted problem-side distinction, state the next relation and participants, apply the pattern whose Solution answers that question, and continue only with its result or honest stop. Split several relation claims; if no relation can be stated, retain the cue and stop.
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. Section 4.6 is the plain branch rule; Relations is the only question-to-pattern map. 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 new local return to the smallest affected application rather than retroactively keeping every earlier application open.
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 exact 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 exact 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 exact question changed. |
| The accepted ProblemCard claim itself | Amend or replace the problem-side result under its direct problem pattern. | Every and only continuation that relied on the changed distinction. |
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
First say the unsettled question as 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. Then name the participants and relation that sentence asserts and take one 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 exact 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 exact 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 exact 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 exact 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 exact blocker. | Carry that result unchanged and stop only the dependent claim. | An honest 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. An ordinary local return uses 4.5 and creates no 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 exact 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 exact 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.