FPF Reference

    C.3.A:C.2 Method–Work obligations (normative)

    Preface node heading:c-3-a-c-2-method-work-obligations-normative:45783

    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

    This Method–Work slice is conditional; it is not a definition that makes every actual change agentic, capability-held, planned, method-mediated, or Work. Open its capability/method/WorkPlan entry checks only when those objects and an A.15.1 Work use are current. A natural, spontaneous, formal, jointly caused, or non-separable U.Transformation remains under A.3/A.3.4 and does not acquire a fictive performer, role assignment, method, capability, plan, or Work to satisfy this guard. A broader scale-free-agency or Work decision remains with A.13, C.9, and A.15.1; this annex neither settles nor forbids it. Reflexive cases require separately grounded acting and affected positions, while joint or non-separable cases keep their direct dynamics, interaction, or causality governors rather than forcing one arbitrary actor-target split.

    When the Method–Work use is current, it has two different boundaries.

    Prospective entry. Before execution, a guard may decide that a holder capability, method, intended U.WorkPlan, JobSlice, and candidate inputs are sufficient to start. That decision SHALL NOT claim that Work already occurred. The capability instance, capability statements or currentness assessments, fit predicates, WorkPlan, JobSlice, and entry record remain distinct.

    Actual result or acceptance. When performed Work is current, the guard SHALL identify exact W : U.Work as an independently grounded, world-side, dated 4D Work occurrence under A.15.1. W is not the U.Work kind, JobSlice, capability, plan item, log, card, row, or assertion. Any plan, log, result record, or assurance record about W is a separate episteme that designates W.

    A conforming Method–Work check SHALL:

    1. require the capability's governed Work scope to cover exact JobSlice with explicit time;
    2. check capability measures, qualification/currentness, and fit as separately governed predicates;
    3. pin every expected input/output local kind and signature edition;
    4. for every actual input candidate, evaluate J(inputCandidate, expectedInputKind, inputSignatureEdition, JobSlice) and preserve all three values;
    5. use exact RoleMask declarations and masked judgments when procedural tailoring is current;
    6. establish exact target bridges/declarations and fresh target judgments for cross-context candidates;
    7. before execution, return only an entry disposition and keep W absent;
    8. after execution, identify W independently and, for every actual output candidate relied on, evaluate the exact output judgment;
    9. keep W, inputs, outputs, JobSlice, capability, plan, logs, and assertions distinct; and
    10. refuse fail-closed on false or unknown without rewriting either value.

    Last Updated: 2026-07-28 — upstream FPF commit 17edd955 (github.com/ailev/FPF)