You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Restructure to hierarchical #/## split (20 dirs, 224 files)
Each top-level heading becomes a directory with _index.md listing
sub-sections. Agent reads _index.md first, then loads only the
specific ~300-line sub-section needed — 20x less context than flat files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+40-23Lines changed: 40 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,38 +2,55 @@
2
2
3
3
AI coding agent skill for the [First Principles Framework (FPF)](https://github.com/ailev/FPF) by [Anatoly Levenchuk](https://github.com/ailev).
4
4
5
-
FPF is a transdisciplinary reasoning architecture for systems engineering, knowledge coordination, and mixed human/AI teams. This skill splits the 56,000-line FPF specification into 20 navigable sections with an INDEX that tells the agent which section to load for a given task.
5
+
FPF is a transdisciplinary reasoning architecture for systems engineering, knowledge coordination, and mixed human/AI teams. This skill splits the 56,000-line FPF specification into a two-level hierarchy (20 directories, 224 files) so an agent loads only the ~300-line sub-section it needs instead of the entire spec.
Copy file name to clipboardExpand all lines: SKILL.md
+34-31Lines changed: 34 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,20 +6,23 @@ license: MIT
6
6
7
7
# First Principles Framework (FPF)
8
8
9
-
An "Operating System for Thought" — a rigorous, transdisciplinary architecture for reasoning,
9
+
An "Operating System for Thought" — a transdisciplinary architecture for reasoning,
10
10
written in human- and machine-readable pseudo-code. FPF turns raw intelligence (human or machine)
11
11
into organisationally usable reasoning: explicit bounded contexts, auditable artefacts, multi-view
12
12
descriptions, and disciplined hand-offs between specialised actors.
13
13
14
14
## How to use
15
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.
16
+
The spec is split into `sections/` with a two-level hierarchy:
19
17
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.
18
+
1. Find the relevant Part from the INDEX below.
19
+
2. Read its `_index.md` to see the list of sub-sections with descriptions.
20
+
3. Read only the specific sub-section file you need.
21
+
4. Apply FPF patterns using plain language; introduce FPF-internal names only when they add precision.
22
+
23
+
IMPORTANT: Always start by reading `_index.md` of the relevant section folder —
24
+
it lists all sub-sections with line counts and descriptions so you can pick the right file
25
+
without loading thousands of lines.
23
26
24
27
## Starter prompt
25
28
@@ -32,27 +35,27 @@ hand-off contracts, and publication surfaces for the user's domain, then iterate
32
35
33
36
## Section INDEX
34
37
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. |
| 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. |
38
+
Each entry is a folder. Read its `_index.md` first, then pick the sub-section file you need.
| 05 |[A.IV.A — Signature Stack & Boundary](sections/05-cluster-a-iv-a---signature-stack-boundary-discipline/_index.md)|18 | System boundaries, APIs, protocols — classifying statements as definitions, gates, duties, or evidence. |
47
+
| 06 |[A.V — Constitutional Principles](sections/06-cluster-a-v---constitutional-principles-of-the-kernel/_index.md)|29 |Prevent category errors: role vs. function, method vs. work, holon vs. system vs. episteme. |
| 10 |[Part E — Constitution & Authoring](sections/10-part-e---fpf-constitution-and-authoring-cluster/_index.md)|0 |Entry point for Part E subsections. |
| 12 |[Part F — Unification Suite](sections/12-part-f-the-unification-suite-concept-sets-sensecells-contextual-role-a/_index.md)|0 |Entry point for Part F subsections. |
0 commit comments