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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 03:40:20 UTC

A.19.SPR:0 - Use this when

Use this pattern when a phrase such as “the system is ready”, “the source is current”, or “the evidence status is incomplete” matters to an FPF claim but does not yet say which item the sentence is about, what is true of it, or which rule makes that statement meaningful.

What goes wrong if missed. A short status word starts carrying several claims at once. A source label becomes evidence, a readiness label becomes gate passage, or a project-side status leaks into pattern guidance.

First question. Ask:

What exact item is this sentence about, what does it say about that item, and which rule or criterion gives the statement its meaning?

Cheap direct repair. Write the answer as one ordinary technical sentence. Name the item, the actual value, relation, result, or claim, and the rule or criterion only when the reader needs it to understand or act. If that sentence is clear and safe for the intended use, stop. Do not create a repair note or list every claim the sentence does not make.

What this buys. A reader can understand the statement and its next practical use without learning a hidden status vocabulary.

Typical triggers include state, status, posture, stance, currentness, validity, stable, accepted, blocked, candidate, degraded, readiness, ready, and similar compounds. A precise-looking field such as LensUseBoundaryValue or dynClaimPosture is also a trigger when its object, possible values, or rule cannot be recovered.

Not this pattern when.

  • If the exact item, claim or value, and applicable rule are already clear, use that rule directly.
  • If readiness or ready still hides whether the sentence concerns a subject state, assignment condition, work entry, gate decision, publication use, permission, or performed Work, use E.10.MOVE first.
  • If the wording is ordinary prose and carries no FPF-governed claim, keep it ordinary.
  • If one Characteristic, Scale, Coordinate, score, or measurement construction is hidden, use C.16.P first.
  • If a source expression, publication, carrier, or source-use relation is hidden, use C.2.P first and return here only if a state-wording problem remains.
  • For relation, architecture, quality, function, or naming problems, use A.6.P, C.30.P, C.16.Q, A.6.F, or F.18 as selected by E.10.