A.6.B:5.4 — Quadrant E: Work‑Effects & Evidence
Preface node
heading:a-6-b-5-4-quadrant-e-work-effects-evidence:8031
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/metrics, produced reports, measurement outcomes.
Adjudication. In‑work: checked by running/operating and inspecting carriers produced in work.
Canonical form. An E-* statement SHOULD include the minimum fields needed for adjudication:
- Observation/measurement conditions (when/where/how observed; workload/window; triggers)
- Carrier class/schema reference (A.7 Carrier) that bears the evidence
- Viewpoint/consumer (who uses this evidence and why; ties to
viewpointRefdiscipline)
Prohibitions.
E-*statements SHOULD NOT use RFC deontic keywords (they are not obligations; they describe adjudicable effects/evidence).- An
E-*statement MUST NOT hide a gate predicate; gate predicates areA-*. - An
E-*statement MUST NOT assign agency (“the interface guarantees …”); if enforceability/commitment is intended, express it asD-*referencing theE-*.
A.7 anchoring. E-* claims are primarily Carrier‑anchored: they assert what carriers exist and how they relate to observed work.
Required references (explicit).
- If the effect/evidence is conditioned on a gate decision, the
E-*statement SHOULD reference the relevantA-*ID(s). - If the evidence is interpreted using metric definitions or invariants, the
E-*statement SHOULD reference relevantL-*ID(s).
Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)