Table of Contents
First Principles Framework (FPF) Readme (non-normative)
| ID & Title | Status | Concise content reminder |
|---|---|---|
| Start here | full text | Directs project users, framework developers, reviewers and coordinators to USING-FPF.md before selecting framework guidance. |
| Practical entries | full text | Shows ordinary direct examples and selected cross-pattern cards as a non-exhaustive sample of how the pattern language helps; every example returns to its direct patterns. |
| Decide Whether FPF Fits | full text | Distinguishes suitable FPF use from cases better served by a narrower method, domain source, or ordinary conversation. |
| When Several Transformation Flows Form One Network | full text | Connects project, reasoning, evidence, and publication flows without collapsing their different results. |
| Perform several levels of work through one action | full text | Connects constituent performance, encompassing work, capability and resources; shows when a changed whole requires a different action. |
| Recover a lost path from outside use to recursive builders | full text | Restores the route from a reader’s question through direct patterns to deeper builders only when needed. |
| One-Minute Example | full text | Shows the ordinary question-to-pattern-to-result rhythm in a compact case. |
| What FPF Is | full text | Defines FPF as a transdisciplinary pattern language and reasoning architecture. |
| What FPF Is Not | full text | Sets boundaries against a universal ontology, linear method, or substitute for domain expertise. |
| How to Use This Repository | full text | Explains how the monolith, pattern hosts, Readme, and project work products relate. |
| License and reuse | full text | Explains CC BY 4.0 reuse and authors’ choice of license for their own DPFs and LPFs. |
| Citation | full text | Gives the public citation and return information. |
Preface (non-normative)
| ID & Title | Status | Concise content reminder |
|---|---|---|
| FPF.Preface:1 - What This Specification Is And How To Use It | full text | Explains Core, Kernel, framework editions, and direct use of adequate methods; distinguishes the Preface, lookup maps and supplying pattern bodies. |
| FPF.Preface:2 - FPF As A Project, Not Only A Pattern List | full text | Explains how domain and local frameworks, optional DPF Suite References, companions and shared carriers relate to Core while preserving their content and edition boundaries. |
| FPF.Preface:3 - Why FPF Exists | full text | Explains why difficult multi-participant work needs explicit distinctions, options, evidence, decisions, and return paths. |
| FPF.Preface:4 - Creativity And Assurance Mature Together | full text | Connects plural option generation, evidence, assurance, currentness, and bounded decisions without making them one lifecycle. |
| FPF.Preface:5 - Local Closure Inside An Open World | full text | Shows how a decision gains local closure by naming the actual source, scope, model-use organization, situation, comparison basis, or other subject-defined boundary it uses, together with its reopen condition. |
| FPF.Preface:6 - FPF As An Evolutionary Architecture For Thought | full text | Treats the framework as evolving reasoning architecture whose components, relations, and evaluations change together. |
| FPF.Preface:7 - Architectural Characteristics Of Thought | full text | Names the characteristics that make reasoning inspectable, composable, evolvable, falsifiable, and usable. |
| FPF.Preface:8 - Beyond Bias Hunting | full text | Replaces negative error catalogues with constructive reasoning objects and direct solution moves. |
| FPF.Preface:9 - Thinking Through Writing | full text | Explains when cards, records, tables, characteristic spaces, term sheets, patterns, and DRRs become useful thinking instruments rather than paperwork. |
| FPF.Preface:10 - Thinking-Oriented Architecture, Not A Descriptive Upper Ontology | full text | Distinguishes FPF’s work of improving reasoning from cataloguing every entity that may exist. |
| FPF.Preface:11 - When A Scale Claim Calls For Comparison | full text | Explains when a scale or generalization claim activates the Bitter-Lesson Preference, what nondominance means, and how ordinary procedures, autonomy and adaptation retain their own grounds. |
| FPF.Preface:12 - From Flat Documents To Multi-View Truth | full text | Separates EntityOfConcern, descriptions, views, publication carriers, and reader uses while preserving return to source structure. |
| FPF.Preface:13 - Architecture As Structure Of Holons | full text | Explains architecture as selected structures of a holon in context rather than the diagram or document that describes them. |
| FPF.Preface:14 - Boundary Statements | full text | Shows where language carries commitments, admissibility, evidence, gates, and other boundary claims. |
| FPF.Preface:15 - Raising Semantic Precision | full text | Explains ontology-first restoration from overloaded wording to explicit kinds, relations, slots, and admissible uses. |
| FPF.Preface:16 - Big FPF Storylines | full text | Follows a report-review inquiry and the construction of a usable method from received material; explains Architectural Rationale, qualified evidence, direct entry, profiles, shared sources, alternatives, costs and selective return after changed conditions. |
| FPF.Preface:17 - Transdisciplinarity As A Meta-Theory Of Thinking | full text | Shows how shared distinctions can connect disciplines without flattening their bounded meanings. |
| FPF.Preface:18 - The Culinary Architecture Of Collective Thought | full text | Uses an assembly analogy to explain why familiar ingredients still need an explicit architecture and quality discipline. |
| FPF.Preface:19 - The Intellect Stack As A Pedagogical Map | full text | Gives a teaching map for locating capabilities without turning the map into the ontology or work order. |
| FPF.Preface:20 - Purpose, Scope, And Non-Goals | full text | States FPF’s intended use, tool independence, and boundaries against domain encyclopedia or one prescribed methodology. |
| FPF.Preface:21 - How To Continue After The readme | full text | Sends the reader from a practical-use card to the direct pattern, then to exact result, receiving use, stop, or return. |
Use Part and cluster headings to locate content. E.4 explains how Kernel, broader Core content and framework editions relate; those distinctions apply across the Parts.
Part A - Kernel Architecture Cluster