FPF Reference

    A.6.B:5.4 — Quadrant E: Work‑Effects & Evidence

    Preface node heading:a-6-b-5-4-quadrant-e-work-effects-evidence:8920

    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

    Intent. State what happens in work and how it can be evidenced: observed effects, emitted events, traces, logs, and metrics, produced reports, measurement outcomes.

    Adjudication. In‑work: checked by running or operating and inspecting carriers produced in work.

    Canonical form. An E-* statement SHOULD include the minimum fields needed for adjudication:

    1. Observation and measurement conditions (when, where, and how observed; workload, window, and triggers)
    2. Evidence carrier or record reference under A.7, A.10, or G.6 as applicable for the evidence relation or source basis
    3. Viewpoint and consumer (who uses this evidence and why; ties to viewpointRef discipline)

    Prohibitions.

    • E-* statements SHOULD NOT use RFC deontic keywords (they are not obligations; they describe adjudicable effects and evidence).
    • An E-* statement MUST NOT hide a gate predicate; gate predicates are A-*.
    • An E-* statement MUST NOT assign agency (“the interface guarantees …”); if enforceability or commitment is intended, express it as D-* referencing the E-*.

    A.7 EntityOfConcern binding. E-* claims are primarily carrier-referenced: they assert what carriers exist and how they relate to observed work.

    Required references (explicit).

    • If the effect or evidence claim is conditioned on a gate decision, the E-* statement SHOULD reference the relevant A-* ID(s).
    • If the evidence is interpreted using metric definitions or invariants, the E-* statement SHOULD reference relevant L-* ID(s).

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