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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:15:20 UTC

A.7:14 - Practitioner one-page review (copy-paste)

Ordinary repair account

Engineer Dana repaired pump P-12. MaintenanceNote-e4 describes the repair. Carrier C bears publication form F.

Keep the sentence this short when the receiving use needs no stronger distinction. Contribution nouns such as engineer, reviewer, pump, team, or service are acceptable when the underlying System and contribution are recoverable and no decision, attribution, admission, or reliance depends on a hidden kind or assignment identity.

Reliance-bearing expansion, when needed

The practitioner used A.13 to identify System S as the actual performer with its core basis, then used A.15.1 to admit dated Work W independently from its performance history, enacted Method M, temporal extent, and obtaining containing-System relation. If the receiving account must also say under which assignment W was performed, the practitioner uses F.6 to check that relation against the same obtaining assignment A and compare S with A's holder. Keep the required core facts recoverable; add Capability C, another Method, further detail of local system-role kind K, method-description episteme D, carrier P, evidence-use relation R, or resource relations only where the receiving claim relies on them.

Six checks

  1. Acting subject: Is the acting System recoverable? If assignment identity is not used, do not invent it.
  2. Current distinctions: Are Method, Capability, Work, assignment, local kind, and MethodDescription named only for claims that actually use them?
  3. Description boundary: Is each Description episteme independently identified by claim content, EntityOfConcern, and effective scheme, with any authoring, measurement, source-use, representation, or refinement relation stated separately?
  4. Method and Work: Use B.1.5 to judge Method composition; use A.15.1 and B.1.6 for the Work occurrence and its resource actuals, and B.1.4 when already established temporal relations need aggregation.
  5. Episteme and carrier: Does the episteme remain non-acting and distinct from its publication form and carrier?
  6. Grouping: If a group acts, is it recoverable as a collective System rather than merely a set?

Diagram legend stub

  • process in source language may mean Method, Work, transformation, mechanism, or another direct object; recover the live claim.
  • A system-role-kind column lists local classifications, not behaviour.
  • A behaviour column states the actual behaviour claim under its direct rule; it need not display a full assignment chain.