fpf-simple-skill
First Principles Framework (FPF)
An "Operating System for Thought" — a transdisciplinary architecture for reasoning, written in human- and machine-readable pseudo-code. FPF turns raw intelligence (human or machine) into organisationally usable reasoning: explicit bounded contexts, auditable artefacts, multi-view descriptions, and disciplined hand-offs between specialised actors.
How to use
The spec is split into sections/ with a two-level hierarchy:
- Find the relevant Part from the INDEX below.
- Read its
_index.mdto see the list of sub-sections with descriptions. - Read only the specific sub-section file you need.
- Apply FPF patterns using plain language; introduce FPF-internal names only when they add precision.
IMPORTANT: Always start by reading _index.md of the relevant section folder —
it lists all sub-sections with line counts and descriptions so you can pick the right file
without loading thousands of lines.
Starter prompt
You have the FPF specification loaded. Help me structure your project / problem / programme. Use plain language for an engineer-manager. Propose: (1) bounded contexts / specialisations, (2) decision criteria, (3) key alternatives, (4) hand-offs, and (5) missing evidence or tests before commitment. Introduce internal FPF names only when they add precision.
Section INDEX
Each entry is a folder. Read its _index.md first, then pick the sub-section file you need.
| # | Section | Sub-sections | When to use |
|---|---|---|---|
| 01 | Title page | 0 | Authorship, version date, top-level identity. |
| 02 | Table of Content | 0 | Navigate the spec, locate a pattern, understand inter-section dependencies. |
| 03 | Preface | 17 | Onboarding to FPF; choosing a reading path by role. |
| 04 | Part A — Kernel Architecture | 19 | Core ontological building blocks: holons, bounded contexts, roles, transformers, method/work separation, generative search. |
| 05 | A.IV.A — Signature Stack & Boundary | 18 | System boundaries, APIs, protocols — classifying statements as definitions, gates, duties, or evidence. |
| 06 | A.V — Constitutional Principles | 29 | Prevent category errors: role vs. function, method vs. work, holon vs. system vs. episteme. |
| 07 | Part B — Trans-disciplinary Reasoning | 24 | Compose subsystem properties, trust scores, cross-scale aggregation (Gamma algebra). |
| 08 | Part C — Kernel Extensions | 30 | Characterize, compose, compare knowledge artifacts. Epistemic scoring (Formality, ClaimScope, Reliability). |
| 09 | Part D — Ethics & Conflict | 1 | Ethical trade-offs, conflict resolution, bias auditing, safety-evidence overriding utility. |
| 10 | Part E — Constitution & Authoring | 0 | Entry point for Part E subsections. |
| 11 | E-I — FPF Constitution | 29 | FPF vision/mission, the 11 Pillars, guard-rails, Multi-View Publication Kit (MVPK). |
| 12 | Part F — Unification Suite | 0 | Entry point for Part F subsections. |
| 13 | F.I — Context of Meaning | 19 | Semantic drift, homonym collisions, cross-domain vocabulary alignment, Alignment Bridges. |
| 14 | UTS Layout A | 0 | Cross-context unification table mapping concepts across standards (BPMN, PROV-O, ITIL). |
| 15 | UTS Layout B | 1 | Discipline-oriented concept unification table (operations, physics, math). |
| 16 | Part G — SoTA Patterns Kit | 15 | Discipline-specific patterns, SoTA Packs, TraditionCards, OperatorCards, selector-ready portfolios. |
| 17 | Part H — Glossary | 0 | Canonical definitions, four-register naming, cross-references for FPF terms. |
| 18 | Part I — Annexes | 0 | Deprecated aliases, walkthroughs, change log, external standards mappings. |
| 19 | Part J — Indexes | 0 | Concept-to-pattern, pattern-to-example, principle-trace indexes. |
| 20 | Part K — Lexical Debt | 2 | Mandatory terminology replacements and migration debt for deprecated terms. |