|
| 1 | +--- |
| 2 | +name: fpf-simple-skill |
| 3 | +description: "First Principles Framework (FPF) — transdisciplinary reasoning architecture for systems engineering, knowledge coordination, and mixed human/AI teams. Use when the user mentions FPF, first principles, bounded contexts, SoTA packs, concept unification, assurance calculus, or FPF Parts A-K. Not for general philosophy or Agile unrelated to FPF." |
| 4 | +license: MIT |
| 5 | +--- |
| 6 | + |
| 7 | +# First Principles Framework (FPF) |
| 8 | + |
| 9 | +An "Operating System for Thought" — a rigorous, transdisciplinary architecture for reasoning, |
| 10 | +written in human- and machine-readable pseudo-code. FPF turns raw intelligence (human or machine) |
| 11 | +into organisationally usable reasoning: explicit bounded contexts, auditable artefacts, multi-view |
| 12 | +descriptions, and disciplined hand-offs between specialised actors. |
| 13 | + |
| 14 | +## How to use |
| 15 | + |
| 16 | +1. Find the relevant section(s) from the INDEX below. |
| 17 | +2. Read the corresponding file from `sections/` into context. |
| 18 | +3. Apply FPF patterns using plain language; introduce FPF-internal names only when they add precision. |
| 19 | + |
| 20 | +FPF is not a narrative textbook — it is source code for an evolvable reasoning architecture. |
| 21 | +Treat it as a design kit: ask for bounded-context maps, decision criteria, option portfolios, |
| 22 | +hand-off contracts, and publication surfaces for the user's domain, then iterate. |
| 23 | + |
| 24 | +## Starter prompt |
| 25 | + |
| 26 | +> You have the FPF specification loaded. |
| 27 | +> Help me structure your project / problem / programme. |
| 28 | +> Use plain language for an engineer-manager. |
| 29 | +> Propose: (1) bounded contexts / specialisations, (2) decision criteria, (3) key alternatives, |
| 30 | +> (4) hand-offs, and (5) missing evidence or tests before commitment. |
| 31 | +> Introduce internal FPF names only when they add precision. |
| 32 | +
|
| 33 | +## Section INDEX |
| 34 | + |
| 35 | +Load the section file that matches the user's need: |
| 36 | + |
| 37 | +| # | File | When to use | |
| 38 | +|---|------|-------------| |
| 39 | +| 01 | [Title page](sections/01-first-principles-framework-core-conceptual-specification.md) | Need the document's authorship, version date, or top-level identity. | |
| 40 | +| 02 | [Table of Content](sections/02-table-of-content.md) | Navigate the spec, locate a specific pattern, or understand inter-section dependencies. | |
| 41 | +| 03 | [Preface](sections/03-preface.md) | Onboarding to FPF; choosing a reading path for a specific role (project user, pattern author, language-state work). | |
| 42 | +| 04 | [Part A — Kernel Architecture](sections/04-part-a-kernel-architecture-cluster.md) | Understand or apply FPF's core ontological building blocks: holons, bounded contexts, roles, transformers, method/work separation, generative search/portfolio vocabulary. | |
| 43 | +| 05 | [Cluster A.IV.A — Signature Stack & Boundary Discipline](sections/05-cluster-a-iv-a---signature-stack-boundary-discipline.md) | Model system boundaries, APIs, protocols, or any interface where statements must be classified as definitions, gates, duties, or evidence. | |
| 44 | +| 06 | [Cluster A.V — Constitutional Principles / Strict Distinction](sections/06-cluster-a-v---constitutional-principles-of-the-kernel.md) | Prevent category errors: role vs. function, method-description vs. method vs. work, holon vs. system vs. episteme, episteme vs. carrier. | |
| 45 | +| 07 | [Part B — Trans-disciplinary Reasoning](sections/07-part-b-trans-disciplinary-reasoning-cluster.md) | Compose or roll up subsystem properties, trust scores, or any cross-scale aggregation (Gamma algebra). Explicit invariants and weakest-link bounds. | |
| 46 | +| 08 | [Part C — Kernel Extensions (CALs, LOGs, CHRs)](sections/08-part-c-kernel-extensions-specifications.md) | Formally characterize, compose, or compare knowledge artifacts (theories, specs, proofs, datasets). Epistemic scoring on Formality, ClaimScope, Reliability. | |
| 47 | +| 09 | [Part D — Multi-scale Ethics & Conflict-Optimisation](sections/09-part-d-multi-scale-ethics-conflict-optimisation.md) | Ethical trade-offs across scales, conflict resolution between stakeholders, bias auditing, or safety-evidence overriding utility. | |
| 48 | +| 10 | [Part E — Constitution & Authoring (header)](sections/10-part-e---fpf-constitution-and-authoring-cluster.md) | Entry point for Part E subsections (constitution, pillars, authoring protocols, lexical rules). | |
| 49 | +| 11 | [Section E-I — FPF Constitution](sections/11-section-e-i---the-fpf-constitution.md) | Understand FPF's foundational purpose, vision/mission ("OS for Thought"), the 11 Pillars, guard-rails, and the Multi-View Publication Kit (MVPK). | |
| 50 | +| 12 | [Part F — Unification Suite (header)](sections/12-part-f-the-unification-suite-concept-sets-sensecells-contextual-role-assignment.md) | Entry point for Part F subsections (Concept-Sets, SenseCells, Contextual Role Assignment). | |
| 51 | +| 13 | [Cluster F.I — Context of Meaning & Raw Material](sections/13-cluster-f-i-context-of-meaning-raw-material.md) | Semantic drift, homonym collisions, cross-domain vocabulary alignment. Contextual Lexicon Principles and Alignment Bridges. | |
| 52 | +| 14 | [UTS Layout A — Cross-context unification table](sections/14-block-fpf-u-type-unified-tech-name-unified-plain-name-plain-twin-governance-twin.md) | Build or read a cross-context unification table mapping concepts across standards or frameworks (BPMN, PROV-O, ITIL, etc.). | |
| 53 | +| 15 | [UTS Layout B — Base-concept pivot](sections/15-block-base-concept-scale-map.md) | Build a discipline-oriented concept unification table mapping unified concepts across discipline columns (operations, physics, math). | |
| 54 | +| 16 | [Part G — Discipline SoTA Patterns Kit](sections/16-part-g-discipline-sota-patterns-kit.md) | Author, extend, or refactor discipline-specific patterns. Harvest competing schools of thought, build SoTA Packs, TraditionCards, OperatorCards, selector-ready portfolios. | |
| 55 | +| 17 | [Part H — Glossary & Definitional Pattern Index](sections/17-part-h-glossary-definitional-pattern-index.md) | Look up canonical definitions, four-register naming, or cross-references for any FPF term. | |
| 56 | +| 18 | [Part I — Annexes & Extended Tutorials](sections/18-part-i-annexes-extended-tutorials.md) | Deprecated aliases, step-by-step walkthroughs, change log, external standards mappings (ISO 15926, BORO, CCO, Constructor Theory). | |
| 57 | +| 19 | [Part J — Indexes & Navigation Aids](sections/19-part-j-indexes-navigation-aids.md) | Find which pattern or example addresses a known concept or principle (concept-to-pattern, pattern-to-example, principle-trace indexes). | |
| 58 | +| 20 | [Part K — Lexical Debt](sections/20-part-k-lexical-debt.md) | Mandatory terminology replacements and migration debt for deprecated scope terms. Consult when authoring or editing normative FPF text. | |
0 commit comments