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

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:40:10 UTC

E.17.AUD.OOTD:11 - SoTA-Echoing

Source boundary. These sources support topic focus, scope/non-scope, reader-need organization, and explicit document structure. None establishes a universal ontological rule that every publication unit has one subject, and none supplies a C.2.1 entity participant. OOTD therefore keeps the one-primary-subject rule as a defeasible local heuristic and compares it with transition, sectioning, and splitting.

Publication-unit obligationExact source and current contributionLocal repair of the source limitWorking implication here
Keep the current unit focused and expose its scope and non-scope.Google Technical Writing One — Documents (updated 2025-07-07) tells authors to state scope and non-scope, then refocus or revise the scope when content veers; Paragraphs (updated 2025-03-28) treats a paragraph as one independent unit of logic focused on one topic.Paragraph focus does not imply one subject for every memo, packet, or document. OOTD scales the move by naming the bounded unit and comparing retention, explicit transition, sectioning, and splitting.E.17.AUD.OOTD:4.2.a, E.17.AUD.OOTD:4.3, E.17.AUD.OOTD:5.1, E.17.AUD.OOTD:5.6
Organize documentation around the user’s need and keep different action/cognition modes visible.Diátaxis organizes content, architecture, and form around four distinct user needs; its compass tests whether material informs action or cognition and supports acquisition or application, at sentence or whole-document scale.The four modes diagnose a use shift but are not an FPF ontology or a formula for document count. OOTD names the actual carried move and downstream use, then keeps one structured unit only when a shared reader goal makes that cheaper and still clear.E.17.AUD.OOTD:4.1.a, E.17.AUD.OOTD:4.2.a, E.17.AUD.OOTD:5.2, E.17.AUD.OOTD:5.6
Use a single-subject reusable topic when modular reuse is the main need.OASIS DITA 1.3 <topic> defines the top-level topic as a single-subject topic or article. This is established structured-authoring lineage (2015), not the current source of OOTD’s whole-document rule.A DITA topic is one valid reusable unit architecture, not evidence that a deliberately sectioned review packet is defective. OOTD selects it when independent reuse or retrieval dominates and otherwise permits the coherent multi-section unit.E.17.AUD.OOTD:4.2.a, E.17.AUD.OOTD:5.6
Keep object words and local designations precise without importing another concept system.ISO 704:2022 and ISO 1087:2019 terminology practice distinguishes objects, concepts, definitions, designations, and terms.Terminology discipline repairs overloaded heads but does not choose the publication architecture. OOTD first uses E.17.AUD.LHR, then makes subject, concern, carried move, and use explicit only when unit-level instability remains.E.17.AUD.OOTD:4.1.a, E.17.AUD.OOTD:4.2, E.17.AUD.OOTD:5.3