Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 18:05:19 UTC

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 questionRequired interface resultP2W 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.