#Table of Content
Preface node
heading:table-of-content:15
#What this page is
This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.
#Methodology
Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.
#Content
Preface (non-normative)
| ID & Title | Status | Concise content reminder |
|---|---|---|
| What This Specification Is And How To Use It | full text | Distinguishes the fifteen practical-use cards, Preface, ToC, direct pattern bodies, ordinary use, reliance-bearing support, exact first results, and three coupled flows. |
| FPF As A Project, Not Only A Pattern List | full text | Places the evolving Core beside companion explanations, domain frameworks, local practice frameworks, publication carriers, and tools without merging their authority. |
| Why FPF Exists | full text | Explains why difficult multi-participant work needs explicit distinctions, options, evidence, decisions, and return paths. |
| Creativity And Assurance Mature Together | full text | Connects plural option generation, evidence, assurance, currentness, and bounded decisions without making them one lifecycle. |
| Local Closure Inside An Open World | full text | Uses bounded contexts and explicit reopen conditions to make decisions possible without pretending the world is closed forever. |
| FPF As An Evolutionary Architecture For Thought | full text | Treats the framework as evolving reasoning architecture whose components, relations, and evaluations change together. |
| Architectural Characteristics Of Thought | full text | Names the characteristics that make reasoning inspectable, composable, evolvable, falsifiable, and usable. |
| Beyond Bias Hunting | full text | Replaces negative error catalogues with constructive reasoning objects and direct solution moves. |
| Thinking Through Writing | full text | Explains when cards, records, tables, characteristic spaces, term sheets, patterns, and DRRs become useful thinking instruments rather than paperwork. |
| Thinking-Oriented Architecture, Not A Descriptive Upper Ontology | full text | Distinguishes FPF's work of improving reasoning from cataloguing every entity that may exist. |
| The Bitter Lesson Stance | full text | Prefers general scalable search and learning while retaining explicit constraints, evidence, and bounded use. |
| From Flat Documents To Multi-View Truth | full text | Separates EntityOfConcern, descriptions, views, publication carriers, and reader uses while preserving return to source structure. |
| 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. |
| Boundary Statements | full text | Shows where language carries commitments, admissibility, evidence, gates, and other boundary claims. |
| Raising Semantic Precision | full text | Explains ontology-first restoration from overloaded wording to explicit kinds, relations, slots, and admissible uses. |
| Big FPF Storylines | full text | Collects the load-bearing commitments that make the framework more than a disconnected pattern list. |
| Transdisciplinarity As A Meta-Theory Of Thinking | full text | Shows how shared distinctions can connect disciplines without flattening their bounded meanings. |
| 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. |
| 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. |
| Purpose, Scope, And Non-Goals | full text | States FPF's intended use, tool independence, and boundaries against domain encyclopedia or one prescribed methodology. |
| 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. |
| Part A - Kernel Architecture Cluster |
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| A.0 | Onboarding Glossary (NQD & E/E‑LOG) | Stable | Keywords: novelty, quality-diversity (NQD), explore/exploit (E/E-LOG), declared set result, typed portfolio publication, SearchSpaceRef, OutcomeSpaceRef, DeclaredSubstrateInterpretiveView, TypedSetViews, ParetoOnly default, scale-probe, BLP. Queries: "What terms must I publish when generating, selecting, or shipping a set result?", "How do I explain search-side vs outcome-side spaces and interpretive views on first use?", "How does FPF avoid single-winner bias in creative search?" | Builds on: E.2, A.5, C.17-C.19. Coordinates with: E.7, E.8, E.10, F.17, A.19.SOURCE-SET-SPACE-SUBSTRATE, A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW, G.5, G.9-G.12. Constrains: any pattern/UTS row that describes a generator, selector, declared set result, typed portfolio publication, or set-return publication. |
| Cluster A.I - Foundational Ontology | ||||
| A.1 | Holon Ontic Foundation (U.Holon and Admitted Holon Kinds) | Stable | Holonic root ontology for U.Holon, admitted holon kinds, U.System, non-agentive epistemes, holon slot relation, system participation, delimitation, and boundary-crossing relations. | Builds on: E.24. Coordinates with: A.1.1, A.2, A.7, A.12, A.14, A.15.1, A.22, C.2.1, C.13, C.30. |
| A.1.1 | U.BoundedContext Semantic Frame | Stable | Semantic-frame ontology for local meaning, local vocabulary, invariant set, local role taxonomy, bridge relations, and non-container context boundary. | Builds on: A.1, E.10.D1. Coordinates with: F.0.1, F.9, F.18, E.24. |
| A.2 | Role Taxonomy | Stable | Keywords: role, assignment, holder, context, function vs identity, responsibility, U.RoleAssignment. Queries: "How to model responsibilities?", "What is the difference between what a thing is and what it does?" | Builds on: A.1, A.1.1. Prerequisite for: A.2.1-A.2.6, A.13, A.15. |
| A.2.1 | U.RoleAssignment: Contextual Role Assignment | Stable | Keywords: Standard, holder, role, context, RoleEnactmentFact, performedBy, RCS/RSG. Queries: "How to formally assign a role in FPF?", "How do I attribute performed work through a role assignment?", "What is the Holder#Role:Context Standard?" | Refines: A.2. Prerequisite for: A.15. |
| A.2.2 | U.Capability: System Ability Envelope and Measures | Stable | Keywords: holder-dependent capability instance, ability envelope, measure set, qualification window, currentness, capability-fit condition. Queries: "What is a capability in FPF?", "How do I separate capability from capability statements, evidence, dashboards, and fit predicates?" | Builds on: A.2, E.24.UK. Informs: A.15, A.2.3. |
| A.2.3 | U.PromiseContent (Promise Content) | Stable | Keywords: promise content, promise content, accessSpec, acceptanceSpec, SLO, SLA, claim scope (G), Work evidence, provider/consumer roles. Queries: "What is a promise content in FPF?", "Promise content vs Work vs MethodDescription", "How do access and acceptance differ?", "How is SLO/SLA adjudicated from Work evidence?" | Builds on: A.2.2. Prerequisite for: F.12. Used by: A.2.8, A.6.C, A.6.8. |
| A.2.4 | Episteme Evidence-Use and Status-Use Relations | Stable | Keywords: evidence-use, status-use, source-use, episteme, claim, provenance. Queries: "How is an episteme used as evidence?", "How do I keep evidence use from becoming a role?", "How do I model status use around an episteme?" | Builds on: A.2. Informs: A.10, B.3. |
| A.2.5 | RoleStateRelation@BoundedContext - Role State Space and Enactable-State Admission | Stable | Keywords: state machine, RSG, role state, enactability, role-state evolution. Queries: "How to model the state of a role?", "What is a Role State Graph?" | Builds on: A.2.1. Prerequisite for: A.15. |
| A.2.6 | Unified Scope Mechanism (USM): Context Slices & Scopes | Stable | Keywords: scope, applicability, ClaimScope (G), WorkScope, set-valued. Queries: "How to define the scope of a claim or capability?", "What is G in F-G-R?" | Builds on: A.1.1. Constrains: A.2.2, A.2.3, B.3. |
| A.2.7 | RoleRelationStructure@BoundedContext - Context-Local Role Relations and Representation-Lens Boundary | Stable | Keywords: role algebra, specialization (≤), incompatibility (⊥), bundles (⊗), separation of duties (SoD), requiredRoles substitution. Queries: "What does RoleS ≤ RoleG mean in FPF?", "How do I encode Separation of Duties with ⊥?", "How do role bundles (⊗) work?" | Builds on: A.2. Prerequisite for: A.15, A.2.5. |
| A.2.8 | U.Commitment (Deontic Commitment Object) | Stable | Keywords: commitment, deontics, obligation, permission, prohibition, modality normalization, scope+validity window, adjudication hooks, evidenceRefs, BCP‑14 (RFC 2119/8174). Queries: "How to represent MUST/SHALL as a lintable object?", "How to keep deontics separate from admissibility gates?", "How to make commitments auditable via evidence hooks?" | Refines: A.2. Builds on: A.2.1, A.2.3, A.2.6, A.7, A.15.1. Used by: A.6.B (Quadrant D), A.6.C. |
| A.2.9 | U.SpeechAct (Communicative Work Object) | Stable | Keywords: speech act, communicative work, approval/authorization/publication/revocation, provenance, act≠utterance≠carrier, judgement context, window/freshness, institutes.*. Queries: "How to model approvals/authorizations as Work?", "How to separate act vs utterance vs carrier?", "How to link commitments to instituting acts without commitment-by-publication?" | Refines: A.2. Builds on: A.2.1, A.2.6, A.7, A.10, A.15.1. Used by: A.2.8, A.6.C (utterance/instituting-act hook). |
| Cluster A.II - Transformation Engine | ||||
| A.3 | Transformer Constitution (Quartet) | Stable | Keywords: action, causality, change, System-in-Role, MethodDescription, Method, Work. Queries: "How does FPF model an action or a change?", "What is the transformer quartet?" | Builds on: A.2. Prerequisite for: A.3.1, A.3.2, A.15. |
| A.3.1 | U.Method: Context-Defined Way of Doing | Stable | Keywords: method, way of doing, submethod, method composition, non-agentive holon, method vs method description vs work. Queries: "What is a Method in FPF?", "When is a step a recovered submethod rather than a work part or description node?", "How is Method different from Work?" | Refines: A.3. Prerequisite for: A.15, B.1.5. |
| A.3.2 | U.MethodDescription: Description Episteme for a Way of Doing | Stable | Keywords: method description, recipe, SOP, code, model, source, U.Episteme, method vs description vs work. Queries: "How do I document a method without treating the document as enacted work?", "What is a MethodDescription?" | Refines: A.3. Informs: A.15, A.15.1. |
| A.3.3 | U.Dynamics: State-Space and Transition-Law Episteme | Stable | Keywords: dynamics, state space, transition law, observation relation, prediction, simulation, calibration. Queries: "How do I model a reusable law of state change?", "When is a process label a dynamics episteme rather than method, work, or transformation?" | Builds on: A.1.1, A.19. Coordinates with: A.3.1, A.3.2, A.3.4, A.15.1, A.15.2, A.6.1, C.27, C.27.TA, C.29, A.10, B.3, A.20, A.21. |
| A.3.4 | U.Transformation: Bounded Change Under Conditions | Stable | Keywords: transformation, bounded change, transformed entity, transformer, input/output conditions, functioning, transformation-flow structure. Queries: "What exactly is changing?", "Who or what is the transformer?", "How do method, mechanism, work, dynamics, function, and evidence stay distinct around one change?" | Builds on: A.3, A.1.1, A.6.0, A.6.5. Coordinates with: A.3.1, A.3.2, A.3.3, A.6.1, A.15.1, A.15.2, E.18, E.18.2, C.27.TA, C.27, C.29, A.6.F, C.30.ASV, A.10, B.3. |
| A.3.4.P | Transformation Ontic Precision Restoration | Stable | Repairs change-situation wording such as transformation, flow, process, workflow, pipeline, dataflow, network, circuit, path, functioning, method, mechanism, work, or evidence by recovering the U.Transformation slot relation and current governing pattern before rewriting. | Builds on: E.10, E.10.ARCH, A.3.4, E.18, E.18.2, A.6.F, C.2.P.DR, C.29, F.18, F.19. Coordinates with: A.3.1, A.3.2, A.6.1, A.15, A.10, B.3, C.30, C.30.ASV, C.27.TA, C.27. |
| Cluster A.III - Time & Evolution | ||||
| A.4 | Temporal Duality & Open-Ended Evolution Principle | Stable | Keywords: design-time, run-time, evolution, versioning, open-ended state change, continuous improvement. Queries: "How does FPF handle plan vs. reality?", "How are systems updated?" | Builds on: P-10 Open-Ended Evolution. Prerequisite for: B.4. |
| Cluster A.IV - Kernel Modularity | ||||
| A.5 | Open-Ended Kernel & Extension Layering | Stable | Keywords: FPF architecture, specialization vs dependancy hierarhies, modularity, extensibility. Queries: "What is the architecture of FPF?", "How are new domains added?" | Builds on: P-4, P-5. |
| Cluster A.IV.A - Signature Stack & Boundary Discipline (A.6.)* | ||||
| A.6 | Signature Stack & Boundary Discipline | Stable | Keywords: boundary, signature stack, boundary claim-classification fields, A.6.B L/A/D/E claims, authority-wording split, register-backed status boundary, promise/commitment/API/policy wording, probe/order/frame/export/state-reading claims. Queries: "How do I classify boundary statements?", "Where do probe, frame, export, and state-reading claims belong?", "When does authority-looking wording split into source, gate, work, assurance, or boundary claims?", "When is a pass, badge, tile, or status display only a publication of a register-backed source?" | Builds on: E.8, A.6.0, A.6.1, A.6.3, E.17.0, E.17, A.7, F.18, E.10.D2, E.10 publication face, form, unit, and carrier discipline. Coordinates with: A.6.B, A.6.P, C.26, C.26.1, F.9, A.10, A.15, B.3, E.17.EFP, A.20, A.21, E.19. |
| A.6.RSIG | Recognition Signatures for Descriptions | Stable | description-recognition signature; encountered carrier vs defining U.Episteme; API/access description not promise; method applicability note; false neighboring description | A.6, A.6.P, F.18, E.10 |
| A.6.B | Boundary Norm Square (Laws / Admissibility / Deontics / Work-Effects) | Stable | Keywords: boundary norm square, atomic claims, L/A/D/E claim classification, laws vs gates vs commitments vs evidence, admissible use, non-admissible use, claim IDs, triangle decomposition. Queries: "What is the Boundary Norm Square in FPF?", "How do I decompose probe-coupled or mixed boundary statements?", "Where do RFC keywords and use conditions belong in FPF patterns?" | Builds on: E.8, A.6.0, A.6.1, A.6.3, E.17.0, E.17, A.7, F.18, E.10.D2, E.10 publication face, form, unit, and carrier discipline. Coordinates with: A.6, A.6.P, C.26.1, A.10, B.3. |
| A.6.C | Contract Unpacking for Boundaries | Stable | Keywords: contract bundle unpacking, SLA/guarantee claim classification, promise content (promise content) ≠ work, promise-act/utterance/commitment separation, Boundary Norm Square (L/A/D/E), MVPK faces “no new semantics”. Queries: "How to unpack contract language into promise content / utterance / commitment / work+evidence?", "How to prevent interface-as-agent / contract soup mistakes?", "How to stop MVPK faces becoming ‘second contracts’?", "When contract talk includes service-cluster tokens, what gets unpacked first?" | Builds on: A.6, A.6.B, A.6.8, A.7, A.2.3, A.2.8, A.2.9, E.10, E.17. Coordinates with: F.12, F.18. |
| A.6.0 | U.Signature - Universal, law-governed declaration for a SubjectKind over a RangedValueKind | Stable | Keywords: signature, vocabulary, laws, applicability, bounded context. Queries: "What is the universal signature block?", "Where do laws vs. implementations live?" | Placement: Kernel; Coordinates: A.6.1. |
| A.6.1 | U.Mechanism - Law-governed application to a SubjectKind over a RangedValueKind | Stable | Keywords: Mechanism, OperationAlgebra, LawSet, AdmissibilityConditions, Transport, Bridge‑only. Queries: "How to define a mechanism like USM/UNM?", "Where do operational guards live?", "How to handle cross‑context transport?" | Builds on: A.6.0, E.10.D1. Instances: USM (A.2.6), UNM (A.19). |
| A.6.2 | U.EffectFreeEpistemicMorphing — Effect‑free morphisms of epistemes | Stable | Effect-free, law-constrained episteme-to-episteme morphisms over ClaimGraph, EntityOfConcern, grounding holon, viewpoint, reference scheme, representation scheme, and metadata; preserve or retarget EntityOfConcern only through declared change mode. | Builds on: A.1, A.6.0, A.6.1, A.6.5, C.2.1, E.10.D2, C.3.*. Used by: A.6.3, A.6.4, E.17.0, E.17, E.18, KD-CAL mapping rules. |
| A.6.3 | U.EpistemicViewing — EntityOfConcern-preserving morphism | Stable | EntityOfConcern-preserving effect-free projection between epistemes: content, representation, viewpoint, or reference scheme may change, but entityOfConcernRef stays fixed unless A.6.4 retargeting is explicitly opened. | Builds on: A.6.0, A.6.2, A.6.5, A.7, E.10.D2, C.2.1, C.2. Used by: E.17.0, E.17, E.17.1, E.17.2, E.18, B.5.3, KD-CAL view operators. |
| A.6.3.CSC | Controlled Semantic Coarsening | Stable | Controlled semantic coarsening of a source-bearing episteme or publication into a narrower-use rendering, with selected preserved/lost structure, admissible use, non-admissible downstream use, source return, and reopen trigger visible. | Builds on: A.6.3, A.6.3.CR, A.6.3.RT, E.17.EFP, A.6.P, E.8, E.10, E.19, F.18. Coordinates with: A.6.3.NAR, C.26, C.26.1, E.17.ID.CR, F.9, F.9.1, A.15, A.6.4, A.20, A.21, C.33. |
| A.6.3.CR | ConservativeRetextualization - entityOfConcernRef-preserving textual re-expression | Stable | Textual re-expression, summary, report rewrite, translation, or filtering that preserves entityOfConcernRef, keeps source tether and omission/loss visible, and exits to explanation, representation change, retargeting, bridge, work, evidence, gate, or assurance patterns when those claims are being made. | Builds on: A.6.3, A.6.2, A.7, E.10.D2, E.17.0, E.17, F.9, F.18, E.10. Coordinates with: A.6.3.CSC, A.6.3.RT, E.17.EFP, E.17.ID.CR, A.6.4, B.5.2, A.15. |
| A.6.3.RT | Representation-Scheme Transition: EntityOfConcern-Preserving Representation-Scheme Transition | Stable | Representation-scheme or reasoning-medium transition that preserves entityOfConcernRef, makes recoverability and loss visible, and blocks geometry, notation, carrier work, decode work, or transformation-flow language from becoming hidden ontology or action force. | Builds on: A.6.3, A.6.2, A.7, E.10.D2, C.2.7, E.17.0, E.17, F.9, F.18. Coordinates with: A.6.3.CSC, A.6.3.NAR, C.26, A.6.3.CR, E.17.EFP, E.17.ID.CR, A.6.4, A.15, A.20, A.21. |
| A.6.3.NAR | Structure-to-Narrative Rendering | Stable | EntityOfConcern-preserving rendering of selected source structure into a sequential narrative path for a declared reader or listener use, with source temporal posture, route family, narrator/reader roles, preserved/foregrounded/coarsened/lost structure, admissible use, and source return explicit. | Builds on: A.6.3, A.6.3.CSC, A.6.3.RT, A.22, C.33, C.34, E.17, E.10. Coordinates with: C.35, A.16.1, C.30, C.30.AD, C.30.ASV, C.32.P2S, E.4.DPF, E.4.DPF.DA. |
| A.6.4 | U.EpistemicRetargeting — EntityOfConcern retargeting morphism | Stable | Effect-free episteme-to-episteme morphism that intentionally changes entityOfConcernRef under a declared KindBridge, invariant, loss boundary, and admissible use while preserving only the commitments that the bridge makes reviewable. | Builds on: A.6.2, A.6.3, A.6.5, A.7, C.2.1, C.2, C.3, F.9, E.10.D2, E.18. Used by: E.18 StructuralReinterpretation, KD-CAL/LOG-CAL retargeting rules, Fourier-style and data-model retargetings. |
| A.6.P | Relational Precision Restoration (RPR) — Kind‑Explicit Qualified Relation Discipline | Stable | Keywords: relation precision restoration, under-specified relational language, support/support-headed wording, selected support reading, RelationKind, QualifiedRelationRecord, coupling, probe, measurement, export, endpoint referential compression, lexical guardrails, language-state seam. Queries: "How do I repair an overloaded relation word without lexicon-only cleanup?", "How do I unpack support without minting a generic SupportRelation?", "How do I keep coupling/probe/measurement/export wording kind-explicit?", "When should quality/action/sameness/wholeness/QL wording apply another governing pattern?" | Builds on: A.6, A.6.B, A.6.S, A.6.0, A.6.5, E.8, E.10, F.18. Coordinates with: A.2.4, A.2.6, A.7, A.10, C.2.1, C.2.2a, C.3.3, C.16.Q, C.26, E.17, F.9, F.17. Specialised by: A.6.A, A.6.5, A.6.6, A.6.8, A.6.9, A.6.H. |
| A.6.RSIR | Relation, Signature, Interface, Role, and Slot Precision Restoration | Stable | Keywords: relation-signature-interface-role-slot recovery, interface wording, role wording, slot wording, field, parameter, endpoint, port, API, protocol, capability, affordance, method, function, concern, interest, shadow ontology. Queries: "How do I repair interface, role, slot, parameter, function, or concern wording before choosing the direct governing pattern?", "When is interface wording a port, API, protocol, signature, module boundary, or publication view?", "When is role wording U.Role, U.RoleAssignment, relation position, evidence use, status use, or source label?" | Builds on: E.10, E.10.ARCH, A.6.P, A.6.5, A.6.0, A.2, A.2.1, A.15, F.18, F.19. Coordinates with: A.6.M, A.6.F, A.6.A, C.2.P, C.2.P.DR, E.17, A.10, F.10, G.6. |
| A.6.A | Action-Invitation Precision Restoration (ACT-INV) | Stable | Keywords: affordance, action invitation, action-first language, post-threshold classification, A.15 docking, language-state seam. Queries: "How do I repair overloaded affordance language in FPF?", "When does action-guiding language become an action invitation?", "How does A.6.A differ from early cue routing?" | Builds on: A.6.P, A.15, C.2.2a, A.16, B.4.1, F.9. Coordinates with: C.16.Q, B.5.2.0. |
| A.6.F | Function and Functional Precision Restoration (RPR-FUNCTION) | Stable | Keywords: function wording, functional architecture, FunctionalStructure, function-use repair, capability/effect, work/method boundary, module allocation, mathematical function. Queries: "When is functional architecture a structure kind rather than a separate ontology?", "How do I repair function-like wording?", "When is a function a capability, method, work, role, quality, module allocation, or mathematical mapping?" | Builds on: A.6.P, A.6.5, A.7, C.30, C.30.ASV, C.29. Coordinates with: A.6.M, A.15, C.16.Q, A.6.0, A.6.5, A.6.B, A.6.C, A.6.8, E.18, C.30.TFS-REL. |
| A.6.M | Module Relation Repair | Stable | Keywords: module relation, component, interface, port, platform, layer, stack, open architecture, substitutability, interface specification. Queries: "When is a module relation being claimed?", "How do I keep functional links, signatures, ports, and implemented interfaces distinct?", "When does open architecture require module-interface repair?" | Builds on: A.6.P, A.6.5, A.6.B, C.30, C.30.ASV, A.6.F. Coordinates with: C.31, C.31.RSA, E.18, C.30.TFS-REL, A.10, B.3, A.20, A.21, C.28, E.20, G.5, C.11. |
| A.6.5 | U.RelationSlotDiscipline - SlotKind, ValueKind, RefKind, and slot-operation discipline | Stable | Keywords: slot, argument position, value, reference, signature, substitution, pass-by-value, pass-by-reference. Queries: “How do I declare positions and references in relations?”, “How do we stop mixing roles, values and ids in signatures?”, “How does SlotKind/ValueKind/RefKind interact with EntityOfConcern / Description / specification-use and Epistemes?” | Builds on: A.6.0 (U.Signature), A.1 (Holon), A.7 (Strict Distinction), E.8 (pattern authoring discipline), E.10 (LEX-BUNDLE; Tech/Plain registers). Used by: C.2.1 (U.EpistemeSlotRelation), A.6.2–A.6.4 (episteme morphisms), A.2.1 and F.6 (RoleEnactmentFact and performed-work attribution), C.3.* (Kinds & KindSignature), E.17.0 (U.MultiViewDescribing), discipline-packs for methods/services. |
| A.6.6 | Base Declaration Discipline - Kind-explicit, scoped, witnessed base declaration discipline (with base-change lexicon) | Stable | Keywords: base declaration, basedness, baseRelation, SWBD, witnesses, scope, Γ_time, anchoring, support-as-basedness, rebase, retime, rescope. Queries: "What is base-declaration discipline?", "How to model base-dependence without anchoring?", "When is support really base-dependence?", "What is a ScopedWitnessedBaseDeclaration (SWBD)?" | Builds on: A.6.0, A.6.5, A.2.6, A.2.4, A.7, E.8, E.10. Coordinates with: A.10, A.14, C.2.1, A.6.3-A.6.4, C.3.3, E.18, F.9, F.15, F.18. Used by: base-relative admissibility/calibration/attribution patterns; anchor* and support-as-basedness rewrites into explicit baseRelation(dependent, base). |
| A.6.7 | MechSuiteDescription — Description of a set of distinct mechanisms | Stable | Keywords: mechanism suite, distinct mechanisms, suite obligations, spec pins, CN-Spec, CG-Spec, P2W, planned baseline, crossing visibility. Queries: "What is a MechSuiteDescription?", "How to describe a bundle of distinct mechanisms without using MechFamilyDescription?", "How do suite obligations differ from gate decisions?" | Builds on: E.8, A.6.1, A.6.5, E.10, E.19. Coordinates with: E.18, A.21. Used by: Part G universalization; CHR mechanism stacks. |
| A.6.8 | Service Polysemy Unpacking (RPR-SERV) | Stable | Keywords: service polysemy, service situation, interface semantics, promise content, provider principal, service/cell analogy, boundary exchange, viability envelope, API read/export. Queries: "How do I unpack service talk in FPF?", "When is an API read interface semantics rather than state evidence?", "When does service viability apply C.26.3?" | Builds on: A.6.P, A.6.B, A.6.5, A.2.3, A.2.8, A.2.9, A.15, E.10, F.17, F.18. Coordinates with: A.6.C, A.7, C.26.1, C.26.3, F.8, E.15. |
| A.6.9 | Cross-Context Sameness Disambiguation - Repairing cross-context "same / equivalent / align" via explicit Bridges (RPR-XCTX) | Stable | Keywords: cross-context sameness, bridge, alignment, mapping, direction, substitution licence, loss notes, CL, SenseCells, weakest-link. Queries: "How to disambiguate 'same' across contexts?", "How to avoid silent inversion in mappings?", "Naming-only vs substitution bridge". | Builds on: A.6.P, F.9, E.10.D1, A.7. Coordinates with: E.17, C.3.3, A.6.6, F.7/F.8. |
| A.6.S | U.SignatureEngineeringPair - Signature engineering via a ConstructorSignature and a TargetSignature | Stable | Keywords: signature engineering, TargetSignature, ConstructorSignature, two-signature arrangement, EFEM, editioning, retargeting, slot/base change lexicon, MVPK views (no new semantics), claim register, no epistemic agency. Queries: "What is U.SignatureEngineeringPair in FPF?", "How do I model TargetSignature vs ConstructorSignature (and keep Work out of edits)?", "How do slot/base change verbs compose into a reproducible signature evolution account?" | Builds on: A.6.0, A.6.2, A.6.3, A.6.4, A.6.5, A.6.6, A.6.B, A.3, A.7, A.12, C.2.1, E.17, E.10. Coordinates with: E.18, E.19. |
| A.6.H | Wholeness Language Unpacking (RPR-WHOLE) | Stable | Keywords: wholeness, integrity, part-of, boundary, environment, mereology, completeness, order/time, publication-carrier and EntityOfConcern/Description distinction, role-method-work. Queries: "How to unpack 'whole/part/integrity' in FPF?", "RPR-WHOLE trigger words", "ComponentOf vs ConstituentOf vs PortionOf vs MemberOf vs PhaseOf", "How to separate order/time from mereology?" | Builds on: A.6.P, A.6.5, A.7. Coordinates with: A.14, B.1.1, B.1.4, A.15. |
| Cluster A.V - Constitutional Principles of the Kernel | ||||
| A.7 | Strict Distinction (Clarity Lattice) | Stable | Keywords: category error, EntityOfConcern ≠ Description episteme, Role ≠ Work, ontology. Queries: "How to avoid common modeling mistakes?", "What are FPF's core distinctions?" | Builds on: A.1, A.2, A.3. Constrains: all patterns. |
| A.8 | Universal Core Principle | Stable | Keywords: universality, transdisciplinary, domain-agnostic, kernel-level U-kind admission. Queries: "How does FPF test whether a U-kind belongs in the universal core?" | Builds on: E.24.UK, A.11, C.3, F.8, F.18. Constrains: kernel-level durable U-kind candidates. |
| A.9 | Cross-Scale Consistency (C-3) | Stable | Keywords: composition, aggregation, holarchy, invariants, roll-up. Queries: "How do rules compose across different scales?", "How to aggregate metrics safely?" | Builds on: A.1, A.8. Prerequisite for: B.1. |
| A.10 | Evidence Graph Referring (C-4) | Stable | Keywords: evidence, traceability, provenance, evidence carrier, claim support, authority-reliance evidence path, status register, register excerpt, generated-explanation source support, exact authority reference, probe/distributed/export/causal evidence, SCR/RSCR. Queries: "How are claims supported by evidence?", "When does a generated explanation become source-backed evidence rather than approval or authorization?", "How do I keep evidence carriers separate from the state they report?", "When is a credential, pass, badge, or status display only an excerpt of a governing register entry or source U.EpistemePublication?" | Builds on: A.1. Coordinates with: A.6, A.15, B.3, E.17.EFP, A.20, A.21, C.16, F.9, C.26.1, C.26.2, C.26.3, C.28. |
| A.11 | Ontological Parsimony | Stable | Keywords: parsimony, composition, non-redundancy, kernel growth, U-kind admission. Queries: "How does FPF avoid adding redundant core concepts?", "When should a candidate be expressed by slots, relations, records, forms, lenses, or an existing root?" | Builds on: E.24.UK, A.8, F.8, F.18. Constrains: new core-concept and durable U-kind proposals. |
| A.12 | Acting-Side Externalization and Reflexive Split | Stable | Separates the system or holon on the acting side of a transformation from the changed holon, transformation evidence, work success, and super-holon claims. | Builds on: A.1, A.3.4, A.15.1. Coordinates with: A.2.1, A.14, B.2, C.30. |
| A.13 | The Agential Role & Agency Spectrum | Stable | Keywords: agency as role, agency spectrum, contextual role assignment, autonomy grading, substrate-neutral autonomy. Queries: "How does FPF model agency without minting a root agent kind?", "How do I grade autonomy on an evidence-backed spectrum?" | Builds on: A.2, A.2.1, A.12. Informs: C.9 Agency Characteristic Profile, E.16. |
| A.14 | Advanced Mereology: Components, Portions, Aspects & Phases | Stable | Keywords: mereology, part-of, ComponentOf, PortionOf, PhaseOf, composition. Queries: "How to model different kinds of 'part-of' relationships?" | Refines: A.1. Prerequisite for: B.1.1. |
| A.15 | Role-Method-Work Alignment (Contextual Enactment) | Stable | Keywords: role-method-work distinction, U.Role, U.Method, U.MethodDescription, U.WorkPlan, actual U.Work, work-entry readiness, contextual enactment, coordinated-work evidence, work admission display, appearance-based reliance boundary. Queries: "How do role, method, plan, readiness, and work stay distinct in FPF?", "When can coordinated work evidence a state that no one report carries?", "When is authorization-looking material an appearance-based reliance repair problem rather than work enactment?", "When does something that looks like permission or prohibition to start work need the governing FPF pattern and project-side record behind it first?" | Integrates: A.2, A.4, A.12. Builds on / coordinates with: A.6, A.10, B.3, E.17, E.17.EFP, A.20, A.21, and C.26.2. Prerequisite for: A.15.1-A.15.5, C.24, E.16. |
| A.15.1 | U.Work: Dated Performed Work Occurrence | Stable | Keywords: work occurrence, performed enactment, actuals, trace, TemporalPartOf_work, EpisodeOf_work, operational work part, concurrent work part. Queries: "What is a Work occurrence?", "How do I distinguish a time slice, episode, operational part, and submethod?", "Where are actual resource costs stored?" | Refines: A.15. Used by: B.1.6, all Part D. |
| A.15.2 | U.WorkPlan: The Schedule of Intent | Stable | Keywords: plan, schedule, intent, forecast. Queries: "How to model a plan or schedule?", "Difference between a WorkPlan and a MethodDescription." | Refines: A.15. Informs: U.Work. |
| A.15.3 | SlotFillingsPlanItem — Planned Slot-Fillings Baseline (WorkPlanning PlanItem) | Stable | Keywords: planned baseline, slot-bearing description, planned filler, edition pins, Γ_time selector, guard pins, WorkPlanning, P2W seam, variance trail. Queries: "What is SlotFillingsPlanItem in FPF?", "How to keep planned slot filling separate from FinalizeLaunchValues?", "How to pin editions and time in WorkPlanning baselines?" | Builds on: A.15.2, A.6.5, E.10.D1, E.17, E.18, E.19. Used by: A.6.7 (suite spec pins), Part G universalization, suite-specific and kit-specific planned baselines. |
| A.15.4 | Work-Relevant Appearance-Based Reliance Repair | Stable | Keywords: appearance-based reliance, reliance appearance, work or reliance use, required claim before use, required instituted effect before use, claim/effect position, project-side claim/effect reference, allowed use now, appearance overread blocked, dashboard display, credential view, generated explanation, copied approval, publication face. Queries: "What must be recovered before a dashboard, copied approval, credential view, generated explanation, or source-finding display can guide work?", "How do I keep cues, publications, credentials, evidence, gate passage, work readiness, and work authorization separate?" | Builds on: A.15, E.17, C.2.1. Coordinates with: A.10, B.3, A.6, A.2.1, A.2.8, A.2.9, A.15.5, A.20, A.21, E.10, E.10.MOVE, and E.17.EFP. |
| A.15.5 | Work-Entry Readiness and Full-Kit Preparation | Stable | Keywords: work-entry readiness, full-kit condition, readiness before work entry, commitment disposition, resource-readiness refs, launch gate, WIP and flow policy, planned slot fillings, blocked readiness overread. Queries: "Is this intended work ready to start?", "What is missing before commitment to work entry is honest?", "How do I keep full-kit readiness separate from performed work, work plans, gates, resources, and evidence?" | Builds on: A.15, A.15.2, A.15.3, B.1.6, A.21. Coordinates with: A.15.1, A.15.4, A.10, B.3, A.20, E.18, and E.10.MOVE. |
| A.16 | Language-State Move Coordination | Stable | Keywords: language-state, move, admissible language-state move, reopen, sketch-backoff, respecify, retire, responsibility transfer. Queries: "How do governed epistemes move across the language-state chart?", "What are the admissible language-state move kinds in FPF?" | Builds on: C.2.2a, C.2.LS, A.19. Coordinates with: A.16.0-A.16.2, B.4.1, E.18, and E.10.MOVE when move-like wording leaves the local language-state object. |
| A.16.0 | U.LanguageStateMoveTrajectory - Optional trajectory-account normal form over the language-state U.CharacteristicSpace | Stable | Keywords: trajectory account, lineage, fork, merge, supersedes, responsibility transfer, heavy history. Queries: "When do I publish a language-state trajectory account?", "How does FPF record lineage and branch history?" | Builds on: A.16, C.2.2a, E.17, E.18. Used by: A.16.1, A.16.2, B.4.1, B.5.2.0. Coordinates with: E.10.MOVE when move-like wording is not a language-state trajectory-account claim. |
| A.16.1 | U.PreArticulationCuePack | Stable | Keywords: cue pack, pre-articulation, early publication, cue nucleus, primary witness, candidate route cues. Queries: "What is a PreArticulationCuePack?", "How do I preserve early cues before RoutedCueSet publication?" | Builds on: A.16, C.2.2a, C.2.LS. Coordinates with: B.4.1, A.16.2. |
| A.16.2 | Reopen / SketchBackoff / Respecify | Stable | Keywords: reopen, backoff, respecify, retire, retreat, branch withdrawal, authority withdrawal. Queries: "How do I admissibly reopen or back off a language-state publication?", "How do I retire a branch without silent deletion?" | Builds on: A.16, A.16.0, C.2.2a. Coordinates with: A.6.P, B.4.1. |
| A.17 | A.CHR-NORM — Canonical “Characteristic” & rename (Dimension/Axis → Characteristic) | Stable | Keywords: characteristic, measurement, property, attribute, dimension, axis. Queries: "What is the correct term for a measurable property?", "How to define a metric?" | Prerequisite for: A.18, A.19, C.16. |
| A.18 | A.CSLC-KERNEL — Minimal CSLC in Kernel (Characteristic/Scale/Level/Coordinate) | Stable | Keywords: CSLC, Characteristic, Scale, Level, Coordinate, polarity, ordinal vs cardinal scale, one-characteristic-one-scale rule, lawful comparability, no illegal averaging, measurement interpretability. Queries: "What must be declared before a value is interpretable?", "When can two measurements be compared?", "Why can ordinal labels not be averaged?" | Builds on: A.17. Coordinates with: C.16, A.19, A.19.CN, G.0, B.3. Prerequisite for: measurement, scoring, comparison, aggregation, and CHR mechanism patterns. |
| A.19 | CharacteristicSpace & Dynamics Hook (A.CHR‑SPACE) | Stable | Keywords: CharacteristicSpace, U.Dynamics.stateSpace, state trajectories, declared Characteristics and Scales, subspace, embedding, product, structural overlays, coordinatewise comparability, role-specific space refs stay outside A.19. Queries: "How do I declare the state space a dynamics model moves through?", "How do Characteristics become a multi-coordinate state space?", "What stays inside A.19 and what belongs in source-set/space substrate or interpretive-view patterns?" | Builds on: A.17, A.18, A.2.5. Coordinates with: C.16, A.19.CN, A.19.SOURCE-SET-SPACE-SUBSTRATE, A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW, A.19.CHR, G.0, E.18, A.3.3. Prerequisite for: CHR mechanisms and dynamics models that quantify over trajectories. |
| A.19.ECS | Evaluation CharacteristicSpace Construction | Stable | Constructs or repairs the evaluation CharacteristicSpace for one evaluated object kind and use: characteristics, scales, value meanings, evidence rules, missingness, protected trade-offs, status meanings, stop or reopen conditions, and declarative governing-neighbour relations without route or reference boilerplate. | Builds on: A.17-A.19, C.16, F.18. Coordinates with: E.22, E.23, C.25, E.21, E.9.DA, E.2.DA, E.8.ECSPF, F.19. |
| A.19.SPR | State-Family Precision Restoration | Stable | Repairs state, status, posture, readiness, stance, currentness, and close state-family wording by recovering bearer, state frame or governing pattern, value set, admissible use, blocked overread, and reopen condition. | Builds on: E.10, E.10.ARCH, A.19, A.3.3, C.2.2a, A.16.*, A.10, B.3, A.20, A.21, C.27, C.29, E.17, E.9.DA, E.21, F.18. Coordinates with: A.17, A.18, C.16, C.16.P, C.16.Q, A.6.P, C.2.P, C.30.P, E.8, E.19, E.11. |
| A.19.SOURCE-SET-SPACE-SUBSTRATE | Source-Set and Search/Outcome-Space Substrate | Stable | Keywords: source set, search-side space ref, outcome-side space ref, source-set/space substrate, SpaceRefRelationKind, SourceToOutcomeRelation, DistortionPosture, SourceSetRef, sameDeclaredSpaceAs, distinctDeclaredSpaceFrom. Queries: "How do I declare one source set plus search-side and outcome-side refs?", "How do I keep source-to-outcome relation and distortion posture explicit?", "When do search and outcome refs resolve to the same declared CharacteristicSpace?" | Builds on: A.19, A.17, A.18. Coordinates with: C.18, C.19, G.5, G.10, A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW, A.6.P, A.0. Specialized by: A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW and later interpretive-view or atlas specializations. |
| A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW | Declared-Substrate Interpretive View | Stable | Keywords: declared-substrate interpretive view, thin interpretation, atlas-form interpretation, DeclaredSubstrateInterpretiveView, DeclaredSubstrateAtlasView, TraditionAtlasView, TypedSetViews, interpretive qualifiers, interpretive-only reading. Queries: "When do I use an interpretive view over an already-declared substrate?", "When is thin interpretation enough and when do I need atlas form?", "How does TraditionAtlasView stay a local specialization instead of the generic head?" | Builds on: A.19.SOURCE-SET-SPACE-SUBSTRATE, A.19, A.6.3, E.17.0, E.17. Coordinates with: G.2, G.5, G.10, C.19, C.24, A.6.P, A.0. Specialized locally by: DeclaredSubstrateAtlasView and TraditionAtlasView under G.2. |
| A.19.CN | CN-frame (comparability & normalization) | Stable | Keywords: CN-frame, CN-Spec, chart, comparability modes, normalization refs, indicator policy refs, Γ-fold governance, registry, bridges, CL/loss notes, WLNK discipline, conformance checklist, SCR/RSCR harness, RSG admission hooks. Queries: "What is a CN-frame in FPF?", "How does CN-Spec govern comparability and normalization by reference?", "How do CN-frames use bridges and CL for cross-context reuse?", "What are the conformance and regression checks for CN-frames?" | Builds on: A.19. Coordinates with: A.6.1 (mechanism intension cards), C.16 (evidence/backing), F.9 (Bridges & CL), G.0 (CG-Spec admissibility gate). |
| A.19.CHR | CHRMechanismSuite — CHR mechanism-suite anchor (suite obligations + P2W planned baseline) | Stable | Keywords: CHR suite, characterization core, CN-Spec, CG-Spec, admissibility gate, suite obligations, set-return selection, tri-state guard decision, crossing visibility, Bridge-only transport, penalties→R_eff, planned baseline, SlotFillingsPlanItem, P2W seam, no hidden scalarization, no hidden thresholds. Queries: "What is CHRMechanismSuite in FPF?", "How do CHR mechanisms cite CN-Spec/CG-Spec?", "How to enforce planned slot filling in WorkPlanning only?", "How to keep UNM/UINDM/ULSAM explicit (no hidden tails)?" | Builds on: A.6.7, A.15.3, A.6.1, A.6.5, A.19, G.0, E.18, E.10, E.19. Coordinates with: A.21, G.5, G.10, C.23. Used by: Part G universalization; CHR mechanism stacks. |
| A.19.UNM | Unified Normalization Mechanism (UNM) | Stable | Keywords: normalization, CV→NCV, ≡_UNM, NormalizationMethodId, NormalizationMethodInstanceId, NormalizationInvariant[*], NormalizationFixSpec, validity window (no implicit “latest”), fail-closed tri-state guard (`pass | degrade |
| A.19.UINDM | Unified Indicatorization Mechanism (UINDM) | Stable | Keywords: indicatorization, indicator set, IndicatorChoicePolicy, CN-Spec.indicator_policy, CHR suite stage indicatorize, tri-state admissibility (`pass | degrade |
| A.19.USCM | Unified Scoring Mechanism (USCM) | Stable | Keywords: scoring, score profile, ScoringMethodDescription, ScaleComplianceProfile (SCP), CSLC-lawful transforms, CG-Spec.MinimalEvidence, tri-state admissibility (`pass | degrade |
| A.19.ULSAM | Unified Lawful Scale Aggregation Mechanism (ULSAM) | Stable | Keywords: lawful aggregation, scale-lawful fold, fold_Γ?, ΓFoldRef, CG-Spec.Γ_fold, CG-Spec.SCP, MinimalEvidence, tri-state guard (`pass | degrade |
| A.19.CPM | Unified Comparison Mechanism (CPM) | Stable | Keywords: comparison, comparator, ComparatorSpecRef, ComparatorSet, set-valued comparison outcome, partial order, tri-state admissibility (`pass | degrade |
| A.19.SelectorMechanism | Unified Selection Kernel (SelectorMechanism) | Stable | Keywords: selection kernel, set-returning selection, selected set, SelectEligibility, tri-state guard (`pass | degrade |
| A.20 | Flow Constraint Validity — Eulerian | Stable | Keywords: flow, ConstraintValidity, Eulerian, TransformationFlowStructure, GateFit, MVPK, SquareLaw, Sentinel, PathSlice. Queries: "What is ConstraintValidity in FPF?", "What is the Eulerian stance in FPF flows?", "How does E.18 relate to flows?" | Builds on: E.18. Coordinates with: A.21, E.17, F.9, F.17, A.19.SelectorMechanism, C.18, C.19, G.5, G.6, G.11. |
| A.21 | GateProfilization: OperationalGate(profile) (GateFit core) | Stable | Keywords: OperationalGate, GateFit, GateProfile, GateChecks, join-semilattice, GateDecision, DecisionLog, EquivalenceWitness, LaunchGate, CV⇒GF. Queries: "What is GateProfilization in FPF?", "How does OperationalGate aggregate GateChecks?", "What is the CV⇒GF activation predicate?" | Builds on: E.18, E.17 (MVPK), A.7. Coordinates with: A.20, A.2.6, F.9, F.17, G.6, G.11, A.19, G.0, G.5, C.18, C.19, G.9. |
| A.22 | Structure and Structural Views (STRUCT-CAL) | Stable | Keywords: structure, structural view, selected structure, preserved and lost structure, source return, architecture-description boundary, structural description. Queries: "What is structure in FPF?", "How do I separate structure from a description, view, graph, decision, or mathematical lens?", "When does an extracted view need source return?" | Builds on: A.1, A.6.3, A.7, C.2.1, E.10.D2, E.17. Coordinates with: C.30, C.30.AD, C.30.ASV, C.29, E.18, A.10, B.3, A.20, A.21. |
| A.22.CGUS | Constraint-Governed Unfolding Structure | Stable | A.22 specialization for graph-shaped or partially ordered structures over typed positions, exact referenced relations, cross-position constraints, preserved structures, C.33 adequacy notes, and admissible next-form kinds. Separates provisional demonstrations, post-admission whole-structure descriptions, and post-admission demonstrative slices over selected traversals. Queries: "When is a readable chain only a provisional demonstration?", "How do I preserve branches, joins, cycles, and alternatives behind one walkthrough?" | Specializes: A.22. Coordinates with: E.18.3, E.18.1, E.23, C.32.P2S, E.11, F.17, C.33, C.35. |
Part B — Trans-disciplinary Reasoning Cluster
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| B.1 | Holon Aggregation and Part-Whole Construction | Stable | Recovers part-whole, membership, collection-as-whole, role or method relation structure, work occurrence holarchy, selected architecture structure, or mathematical-description claims before using aggregation notation. | Builds on: A.1, A.14, C.13. Coordinates with: A.15.1, C.29, C.30.ASV, B.2, B.3.5. |
| B.1.1 | Dependency Structure and Relation Grounding | Stable | Keeps dependency structure, graph or representation lens, relation grounding, constructive grounding, and proof or evidence claims separate. | Builds on: B.1, A.14, C.13. Coordinates with: C.29, A.10, B.3.5. |
| B.1.2 | System Aggregation and Holon Delimitation | Stable | Repairs system aggregation, system delimitation, boundary-crossing relation, and acting-system admission without minting generic boundary, interaction, or system-subtype ontology. | Builds on: B.1, A.1, A.12, A.14, C.13. Coordinates with: A.3.4, A.15.1, C.30. |
| B.1.3 | Γ_epist — Knowledge-Specific Aggregation | Stable | Keywords: knowledge aggregation, epistemic, provenance, trust, KD-CAL. Queries: "How to combine epistemes?", "How does trust propagate in FPF?" | Builds on: B.1, A.1, C.2. |
| B.1.4 | Contextual and Temporal Aggregation | Stable | Aggregates bounded-context slices, temporal slices, phases, windows, and context-local whole claims without treating context, time, or process wording as generic interaction ontology. | Builds on: B.1, A.1.1, A.14, C.27.TA. Coordinates with: A.15.1, A.3.4, C.29. |
| B.1.5 | Gamma_method - Order-Sensitive Method Composition and Work Enactment | Stable | Keywords: method composition, submethod, order-sensitive method, method relation structure, MIC, typed join, capability continuity, work enactment, method/work granularity, assurance hooks. Queries: "How do I combine methods?", "When is a step a submethod rather than a work part, plan item, or description node?", "How do MIC, typed joins, Gamma_ctx, Gamma_work, and B.3 assurance hooks stay distinct?" | Builds on: B.1, B.1.4, A.3.1. Coordinates with: A.15.1, B.1.6, B.3. |
| B.1.6 | Work-Resource Aggregation | Stable | Aggregates dated work-resource use and work occurrence holarchy while keeping method structure, work plans, resource ledgers, evidence, and mathematical notation with direct owners. | Builds on: B.1, A.15.1, A.14. Coordinates with: A.3.4, A.15.2, C.29, B.2. |
| B.2 | Meta-Holon Transition - Whole Reidentification | Stable | Whole-reidentification pattern for MHT claims: existing whole, candidate result holon kind, trigger profile, changed-content owner, evidence or source relation, and blocked overread. | Builds on: A.1, A.14, B.1, C.13. Coordinates with: B.2.P, B.2.2, B.2.3, B.2.4, C.16, C.29, C.30.ILC. |
| B.2.P | Emergence and MHT Precision Restoration | Stable | Repairs emergence, synergy, higher-level property, MHT, MET, MFT, metric mirage, and collection words entangled with whole-reidentification by recovering the claim kind first. | Builds on: E.10, E.10.ARCH, B.2, A.14, C.13, B.3.5. Coordinates with: B.2.2, B.2.3, B.2.4, C.16, A.2.2, A.6.F, A.3.4, C.30.ILC. |
| B.2.2 | Meta-System Transition - System Specialization of MHT | Stable | Specializes B.2 for result holons admitted as U.System, with system participation, agency-threshold, structure, evidence, and whole-reidentification boundaries. | Builds on: B.2, A.1, A.12. Coordinates with: A.2.1, A.19, C.16, C.30. |
| B.2.3 | Meta-Holon Transition With Episteme Result | Stable | Specializes B.2 for MHT-result holons admitted as U.Episteme, while C.2.1 and publication/source-use patterns govern episteme slot relation and publication claims. | Builds on: B.2, A.1, C.2.1. Coordinates with: E.17, A.10, B.3, C.29. |
| B.2.4 | Capability and Functioning Whole Reidentification | Stable | B.2-facing specialization for cases where capability envelope, functioning relation, or transformation-flow structure creates or reveals a whole-reidentification question. | Builds on: B.2, A.2.2, C.16, A.6.F, A.3.4. Coordinates with: C.30.ASV, C.30.TFS-REL, A.6.M, A.15.1. |
| B.2.5 | Supervisor-Subholon Feedback Relation | Stable | Governs supervisor-subholon feedback relation claims without turning supervisor wording into generic interaction, transformer, or loop-mathematical-lens ontology. | Builds on: B.2, A.1, A.12. Coordinates with: A.2.1, A.3.4, C.30.LCA, C.29, A.10, B.3. |
| B.3 | Trust & Assurance Calculus (F–G–R with Congruence) | Stable | Keywords: trust, assurance, reliability, F-G-R, formality, scope, congruence, evidence, claim-support posture, authority-looking labels, dashboard tiles, probe/distributed/export/causal assurance. Queries: "How is trust calculated in FPF?", "When does an authority-looking label or dashboard tile fail to raise assurance?", "How does FPF handle evidence and confidence?" | Builds on: A.10. Coordinates with: A.6, A.15, E.17.EFP, A.20, A.21, C.26, C.26.1, C.26.2, C.26.3, C.16, C.28, F.9. Prerequisite for: All B.3.x, D.4. |
| B.3.3 | Assurance Subtypes & Levels | Stable | Keywords: assurance levels, L0-L2, TA, VA, LA, typing, verification, validation. Queries: "What are the assurance levels in FPF?", "How does an assurance record mature in FPF?" | Builds on: B.3. |
| B.3.4 | Evidence Decay & Epistemic Debt | Stable | Keywords: evidence aging, decay, freshness, epistemic debt, stale data. Queries: "How does FPF handle outdated evidence?", "What is epistemic debt?" | Builds on: B.3. |
| B.3.5 | Working-Model Relations & Grounding (CT2R-LOG) | Stable | Keywords: grounding, constructive trace, working model, assurance layer, CT2R, Compose-CAL. Queries: "How are FPF models grounded in evidence?", "What is the CT2R-LOG?" | Builds on: B.3, E.14, C.13. |
| B.4 | Canonical Evolution Loop | Stable | Keywords: evolution loop, DesignRunTag feedback, observe-notice-stabilize-route, drift repair, knowledge refinement, method refinement, open-ended evolution. Queries: "How does FPF evolve a system or episteme without design-reality drift?", "Where do knowledge and method instantiation sit in the canonical loop?", "Where does pre-abductive routing sit?" | Builds on: A.4, A.12. Refined by: B.4.1. Carries embedded slices for: knowledge instantiation and method instantiation. |
| B.4.1 | Observe -> Notice -> Stabilize -> Route | Stable | Keywords: routed cue set, route plurality, route selection, pre-abductive seam, task-family specialization route. Queries: "How do under-articulated cues become routed before endpoint claim publication?", "When should a cue become a routed cue set instead of an abductive prompt?" | Builds on: A.16, A.16.1, C.2.2a. Coordinates with: B.5.2.0, C.16.Q, A.6.A, C.22.1. |
| B.5 | Canonical Reasoning Cycle | Stable | Keywords: reasoning, problem-solving, Abduction-Deduction-Induction, scientific method. Queries: "How does FPF model problem-solving?", "What is the canonical reasoning cycle?" | Builds on: A.10. Prerequisite for: All B.5.x. |
| B.5.1 | Explore → Shape → Evidence → Operate | Stable | Keywords: development state cycle, open-ended progression, state machine, Explore, Shape, Evidence, Operate. Queries: "What states can project work and its records pass through in FPF?" | Builds on: B.5. |
| B.5.2 | Abductive Loop | Stable | Keywords: abduction, explanatory prompt, candidate hypotheses, plausibility filters, origin trace, route-to-hypothesis. Queries: "How does FPF model abductive hypothesis generation?", "What is the abductive loop?" | Builds on: B.5, B.5.2.0, A.10, B.3.3. Coordinates with: B.4.1, A.16, A.6.P. |
| B.5.2.0 | U.AbductivePrompt | Stable | Keywords: abductive prompt, prompt species, rival-set discipline, threshold crossing, explanation-ready cue. Queries: "When is a routed cue ready to enter abduction?", "What prompt species does FPF distinguish before hypothesis work begins?" | Builds on: B.4.1, A.16, C.2.2a. Coordinates with: A.6.P, A.6.A, C.16.Q. Used by: B.5.2. |
| B.5.2.1 | Creative Abduction with NQD | Stable | Keywords: creative abduction, NQD binding, Γ_nqd.generate, Creativity-CHR, Q-front, declared Q components, retained exploration/archive evidence, Novelty@context, ΔDiversity_P, E/E-LOG, DecisionSubject note. Queries: "How do I make abductive idea generation instrumented instead of ad-hoc?", "How does B.5.2 delegate generation to C.18 and pool policy to C.19?", "Why does creative abduction return a front/evidence set rather than one bundled winner?" | Builds on: B.5.2, A.17, A.18, C.17, C.18, C.19. Coordinates with: B.4, C.11, G.5. |
| B.5.3 | Domain-Concept Bridge | Stable | Keywords: domain vocabulary, concept bridge, local sense, bounded context, bridge scope, role assignment boundary. Queries: "How does FPF integrate domain-specific language without minting false kinds?", "When is a domain word a role, a kind, a characteristic, or a local sense?" | Builds on: A.2, A.6.5, C.3, E.24.UK, F.1, F.2, F.3, F.5, F.8. |
Part C — Kernel Extension Specifications
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| Cluster C.I – Core CALs / LOGs / CHRs | ||||
| C.1 | Physical System State, Conservation, and Resource-Flow Calculus (Sys-CAL) | Planned | Keywords: physical system, composition, conservation law, stock-flow, energy, mass, resource flow, U.System. Queries: "How to model physical systems in FPF?", "What conservation or stock-flow claim is being made?", "How do resources move through a system?" | Builds on: A.1, A.14, A.22, A.3.4, A.19, C.16. Coordinates with: B.1.6, C.5, C.14, C.30. |
| C.2 | KD‑CAL | Stable | Keywords: knowledge, epistemic, evidence, trust, assurance, F-G-R, Formality, ClaimScope, Reliability, provenance. Queries: "What is F-G-R?", "How does FPF handle evidence and trust?", "How to model a scientific theory?". | Builds on: A.1, A.10, B.3. Prerequisite for: All patterns using F-G-R. |
| C.2.1 | U.Episteme - Epistemes and their slot relation | Stable | U.EpistemeSlotRelation organizes EntityOfConcern, GroundingHolon, ClaimGraph, Viewpoint, View, ReferenceScheme, RepresentationScheme, and related slots for claim-bearing epistemes across symbolic, diagrammatic, latent, and tool-mediated representations. | Builds on: C.2, A.1, A.6.5, A.7, E.10.D2. Used by: A.6.2-A.6.4, E.17.0-E.17.2, E.17, E.18, B.1.3, KD-CAL/LOG-CAL discipline packs. |
| C.2.P | Epistemic Precision Restoration | Stable | Restores precision for source expression, claim-bearing episteme, publication, view, face, carrier, PublicationUnit, EntityOfConcern, grounding relation, pattern-application wording, and FPF-governed use dispositions without turning files or names into claim objects. | Builds on: E.10, C.2.1, A.7, E.17.0, E.17, A.6.P, F.18. Coordinates with: E.8, E.12, E.17.AUD, E.17.EFP, E.17.ID.CR, A.10, A.15, A.20, A.21, B.3, C.11. |
| C.2.2 | Reliability R in the F–G–R triad | Stable | Keywords: Reliability (R), warrant, evidence-bound, F–G–R, ClaimScope (G), Bridge-only reuse, Congruence Level (CL / CL^k / CL^plane), weakest-link, pathwise justification (PathId), TA/VA/LA lanes, no implicit averaging. Queries: "What is R in F–G–R?", "How does FPF propagate reliability?", "How do CL penalties route under transport?", "Bridge-only reuse of claims in FPF". | Builds on: C.2, A.2.6, C.2.3, B.3, B.1.3, C.3, F.9. Coordinates with: G.6, G.7, E.14, E.18. Constrains: any cross-context claim reuse and any publication of R_eff. |
| C.2.2a | U.LanguageStateSpace - Language-state chart over U.CharacteristicSpace | Stable | Keywords: language-state chart, characteristic space, position claim, partial coordinates, thresholds, governed episteme publication. Queries: "What is the language-state space in FPF?", "How do I publish a position claim before endpoint claim publication?" | Builds on: A.19, E.10, F.18. Used by: C.2.LS, A.16, B.4.1, C.16.Q, A.6.A. |
| C.2.3 | Unified Formality Characteristic F | Stable | Keywords: Formality, F-scale, F0-F9, rigor, proof, specification, language-state separation. Queries: "What is Formality F in FPF?", "How does F differ from articulation, closure, or anchoring?" | Builds on: C.2. Constrains: all patterns referencing F-G-R or language-state facets. |
| C.2.LS | U.LanguageStateFacetProfile - Thin profile bundle for language-state facets | Stable | Keywords: facet profile, articulation, closure, anchoring, representation factors, threshold package. Queries: "How are language-state facets named together in FPF?", "What is a LanguageStateFacetProfile?" | Builds on: C.2.2a, C.2.4-C.2.7. Coordinates with: A.16. |
| C.2.4 | U.ArticulationExplicitness | Stable | Keywords: articulation explicitness, semantic shape, under-articulated cue, explicitness, early repair readiness. Queries: "How explicit is a governed episteme already?", "What is ArticulationExplicitness in FPF?" | Builds on: C.2.2a. Coordinates with: C.2.LS, A.16. |
| C.2.5 | U.LanguageStateClosureDegree | Stable | Keywords: closure degree, candidate-space closure, reopen, rival routes, settledness. Queries: "How closed is the current candidate space?", "What is LanguageStateClosureDegree in FPF?" | Builds on: C.2.2a. Coordinates with: C.2.LS, A.16. |
| C.2.6 | U.LanguageStateAnchoringMode | Stable | Keywords: anchoring mode, embodiment, trace, model state, document, operator loop. Queries: "How is a language-state claim anchored in FPF?", "What is LanguageStateAnchoringMode?" | Builds on: C.2.2a. Coordinates with: C.2.LS, F.9.1. |
| C.2.7 | U.LanguageStateRepresentationFactorBundle | Stable | Keywords: representation factors, locality, sparsity, symbolicity, factor bundle, representation organization. Queries: "How does FPF describe representation factors in language-state work?", "What is the representation-factor bundle?" | Builds on: C.2.2a. Coordinates with: C.2.LS, C.2.6. |
| C.2.P.DR | Declarative Representation Precision Restoration | Stable | Repairs overread of graph paths, evidence paths, query paths, dashboards, schemas, formal substrates, method descriptions, publication faces, and pattern relations when a declarative representation is treated as method, work, gate, release, proof, or pattern application by shape alone. | Builds on: C.2.P, E.10, E.10.ARCH, F.19. Coordinates with: E.18, A.10, E.17, A.3.1, A.3.2, A.6.1, A.15.1, A.15.2, C.29. |
| C.3 | Kinds, Intent and Extent, and Typed Reasoning | Stable | Keywords: kind, type, intension, extension, subkind, typed reasoning, classification, vocabulary. Queries: "How does FPF handle types?", "What is a 'Kind'?", "Difference between 'scope' and 'type'?". | Builds on: A.1, A.2.6 (USM). Prerequisite for: LOG-CAL and any pattern needing typed guards. |
| C.3.1 | U.Kind and U.SubkindOf Core | Stable | Keywords: kind, subkind, partial order, type hierarchy. Queries: "What is U.Kind in FPF?", "How to model 'is-a' relationships?". | Builds on: A.1, A.2.6 (USM). Prerequisite for: C.3.2, C.3.3. |
| C.3.2 | KindSignature (+F) & Extension/MemberOf | Stable | Keywords: KindSignature, intension, extension, MemberOf, Formality F, determinism. Queries: "How to define the meaning of a Kind?", "What is the difference between intent and extent in FPF?". | Builds on: C.3.1. Prerequisite for: C.3.3, C.3.4. |
| C.3.3 | KindBridge & CL^k — Cross‑context Mapping of Kinds | Stable | Keywords: KindBridge, type-congruence, CL^k, cross-context mapping, R penalty. Queries: "How to map types between domains?", "What is a KindBridge?". | Builds on: C.3.1, C.3.2, A.2.6, C.2.2. |
| C.3.4 | RoleMask — Contextual Adaptation of Kinds (without cloning) | Stable | Keywords: RoleMask, context-local adaptation, constraints, subkind promotion. Queries: "How to adapt a Kind for a local context?", "What is a RoleMask in FPF?". | Builds on: C.3.1, C.3.2. |
| C.3.5 | KindAT — Intentional Abstraction Facet for Kinds (K0…K3) | Stable | Keywords: KindAT, abstraction tier, K0-K3, informative facet, planning. Queries: "What are the abstraction tiers for Kinds?", "How to plan formalization effort?". | Builds on: C.3.1. |
| C.3.A | Typed Guard Macros for Kinds + USM (Annex) | Stable | Keywords: Typed guard, ESG, Method-Work, USM, Kind-CAL, regulatory profile. Queries: "How to write a typed guard?", "How do Kinds and USM interact in gates?". | Builds on: All C.3.x, A.2.6. |
| C.5 | Resource Use and Work-Cost Calculus (Resrc-CAL) | Planned | Keywords: resource use, dated consumption, work cost, budget, cost bearer, resource ledger, efficiency claim. Queries: "How does FPF model resource use by work?", "How to keep resource cost separate from evidence or value?", "What resource ledger supports a work-cost claim?" | Builds on: A.15.1, A.15.2, B.1.6, C.16, A.10. Coordinates with: C.1, C.24, G.9, B.3. |
| C.6 | Proof and Inference Use Calculus (LOG-CAL) | Planned | Keywords: proof use, inference rule, typed guard, claim entailment, proof obligation, reasoning support. Queries: "What inference is licensed here?", "When is a proof claim separate from evidence?", "Which typed rule supports this conclusion?" | Builds on: C.3, C.2.1, A.10, B.3. Coordinates with: B.3.5, C.23, G.8, A.6.B. |
| Cluster C.II – Domain‑Specific Patterns | ||||
| C.9 | Agency Characteristic Profile | Planned | Keywords: agency, autonomy, responsibility threshold, decision capacity, intervention capacity, agentive role. Queries: "What agency claim is being made?", "When does a system or role holder count as agentive enough for this decision?", "How should autonomy be characterized without minting a new agent kind?" | Builds on: A.13, A.17, A.18, A.19, C.16, A.10. Coordinates with: B.3, C.11, C.24, D.2. |
| C.11 | Decision Theory (Decsn-CAL) | Stable | Keywords: decision theory, DecisionSubject, OptionSet, comparison basis, ChoiceRule, ChoiceResult, question order, probe-worthiness, non-shared comparison frame, ValueOfInformation, ValueOfComputation, choose now, reject current set, probe again, reroute. Queries: "When should one choose now versus probe again?", "What must be explicit before a choice among already-available options is lawful?", "When do question order or incompatible frames require C.26 rather than ordinary choice?" | Builds on: A.6.P, A.6.5, A.13, C.9, A.18, A.19. Coordinates with: C.26, C.18, C.19, C.24, G.5. |
| Cluster C.III – Meta‑Infrastructure CALs | ||||
| C.13 | Constructional Mereology (Compose‑CAL) | Stable | Keywords: mereology, part-whole, composition, sum, set, slice, extensional identity. Queries: "How does FPF formally construct parts and wholes?", "What is Compose-CAL?". | Builds on: A.14. Is used by: B.3.5 (CT2R-LOG). |
| Cluster C.IV – Composite & Macro‑Scale | ||||
| C.14 | System-of-Systems and Infrastructure Calculus (M-Sys-CAL) | Planned | Keywords: system-of-systems, infrastructure, inter-system dependency, service network, infrastructure boundary, operational coupling. Queries: "How to model a complex infrastructure such as a power grid?", "Which cross-system dependency changes the claim?", "When is this a system-of-systems rather than one system?" | Builds on: C.1, B.2.2, A.22, C.30, B.1.6. Coordinates with: C.30.ILC, C.5, D.2, G.6, B.3. |
| C.16 | Measurement & Metrics Characterization (MM‑CHR) | Stable | Keywords: measurement, measurement template, U.DHCMethod(Ref), U.Measure, U.Unit, U.EvidenceStub, polarity, direct comparability, scoring method disclosure, probe-changing-state, shared-frame check, CSLC. Queries: "How do I define a measurement template in FPF?", "When is a metric a passive read and when does it change the state?", "How do EvidenceStubs support measurement claims?" | Builds on: A.17, A.18. Coordinates with: A.10, B.3, C.26, C.26.1. Is a prerequisite for: All CHR patterns and any pattern that issues typed measures/scores. |
| C.16.P | Characteristic and Scale Precision Restoration | Stable | Repairs overloaded characteristic, scale, coordinate, metric, score, indicator, threshold, comparison, and scalar-quality wording before C.16/A.17-A.19/C.25/C.29/E.21 or another governing pattern is applied. | Builds on: E.10, E.10.ARCH, A.17, A.18, C.16, A.19, C.25, C.29, E.21, F.18, A.6.P. Coordinates with: C.16.Q, A.19.ECS, evidence, assurance, gate, decision, causal-use, benchmark, and publication patterns governing those claims. |
| C.16.Q | Quality-Term Precision Restoration | Stable | Repairs overloaded quality and evaluative-characterization wording by selecting an endpoint-governed evaluative form or a bounded transitional quality-term repair form with declared bearer, evaluation frame, sense family, admissible normal form, and governing pattern. | Builds on: E.10, E.10.ARCH, C.16.P, C.16, C.25, E.21, A.17, A.18, A.19, A.7, C.2.1, E.8, F.9, F.18. Coordinates with: A.6.P, A.6.A, A.16, B.4.1, B.5.2.0, A.10, B.3, F.9.1. |
| C.17 | Creativity‑CHR — Characterising Generative Novelty & Value | Stable | Keywords: Creativity-CHR, Novelty@context, Use-Value and ValueGain, Surprise, ConstraintFit, Diversity_P, Originality, ResourceEfficiency, MM-CHR measurement templates, ReferenceBase, evidence, portfolio composition. Queries: "How do I make a creativity claim measurable and evidence-bound?", "Which characteristics distinguish novelty, value, surprise, constraint fit, diversity, originality, and resource efficiency?", "How do creative outputs compose from individuals to portfolios?" | Builds on: C.16, A.17, A.18, A.19. Coordinates with: B.5.2.1, C.18, C.19, C.9, B.3, B.4, F.5/F.18. |
| C.18 | NQD‑CAL — Open‑Ended Search Calculus | Stable | Keywords: NQD-CAL, Γ_nqd.generate, Γ_nqd.updateArchive, Γ_nqd.illuminate, Γ_nqd.selectFront, DescriptorMapRef, DistanceDefRef, NQDArchive, CandidateSet, Front vs ExplorationArchive, IlluminationSummary report-only telemetry, EmitterPolicyRef, InsertionPolicyRef, provenance editions. Queries: "How does FPF run open-ended search without illegal scalarization?", "What is the difference between a front and an exploration archive?", "What provenance must an NQD generation call publish?" | Builds on: C.16, C.2, A.17-A.19. Coordinates with: B.5.2.1, C.17, C.19, G.5, G.6, G.11. |
| C.18.1 | Scaling‑Law Lens Binding (SLL) | Stable | Keywords: scaling law, scale variables (S), compute‑elasticity, data‑elasticity, resolution‑elasticity, exponent class, knee, diminishing returns. Queries: "How to make search scale‑savvy?", "Where to declare scale variables and expected elasticities?" | Builds on: C.16, C.17, C.18. Coordinates with: C.19, G.5, G.9, G.10. |
| C.19 | Explore–Exploit Governor (E/E‑LOG) | Stable | Keywords: explore-exploit, live candidate pool, pool-policy result, widen, keep frontier, narrow to subset, sunset line, reroute, EmitterPolicy, InsertionPolicy, lens id, dominance default routing, DecisionSubject clarification. Queries: "How should one govern a still-live candidate pool?", "When do I widen, keep frontier, narrow, sunset, or reroute?", "How does pool policy stay separate from C.11 choice, C.24 planning, and G.5 publication?" | Builds on: C.18, C.17, C.11, B.3, Compose-CAL. Coordinates with: C.24, G.5, G.9. |
| C.19.1 | Bitter‑Lesson Preference (BLP) | Stable | BLP comparison and waiver discipline for scalable general methods versus bounded specialization, including E.23 method-family choice and cost/risk posture. | Builds on: C.19, C.24, B.3. Coordinates with: E.23, G.5, G.8, G.9, G.11, A.0. |
| C.20 | Composition of U.Discipline (Discipline‑CAL) | Stable | Keywords: discipline, U.AppliedDiscipline, U.Transdiscipline, episteme corpus, standards, institutions, Γ_disc. Queries: "How to compose and assess a discipline in FPF?" | Builds on: C.2 KD‑CAL, G.0, Part F (Bridges/UTS). Coordinates with: C.21, C.23. |
| C.21 | Discipline‑CHR - Field Health & Structure | Stable | Keywords: discipline, field health, reproducibility, standardisation, alignment, disruption. Queries: "How to measure the health of a scientific field?", "What is reproducibility rate?". | Builds on: C.16, C.2, A.2.6, B.3. Coordinates with: C.20, G.2. |
| C.22 | Problem Typing & TaskSignature Assignment (Problem-CHR) | Stable | Constructs TaskSignature@Context as a Context-local U.Signature species and, when a receiving use is current, separately assigns its exact edition to one problem-side episteme. Preserves CHR typing, unknowns, scope, evidence, currentness, and crossing conditions before method selection. | Builds on: A.6.0, C.16, G.0. Coordinates with: C.22.1, C.22.2, C.23, G.4, G.5. |
| C.22.1 | Task-family adaptation signature | Stable | Durable task-family specialization fields: threshold target, time-to-threshold, budget-to-threshold, prior exposure, transfer, retention, downside, and corridor entry. | Builds on: C.22, C.19.1, A.15, C.24, E.16. Coordinates with: E.23, G.5, G.9, G.11. |
| C.22.2 | ProblemCard@Context | Stable | Keywords: problem card, problem-side record, P2W-ready, Thin problem card, setContextRef, problem signal, support posture, validation boundary, first-principles cue, safe-probe-needed, freshness and unknown disposition. Queries: "How do I turn a messy signal into a reviewable problem before P2W?", "When is a problem card P2W-ready?", "How do problem cards keep evidence, gates, autonomy, archives, and method selection in neighboring patterns?" | Builds on: E.2, E.9, E.10, C.2.P, A.6.P, C.16.Q, C.16, A.19, C.22, C.25, C.29, G.5, G.9, A.6.3.RT, A.6.4. Coordinates with: C.11, C.18, C.19, C.22.1, C.24, C.27, C.28, A.15, A.21, E.16, G.6, G.11, A.10, B.3, E.17, E.17.ID.CR, A.6.3, F.9, E.18. |
| C.23 | Method‑SoS‑LOG — MethodFamily Evidence & Maturity | Stable | Keywords: MethodFamily, evidence, maturity, SoS-LOG, admit, degrade, abstain, selector. Queries: "How is method family maturity assessed?", "What is the SoS-LOG for selection?". | Builds on: G.5, G.4, C.22, B.3. |
| C.24 | Agentic Tool-Use and Call Planning (C.Agent-Tools-CAL) | Stable | Call-route and call-plan discipline for tool-using agents: plan/work separation, checkpoint return, tool-call budget, stop or replan condition, and overread boundaries. | Builds on: A.15, B.3, C.5, C.18, C.19. Coordinates with: E.23, C.11, C.28, G.5, G.6, G.9. |
| C.25 | Q-Bundle: Authoring "-ilities" as Structured Quality Bundles | Stable | Keywords: quality bundle, -ility, quality family, characteristic plus scope, mechanism/status slots, endpoint classification, viability envelope, proxy metric, admissible quality-family use, failure mode. Queries: "What is a Q-Bundle in FPF?", "When is an -ility one characteristic and when is it a bundle?", "When does a viability claim need C.26.3 rather than one metric?" | Builds on: A.2.6, A.6.1, C.16, B.3. Coordinates with: C.16.Q, A.15, C.26.3. |
| C.26 | Quantum-Like Modeling Lens | Stable | Keywords: quantum-like, QL-lite, QL-NQ, probe frame, order effect, incompatible probes, instrument update, state export, source-loss coarsening, minimal admissible output. Queries: "When is quantum-like useful as a mathematical lens in FPF?", "What representational mistake does QL-lite prevent?", "How do I use QL without making a physical quantum claim?" | Builds on: C.11, C.16, A.6, A.10, B.3, F.9, A.6.3.CSC, A.6.3.RT. Constrains: C.26.1-C.26.3. Coordinates with: A.15, C.25, C.18, C.19. |
| C.26.1 | Probe-Coupled Boundary Interaction | Stable | Keywords: probe-coupled boundary, passive read, dashboard as instrument, workshop as state-changing interaction, API read, survey, bridge result, export loss, evidence window. Queries: "When does a dashboard, workshop, metric, or API read change what it reports?", "How do I stop treating a boundary interaction as a passive read?", "When should a probe-coupled case apply evidence or assurance patterns?" | Builds on: C.26, A.6, A.6.B, A.10, B.3, C.16, F.9, A.15. Coordinates with: C.26.2, C.26.3, A.6.8. |
| C.26.2 | Enacted Distributed State Evidence | Stable | Keywords: distributed-state evidence, coordinated work, enacted state, minimal state reading, evidence carrier, window, rival explanation, no group mind, report/export loss. Queries: "When does coordinated work evidence a state no participant report carries?", "How do I bound a distributed-state reading?", "When is a survey or dashboard thinner than the enacted state?" | Builds on: C.26, A.15, A.10, B.3, F.9, C.16. Coordinates with: C.26.1, C.26.3. |
| C.26.3 | Viability-Envelope Boundary Regulation | Stable | Keywords: viability envelope, homeostasis, allostasis, boundary regulation, sensor/probe/actuator split, metric-induced distortion, service viability, quality bundle, failure mode. Queries: "When is viability more than one green metric?", "How do boundary probes or metrics change a viability envelope?", "When does a service split or support load need envelope regulation?" | Builds on: C.26, C.25, U.Dynamics, A.6, A.15, C.16, A.10, B.3, A.3, A.19, C.18, C.19. Coordinates with: C.26.1, C.26.2. |
| C.27 | Temporal Claim Adequacy: State Readings, Temporal Trends, and Intervention-Sensitive Temporal Change | Stable | Keywords: temporal claim adequacy, temporal claim, state reading, rate reading, temporal trend, rate-change, intervention-sensitive temporal change, effort window, resistance/inertia, rhythm/cadence, throughput, recovery, braking, coasting, stabilization, dynamic benchmark. Queries: "When does a speed, rhythm, throughput, or recovery claim need temporal adequacy?", "How do I separate state, rate, and intervention-sensitive rate-change?", "When is faster improvement not enough for benchmark, quality, viability, or QL claims?" | Builds on: C.16, A.3.3, B.1.4, B.1.6. Coordinates with: C.27.TA, A.3.4, C.18.1, C.19, C.22.1, C.24, C.25, C.26, C.26.3, G.9, A.10, B.3. |
| C.27.TA | Temporal Aspect: Time Windows, Rhythm, Cadence, and Currentness | Stable | Keywords: temporal aspect, time window, freshness, currentness, rhythm, cadence, validity window, recovery timing. Queries: "Which time relation matters for this claim or object?", "How do I state freshness, rhythm, latency, or validity window without turning it into evidence, work, or dynamics law?" | Builds on: A.3.4, A.3.3, C.27, E.24. Coordinates with: A.10, B.3, A.15.1, A.15.2, A.20, A.21, C.16, C.29, E.18, G.11. |
| C.28 | CausalUse-CAL: Causal-Use Questions, Causality-Ladder Rungs, Identification and Realizability | Stable | Keywords: causal-use question, causality ladder, association, intervention, counterfactual, Pearl Causal Hierarchy, Structural Causal Model, causal diagram, causal estimand, identification, counterfactual sampling realizability, causal evidence support basis, target trial, causal fairness, off-policy causal evaluation, causal-RL evaluation. Queries: "Can I say this caused that?", "Is this intervention claim supported?", "What evidence supports a counterfactual claim?", "When does a fairness metric need causal support?", "Is simulation enough for a counterfactual claim?", "Which pattern handles causal benchmark parity?", "When should causal language be downgraded to association, measurement, temporal, QL, or local prose?" | Builds on: A.10, B.3, C.11, C.19, C.24, C.26, C.27, D.5, G.5, G.9. Coordinates with: A.2.4, A.3.2, A.6, A.15, C.16, G.11. |
| C.29 | Mathematical Lens Use | Stable | Keywords: mathematical lens, structure-preserving representation, lens mapping mode, preserved structure, lost structure, invariants, stop condition, scale window, coarse-graining, rival lens, LensUseAdmissibilityValue, validation boundary, learned lens, ontology smuggling. Queries: "When does a mathematical analogy become an admissible FPF lens?", "What structure is preserved by this lens?", "Where must this math transfer stop?", "How do I use mathematical structure without importing ontology?" | Builds on: A.1.1, A.6.P, A.3.3, A.19, A.10, A.15, B.3, C.16, E.17.EFP, E.17.ID.CR, A.6.3.RT, A.6.3.CSC, F.9. Constrained by: E.8, E.10, C.2.P, E.19. Decision basis: E.9 and C.29:13a. Coordinates with: C.11, A.15.1, A.15.4, C.18.1, C.19.1, C.26, C.27, C.28, G.5, G.9, G.2, G.10. |
| C.30 | Grounded Architecture and Selected-Structure Adequacy | Stable | Keywords: grounded architecture, ArchitectureOf@Context, selected structure, architecture claim, architecture question card, candidate architecture use, architecture-description boundary, artifact-as-architecture guard. Queries: "How do I recover a grounded architecture claim?", "Which selected structure changes the architecture move?", "When does candidate synthesis go to C.32 rather than C.30?" | Builds on: A.22, C.2.1, A.6.3, A.7, E.17.0, E.17, E.10.D2, F.18. Coordinates with: C.30.AD, C.30.ASV, A.6.F, C.30.TFS-REL, C.30.LCA, C.30.ILC, C.32, C.32.MLAO, C.32.CONWAY, C.32.PAD, C.32.ADR, C.32.ADA, C.29, C.16, C.25, C.28, A.19.CPM, A.19.SelectorMechanism, C.18, C.19, G.5, C.11, A.10, B.3, A.20, A.21, A.15. |
| C.30.AD | Architecture Description Adequacy | Stable | Keywords: architecture description, ArchitectureDescription@Context, architecture description use card, architecture structural view, viewpoint, correspondence, source return, specification-use boundary, candidate-description boundary. Queries: "When is an architecture description the EntityOfConcern under repair?", "How do I keep views, viewpoints, selected structures, and publication boundaries distinct?", "Where do described candidate palettes and residual frames go?" | Builds on: C.30, C.30.ASV, A.22, A.7, A.6.3, E.17.0, E.17.1, E.17.2, E.17, C.2.P, E.10, E.10.ARCH. Coordinates with: C.30.P, C.30.TFS-REL, C.30.LCA, C.30.ILC, C.32, C.32.MLAO, A.19.CPM, A.19.SelectorMechanism, C.18, C.19, G.5, C.11, A.6.F, A.6.M, C.29, C.16, C.16.P, A.10, B.3, A.20, A.21, A.15, C.28, E.8, F.18. |
| C.30.AD.BA | Built-Asset Architecture Description and Reference Designation | Stable | Built-asset architecture-description use for BIM, IFC, asset registers, digital-twin views, handover tables, and ISO/IEC 81346-style reference designations without turning descriptions into assets, evidence, gates, work, or decisions. | Builds on: C.30, C.30.AD, C.30.ASV, A.22, E.17. Coordinates with: A.6.F, A.6.M, C.30.TFS-REL, C.30.LCA, C.30.ILC, A.10, B.3, A.20, A.21, C.11, C.28. |
| C.30.P | Architecture and Structure Precision Restoration | Stable | Repairs architecture or structure wording whose EntityOfConcern or claim kind is hidden before A.22, C.30, C.30.AD, C.30.ASV, a selected C.30.* pattern, C.32-family synthesis work, or another governing pattern is applied. | Builds on: E.10, E.10.ARCH, A.22, C.30, C.30.AD, C.30.ASV, C.2.P, A.6.P, A.6.F, C.29, C.16.P, C.16, C.25, E.17, E.8. Coordinates with: C.30.TFS-REL, C.30.LCA, C.30.ILC, C.32, C.32.MLAO, C.32.CONWAY, C.32.FAIL, A.19.CPM, A.19.SelectorMechanism, C.18, C.19, G.5, A.10, B.3, A.20, A.21, C.11, C.28, A.15, E.11. |
| C.30.STRAT | Stratification Wording Precision Restoration | Stable | Repairs source-label uses such as layer, level, tier, stack, ladder, rung, block, expert, cache, router, and gate by recovering selected ontological neighborhood, primary EntityOfConcern kind, governing pattern, admissible use, and remaining reader use before FPF-governed use. | Builds on: E.10, E.10.ARCH, E.8, F.18, C.30.P, A.22, C.30. Coordinates with: C.30.ASV, C.30.LCA, C.30.TFS-REL, C.30.ILC, A.6.M, A.6.F, E.18, C.16.P, C.16, A.19.SPR, C.2.P, E.17, C.29, C.28, A.10, G.6, B.3, A.20, A.21, A.15, A.2, G.5, C.11, E.11, I.2. |
| C.30.ASV | Architecture Structural View Adequacy (ASV) | Stable | Keywords: architecture structural view, ArchitectureStructureKindRef, VF.ARCH.STRUCTURE, viewpoint bundle, structure kind, hidden or lost structure, correspondence, source return. Queries: "Which structure kind does this architecture view describe?", "How do viewpoint and structure kind stay distinct?", "When does a view hide or lose structure?" | Builds on: C.30, A.22, A.6.3, E.17.0, E.17.1, E.17.2, E.17, E.10.D2. Coordinates with: A.6.F, C.30.TFS-REL, C.30.LCA, C.30.ILC, E.18, C.29. |
| C.30.LCA | Control Structure View Adequacy (LCA) | Stable | Keywords: control-structure view, layered control architecture, supervisor loop, controller and plant, rate band, control layer, proof overread. Queries: "When is LCA a control-structure view rather than proof?", "How do layer, level, stack, and rate labels recover fields named by value?", "Where do stability, safety, evidence, and gate claims go?" | Builds on: C.30, C.30.ASV, B.2.5, A.22. Coordinates with: A.3.3, C.27, C.28, A.10, G.6, B.3, A.20, A.21, C.29. |
| C.30.ILC | Cross-Scope Architecture Residual Triage | Stable | Keywords: cross-scope residual, interlevel conflict, frustration, declared scope, structure kind, local repair, residual-bearing locus, first architecture move. Queries: "What is the first architecture move when a local fix creates a residual elsewhere?", "When does residual-reducing synthesis go to C.32.MLAO and C.32?", "When should the case exit to measurement, scale, evidence, decision, or selected-set publication?" | Builds on: C.30, C.30.ASV, A.22. Coordinates with: C.32.MLAO, C.32, C.32.PAD, C.31.ASAP, C.16, C.29, G.5, C.11, C.28, A.10, B.3, G.6, D.3, D.4. |
| C.30.TFS-REL | Architecture Transformation-Flow Structure Relation | Stable | Keywords: architecture-to-transformation-flow relation, transformation-flow structure, functional behavior, selected structure, architecture structural view, candidate architecture input. Queries: "When can a transformation-flow structure inform a grounded architecture or structural view?", "How do architecture, function, and transformation flow stay distinct?", "When do transformation-flow variants become C.32 candidate inputs?" | Builds on: C.30, C.30.ASV, E.18, A.22. Coordinates with: C.32, A.6.F, E.18.2, C.29, C.16, C.28, A.10, B.3, A.20, A.21, A.15. |
| C.31 | Modularity and Reusable Structure Characteristics | Stable | Keywords: modularity characteristics, reusable-structure characteristics, coupling, cohesion, substitutability, interface variation, evidence reuse, bespoke residue, ModularityVectorLite. Queries: "Which modularity characteristic is under evaluation?", "When is a modularity score report-only?", "How do I keep module, interface, reuse, and evidence-reuse claims distinct?" | Builds on: C.16, A.17, A.18, A.19, C.25, C.30, C.30.ASV. Coordinates with: A.6.M, C.31.RSA, C.31.ASAP, C.32, C.29, A.10, B.3, G.5, C.11. |
| C.31.RSA | Reusable Structure Accounting | Stable | Keywords: reusable-structure accounting, reusable share, bespoke residue, accounting basis, report-only share, source return, refactoring opportunity. Queries: "Where is reusable structure located?", "When is a reusable share only report-only?", "What gets worse when we increase reuse?" | Builds on: C.31, C.30, C.30.ASV, C.16, A.19. Coordinates with: A.6.M, C.31.ASAP, C.29, A.10, B.3, G.6, C.27, C.28, G.5, C.11. |
| C.31.ASAP | Architecture Scale-Amenability Preference | Stable | Keywords: architecture scale preference, scale amenability, ScaleClaimTriage, scale variable, scale window, architecture alternatives, source-return condition, coarse-graining, RG, platform scale claim, waiver reason. Queries: "When does modularity or platform wording carry an architecture scale-preference claim?", "How can scale preference inform C.32 candidate generation without selecting the architecture?", "When is coarse-graining or RG-like language only a mathematical lens?" | Builds on: C.31, C.31.RSA, C.16, A.17, A.18, A.19, C.18.1, C.19.1, C.29. Coordinates with: C.32, C.32.PAD, A.6.M, C.30, C.30.ASV, C.30.LCA, C.30.ILC, A.10, B.3, G.6, G.5, G.9, C.11. |
| C.32 | Architecture Candidate Synthesis | Stable | Keywords: architecture candidate synthesis, CandidateArchitecturePalette@Project, selected structures, architecture characteristics, synthesis structure map, candidate configurations, trade-off front, retained alternatives. Queries: "How do I synthesize candidate architecture configurations before comparison?", "Which selected structures and architecture characteristics change?", "When does C.32 stop before comparison, selected-set publication, local choice, or project architecture decision?" | Builds on: C.30, A.22, A.6.F, A.6.M, C.16, C.25, C.31, C.30.ILC. Coordinates with: C.32.P2S, C.32.HCS, C.32.ACS, C.32.ACE, C.32.CONWAY, C.32.MLAO, C.32.FAIL, C.32.PAD, A.19.CPM, A.19.SelectorMechanism, C.18, C.19, G.5, C.11, A.10, B.3. |
| C.32.P2S | Problem-to-Structure Architecturing Unfolding | Stable | Keywords: problem-to-structure architecturing unfolding, ProblemToStructureArchitecturingFlowCard@Project, ArchitectureUnfoldingStructureUse@Project, structural uncertainty, candidate structures, selected structures, expected structures, actual-structure feedback, governing-pattern-specific return. Queries: "How do I carry architecture pressure from problem to realized selected structures?", "When does architecturing stop at C.30, C.32, C.32.PAD, C.32.ADR, A.15, C.16, C.29, E.23, G.11, or E.18?", "How do descriptions, decisions, work, evals, and feedback stay with their governing patterns?" | Builds on: C.22.2, C.30, C.30.AD, C.30.ASV, C.32, C.32.HCS, C.32.ACS, C.32.ACE, C.33, C.34, C.35, C.25, C.31, C.29, E.17, E.24.PUB. Coordinates with: A.22.CGUS, E.18.3, A.19.CPM, A.19.SelectorMechanism, C.18, C.19, G.5, C.11, C.32.PAD, C.32.ADR, C.32.ADA, A.15, A.15.1, A.15.2, A.15.5, C.16, E.23, G.11, E.18, C.32.CONWAY, C.32.FAIL. |
| C.32.HCS | Architecture-Bearing Family Characteristic Starter Packs | Stable | Keywords: architecture-bearing family characteristic starter pack, architecture characteristic heads, source catalogue narrowing, first criteria questions, characteristic transfer. Queries: "Which few architecture-characteristic heads should we inspect first?", "How do software-quality catalogues transfer to systems, methods, roles, cultures, AI workflows, or evidence practices without admitting those source labels as holon kinds?", "When does starter work hand off to ACS?" | Builds on: C.32, C.25, C.16, E.13. Coordinates with: C.32.ACS, C.32.ACE, C.30, C.31, A.19, G.5, C.11, C.32.PAD. |
| C.32.ACS | Architecture Characteristic Criteria Set for Improvement Cycles | Stable | Keywords: architecture characteristic criteria set, criteria row, Q-Bundle, improvement cycle, proxy risk, protected counter-characteristic, anti-Goodhart guard. Queries: "How do I turn broad -ility names into project criteria rows?", "Which three to five characteristics enter optimization and which remain guardrails?", "How does the criteria set feed eval and candidate synthesis?" | Builds on: C.32.HCS, C.25, C.16, E.13. Coordinates with: C.32, C.32.ACE, C.32.PAD, E.22, E.23, A.19.CPM, G.5, C.11, A.10, B.3. |
| C.32.ACE | Architecture Characteristic Eval Programs | Stable | Keywords: architecture-characteristic eval program, eval result, measurement boundary, parity frame, missing-data policy, proxy risk, comparison input. Queries: "How do I evaluate architecture candidates against criteria rows?", "Why is eval not the characteristic itself?", "When does an eval result feed comparison, publication, or decision without replacing them?" | Builds on: C.32.ACS, C.16, C.25, E.13. Coordinates with: C.32, C.32.MLAO, C.32.PAD, A.19.CPM, G.5, C.11, A.10, B.3. |
| C.32.CONWAY | Transformer and Transformed Architecture Correspondence | Stable | Keywords: Conway correspondence, inverse Conway maneuver, transformer holon, transformed holon, changing relation, selected-structure correspondence, coordination cost. Queries: "When must the architecture of the transforming holon and transformed holon be synthesized together?", "Which selected structures correspond across the changing relation?", "When is mirroring only a source cue rather than architecture adequacy?" | Builds on: C.32, A.3.4, E.18, A.15, C.29. Coordinates with: C.32.MLAO, C.32.FAIL, C.32.PAD, A.19.CPM, G.5, C.11, A.10, B.3. |
| C.32.MLAO | Multilevel Architecture Residual Optimization | Stable | Keywords: multilevel architecture residual optimization, residual-reducing candidate frame, declared level, declared scope, Pareto front, stepping stone, ideality pressure, scale amenability. Queries: "How do I prepare candidate architecture changes after cross-scope residual triage?", "How do residuals, fronts, archives, and stepping stones inform synthesis without deciding?", "When does the case return to C.30.ILC, C.29, C.31.ASAP, C.32, G.5, C.11, or C.32.PAD?" | Builds on: C.30.ILC, C.32, C.32.ACS, C.32.ACE, C.29, C.31.ASAP. Coordinates with: C.32.CONWAY, C.32.FAIL, C.32.PAD, C.18, C.19, G.5, C.11, A.10, B.3. |
| C.32.FAIL | Architecture Failure Recognition and Repair | Stable | Keywords: architecture failure cue, architecture repair cue, stressed architecture object, selected-structure relation, candidate repair, repair-entry family, source overread. Queries: "How do I turn an architecture warning into the smallest repair action?", "Which governing pattern owns the repair?", "When should evidence, assurance, comparison, selection, publication, choice, or decision claims leave the repair cue?" | Builds on: C.32, C.30.P, A.6.F, A.6.M, C.31, C.29, E.10. Coordinates with: C.32.MLAO, C.32.CONWAY, C.32.PAD, C.30, A.19.CPM, A.19.SelectorMechanism, C.18, C.19, G.5, C.11, E.17, E.24.PUB, A.10, B.3, A.20, A.21. |
| C.32.PAD | Project Architecture Decision After Candidate Synthesis | Stable | Keywords: project architecture decision, ArchitectureDecisionRelation@Project, selected architecture option, affected selected structure, architecture-characteristic trade-off, accepted loss, method-use instruction, architect-developer split, reopen condition. Queries: "How do I turn candidate architecture configurations into a project decision?", "Which selected structures and accepted losses does the architecture decision commit?", "How does an architecture decision guide developer methods without becoming an ADR or work plan?" | Builds on: C.32, C.32.MLAO, C.32.CONWAY, C.32.FAIL, A.19.CPM, A.19.SelectorMechanism, C.11, G.5, C.30, C.30.AD, C.30.ASV. Coordinates with: C.32.ADR, C.32.ADA, C.32.ACS, C.32.ACE, C.16, C.25, C.29, A.15, E.8, E.11.PUR, E.17, E.24.PUB, A.10, B.3, A.21, B.2, B.2.P. |
| C.32.ADR | Architecture Decision Record Projection | Stable | Keywords: architecture decision record, ADR projection, ArchitectureDecisionDescription@Project, ArchitectureDecisionRecordProjection@Project, section function, rationale, consequences, method-use instruction, supersession, publication boundary. Queries: "How do I write an ADR-like record from an architecture decision relation?", "Which ADR sections are required by the decision use?", "When is an ADR only a publication projection rather than the decision?" | Builds on: C.32.PAD, C.30.AD, C.30.ASV, E.17, E.24.PUB, A.15, E.8, E.11.PUR. Coordinates with: C.32.ADA, A.10, B.3, A.21, C.16, C.25, C.29. |
| C.32.ADA | Architecture Decision Adequacy Scales | Stable | Keywords: architecture decision adequacy, ArchitectureDecisionAdequacyEvaluation@Project, declared use, complete coordinate set, E.21 labels, method docking, publication projection, no average, repair target. Queries: "How do I evaluate whether an architecture decision is adequate for a declared use?", "Which weak coordinate should be repaired before developer work?", "Why does an ADR score not approve an architecture decision?" | Builds on: C.32.PAD, C.32.ADR, E.21, E.22. Coordinates with: C.32, C.32.ACS, C.32.ACE, C.30.AD, A.15, C.16, C.25, C.29, E.13, E.17, E.24.PUB, A.10, B.3, A.21. |
| C.33 | Structural Information Adequacy for Architecture Capture and Missing-Structure Return | Stable | Keywords: structural information adequacy, captured selected structure, missing structure, lost structure, missing-structure return, carrier, observer boundary, selected structure. Queries: "What selected structure can I safely take from this carrier?", "What structure did the view, ADR, graph, report, or observation lose?", "When must architecture work return to a receiving governing pattern because selected structure is missing?" | Builds on: A.22, C.30, C.30.AD, C.30.ASV, C.32.P2S, C.32. Coordinates with: C.29, C.16, C.25, C.32.ACE, C.30.STRAT, C.30.TFS-REL, A.6.M, C.31, C.31.ASAP, C.32.PAD, C.32.ADR, G.5, C.18, C.19, E.18, F.9, F.15. |
| C.34 | Structural Correspondence, Equivalence, and Morphism Adequacy | Stable | Keywords: structural correspondence, equivalence, morphism, mapping mode, preserved structure, lost structure, directionality, scope. Queries: "When are two structure-bearing objects same enough for architecture work?", "Which selected structure is preserved and what is lost?", "When is a graph match or morphism only a lens?" | Builds on: A.22, C.30, C.30.ASV, C.30.AD, C.29, F.9. Coordinates with: C.16, C.25, C.32.ACE, C.32, C.32.PAD, C.32.ADR, C.30.TFS-REL, C.30.STRAT, A.6.M, C.31, C.31.ASAP, E.18, F.15. |
| C.35 | Structural Synthesis and Discovery Adequacy | Stable | Keywords: structural synthesis, structural discovery, generated carrier, produced carrier, described structure, candidate admission, source return, DSM, NAS, LLM. Queries: "Can a generated architecture output seed synthesis?", "When is a DSM cluster, NAS graph, LLM diagram, or model transformation ready for C.32?", "What must be recovered before treating a discovered structure as architecture material?" | Builds on: C.30, C.30.AD, C.30.ASV, A.22, C.32.P2S, C.32. Coordinates with: C.33, C.34, C.29, C.30.STRAT, C.30.TFS-REL, A.6.M, C.31, C.31.ASAP, C.32.ACS, C.32.ACE, C.16, C.25, G.5, C.18, C.19, E.18, C.32.PAD, C.32.ADR. |
| C.36 | Cultural Evolution and Cultural-Evolution Engineering | Stable | Cultural-evolution and cultural-evolution-engineering case use: collective holons, roles, work and method families, canon or memory epistemes, recognition and selection regimes, mediation systems, variant sets, term bridges, intervention, measurement, and refresh relations without minting root culture, style, or tradition kinds. | Builds on: A.1, A.2.1, A.3.1, A.15, C.18, C.19, C.20, C.23, E.18.1, F.9, F.17, F.18, G.5, G.11. Coordinates with: C.36.P, E.10, E.10.ARCH, C.30, C.16, C.11, A.10, B.3. |
| C.36.P | Cultural-Evolution Wording-Use Precision Restoration | Stable | Recovers the FPF object hidden by culture, style, tradition, genre, scene, practice, technique, platform, regime, attractor, or developmental-machinery wording; returns subject work to C.36 or the direct governing pattern. | Builds on: E.10, E.10.ARCH, C.36, F.17, F.18, F.9. Coordinates with: A.3.1, A.3.2, A.15, C.18, C.19, G.5, G.11. |
| Part D – Multi-scale Ethics & Conflict-Optimisation |
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| D.1 | Ethical Value Plurality and FPF Boundary | Stable | Makes value concerns, affected EntityOfConcern, evidence, currentness, and admissible use explicit when an FPF claim, method, work plan, architecture move, policy, recommendation, model, or system change has ethical force. | Builds on: E.2, A.1, A.7. Coordinates with: D.2, D.3, D.4, D.5, A.10, B.3, C.11. |
| D.2 | Multilevel Ethics For System-Holon Work | Stable | Entry pattern for ethical questions where a system, holon, method, work, policy, recommendation, or architecture move may improve one declared level or scope while harming another. | Builds on: D.1, A.1, B.1, C.30.ILC. Coordinates with: D.3, D.4, D.5, A.15, A.3.4, C.16. |
| D.3 | Interlevel Ethical Conflict Structure | Stable | Maps affected holons and systems, declared levels or scopes, interests, role holders, agency or responsibility thresholds, methods, work, transformations, evidence, uncertainty, value theories, and consequence horizons. | Builds on: D.1, D.2, A.1, A.14, C.13. Coordinates with: D.4, C.2.1, E.17, C.30.ILC, C.16, A.10, B.3. |
| D.4 | Ethical Mediation and Decision Use | Stable | Governs how an interlevel ethical conflict structure is used in mediation, refusal, decision, evidence demand, causal return, assurance return, or architecture return. | Builds on: D.3, C.11. Coordinates with: D.5, A.10, B.3, C.28, C.30.ILC, A.20, A.21. |
| D.5 | Bias Audit and Ethical Assurance | Stable | Bias, fairness, human or group impact audit, causal-fairness audit consumption, and ethical assurance boundary that complements multilevel ethics without replacing D.1-D.4. | Builds on: D.1, D.4, E.5.4. Coordinates with: A.10, B.3, C.16, C.28, E.13. |
Part E – The FPF Constitution and Authoring Guides
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| Cluster E.I — The FPF Constitution | ||||
| E.1 | Vision & Mission | Stable | Keywords: vision, mission, operating system for thought, purpose, scope, goals, non-goals. Queries: "What is FPF?", "What is the purpose of the First Principles Framework?", "What problem does FPF solve?". | Prerequisite for: All other patterns, especially E.2. |
| E.2 | The Eleven Pillars | Stable | Keywords: principles, constitution, pillars, invariants, core values, rules, P-1 to P-11. Queries: "What are the core principles of FPF?", "What are the eleven pillars?". | Builds on: E.1. Prerequisite for: E.3 and all normative patterns. |
| E.2.DA | FPF Pillar-Adequacy Evaluation CharacteristicSpace | Stable | FPF-level object-under-improvement evaluation derived from the E.2 Pillars for FPF as a whole, a corpus slice, release candidate, pattern family, projection set, or host set, including content-loss and excess-apparatus regressions. | Builds on: E.2, A.19.ECS. Coordinates with: E.21, E.9.DA, E.22, E.23, E.11, E.10, F.18, F.19. |
| E.3 | Principle Taxonomy & Precedence Model | Stable | Keywords: taxonomy, precedence, conflict resolution, hierarchy, principles, classification, Gov, Arch, Epist, Prag, Did. Queries: "How does FPF resolve conflicting principles?", "What is the hierarchy of FPF rules?". | Builds on: E.2. Constrains: All patterns and DRRs. |
| E.4 | FPF Ecosystem Family Architecture | Stable | FPF-grounded pattern ecosystem family architecture; separates the FPF edition, domain principle frameworks, local practice frameworks, source packs, relation records, decisions, publication/access carriers, quality and refresh owners, while treating principle frameworks as reader-facing renderings of selected problem-solution architecture. | Builds on: E.1, E.2/P-5, E.5.3. Coordinates with: E.4.FPF, E.4.PFAD, E.4.DPF, E.4.DPF.DA, E.4.PFR, E.11, E.17, G.2, G.5, G.11, C.33, C.34, C.35, F.18, E.21, E.23, E.19. |
| E.4.FPF | First Principles Framework Form and Publication-or-Access Carrier Assembly | Stable | Treats FPF itself as one first-principles framework edition with selected Core pattern set, publication/access carriers, relation and edition records, quality route through E.2.DA, currentness route, and blocked overreads. | Builds on: E.4, E.2.DA, E.11, E.17, E.21. Coordinates with: E.4.PFAD, E.4.PFR, E.4.DPF, E.4.DPF.DA, G.11, F.18. |
| E.4.PFAD | Principle-Framework Architecture Decision | Stable | Framework-local architecture decision relation for a domain or local principle framework: selected pattern set, relation structure, publication unit, dependency boundary, source basis, quality route, and refresh or supersession. | Builds on: E.4, E.9, C.32.PAD. Coordinates with: C.32.ADR, E.17, E.4.PFR, F.18, G.2, G.11, E.21, E.19. |
| E.4.DPF | Domain Principle Framework Authoring and Publication-or-Access Carrier Assembly | Stable | Evolutionary authoring spine for DPF and local-practice frameworks. Distinguishes pre-PFAD proposal, binding PFAD, post-existence architecture-description use, and post-PFAD dependency description; then carries sources, E.8 patterns, PFR relations, reader carriers, evaluation, improvement, and currentness without reverse Core dependency. | Builds on: E.4, G.2, E.8, E.10, F.18. Coordinates with: E.4.PFAD, E.4.PFR, E.4.DPF.DA, E.11, E.17, E.21, E.22, E.23, G.11, C.33-C.35. |
| E.4.DPF.DA | Domain Principle Framework Package-Adequacy Evaluation CharacteristicSpace | Stable | DPF-specific package evaluation characteristic space for one declared domain or local use, covering domain scope, source basis, Core dependency, package form, pattern-set coverage, relation records, publication/access carriers, refresh, and adoption utility. | Builds on: E.4.DPF, E.4.PFAD, E.4.PFR, E.21, E.2.DA, E.22, E.23, A.19.ECS. Coordinates with: G.2, G.11, E.11, E.17, C.33, C.34, C.35. |
| E.4.PFR | Pattern-Framework Relation and Edition Discipline | Stable | Relation and edition records for FPF-grounded pattern frameworks: relation functions, dependency direction, compatibility boundaries, publication, source/decision reuse, produced-carrier admission, deprecation, supersession, and refresh. | Builds on: E.5.3, E.4. Coordinates with: E.4.PFAD, E.11.PUR, E.11, E.17, G.5, F.18, G.11, E.21, E.22, E.23, C.33, C.34, C.35, G.2, E.9, A.10. |
| E.5 | Four Guard-Rails of FPF | Stable | Keywords: guardrails, constraints, architecture, rules, safety, GR-1 to GR-4. Queries: "What are the main architectural constraints in FPF?". | Builds on: E.2, E.3. Prerequisite for: E.5.1, E.5.2, E.5.3, E.5.4. |
| E.5.1 | DevOps Lexical Firewall | Stable | Keywords: lexical firewall, jargon, tool-agnostic, conceptual purity, DevOps, CI/CD, yaml. Queries: "Can I use terms like 'CI/CD' in FPF core patterns?". | Refines: E.5. Constrains: All Core patterns. |
| E.5.2 | Notational Independence | Stable | Keywords: notation, syntax, semantics, tool-agnostic, diagram, UML, BPMN. Queries: "Does FPF require a specific diagram style?", "How is meaning defined in FPF?". | Refines: E.5. Constrains: All Core patterns. |
| E.5.3 | Unidirectional Dependency | Stable | Keywords: dependency, layers, architecture, modularity, acyclic, Core, Tooling, Pedagogy. Queries: "What are the dependency rules between FPF ecosystem families?". | Refines: E.5. Constrains: E.4. |
| E.5.4 | Cross-Disciplinary Bias Audit | Stable | Keywords: bias, audit, ethics, fairness, trans-disciplinary, neutrality, review. Queries: "How does FPF handle bias?", "Is there an ethics review process in FPF?". | Refines: E.5. Constrains: All Core patterns. Links to: Part D. |
| Cluster E.II — The Author’s Handbook | ||||
| E.6 | Didactic Architecture of the Spec | Stable | Keywords: didactic, pedagogy, structure, narrative flow, on-ramp, learning. Queries: "How is the FPF specification structured for learning?", "What is the 'On-Ramp first' principle?". | Builds on: E.2 (P-2 Didactic Primacy). |
| E.7 | Archetypal Grounding Principle | Stable | Keywords: grounding, examples, archetypes, U.System, U.Episteme, Tell-Show-Show. Queries: "How are FPF patterns explained?", "What are the standard examples in FPF?". | Builds on: E.6. Constrains: All architectural patterns. |
| E.8 | FPF Authoring Conventions & Style Guide | Stable | Pattern body as user-facing pattern body; recognition text and assurance text; working-reader boundary; positive subject/action spine; precision-restoration profile and phrase-apparatus cleanup; evaluation-characteristic-space pattern publication form is delegated to E.8.ECSPF. | E.6, E.7, E.8.ECSPF, E.9, E.10, E.19, E.21, F.18, F.19 |
| E.8.ECSPF | Evaluation CharacteristicSpace FPF Pattern Publication Form | Stable | Authoring form for publishing an accepted evaluation CharacteristicSpace as an FPF pattern while preserving working-reader recognition, value meanings, non-use boundaries, neighbour relations, governing-pattern references, and phrase-apparatus discipline. | Builds on: E.8, A.19.ECS. Coordinates with: E.21, E.9.DA, E.2.DA, E.22, E.23, F.18, F.19, C.25. |
| E.9 | Design-Rationale Record (DRR) Method | Stable | DRR as one bounded decision and rationale record: exact basis, selected answer, source and decision carry-through, positive content distribution to patterns and selected non-pattern FPF kind-reference pairs, kind-or-boilerplate diagnostic for draft wording, and decision-adequacy evaluations through E.9.DA. | E.2, E.8, E.9.DA, E.10, E.19, E.22, F.19 |
| E.9.DA | DRR Decision-Adequacy Evaluation CharacteristicSpace | Stable | Evaluates whether one DRR is decisive enough for its declared FPF authoring use: selected answer, source carry-through, selected-locus distribution, rejected alternatives, first drafting action, and phrase-apparatus or boilerplate debt before pattern drafting. | Builds on: E.9, A.19.ECS. Coordinates with: E.8, E.10, E.19, E.21, E.22, E.23, F.19. |
| E.10 | Unified Lexical Rules for FPF | Stable | Word, head, and use precision; register discipline; term formation; ontology guards; precision-restoration trigger registry; and closure rule: local wording accepted, rewritten to kind or relation named by value, or sent to the selected restoration or governing pattern. | Builds on: A.7, E.5, F.5, F.18. Coordinates with: E.10.ARCH, E.10.MOVE, A.6.P, C.2.P, A.19.SPR, E.24.CD, E.24.PUB, F.19. |
| E.10.MOVE | Move and Readiness Wording Precision Restoration | Stable | Restores the governed value hidden by move, movement, step, action, and readiness wording. Keeps mantra move only for one A.22.CGUS demonstrated row, restores evaluation-result change to an E.23 prediction, and sends recommendation, transformation, readiness, gate, publication, and Work claims to their direct patterns. | Builds on: E.10, E.10.ARCH, A.3.4.P, A.22.CGUS, E.11.PUR, E.23, A.15.5. Coordinates with: E.18.1, A.15, A.21, C.24, C.30, F.17, G.11. |
| E.10.ARCH | Wording-Use Ontological Precision Restoration Architecture | Stable | Distributes wording-use precision restoration: E.10 catches overloaded wording, E.10.ARCH selects the applicability row, selected restoration or governing patterns recover ontology, F.19 handles phrase-level apparatus after kind recovery, and subject patterns keep thin local cues plus declarative relations. | Builds on: E.10, A.6.P, A.6.F, C.2.P, A.6.3.CSC, F.18, F.19, E.8, E.19, E.2. Coordinates with: C.30.P, C.16.P, C.16.Q, A.22, C.30, C.30.ASV, C.16, A.19, C.25, C.27, C.29, E.21, E.11, I.2. |
| E.10.P | Conceptual Prefixes (policy & registry) | Stable | Keywords: prefixes, U., Γ_, ut:, tv:, namespace, registry. Queries: "What do the prefixes like 'U.' mean in FPF?". | Depends on: E.9. Constrains: E.5.1, E.5.2. |
| E.10.D1 | Lexical Discipline for “Context” (D.CTX) | Stable | Keywords: context, U.BoundedContext, anchor, domain, frame. Queries: "What is the formal meaning of 'Context' in FPF?". | Builds on: A.7, A.4. Coordinates with: F.1, F.2, F.3, F.7, F.9. |
| E.10.D2 | EntityOfConcern, Description Episteme, and Specification-Use Discipline | Stable | Keywords: EntityOfConcern, Description episteme, specification use, DescriptionContext, testable, verifiable. Queries: "Difference between a description and a specification in FPF?". | Builds on: A.7, E.10.D1, C.2.1, C.2.3. Constrains: F.4, F.5, F.8, F.9, F.15. |
| E.11 | Practical-Use Guidance and Pattern Discovery | Stable | Fifteen context-free public practical-use cards with recognizable situations, current questions, exact first-result templates, direct Solution refs, stop and return boundaries, and one ordinary or CGUS-demonstrative walkthrough. Ordinary comparison stays conversational; addressable shortlist history appears only under named reliance. | Builds on: E.8, E.17.AUD, F.17, F.18. Leads to: E.11.PUA and E.11.PUR. Coordinates with: A.22.CGUS, E.18, G.11. |
| E.11.PUA | Pattern Use in a Working Situation and First Useful Result | Stable | Applies one inspected direct pattern to a current working situation. Keeps ordinary use light, materializes support only under named reliance, returns the exact direct-pattern result and receiving use, and distinguishes selection, application, and downstream-work flows. | Builds on: E.11, E.8. Coordinates with: E.11.PUR, E.18, E.18.1, E.18.3, A.15, and every selected direct pattern. |
| E.11.PUR | Pattern-Use Applicability, Recommendation, and Coordination | Stable | Governs reliance-bearing applicability findings, one pattern-use recommendation, and coordination among candidate pattern uses. Pairwise order exists only for prerequisite result, method precondition, or shared-constraint resolution; presentation order is not workflow or WorkPlan order. | Builds on: E.11, E.11.PUA, E.10.MOVE. Coordinates with: E.18.1, A.15, A.21, C.24, C.30, and direct decision patterns. |
| E.12 | Didactic Primacy & Cognitive Ergonomics | Stable | Keywords: didactic, cognitive load, ergonomics, usability, Rationale Mandate, HF-Loop. Queries: "How does FPF ensure it's understandable?", "What is the 'So What?' test in FPF?". | Builds on: E.2 (P-2). Complements: E.13. |
| E.13 | Pragmatic Utility and Value Alignment | Stable | Keywords: pragmatic utility, proxy-to-value alignment, Goodhart, Campbell, surrogation, minimally viable value slice. Queries: "How does FPF keep measures from replacing value?", "What got worse when the score improved?". | Builds on: E.2 (P-7). Complements: E.12 and E.14; coordinates with E.8, E.19, E.21, E.22, E.23, E.9.DA, and E.2.DA. |
| E.14 | Human-Centric Working-Model | Stable | Keywords: working model, human-centric, publication surface, grounding, assurance layers. Queries: "What is the main interface for FPF users?", "How does FPF separate human-readable models from formal assurance?". | Builds on: E.7, E.8, C.2.3. Coordinates with: B.3.5, C.13, E.10. |
| E.15 | Lexical Authoring & Evolution Protocol (LEX-AUTH) | Stable | Keywords: lexical authoring, evolution protocol, LAT, delta-classes. Queries: "How are FPF patterns authored and evolved?", "What is a Lexical Authoring Trace (LAT)?". | Builds on: E.9, E.10, B.4, C.18, C.19, A.10, B.3, F.15. |
| E.16 | RoC‑Autonomy Budget & Enforcement | Stable | Keywords: autonomy budget, guarded enactment, autonomy ledger, override speech act, scout/probe/commit checkpoint. Queries: "How does FPF make autonomy enforceable and auditable?", "How do bounded specialization budgets stay separate from committed rollout?" | Builds on: A.13, A.15, A.21, B.3. Coordinates with: C.24, G.4, G.5, G.9. |
| E.17.0 | U.MultiViewDescribing - Viewpoints, Views & Correspondences | Stable | Multi-view describing for families of Description epistemes and specification-use Description epistemes indexed by EntityOfConcernClass, EntityOfConcernRef, bounded context, and viewpoint; keeps viewpoint, episteme-lane view, publication face/form, and carrier distinct. | Builds on: C.2.1, A.6.2, A.6.3, A.6.4, A.7, E.10.D1, E.10.D2. Used by: E.17, E.17.1, E.17.2, E.18, domain-specific description schemes. |
| E.17.1 | U.ViewpointBundleLibrary — Reusable Viewpoint Bundles | Stable | Keywords: viewpoint bundle, reusable viewpoint family, import discipline, alias discipline, governance, engineering/management/research bundles. Queries: "How do I define reusable viewpoint bundles in FPF?", "What is a ViewpointBundleLibrary?" | Builds on: E.17.0, A.6.2-A.6.4, A.7, E.7, E.10. Used by: E.17.2, E.18, domain-specific viewpoint-bundle libraries. |
| E.17.2 | TEVB - Typical Engineering Viewpoints Bundle | Stable | Archetypal engineering viewpoint bundle for holons, with Functional, Procedural, Role-Enactor or Device-Structure, and Module-Interface viewpoints over an EntityOfConcernClass = U.Holon; architecture-specific viewpoint bundles import TEVB rather than mutating it. | Builds on: E.17.0, E.17.1, C.2.1, A.1, A.6.2-A.6.4, A.7, E.10.D2. Used by: E.18, E.17, engineering Description-episteme and specification-use patterns, ISO-aligned architecture-description bundles. |
| E.17 | Multi‑View Publication Kit | Stable | Publication discipline for generic publication faces and governed MVPK faces; U.View, publication form, carrier and front-end, source pins, admissible publication use, and no face becoming evidence, gate, decision, or work by presentation. | E.17.0, E.17.1, E.17.2, A.7, E.10, C.2.P; coordinates with E.17.EFP, E.17.ID.CR, E.17.AUD |
| E.17.EFP | ExplanationFaithfulnessProfile — explanation-use discipline over existing MVPK faces | Stable | Explanation-facing rendering classes; source-pinned rendering, source-linked reconstruction, didactic retelling, speculative retelling; admissible explanation use and boundary to evidence, gate, work, and source return. | E.17, A.7, A.6.B, F.9, F.18; coordinates with A.10, A.15, A.15.4, A.6.3.CSC, E.17.ID.CR |
| E.17.ID.CR | ComparativeReviewUnit - bounded comparison over comparative review units | Stable | Comparative review unit, source anchors, comparison basis, bounded lift, blocked downstream claim or effect, and boundary to decision, equivalence, bridge, coarsening, explanation, prompt, ontology, or gate work. | C.2.2a, A.16.0, F.9, E.14; coordinates with E.17.EFP, E.17.AUD.LHR, E.17.AUD.OOTD, A.6.3.*, A.15, A.20, A.21 |
| E.17.AUD | PublicationUnit Stability Discipline | Stable | One bounded publication unit as a readable unit; primary EntityOfConcern or subject named by value, carried publication move, and outside boundary to work, decision, gate, or reliance claim; choose local head restoration, whole-unit stabilization, bounded comparison, or neighboring pattern. | C.2.2a, A.16.0, A.7, E.10, F.18, E.14, E.19; coordinates with E.17.AUD.LHR, E.17.AUD.OOTD, E.17.ID.CR, E.17.EFP |
| E.17.AUD.LHR | PublicationUnit Stability Discipline and Local Head Restoration | Stable | Repair one overloaded local lexical head inside one publication unit before the whole publication unit inherits ambiguity; recover local head kind, active local reading, local head kind, carried action or question under repair, and outside-work boundary. | A.6.P, A.7, E.10, C.2.P, F.18, E.14; coordinates with E.17.AUD, E.17.AUD.OOTD, E.17.ID.CR, E.17.EFP |
| E.17.AUD.OOTD | PublicationUnit Stability Discipline and PublicationUnit Primary EntityOfConcern Discipline | Stable | Keep one publication unit explicit about one primary EntityOfConcern or subject named by value, one carried move over that entity, and one outside-work boundary; stop quiet shifts into another primary EntityOfConcern, concern, or wider process. | A.6.P, A.7, E.10, F.18, E.14, E.19, C.2.2a, A.16.0; coordinates with E.17.AUD.LHR, E.17.ID.CR, E.17.EFP |
| E.18 | Transformation Flow Structure | Stable | Keywords: transformation flow structure, selected transformations, flow valuation, crossings, guards, composition, P2W support. Queries: "How do transformations compose into a selected flow structure?", "When is a graph/path a selected structure, a mathematical description, or a publication?" | Builds on: A.3.4, E.17, E.8, E.10, A.7. Coordinates with: E.18.1, E.18.2, C.29, A.20, A.21, A.2.6, F.9, F.17, G.5, G.9, G.11, C.30.TFS-REL. |
| E.18.1 | P2W Problem-to-Work Carry-Through | Stable | Relates one accepted ProblemCard@Context and carried ClaimGraph to the next direct pattern-owned value. A short local P2W mantra preserves the practical sequence of questions; explicit structure uses E.18.3 positions and A.22.CGUS only when its admission conditions hold. | Builds on: E.18, C.22.2. Coordinates with: E.11.PUA, E.11.PUR, E.18.3, A.15, G.2, G.11, and every continuing direct pattern. |
| E.18.2 | Transformation Flow Mathematical Description | Stable | Keywords: mathematical description, transformation-flow math, graph expression, path expression, algebraic description, C.29 boundary. Queries: "When is a transformation-flow graph a mathematical description rather than the project structure?", "How do I use math for transformation flow without granting work, gate, evidence, or architecture authority?" | Builds on: E.18, C.29, A.3.4, E.17. Coordinates with: A.6.0, A.10, B.3, A.20, A.21, C.30.TFS-REL, E.18.1. |
| E.18.3 | Constraint-Governed Transformation-Flow Unfolding Structure | Stable | Transformation-flow specialization of A.22.CGUS with typed transformation positions, exact dependency, transfer, crossing, and guard references, governed-position connections, preserved structures, C.33 notes, and separate E.18 slice-local refresh and G.11 currentness. | Builds on: E.18, A.22.CGUS, A.3.4. Coordinates with: E.18.1, C.32.P2S, C.30.TFS-REL, E.23, C.18, C.19, G.5, A.15, G.11. |
| E.19 | Pattern Quality Gates: Review and Refresh Profiles | Stable | Pattern-quality review and refresh profiles; PCP-TERM, PCP-ENTRY, SoTA binding, terminology restoration, reader-role discipline, support-role parity, phrase-apparatus cleanup, semantic trust, profile-depth decisions, and quality-evaluation routing to E.21, E.9.DA, E.2.DA, or E.22 when those evaluations are being made. | E.8, E.9, E.10, E.21, E.22, E.23, C.2.P, F.18, F.19, A.6.P |
| E.20 | Mechanism Introduction Protocol (MIP) | Stable | Keywords: mechanism introduction, authoring protocol, governing-definition assignment, MIP-run manifest, canonical card-first, no dangling …IntensionRef, suite boundary hygiene, P2W seam, SlotKind lexicon discipline, alias docking, typed RSCR triggers, regression envelope, PQG profiles. Queries: "How to introduce a new mechanism in FPF?", "How to avoid dangling IntensionRefs in suites?", "How to assign mechanism changes to their governing definitions?", "How to evolve mechanism suites without drift?" | Builds on: E.8, E.9, E.10, E.15, E.19. Coordinates with: A.6.1, A.6.7, A.15.3, F.18, E.18, G.Core, G.2, G.x:Ext.*. Constrains: Any change-set that introduces or revises mechanisms, suites, planned baselines, wiring modules, or citeable tokens. |
| E.21 | FPF Pattern-Quality Evaluation CharacteristicSpace | Stable | Evaluates one FPF pattern version for a declared reader, use, and scope with one required coordinate set, ordinal values with short rationales, protected trade-offs, precision-restoration profile, status, and stop or reopen conditions. | Builds on: E.8, E.19, C.25, C.16, A.17-A.19, F.18, A.19.ECS. Coordinates with: E.22, E.23, E.9.DA, E.2.DA, E.10, F.19, A.6.P, C.2.P, E.11, I.2. |
| E.22 | Improvement-Oriented Quality Evaluation Question Framing | Stable | Frames one quality evaluation over an object version, evaluation use, purpose, floor or aim, protected trade-offs, evidence basis, and result form. Returns typed finding or proposal epistemes without turning proposals into selected repairs, Work, evidence, release, or improvement proof. | Builds on: A.19.ECS, E.21, E.9.DA, E.2.DA. Coordinates with: E.23, E.19, E.10, C.25, C.17-C.19, G.5, G.9, G.11. |
| E.23 | Quality Improvement Loop Method | Stable | Repeatedly changes one object version and re-evaluates it under one declared evaluation. Uses exact E.22 proposal rows, scale-qualified predicted evaluation-result changes, protected trade-offs, evidence basis, and one loop decision; a visible cycle stays provisional until A.22.CGUS admission. | Builds on: E.22, A.19.ECS. Coordinates with: E.21, E.9.DA, E.2.DA, A.22.CGUS, C.17-C.19, G.5, G.9, G.11. |
| E.24 | U.Ontic and Ontic Introduction Discipline | Stable | Governs when a repeated FPF construct becomes a durable action-facing ontic with stable identity, typed slot relation, dependent-pattern obligations, local-use-frame alternatives, and publication boundary. | Builds on: E.8, E.10, E.10.ARCH, F.18, F.19, C.2.1, A.6.5. Coordinates with: E.24.CD, E.24.PUB, A.19.ECS, E.21, E.9.DA, E.2.DA. |
| E.24.CD | Ontic Candidate Detection | Stable | Detects when repeated FPF or project material may need a durable ontic rather than a local record, table, schema, card, publication form, or wording repair; names candidate signals, sufficiency rationale, hidden-form classifications, and non-use boundaries without turning frequency into proof. | Builds on: E.24, E.10, E.10.ARCH, F.19, A.19.ECS, C.2.1. Coordinates with: E.21, E.9.DA, E.2.DA, F.18. |
| E.24.PUB | Ontic Description and Publication Discipline | Stable | Keeps an ontic, its description episteme, its publication, and the publication form distinct; prevents cards, records, tables, schemas, diagrams, views, pattern hosts, or source packets from becoming the ontic by appearance. | Builds on: E.24, C.2.1, E.17, E.8, E.10, F.19. Coordinates with: E.24.CD, C.30.AD, E.21, E.9.DA. |
| E.24.UK | U-kind Governance and Ontic Settlement Coupling | Stable | Governs whether a public FPF U.*, type, kind, or subkind name is an admitted durable U-kind, a dependent durable value under an existing settlement, a C.3 typed-reasoning value, a slot position, relation structure, record, publication form, lens, local frame, or source wording outside current FPF vocabulary. | Builds on: E.24, E.24.CD, E.24.PUB, C.3, C.3.1, A.8, A.11, F.5, F.8, F.18, E.10, A.6.5. |
Part F — The Unification Suite (U‑Suite): Concept‑Sets, SenseCells & Contextual Role Assignment
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| F.0.1 | Contextual Lexicon Principles | Stable | Keywords: local meaning, context, semantic boundary, bridge, congruence, lexicon, U.BoundedContext. Queries: "How does FPF handle ambiguity?", "What is the principle of local meaning?", "How do different contexts communicate?". | Builds on: A.1.1. Prerequisite for: All patterns in Part F. |
| Cluster F.I — Context of Meaning and Lexical Inputs | ||||
| F.1 | Domain‑Family Landscape Survey | Stable | Keywords: domain‑family survey, context map, canon, scope notes, versioning, authoritative source. | Builds on: E.10.D1, F.0.1, A.7. Prerequisite for: F.2, F.3, F.4, F.9. |
| F.2 | Term Harvesting & Normalisation | Stable | Keywords: term harvesting, lexical unit, normalization, provenance, source-text terms. Queries: "How to extract terminology from a standard?", "What is a local lexical unit?", "How to handle synonyms within one domain?". | Builds on: F.1. Prerequisite for: F.3. |
| F.3 | Intra‑Context Sense Clustering | Stable | Keywords: sense clustering, disambiguation, Local-Sense, SenseCell, counter-examples. Queries: "How to group similar terms within a single domain?", "What is a SenseCell?", "How to handle words with multiple meanings in one context?". | Builds on: F.2. Prerequisite for: F.4, F.7, F.9. |
| Cluster F.II — Concept-Sets & Role Assignment/Description (definition, naming, decision) | ||||
| F.4 | Role Description (RCS + RoleStateGraph + Checklists) | Stable | Keywords: role template, status template, invariants, RoleStateGraph (RSG), Role Characterisation Space (RCS). Queries: "How to define a role in FPF?", "What is a Role Description?", "How to specify the states of a role?". | Builds on: F.3, A.2.1. Prerequisite for: F.6, F.8. |
| F.5 | Naming Discipline for U-kind Names and RoleDescription Labels | Stable | Keywords: naming conventions, lexical rules, morphology, twin registers, U-kind naming, role-description labels. Queries: "How do I name admitted U-kinds and role descriptions?", "How do I avoid false kindhood from a useful label?" | Builds on: F.4, E.10, E.24.UK, F.18. |
| F.6 | Role Assignment & Enactment Cycle (Six-Step) | Stable | Keywords: role assignment, enactment, conceptual moves, asserting status. Queries: "What is the process for assigning a role?", "How is a role enacted in FPF?", "What are the six steps of role assignment?". | Builds on: F.4, A.2.1, A.15. |
| F.7 | Concept‑Set Table Construction | Stable | Keywords: concept-set, table, row, columns, differences, comparisons. Queries: "How do I create a concept-set table?", "How do I compare concepts across contexts?". | Builds on: F.3, F.9. Coordinates with: A.6.9. Prerequisite for: F.8. |
| F.8 | Mint-or-Reuse Decision | Stable | Keywords: decision lattice, type explosion, reuse, minting new U-kinds, parsimony. Queries: "When should I create a new U-kind or reuse an existing governed value?", "How do I avoid creating too many roles or kinds?", "Decision guide for new concepts." | Builds on: F.4, F.7, E.24.UK, A.11. |
| Cluster F.III — Cross‑Context Alignment & Applied Bindings | ||||
| F.9 | Alignment and Bridge across Contexts | Stable | Keywords: bridge, cross-context alignment, CL, direction, loss notes, Bridge-supported use, bridge reading, weakest-link scope, state export. Queries: "How do I bridge concepts across contexts?", "How do I express alignment safely in FPF?", "When is an orientation note not enough for a bridge card?" | Builds on: E.10.D1, F.0.1, F.1, F.2/F.3, F.7, F.8. Coordinates with: C.26, C.26.1, A.6.3.CSC, A.6.9, E.17.ID.CR, F.9.1. Prerequisite for: F.7, F.10. |
| F.9.1 | Bridge Stance Overlay | Stable | Keywords: bridge stance, stance overlay, interpretive gloss, projection note, rename note, language-state comparisons, overlay annotation. Queries: "How do I add a stance gloss to a bridge card without changing bridge semantics?", "What is the Bridge Stance Overlay?", "When does a stance label still depend on the underlying F.9 bridge card?" | Builds on: F.9, C.2.2a, A.16.0. Coordinates with: A.6.3.CSC, E.17.ID.CR, E.17.1, C.16.Q, A.6.A. |
| F.10 | Status Families Mapping (Evidence • Standard • Requirement) | Stable | Keywords: status, evidence, standard, requirement, polarity, applicability windows. Queries: "How to map different types of status like 'evidence' and 'requirement'?", "How does FPF handle compliance?". | Builds on: F.9, B.3. |
| F.11 | Method Quartet Harmonisation | Stable | Keywords: Method, MethodDescription, Work, Actuation, Role–Method–Work alignment. Queries: "How to align the concepts of 'method' and 'work' across domains?", "What is the method quartet?". | Builds on: F.9, A.15. |
| F.12 | Service Acceptance Binding | Stable | Keywords: Service Level Objective (SLO), Service Level Agreement (SLA), acceptance criteria, binding, observation. Queries: "How to bind an SLO to actual work?", "How is service acceptance modeled in FPF?". | Builds on: F.9, A.2.3, KD-CAL. |
| Cluster F.IV — Lexical Development Cycle, Growth Control, Tests & Examples | ||||
| F.13 | Lexical Continuity & Deprecation | Stable | Keywords: evolution, deprecation, renaming, splitting terms, merging terms. Queries: "How to manage changes to terminology over time?", "What is the process for renaming a concept?". | Builds on: F.5. |
| F.14 | Anti‑Explosion Control (Roles & Statuses) | Stable | Keywords: vocabulary growth, guard-rails, separation-of-duties, bundles, reuse. Queries: "How to prevent having too many roles and statuses?", "What are the strategies for controlling vocabulary size?". | Builds on: F.4, F.8. |
| F.15 | Static and Regression Conformance Harness for Unification | Stable | Keywords: static checks, regression tests, acceptance tests, validation, SenseCell testing. Queries: "How is the unification process validated?", "What are SCR/RSCR tests in FPF?". | Builds on: All of F.1-F.14. |
| F.16 | Worked‑Example Template (Cross‑Domain) | Stable | Keywords: didactic template, example, pedagogy, cross-domain illustration. Queries: "What is the standard format for a worked example in FPF?", "How to show a concept applied across different fields?". | Builds on: All of F.1-F.12. |
| F.17 | Unified Term Sheet | Stable | Publishes one governed value and kind with direct pattern, NameCard, SenseCell refs, local-sense basis relations, directional Bridges, admitted use, blocked use, and currentness. Includes bounded rows for demonstrative walkthrough, seminar mantra, and seminar mantra move; ordinary local mantras need no UTS row. | Builds on: F.1-F.12, F.18, F.9. Coordinates with: A.22.CGUS, E.10.MOVE, E.11. |
| F.18 | Local-First Unification Naming Protocol | Stable | Local-first naming; Name Cards; guarded heads; NQD-front label candidates; context-bound semantic read-through; interpretive-view wording; stewardship context examples; FPF kind named by value and reference naming instead of topic-like or entity-interest wording. | F.0.1, F.1-F.17, E.10, C.2.P; coordinates with A.6.P, A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW, G.2, G.6, G.10 |
| F.19 | Ontology-First Plain Technical Rewriting | Stable | Ontology-first plain rewriting; phrase-level boilerplate; negative catalogue; pattern-application drift; kind-preserving plain technical prose. | Builds on: E.8, E.10, E.10.ARCH, F.18, A.6.P, A.7, E.18, E.21. Coordinates with: E.19, E.22, E.23, A.19.SPR, C.2.P, C.16.P, C.30.P, E.11, I.2. |
Part G – Discipline SoTA Patterns Kit
| § | ID & Title | Status | Keywords & Search Queries | Dependencies |
|---|---|---|---|---|
| G.Core | Part G Core Invariants | Stable | Keywords: Part‑G invariants, delegation-first core, RSCR trigger kinds, Default Governing Definition Index, ID continuity, core linkage. Queries: "How to universalize Part G without drift?", "How to make RSCR triggers id-based?" | Builds on: E.8/E.10/E.19, A.6.7, A.15.3, A.19, G.0, A.19.CHR. Used by: all G.0…G.13. |
| G.0 | CG-Spec — Frame Standard & Comparability Governance | Stable | Keywords: CG-Spec, CG-Frame, admissibility gate, ComparatorSet, ScaleComplianceProfile (SCP), MinimalEvidence, Γ-fold, Φ(CL), Φ_plane, CL-routing, ReferencePlane, edition pins, RSCRTriggerKindId. Queries: "What is CG-Spec in FPF?", "How does CG-Spec constrain lawful comparison and aggregation?", "What must be pinned for CG-Spec reproducibility?" | Builds on: G.Core, A.19 (CN-Spec), A.10, A.17–A.19 / C.16 (MM-CHR admissibility), A.18 (CSLC), B.3, Part F (Bridges/UTS), E.10, E.5.2. Prerequisite for: G.1–G.6. |
| G.1 | CG-Frame-Ready Generator | Stable | Keywords: generator chassis, generator, selector, and set-result scaffold, six-card kit (M1-M6), CGKitId manifest, SoTA_SetId, VariantPoolId, ShortlistId, CGFrameLibraryId, RefreshReadinessCardId, set-return selection, set-result outcome, UTS/Name Cards, RSCR linkage surfaces, edition pins, shipping and refresh boundaries. Queries: "How do I author a reusable CG-Frame generator kit?", "What belongs in the six-card chassis M1-M6?", "How do G.2 harvesting, G.5 set-return selection, G.10 shipping, and G.11 refresh connect without becoming one method spec?" | Builds on: G.Core, E.8, E.10, E.19. Uses: A.10, A.15.3, A.19 (CN-Spec), G.0 (CG-Spec), G.2, G.3, G.4, G.5, G.10, G.11; (via Extensions) C.17, C.18, C.19. Produces: CGKitId plus reusable CG-Frame kit or chassis, set-result scaffold, and linkage surfaces (UTS and RSCR ready). |
| G.2 | SoTA Harvester & Synthesis | Stable | Keywords: SoTA harvest, synthesis, SoTA Synthesis Pack@CG-Frame, SoTAPaletteDescription, Tradition, TraditionAtlasView, DeclaredSubstrateAtlasView, TypedSetViews, BridgeMatrix, GammaEpistSynthId, FlowRecord, palette-first. Queries: "How does FPF harvest and synthesize SoTA for a CG-Frame?", "When is TraditionAtlasView lawful and when is palette-first or thinner interpretation enough?", "How do competing Traditions stay plural while bridgeable and refreshable?" | Builds on: G.Core, E.8, E.10, E.19, A.10, B.3, F.9, F.17, G.0. Used by: G.1, G.3-G.5, G.10, G.11. Coordinates with: A.19.DECLARED-SUBSTRATE-INTERPRETIVE-VIEW, A.6.P, G.13. |
| G.3 | CHR Authoring: Characteristics - Scales - Levels - Coordinates | Stable | Keywords: CHR authoring, characteristics, scales, levels, coordinates, CSLC lawfulness, typed measurement, CHR Pack@CG-Frame, ReferencePlane, Φ/CL policy pins, edition pins, RSCRTriggerKindId. Queries: "How do I author CHR packs (typed characteristics and scales) for a CG-Frame?", "How to keep measurement lawful (CSLC) and refreshable (RSCR)?" | Builds on: G.Core, G.2, G.0, A.17–A.19, A.18 (CSLC), C.16 (MM-CHR), A.19.CHR, A.15.3, G.6, F.17. Prerequisite for: G.4. Used by: G.4, G.5, G.10, G.11. |
| G.4 | CAL Authoring: Calculi - Acceptance - Evidence | Stable | Keywords: CAL authoring, operators, acceptance clauses, evidence profiles, tri-state admissibility, Γ-fold hooks, Φ/Ψ/Φ_plane policy pins, admissibility gates, edition pins, RSCRTriggerKindId. Queries: "How to author CAL operators and acceptance clauses for CG-Frames?", "How to keep acceptance/evidence wiring auditable and refreshable?" | Builds on: G.Core, G.3, G.0, B.3 (Trust), A.18 (CSLC), G.6. Prerequisite for: G.5. Used by: G.5, G.8–G.10, G.11. |
| G.5 | Multi‑Method Dispatcher & MethodFamily Registry | Stable | Keywords: method-family registry, generator-family registry, dispatcher, SelectorOutcomeKind, selected-set publication, set-result outcome, Shortlist, RankedShortlist, ShortlistId, SpecialistHandoff, abstain/escalation result, basis pins, no hidden scalar winner. Queries: "How does FPF dispatch among rival method families without hidden scalarization?", "How do I publish a Shortlist or RankedShortlist honestly?", "When does G.5 begin after C.11 choice, C.19 pool policy, or C.24 planning?" | Builds on: G.Core, G.0, G.2-G.4, G.6. Coordinates with: C.11, C.19, C.24, G.9-G.11. |
| G.6 | Evidence Graph & Provenance Ledger | Stable | Keywords: EvidenceGraph, provenance, PathId, PathSliceId, lane tags (TA/VA/LA), SCR/RSCR, GateCrossing, CrossingBundle, UTS PathCard, TriggerAliasMap, Γ-fold pinning. Queries: "How does FPF trace claims to evidence?", "What is an EvidenceGraph?", "How do PathId/PathSliceId support audit and refresh?" | Builds on: G.Core, A.10, B.3, G.4, F.9, F.15, F.17, E.18, A.21, E.10, E.5.2. Used by: G.5, G.8, G.9, G.10, G.11. |
| G.7 | Cross-Tradition Bridge Calibration Kit (BridgeMatrix → BridgeCards + BCT/Sentinels) | Stable | Keywords: bridge calibration, BridgeCard, BridgeCalibrationTable (BCT), RegressionSet, SentinelSet, BridgeSentinel, Congruence Level (CL/CL^k/CL^plane), loss notes, waivers, ReferencePlane, Φ(CL)/Ψ(CL^k)/Φ_plane policy pins, PathSliceId, GateCrossing, UTS, RSCRTriggerKindId. Queries: "How to calibrate cross-Tradition bridges in Part G?", "What is BCT and how is it used?", "How do Bridge Sentinels trigger RSCR?" | Builds on: G.Core, G.2, F.9, F.3, F.7, B.3, G.6, E.18, A.21, E.10, C.21. Prerequisite for: G.5. Used by: G.9–G.11, G.10, G.12. |
| G.8 | SoS-LOG Bundles & Maturity Ladders | Stable | Keywords: SoS-LOG, rule ids, admissibility ledger, tri-state `{pass | degrade |
| G.9 | Parity / Benchmark Harness | Stable | Keywords: parity harness, benchmark plan, adaptation parity, freshness windows, comparator pins, selected-set outcomes. Queries: "How does FPF run reproducible parity with explicit pins and windows?", "How do adaptation-speed and specialization claims become lawful parity questions?" | Builds on: G.Core, G.5, G.6, G.4, F.15. Uses: G.0, A.19, C.22.1. Coordinates with: C.27 when parity compares rate-change, rhythm change, recovery speed, intervention effect, effort budget, or dynamic outcome. |
| G.10 | SoTA Pack Shipping (pack-boundary governing definition; SoTA-Pack(Core)) | Stable | Keywords: shipping, SoTA-Pack(Core), pack-boundary governing definition, selector-ready publication surface, AuditPins, MOOManifest, PortfolioRosterId, UTS publication, PathId/PathSliceId, CrossingBundle, edition pins, telemetry pins, RSCR wiring, parity pins, notation-independent pack, no semantic respecification. Queries: "How does FPF ship a SoTA pack without smuggling semantics?", "What is SoTA-Pack(Core) as a pack rather than a kit or suite?", "How do AuditPins, MOOManifest, path citations, and crossing bundles support replay and refresh?" | Builds on: G.Core, F.17-F.18, E.5.2, E.18, A.10, A.15.3. Consumes/cites: G.2-G.9, optional G.12-G.13. Used by: selector-facing consumers via G.5 and refresh orchestration via G.11. |
| G.11 | Telemetry-Driven Refresh & Decay Orchestrator | Stable | Keywords: telemetry, refresh, decay, RSCR, PathSlice, Bridge Sentinels, edition-aware, epistemic debt, deprecation, edition bumps, re-shipping. Queries: "How does FPF keep SoTA packs up-to-date?", "What triggers refresh / RSCR reruns?", "How are deprecations and edition bumps governed?". | Builds on: G.Core, G.6, G.7, G.5, G.8, G.9, G.10, B.3.4, E.18. Coordinates with: G.12, C.18 and C.19, C.23, F.15. |
| G.12 | DHC Dashboards — Discipline-Health Time-Series (admissible telemetry, generation-first) | Stable | Keywords: dashboard, DHC, discipline health, time-series, admissible telemetry, view-only slices, PathId/PathSliceId, edition pins, UTS twins, RSCR/refresh wiring. Queries: "How to build DHC dashboards in FPF?", "How to publish admissible DHC time-series with evidence and edition pins?", "How to wire dashboard telemetry into RSCR refresh?" | Builds on: G.Core, C.21, G.6, G.11, A.19, G.0, F.17/F.18, E.5.2, E.10. Coordinates with: G.5 (selector set-result outputs), G.7 (crossings/CL/Φ_plane pins), G.8 (maturity ladder panel), G.10 (shipping inclusion), C.18 and C.19 (QD/OEE telemetry), G.2 (SoTA palette hooks). |
| G.13 | External Interop Hooks for SoTA Discipline Packs (conceptual; normative when used) | Stable | Keywords: interop, external index, claim mapper, mapping policy, plane map, embedding spec, ExternalIndexCard@Context, ClaimMapperCard@Context, InteropSurface@Context, CHR-typed SoS features, edition pins, UTS twins, RSCRTriggerKindId, telemetry pin. Queries: "How does FPF integrate external scholarly indexes into Part G?", "What is an ExternalIndexCard / ClaimMapperCard / InteropSurface in FPF?", "How to make interop refreshable with RSCR trigger kinds and edition pins?" | Builds on: G.Core, G.2–G.7, G.9–G.12, A.19, A.18, G.0, F.17, E.5.2, E.18. |
Part I – Annexes & Extended Tutorials
| § | ID & Title | Status | Concise reminder |
|---|---|---|---|
| I.2 | Expanded Entry Disambiguation Cases | Stable | Expanded entry-disambiguation cases for high-risk or compact-insufficient first-entry pattern comparison; compact-index-only is a complete admissible posture when enough. |
Last Updated: 2026-07-12 — upstream FPF commit 44dd8818 (github.com/ailev/FPF)