FPF.Preface:19 - The Intellect Stack As A Pedagogical Map
The phrase “Intellect Stack” names a learning map of capabilities. In this specification it is pedagogy, not a prescribed sequence or a new ontology.
The point is simple: complex reasoning usually needs several capability families, and teams often underinvest in one of them.
| Capability area | Question it helps a learner ask | FPF families that often appear |
|---|---|---|
| Structure and reality | What exists, how is it bounded, and what structure matters? | Holons, contexts, architecture, selected structures, signatures, and discipline about the project entity under concern. |
| Knowledge and reasoning | Why should this claim be trusted, and what would change that trust? | Evidence, assurance, source-use, publication, views, explanations, and refresh. |
| Action and work | How does intent become change, and what work actually happened? | System-role kinds and assignments, methods, method descriptions, plans, performed work, design-run linking records, and P2W. |
| Strategy and choice | Which option is better under uncertainty and for whom? | Characteristics, comparison, local decision, selected options, portfolios, and current-option publications. |
| Purpose and governance | Why act, which outcomes are inadmissible, and what counts as success? | Objectives, constraints, gates, ethics, assurance, budgets, and improvement loops. |
This stack is not a universal project sequence. It is a way to notice missing capability. A team may enter through architecture and discover that it lacks evidence. It may enter through naming and discover that it has not named the project entity under concern. It may enter through mathematical modeling and discover that it lacks declared characteristics for comparison.
The learning value is that FPF can be taught as a set of capabilities, not only as a list of pattern ids.