fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 109578–109592

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 08:30:15 UTC

F.12:12 - Safe reasoning moves

  1. Match scope. Confirm that the promise content covers the exact delivery Work or population and keep A.2.3 promise use, delivery, and fulfilment distinct.
  2. Name the window. Make time, batch, phase, and exclusions explicit.
  3. Test direct measurement first. Confirm whether each observation and its measurement model directly concern the promised characteristic; if so, use C.16 and A.10 and add no proxy.
  4. Recover an indicator only when needed. When another characteristic stands in, name both participants, the defining or testing pattern, coverage, and loss. Use C.16.P for recovery and A.6.RCD missing-governor when the relation is absent.
  5. Check values. Name characteristic, scale, unit, aggregation, and uncertainty.
  6. Perform the evaluation. Name the performing System, evaluation Work, enacted Method, exact A.6.1 application, input bindings, and result binding. Cite a particular MethodDescription edition only when it changes the result or replay.
  7. Use evidence directly. Recover the direct evidence-use claims, the descriptive A.10 path and its bounded-reliance disposition. Enter B.3 only for an actual named assurance claim, and E.13 only when a proxy is optimized or drives a decision, gate, incentive, release argument, reputation signal, or repair.
  8. Keep the result on its declared scale. Boolean, trichotomous, graded, N/A, and Inconclusive-including scales are examples, not defaults.
  9. Map status separately. Use RequirementStatus=Satisfied or RequirementStatus=Violated only through the direct acceptance result. Evidence insufficiency can support EvidenceStatus=Inconclusive and leave the requirement pending, or produce an exact locally declared result.
  10. Create a verdict episteme only on demand. Use C.2.1 only when another use needs a durable assertion about the result or status.
  11. Aggregate explicitly. Population-level results and statuses follow the promise’s stated quantifier; they are not inferred from a few green cases.
  12. Preserve history. New promises, monitors, evaluation methods, or scales create new evaluations rather than changing old ones silently.