FPF Reference

    WORKING-DOCUMENTS - Create a document another participant can use

    Preface node heading:working-documents-create-a-document-another-participant-can-use:502

    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

    • Situation and question. A participant asks for a regulation, procedure, plan, interface description, permission text, evidence note, gate record, publication, or AI tool-use plan. Ask first which use is current for the text: preserve meaning and boundary claims, prepare enactment, support reliance or a gate, or publish already governed content. The reader inspects only the branch selected by that question.

    Branch A: preserve meaning and boundary claims.

    • A.6 Solution -> Claim Register or an equivalent small claim set classified as L, A, D, and E when one text mixes definitions, admissibility, commitments, and evidence claims.
    • A.3.2 Solution -> U.MethodDescription when an already identified claim-bearing episteme has one admitted U.Method as its exact EntityOfConcern and makes at least one substantive claim about that way of doing; representation, publication, plan, and Work remain separate.
    • A.2.8 Solution -> U.Commitment when an accountable subject's obligation, recommendation-as-duty, or prohibition, scope, validity window, and referents are the actual result.
    • A.2.8.PER Solution -> NonProhibitionFinding@Context | GrantedPermissionRelation@Context | PermissionExerciseRelation@Context | NonViolationFinding@Context | PermissionNormConflictFinding@Context when strong/weak permission, actual exercise, non-violation, or conflict is the actual result.
    • If interface still hides whether the current claim concerns a signature, slot, module interface, functional port, protocol, service relation, or publication, use A.6.RSIR only to select the direct governing pattern, retain a reduced-use source label, or return a blocker. RSIR does not produce the downstream interface result. Once the direct claim is recovered, use its pattern and exact result; use A.6.M directly only for a recovered module-interface relation.

    Branch B: prepare enactment.

    • A.15.2 Solution -> U.WorkPlan when stating intended dated work, PlanItems, assignments, resources, windows, or sequencing constraints is current.
    • C.24 Solution -> CallPlan | CheckpointReturn when tool-call enactment is current: use CallPlan after routes and budgeted execution are fixed enough, or CheckpointReturn while bounded probing remains the honest result.
    • A.15.5 Solution -> WorkEntryReadiness@Context only when intended work already exists and readiness to cross its work boundary is current.

    Branch C: support reliance or a gate.

    • A.10 Solution -> claim-bound evidence-provenance graph relation when a named receiving use relies on recovering the basis for one claim or effect through evidence-producing or interpreting work, trace, time window, and bounded use.
    • B.3 Solution -> the lightest result for the named use: an explicit no-assurance-claim disposition, a compact bounded assurance-result claim, or a full AssuranceResult(E_C, U_A | RS_A, G_A, T_A) when the text is expected to carry a named assurance claim rather than merely point to evidence.
    • A.21 Solution -> OperationalGate(profile) use with GateProfile, effective GateCheckRefs, aggregated CV status, GateDecision, and DecisionLogRef when exposing an actual gate decision is current. A readable checklist is not that decision.

    Branch D: publish governed content.

    • E.17 Solution -> source-pinned publication face when readable, exchangeable, or citable publication of an already governed episteme or relation is current without changing the underlying claim.

    • Boundaries. Stop when the selected branch yields the exact result needed by the named use. Reconsider branch selection when that use changes. A single document may cite results from several branches, but page proximity does not merge their kinds or transfer their claims. RSIR stops at pattern selection, reduced-use source labeling, or a blocker; it never certifies that an interface relation now exists.

    • Result test. Start with the useful result or honest stop named by the selected bullet and the current project question or action it answers; a document label or file does not identify that result. If this is sufficient and no downstream identity or reliance is current, stop there. When the result's kind, identity, obtaining, application, or reliance changes the claim, identify it with the definition or test in that bullet's Solution, name the relevant method, U.WorkPlan, dated U.Work, evaluation, GateDecision, assurance or evidence-reliance use, permission exercise, or publication occurrence, and cite the relation, binding, or supported local claim that makes it a result for that use. Name a downstream reader, gate, work item, or publication only when it is current; otherwise state the exact missing predicate, fact, reliance, or information.

    • Public coarsening. “Working document” is only a recognizable situation label. The expansion restores the selected branch, the concrete contribution from its cited Solution, the exact result, and the named use.

    Last Updated: 2026-08-05 — upstream FPF commit 3dbce514 (github.com/ailev/FPF)