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:7171

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:

  1. Observation/measurement conditions (when/where/how observed; workload/window; triggers)
  2. Carrier class/schema reference (A.7 Carrier) that bears the evidence
  3. Viewpoint/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/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/commitment is intended, express it as D-* referencing the E-*.

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 relevant A-* ID(s).
  • If the evidence is interpreted using metric definitions or invariants, the E-* statement SHOULD reference relevant L-* ID(s).