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

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 09:45:10 UTC

E.10:9.2 - Diagnostic examples, not substitutions

Use these rows only after the compact cue surface selects the named lexical problem. Accept a repaired sentence when its object, head kind, relation or claim, use, and scope are preserved, the applicable § 7 or § 8 rule passes, and the changed sentence passes the local F.19 reread. If an example would change the kind in the current sentence, split the claim or leave a blocker; do not copy it as a ready-made rewrite.

Trigger symptomRecovered ontology example
“the process owner approves”Start with E.10.ROLE for the title-like wording. If owner names an architectural or responsibility relation, keep that relation instead of forcing a system-role reading. State ApproverSystemRole separately only when the classification matters. If approval is precise performed Work, recover ApprovalSystem through A.13 and let A.15.1 independently admit the dated Work. Add F.6 only when the sentence or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Keep the approval speech act, authority, and decision separate.
“the document enforces policy”Policy_vN states the policy used by the applicable gate, constraint, commitment, or evidence relation. When enforcement Work is current, name its actual performer, admit the dated Work through A.13 and A.15.1, and add F.6 only for a precise assignment-bound attribution. Add PolicyEnforcementSystemRole only when that classification changes the claim.
“our service runs nightly jobs”Apply L-SERV and A.6.P:4.11a first. If the sentence means dated service-provision Work performed by a scheduler system, recover that exact actual performer through A.13 and let A.15.1 independently admit the Work. Add F.6 only when the sentence or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Add SchedulerSystemRole only when that classification matters. Promise content remains separate.
“the API is the service”Apply L-SERV and A.6.P:4.11a. A reusable way of access may be API_Access_Method : U.Method; a claim-bearing interface specification is an episteme and becomes U.MethodDescription only under A.3.2; an addressable endpoint is a separate bearer; use A.1.SCR for it only when the claim depends on systemhood. Any API publication form/carrier remains separate, and promise content states the promised result and acceptance criteria. The source wording chooses none of these by itself.
“capability assigned to team Y”Split the claims. TeamY may be an admitted System that has Capability C within envelope E. If the wording also means a work-facing classification, name its local system-role kind; if it means an assignment, name the occurrence with TeamY as holder and its declared U.SystemRoleAssignment species. Capability, classification, and assignment do not establish one another.
“process health green”Apply A.19.SPR: name the bearer, state frame, value green, criteria or evidence, admissible use, and change condition; the color alone does not establish health or acceptance.
“function of component A fails”Apply A.6.F. If the recovered claim is behavior performed as Work, recover the exact actual performer system through A.13 and let A.15.1 independently admit the dated Work. Add F.6 only when the sentence or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Add ServiceOperatorSystemRole only when that classification matters. The evaluation result separately records failed acceptance on the cited observations.
“context is unclear here”Apply E.10.D1 and name what changes the interpretation or next action: the exact source and edition, effective scheme, claim scope, model-use structure, working situation, frame, referent, or local practice. If two local senses are compared, identify them; assert an F.9 Bridge only when its direct relation between exact cells actually obtains.