FPF Reference

    C.3.A:B.3 Designing the evidence matrix [I]

    Preface node heading:c-3-a-b-3-designing-the-evidence-matrix-i:39628

    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

    A practical way to plan LA/VA is a matrix:

    Row setColumn setCell content
    Kinds (subkinds or masks)Context slices (Standard versions, env ranges, Γ_time)Evidence unit (proof fragment, test batch, monitoring window), with Scope and MemberOf predicates attached
    • Choose rows. Start with the kind and list relevant subkinds (notation hint: kᵢ is a subkind of k) or stable RoleMasks.
    • Choose columns. Split your declared Scope (G) into named slices you intend to support (e.g., “dry, speed up to 50” and “wet, speed up to 40” with specific rigs and versioned Standards).
    • Fill cells. Attach one or more evidence units per cell (proof obligations for VA; test campaigns/monitoring windows for LA). Mark bridged cells and their CL/CL^k penalties to R.

    Tip. For formal kinds and “up‑to‑iso” kinds (AT K2/K3), expect more rows (more variants to cover). For instance‑like kinds (AT K0), expect fewer rows and tighter columns (narrow slices, stricter freshness).

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)