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

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

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 an actual occurrence, evaluated finding, observed condition or evidence-support claim. Settle it from the actual work, evaluation, observation, or carrier conditions required by its predicate.

Adjudication. From actual work, evaluation or observation under the claim’s subject predicate. A record can support that judgment through its evidence relation; its presence alone does not settle the claim.

Canonical form. Write the ordinary result first, then make recoverable only what settles it:

  1. the predicate and object that the claim concerns;
  2. the participants, work or evaluation occurrence, scope/window, comparison frame, and other conditions required by that predicate; and
  3. the evidence or source-use relation when the receiving use needs that support; identify the supporting carrier only when carrier identity matters to that use. A carrier may support the claim but does not create the work, effect, or finding.

When permission wording is current, use the branch in §8.4.1 for the occurrence or finding, its failure test, predicate, and subject-pattern locator; do not repeat that subject-question catalogue here.

Prohibitions.

  • E-* statements SHOULD NOT use RFC deontic keywords; they report adjudicable results rather than obligations.

  • An E-* statement MUST NOT hide a gate predicate; gate predicates are A-*.

  • For a claim about a particular dated Work, first recover each actual performer through A.13 and let A.15.1 independently admit the Work. Ordinary metonymy is usable when the capable performer remains recoverable; an interface, record or publication does not supply a performer merely by being named.

    Add an A.2.1 assignment reference and F.6 only when this claim or its receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither the assignment nor the performer. Missing or failed F.6 alone does not overturn independently admitted Work.

    If the attribution finding questions a premise consumed by Work admission, recheck that premise and the dependent claims. If a duty or commitment is also claimed, express it separately in D-*.

A.7 EntityOfConcern binding. An E-* claim episteme concerns the work effect, evaluated finding, evidence relation, or carrier condition named by its predicate. A record or carrier is a separate object and becomes the concern only when its existence or condition is itself the claim.

Required references.

  • If the result depends on an entry predicate, the E-* statement SHOULD reference the relevant A-* claim. If it depends on an actual gate decision, reference the separate E-* claim about that A.21 decision result.
  • If another object is needed to settle the predicate, reference that object's subject pattern without importing its quadrant.
  • If evidence is used for reliance, recover the independently established support or evidence-use relation and its basis. Use A.2.4 for the first evidence-use or status-use classification; use A.10 when the source-to-use account must remain replayable, and G.6 when an addressable provenance path is needed. Carrier presence alone is not support.

Last Updated: 2026-11-22 — upstream FPF commit 7a93d8f8 (github.com/ailev/FPF)