FPF Reference

    Core stress-case rule

    Preface node heading:core-stress-case-rule:21756

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    Ordinary source-restoration note. In ordinary use, do not build a source dossier. The first useful note is:

    encounteredSourceCandidate; work or reliance claim under repair; claim or effect needed; governing source needed; relation-governed move now; blocked overread; stop or reopen condition

    The encountered source candidate may be a tile, credential view, approval-looking memo, generated explanation, copied review, provenance mark, API wording, functional-description publication, or composed source chain. The pattern asks whether the requested claim is currently carried by a project-side source named by value, not whether the source candidate is impressive, fluent, easy to inspect, or visually salient.

    Conditional source-relation field set. Use the fuller fields below only when release, safety, compliance, role assignment, status, gate, assurance, contested source, external reliance, cross-context reuse, currentness, revocation, generated source relation, or copied source relation is being relied on for the claim under repair. These fields are local restoration aids, not a new record kind.

    FieldWorking question
    subject or actorWho or what would perform the work, rely on the source candidate, hold the status, or be affected by the claim?
    role-assignment claimWhich U.RoleAssignment or role-context claim is being made?
    guided action or work targetWhich selected method, method of work, U.WorkPlan, planned work, dated U.Work, work result, release move, reliance move, source status, or effect is being guided?
    affected resource or claimWhich resource, claim, gate, credential, status, evidence, approval, or source finding with authority-reference relation is supposedly affected?
    contextWhich bounded context, environment, project slice, API setting, connector setting, protocol setting, or relying situation makes the claim applicable?
    policy or gate versionWhich policy, gate profile, constraint version, method version, or register edition is supposed to govern the claim?
    time windowDuring which window is the claim, effect, source relation, or recovered-use boundary claimed to hold?
    currentness or revocation fieldIs the source relation current, stale, revoked, superseded, expired, contradicted, or unknown?
    issuer or sourceWhich issuer, governing source, register source, source-status record, speech act, gate decision, evidence path, or work-occurrence record carries the claim, effect, source relation, or recovered-use boundary?
    verifier or relying contextWho is checking or relying on the claim, and in which context?
    evidence or attestation pathWhich A.10 evidence, provenance, or attestation path, if any, justifies the claim without itself becoming approval, gate passage, assurance, or work occurrence?
    sourceRelationClassWhich E.17:5.1b source-relation class or claim-use class applies to the encountered source candidate and required claim or use?
    unsupported effectWhich requested work claim, reliance claim, or downstream effect remains unsupported and needs narrowing, repair, reopening, probing, or blocking?

    Start with the A.15.4 first restoration checks above when the encountered source candidate is about to guide a work move, reliance move, or work-relevant claim. If the issue under repair is only evidence, currentness, gate-passage claim, ConstraintValidity status, engineering justification, commitment, speech act, boundary wording, use-boundary wording, credential proof, source-status proof, explanation, comparison, or publication-carrier or front-end behavior, use the pattern governing that issue directly. Use A.15.4 only when source restoration is needed before role assignment, method, plan, work, work result, result measurement, or another work move or reliance move can proceed.

    Authority-looking source-backed work or reliance case. Use A.15.4 when an approval-, permission-, gate-, command-, credential-, delegation-, revocation-, status-, provenance-, dashboard-, copied-review-, generated-explanation-, schema-, API-, or composed-chain case is about to be used as a work cue, reliance claim source, release-reliance claim source, performed-work evidence source, approval-claim source, approval-effect source, role-assignment-claim source, status-claim source, or next work-relevant move. The recognition moment is that an encountered publication, display, credential view, wording, or explanation looks like permission, prohibition, readiness, or evidence for starting work. The repair question remains: which work or reliance claim is being made, and which source is required for it?

    Here "authority-looking case" is only a recognition phrase for the encountered situation. The governing source that permits, forbids, records, or carries the work-relevant claim may instead be a GateDecision, SpeechAct, U.Commitment, U.RoleAssignment, credential record, status record, A.6.B-claim being made, A.10 evidence path, or B.3 assurance claim. Use E.17:5.1c for the shared meanings of orientation use, reliance use, work claim, reliance claim, operative claim, unsupported downstream use, and reopen trigger; use E.17:5.1d when the primary question under repair belongs to another governing pattern.

    The central behaviour is: name the work or reliance claim under repair, work-relevant P2W claim under repair, or P2W chain position under repair; name the source that carries the needed claim or effect; keep the U.Episteme or U.EpistemePublication distinct from publication form, MVPK face, publication carrier, rendering, and source-finding cue; choose the minimum sufficient next move; and do not raise the claim beyond the recovered relation, source relation, or recovered use boundary. If the named project record states the governing FPF relation, use that recorded relation directly rather than inferring it from wording.

    Positive repaired disposition. An encountered U.Episteme publication, publication form, MVPK face, publication carrier, rendering, or source-finding cue may guide work or reliance only to the claim or effect carried by the recovered source, actor or role assignment, work or reliance claim under repair, work-relevant P2W claim under repair, or P2W chain position under repair, affected work target, context, window, and source-recoverable claim or effect. The repaired outcome is the smallest relation-governed work or reliance statement plus the unsupported work claim or reliance claim still blocked.

    Reliance dispositions by recovered source relation:

    Work or reliance dispositionUse whenMinimum useful record
    Orientation or source-finding noteThe encountered source candidate is only a publication face, publication carrier, rendering, cue, retrieval cue, learning aid, or reversible local probe trigger.encounteredSourceCandidate; required claim or effect not yet carried by a recovered source; source to reopen; stop condition.
    Routine reliance noteThe team needs ordinary bounded reliance without release, safety, compliance, delegated role-assignment or status claim, contested source, or cross-context reuse.Work or reliance claim under repair, work-relevant P2W claim under repair, or P2W chain position under repair; required claim or effect; actor or role assignment; affected work target, context, effective window; source reference exposed by the encountered source candidate; and reopen condition.
    High-impact reliance dispositionThe required claim or effect is external-impact, irreversible, release-bearing, gate-bearing, compliance-bearing, safety-bearing, delegated, revoked, status-claim-bearing, generated-source-mediated, copied-source-mediated, provenance-mediated, contested, or cross-context.Governing source with the A.10, A.6, B.3, A.2.9, A.2.8, A.21, A.20, or A.15.1 fields needed for that claim or effect.

    A small A.15.4 restoration note is enough for the first disposition:

    FieldValue
    work or reliance claim under repair, work-relevant P2W claim under repair, or P2W chain position under repairName the claim or P2W chain position by value: method-family selection, selected method, method of work, work plan, planned work, dated U.Work occurrence, work result, result-measurement, release reliance decision, or non-work reliance claim. A planned baseline remains a U.WorkPlan or U.WorkPlanning plan record; performed work becomes U.Work only after it occurs and is recorded under A.15.1; work-result measurement belongs with the evidence or result-measurement source. This row is a local restoration label unless it cites an existing FPF kind or governing FPF relation.
    governing source neededApproval, permission, gate passage, role-assignment or status currentness, work occurrence, evidence relation, assurance claim, boundary claim, or other claim named by value or effect needed before that work claim, reliance claim, or P2W chain-position claim can be treated as carried by a recovered source. The governing relation is carried by the named FPF pattern and recovered project-side reference, not by a new A.15.4 kind.
    actor or role assignmentWho would act or rely, and which U.RoleAssignment matters when the acting capacity is part of the claim.
    affected work target, context, and windowRelease, service, person, role-assignment holder, work target, claim, tenant, environment, physical batch, construction element, machine state, or effective window affected by that class or claim.
    claim-bearing episteme or episteme publicationThe claim-bearing FPF kind is U.Episteme or a species such as U.EpistemePublication; if the encountered source candidate is only a publication form, MVPK face, publication carrier, rendering, PublicationUnit, dashboard tile, copied text, credential view, generated explanation, API wording, or cue, name that kind named by value separately.
    source needed or safe next moveSource U.Episteme, source U.EpistemePublication, register entry, governing source, source status to refresh, reversible probe, role assignment accountable for exposing or repairing the missing source, or narrower relation-governed use.
    stop or reopen conditionWhat blocks the work claim or reliance claim and what would reopen it.

    Borrowed episteme and publication discipline. A.15.4 borrows the C.2.1, E.17, and A.16.0 distinction rather than minting a new generic U.* kind. The claim-bearing FPF kind here is U.Episteme; U.EpistemePublication is used only when that episteme is available as a published episteme with MVPK-face references. Publication forms, MVPK faces, publication carriers, renderings, PublicationUnit instances, and source-finding cues are separate kinds or relation positions in the case. A planned baseline remains a U.WorkPlan or U.WorkPlanning plan record such as SlotFillingsPlanItem; launch values and finalization values remain their own project records, decision logs remain gate or decision records, performed-work evidence remains evidence, and dated work occurrences remain A.15.1 or U.Work matters.

    When the required source is incomplete, choose one relation-governed source-restoration disposition after naming the work or reliance claim under repair, work-relevant P2W claim under repair, or P2W chain position under repair and the source required for that claim or effect; pick the lightest move that preserves practical work and source recoverability:

    1. Use the encountered source candidate only for orientation or source-finding.
    2. Reopen the required source U.Episteme, source U.EpistemePublication, register entry, or governing source, or refresh status or currentness.
    3. Narrow actor and role assignment, requested operation or work class, affected work target, affected resource, affected claim, context, and effective window until the recovered source really covers the move.
    4. Run a bounded reversible probe under an explicit U.WorkPlan when no external-impact reliance is being made.
    5. Ask the role assignment accountable for the issuer, gate decision, evidence path, role-assignment record, status record, or boundary claim set to expose or repair the missing source.
    6. Repair the U.WorkPlan, U.MethodDescription, dashboard label, source link, or boundary wording that made the overread plausible.
    7. Proceed only inside the recovered scope and window.
    8. Block only the work claim or reliance claim that lacks source relation.

    Last Updated: 2026-06-17 — upstream FPF commit 646b0b9b (github.com/ailev/FPF)