Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 19:05:20 UTC

A.19.SPR:4.1 - Direct repair

For ordinary prose, inspect only the current sentence:

  1. Find the item. For system-role wording, distinguish an exact local system-role kind, an obtaining assignment, its state condition, the world-side assignment-state relation, and an assertion about either. Do not stop at bare role.
  2. Write the claim. Say that the item has a value, that a relation obtains, that an assertion or result says something, or that a project record has a field value.
  3. Use the direct rule. Cite the applicable pattern when its criterion or distinction matters. If the direct rule already settles the sentence, A.19.SPR has finished its job.

Add a time boundary, evidence basis, allowed use, or blocked inference only under the triggers above. If the item or claim still cannot be recovered, keep the wording as a quotation or navigation cue, narrow its use, or state the exact blocker.

A.19.SPR:4.1.1 - Assignment-state exits
Recovered claimDirect exit
One exact system-role assignment or its holder, with no state condition claimedA.2.1; the assignment itself is not readiness.
A reusable condition for assignments to one exact local system-role kindA.2.5 SystemRoleAssignmentStatePredicate, by value.
One exact assignment satisfies that condition during the relevant intervalThe world-side A.2.5 SystemRoleAssignmentStateRelation occurrence.
An affirmative or negative claim about the assignment or an established relation occurrenceA.2.5 SystemRoleAssignmentStateAssertion : U.Episteme; the assertion is not its EntityOfConcern.
Evidence, currentness, reliance, or an evaluation concerning that assertion epistemeA.2.4, A.10, or the direct evaluation pattern. Keep the assertion episteme distinct from the assignment and world-side relation.
Whether intended Work may enter nowA.15.5 or the direct receiving pattern. A.2.5 may supply an assignment-state input; it does not publish the admission result, gate decision, or Work occurrence.
A.19.SPR:4.1.2 - Readiness exits

When readiness or ready still hides which governed value is meant, use E.10.MOVE first. Once the claim is recovered, leave the wording repair through exactly one direct exit:

Recovered readiness-like claimDirect exit
A subject such as a patient or system has a value in a still-hidden state frameA.19.SPR, followed by the subject pattern that defines or tests that value.
An assignment satisfies an assignment-state conditionA.2.5.
One intended performance satisfies a work-entry criterionA.15.5 work-entry readiness result.
A distinct OperationalGate(profile) consumes declared checks and publishes a decisionA.21; a ready label alone is not gate passage.
A publication use, permission claim, or dated performed Work is meantE.17, the direct permission pattern, or A.15.1, respectively. Readiness wording establishes none of them.