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

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:50:20 UTC

C.20:5.0 - Keep the System/Episteme contrast without making the table a constructor

The former Tell-Show-Show contrast remains useful because it asks five different reader questions. Read every cell as an independently governed example, not as a slot or a recipe for manufacturing a discipline.

Reader functionSystem-side safety sceneEpisteme-side discipline sceneC.20 boundary
Exact objectOne production line with hazardous operations is an exact U.System under A.1; its work and state remain separate.One exact canon or discipline-description U.Episteme states accident-model and tolerable-risk claims about its declared EntityOfConcern under its effective ReferenceScheme. The SafetyEngineering-SE field candidate remains another entity.Neither the system nor one episteme is the discipline; identify the field candidate and test its construction independently.
Concept contributionAcceptance clauses and evaluation templates bound to exact rigs and windows are epistemes used by the plant system and its Work, not concepts owned by the system.Canon content can include causality models, design rules, proofs, benchmarks, formal knowledge bases, proof carriers, and concept schemas under their direct episteme, form, or representation patterns.Ask which exact claim-bearing contribution is constitutive and which whole-forming claim states how it connects to the assembly; conceptual relevance alone creates no part.
Symbolic representationLocal SOP and checklist notation can express plant procedures for one bounded use.CLIF, RDF/TriG, proof scripts, diagrams, and other notation packages can express or represent canon content.E.17/E.24.PUB and C.29 govern form, carrier, publication, and representation; symbolic appearance identifies none of System, Episteme, or Discipline.
Assembly contrastA line-specific standard, plant procedures, and a certifying unit are exact epistemes, Methods, systems, system-role kinds or assignments, or Work inputs around a possible Safety-Plant-A field candidate.Canon papers, formal models, a journal or committee, and system-safety or resilience-engineering tradition claims are likewise separately governed around SafetyEngineering-SE.A list or historical Gamma_disc fold constructs neither candidate. For either scene, recover exact parts, obtaining disciplinePartOf occurrences, whole-forming couplings, assembly, reidentification, whole characteristic, and larger-assembly compatibility.
Evidence-lane contrastLA test campaigns with freshness windows, VA design proofs, and TA tool qualifications can support exact plant-side claims.VA proofs over kinds, LA replications or meta-analyses, and TA evidence for checkers can support exact canon or construction claims.A.10 keeps the exact source, currentness, and reliance needed by the use. When an actual named assurance claim is current, B.3 adds only the characteristics and result fields that its argument consumes. Evidence changes no System, Episteme, or Discipline identity and creates no part relation.