FPF Reference

Patterns
Routes
Preface

Preface

Preface Catalog

First Principles Framework (FPF) — Core Conceptual Specification

Table of Content

Preface (non-normative)

What this specification is (and how to use it)

Creativity in Open-Ended Evolution and Assurance*

Navigating Uncertainty: Building Closed Worlds within an Open World (non-normative)

FPF as an Evolutionary Architecture for Thought

Architectural Characteristic of Thought

Beyond Cognitive Biases: FPF as a Generative Architecture for Thought

Thinking Through Writing: The FPF Discipline of Conceptual Work

Descriptive Ontologies vs. A Thinking-Oriented Architecture

The "Bitter Lesson" trajectory — compute, data, and freedom over hand‑tuned rules (FPF stance)

From Flat Documents to High-Dimensional Truth: The Multi-View Architecture

Boundary Statements: Where Language Becomes a System Boundary

Raising Semantic Precision: From Triggers to Math‑Backed Ontics

The “big storylines” unique to FPF (load‑bearing commitments)

Transdisciplinarity as a Meta‑Theory of Thinking

FPF as a Culinary Architecture for Collective Thought: Why We Formalize “Obvious” Ideas

Intellect Stack

Purpose, Scope, and Explicit Non‑Goals

Part A – Kernel Architecture Cluster

1) Problem frame

2) Problem

3) Forces

4) Solution — Normative onboarding glossary and publication hooks

4.1 Plain one‑liners (normative on‑ramp; formal anchors in C.17–C.19)

4.2 Publication & telemetry duties (where these terms show up)

4.3 Minimal recipe (run this on day one)

5) Archetypal Grounding

6) Bias‑Annotation

7) Conformance Checklist (SCR/RSCR stubs)

8) Consequences

9) Rationale

10) Relations

Editor’s note (implementation hint)

A.2.2:4.2 Conceptual descriptors (not a data schema)

A.2.2:4.3 Shorthand for everyday speech

A.2.2:6.1 Physical system on a line (structural example)

A.2.2:6.2 Software service in operations (structural, cyber-physical)

A.2.2:6.3 Organizational unit (enterprise sense)

A.2.6:17. 4 Rationale - F‑Cluster Unification for A.2.6 (F.17 / F.18)

A.2.6:End

A.2.7:End

A.2.8:End

A.2.9 — U.SpeechAct (Communicative Work Object)

A.2.9:1 — Problem frame

A.2.9:2 — Problem

A.2.9:3 — Forces

A.2.9:4 — Solution

A.2.9:4.1 — Normative definition

A.2.9:4.2 — Minimal structure (normative)

A.2.9:4.3 — SpeechActRef discipline (normative)

A.2.9:4.4 — Separation rules with U.Commitment and U.PromiseContent (normative)

A.2.9:4.5 — Multi-function and multi-party support (normative)

A.2.9:5 — Archetypal Grounding (Tell–Show–Show)

A.2.9:5.1 — Tell (universal rule)

A.2.9:5.2 — Show #1 (system archetype: change-control approval gates a deployment)

A.2.9:5.3 — Show #2 (episteme archetype: publishing a spec edition without making the spec an agent)

A.2.9:6 — Bias-Annotation

A.2.9:7 — Conformance Checklist (normative)

A.2.9:8 — Common Anti-Patterns and How to Avoid Them

A.2.9:9 — Consequences

A.2.9:10 — Rationale

A.2.9:11 — SoTA‑Echoing (informative; post‑2015 alignment)

Cluster A.IV.A - Signature Stack & Boundary Discipline (A.6.\)*

Tell (universal rule)

Show #1 (U.System): effectful API boundary (algebraic effects intuition)

Show #2 (U.Episteme): published evaluation protocol boundary (multi‑view + evidence)

A.6:End

A.6.B — Boundary Norm Square (Laws / Admissibility / Deontics / Work‑Effects)

A.6.B:0 — Conventions

A.6.B:1 — Problem frame

A.6.B:2 — Problem

A.6.B:3 — Forces

A.6.B:4.2 — The square

A.6.B:4.3 — Canonical landing zones in the Signature Stack

A.6.B:5 — Quadrant specifications

A.6.B:5.1 — Quadrant L: Laws & Definitions

A.6.B:5.2 — Quadrant A: Admissibility & Gates

A.6.B:5.3 — Quadrant D: Deontics & Commitments

A.6.B:5.4 — Quadrant E: Work‑Effects & Evidence

A.6.B:6 — Cross‑quadrant link discipline

A.6.B:6.1 — Explicit reference rule

A.6.B:6.2 — Canonical cross‑quadrant dependency patterns

A.6.B:6.3 — The “triangle decomposition” for mixed sentences

A.6.B:6.4 — Dependency direction (no “upward” imports)

A.6.B:7 — Mini‑artifact: Claim Register (informative, recommended)

A.6.B:8.4 — Worked Rewrite Kit (informative, recommended)

A.6.B:9 — Bias‑Annotation

A.6.B:10 — Conformance Checklist

A.6.B:12 — Consequences

A.6.B:13 — Rationale

A.6.B:14 — SoTA‑Echoing (post‑2015 practice alignment)

A.6.B:15 — Relations

A.6.B:End

A.6.C — Contract Unpacking for Boundaries

A.6.C:1 — Problem frame

A.6.C:2 — Problem

A.6.C:3 — Forces

A.6.C:4 — Solution

A.6.C:4.1 — The Contract Bundle (four-part unpacking)

A.6.C:4.2 — Routing recipe into A.6.B (L/A/D/E)

A.6.C:4.3 — “Guarantee” disambiguation

A.6.C:4.4 — MVPK faces are not second contracts

A.6.C:4.5 — Default artefact: Contract Claim Register (recommended)

A.6.C:5 — Archetypal Grounding (Tell–Show–Show)

A.6.C:5.1 — Tell

A.6.C:5.2 — Show (System archetypes)

A.6.C:5.3 — Show (Episteme archetypes)

A.6.C:6 — Bias-Annotation

A.6.C:7 — Conformance Checklist

A.6.C:8 — Common Anti-Patterns and How to Avoid Them

A.6.C:9 — Consequences

A.6.C:10 — Rationale

A.6.C:11 — SoTA‑Echoing (informative; post‑2015 alignment)

A.6.3.CR:4.5.a. Preservation law

A.6.3.CR:4.5.b. Loss and reliability law

A.6.3.CR:4.5.c. Authority and handoff law

A.6.3.CR:4.5.d. Composition and reopen law

A.6.3.CR:4.5.e. Non-collapse note for correspondence

A.6.3.CR:4.5.f. Local conservativity witness for borderline textual cases

A.6.3.CR:End

A.6.3.RT:4.5.a. Preservation law

A.6.3.RT:4.5.a.1. Local conservativity witness

A.6.3.RT:4.5.b. Loss and reliability law

A.6.3.RT:4.5.c. Authority and handoff law

A.6.3.RT:4.5.c.1. Same-entity entry condition for decode-mediated cases

A.6.3.RT:4.5.d. Composition and reopen law

A.6.3.RT:End

A.6.4:End

A.6.P — U.RelationalPrecisionRestorationSuite — Relational Precision Restoration (RPR) — Kind‑Explicit Qualified Relation Discipline

A.6.P:0 — TERM/LEX token guards (local-first)

A.6.P:1 — Problem frame

A.6.P:2 — Problem

A.6.P:3 — Forces

A.6.P:4 — Solution — The RPR recipe (Lens → Slots → Change Lexicon → Guardrails), aligned to A.6 / A.6.B / A.6.S

A.6.P:4.0 — Trigger rule (when A.6.P applies)

A.6.P:4.0a — Operational repair sequence (how repairs actually proceed)

A.6.P:4.0b — Candidate‑Set Note (informative; review artifact)

A.6.P:4.1 — Stable lens

A.6.P:4.2 — Kind‑explicit relation tokens (no umbrella meaning‑surrogates)

A.6.P:4.3 — Slot‑explicit qualified relation records (recover hidden arity)

A.6.P:4.4 — Change‑class lexicon (operations are not adjectives)

A.6.P:4.5 — Lexical guardrails (ban umbrella metaphors as meaning‑surrogates)

A.6.P:4.6 — Progressive elaboration (the “precision dial” rule)

A.6.P:4.7 — Two‑view / polarity discipline (no silent role flips)

A.6.P:4.8 — Disambiguation guide (rewrite/selection)

A.6.P:4.9 — A.6.B routing template for RPR relation families

A.6.P:4.10 — A.6.S compatibility note (ConstructorSignature is optional but canonical for engineered families)

A.6.P:5 — Archetypal Grounding (System / Episteme)

A.6.P:5.1 — System archetype: “same system across environments”

A.6.P:5.2 — Episteme archetype: “the models are synced”

A.6.P:6 — Bias‑Annotation

A.6.P:7 — Conformance Checklist (CC‑A.6.P)

A.6.P:8 — Common Anti‑Patterns and How to Avoid Them

A.6.P:9 — Consequences

A.6.P:10 — Rationale

A.6.P:11 — SoTA‑Echoing (informative; post‑2015 alignment)

A.6.7:4.1 MechSuiteDescription (data model)

A.6.7:4.2 SuiteObligations (canonical obligation vocabulary)

A.6.7:4.3 SuiteContractPins

A.6.7:4.4 SuiteProtocols

A.6.7:4.5 SuiteAuditObligations

A.6.7:4.6 Examples (tell–show–show discipline)

A.6.7:End

A.6.8:4.0 — UTS + LEX preparation (mandatory for authoring/repair)

A.6.8:4.1 — Trigger rule

A.6.8:4.2 — Stable lens: the Service Situation Bundle

A.6.8:4.3 — Facet headwords (mandatory lexical rule)

A.6.8:4.4 — Addressability rule (the “can you call it?” test)

A.6.8:4.4b — Method/mechanism rule (the “how does it work?” test)

A.6.8:4.5 — Deontic rule (the “must/shall” test)

A.6.8:4.6 — Speech‑act rule (the performative verb test)

A.6.8:4.7 — Runtime/telemetry rule (the “actuals” test)

A.6.8:4.8 — Change‑class lexicon (service‑specific narrations)

A.6.8:4.9 — Disambiguation guide (rewrite/selection)

Show 1 — System archetype (microservices + SRE)

Show 2 — Episteme archetype (physical/human service)

Cluster A.V - Constitutional Principles of the Kernel

A.7:5.10.1 — Definition (normative)

A.7:5.10.2 — Minimal structure (conceptual; normative constraints)

A.7:5.10.3 — unitOfDelivery and countingRule mini‑schema (normative)

A.7:5.10.4 — Bridge to U.Work (normative invariants)

A.7:5.10.5 — Canonical examples (didactic)

A.7:End

A.8:End

A.9:End

A.10:4.3 SCR / RSCR (Symbol Carrier Registers).

A.10:4.4 Scope alignment (A.4) across Role–Method–Work (A.15).

A.10:4.5 External TransformerRole (A.12).

A.10:4.6 Γ‑flavour hooks (how each flavour anchors).

A.15.3:4.1 Definition

A.15.3:4.2 Core conceptual descriptors (not a data schema)

A.15.3:4.2.1 Canonical skeleton (Show)

A.15.3:4.3 Relation to Work enactment (planned baseline vs actuals)

A.15.3:4.4 Relation to suites/kits

A.19:5.2.1.2 Embedding – Injection ι : CS₁ ↪ CS₂.

A.19:5.2.1.3 Product – Combination CS₁ ⊗ CS₂ = CS⊗.

A.19:5.2.2.1 Coordinatewise comparability (≼_coord)

A.19:5.2.2.2 Normalization‑based comparability (≼_normalization)

A.19:5.2.4.1 Direction & loss (Bridges).

A.19:5.2.4.2 Confidence penalties for mapped comparisons.

A.19:5.2.4.3 Declare “incomparable” when appropriate.

A.19:End

A.19.CN:8.4.3 Alignment CN‑frame — Design-time reuse of states across Contexts

A.19.SelectorMechanism:End

A.20:Appendix A — CV Class Gloss (normative)

A.20:Appendix B — LEX discipline (summary)

A.20:End

A.21 — GateProfilization: OperationalGate(profile) (GateFit core)

A.21:End

Part B – Trans‑disciplinary Reasoning Cluster

B.2.5 — Supervisor–Subholon Feedback Loop

B.2.5:End

B.3:5 Proof obligations (attach these when producing an Assurance tuple)

B.3:End

B.3.3 — Assurance Subtypes & Levels

Part C — Kernel Extensions Specifications

C.3:7.1 How typed reasoning plugs into F–G–R & USM

10 - Review & integration guidance

C.3.A:Annex A - How typed reasoning plugs into Compliance & Regulatory Alignment \[A/I]

C.3.A:A.1 Purpose & fit

C.3.A:A.2 Normative obligations

C.3.A:A.3 Guard macros (ready to use)

C.3.A:A.4 Worked examples \[I]

C.3.A:A.5 Design guidance & pitfalls \[I]

C.3.A:A.6 Migration checklist \[I]

C.3.A:A.7 Manager’s one‑page pattern \[I]

C.3.A:Annex B - How typed reasoning plugs into Assurance Lanes (VA/LA/TA) & Evidence design \[A/I]

C.3.A:B.1 What you get with typed assurance \[I]

C.3.A:B.2 Normative obligations for evidence design

C.3.A:B.3 Designing the evidence matrix \[I]

C.3.A:B.4 VA lane — proofs that match the kind \[A/I]

C.3.A:B.5 LA lane — tests & monitoring that cover the right variants \[A/I]

C.3.A:B.6 TA lane — tool qualification where it belongs \[A/I]

C.3.A:B.7 Guard macros for evidence planning & attachment

C.3.A:B.8 Anti‑patterns & remedies

C.3.A:B.9 End‑to‑end example (manager’s cheat‑sheet) \[I]

C.3.A:Annex C. ESG guards

C.3.A:C.1 ESG guard obligations (normative)

C.3.A:End

C.11:End

C.13 — Constructional Mereology (Compose‑CAL)

C.13:End

C.16:5.7 Cross‑references & anchors

C.16:End

C.17:15.4 What these cases illustrate (tie‑backs)

C.17:26- Open questions (non‑normative, research hooks)**

Part D – Multi-scale Ethics & Conflict‑Optimisation

D.5:End

Part E - FPF Constitution and Authoring Cluster

Section E‑I - The FPF Constitution

E.10.D1:9.1 Enactment — process vs activity (two context of meaning).

E.10.D1:9.2 Roles — behavioural mask vs access status.

E.10.D1:9.3 Services & evidence.

E.10.D1:End

E.10.D2:4.1 The triad (applies to any intensional U.T)

E.10.D2:4.2 The Spec‑gate (when “–Spec” is allowed)

E.10.D2:4.3 Where RCS/RSG and evaluations sit

E.10.D2:4.4 Plain‑language memory hook

E.10.D2:12.1 Static conformance checks (SCR)

E.10.D2:12.2 Regression checks (RSCR)

E.17.EFP:4.5.a. Preservation law

E.17.EFP:4.5.b. Loss and reliability law

E.17.EFP:4.5.c. Authority and handoff law

E.17.EFP:4.5.d. Composition and reopen law

E.18::5.1 - S1 - Graph object (conceptual)

E.18:End

E.19:End

E.20:End

Part F — The Unification Suite (U‑Suite): Concept‑Sets, SenseCells & Contextual Role Assignment

Cluster F.I — context of meaning & Raw Material

F.0.1:9.1 Enactment × Provenance — process vs activity

F.0.1:9.3 Measurement × Service — observation vs service metric

F.0.1:9.4 Type reasoning — subclass‑of (OWL) vs is‑a (plain)

F.0.1:9.5 Deontics × Access — permission vs role (RBAC)

F.0.1:End

F.1:12.1 Enactment (U.RoleAssignment + U.RoleEnactment) with sensing & execution (service acceptance)

F.1:12.2 Method quartet with types & measurement (model state graph)

F.1:12.3 Control & actuation with services (operational SLOs in plants)

F.1:End

F.2 — Term Harvesting & Normalisation

F.2:6.2 -Move B — Name it in the Context’s idiom

F.2:11.1 Enactment + sensing

F.2:11.2 Sys‑CAL / LCA‑CAL + services

F.2:11.3 Kind-CAL + Method‑CAL + KD‑CAL

F.8:12.4 Subtype relation across OWL and a curated taxonomy (formalists)

F.11:11.4 Incident response (services + enactment)

F.11:End

F.12 — Service Acceptance–Work Evidence Link

F.12:15.3 Didactic distillation (60‑second recap)

F.12:End

F.13:12.2 -Local alias

| Block | Base concept (EN / RU) | Scale‑map (Σ/Π/μ)

F.17:End

F.18:End

Part G – Discipline SoTA Patterns Kit

G.Core - Part G Core Invariants

G.Core:1 - Problem frame

G.Core:2 - Problem

G.Core:3 - Forces

G.Core:4 - Solution

G.Core:4.1 - Delegation-first routing for Part‑G‑wide invariants

G.Core:4.2 - Mandatory G.Core linkage contract for every G.x

G.Core:4.2.1 - GCoreLinkageManifest (canonical shape)

G.Core:4.2.2 - GCoreConformanceProfileId catalogue (compression primitive)

G.Core:4.2.3 - GCorePinSetId catalogue (compression primitive)

G.Core:4.3 - RSCR Trigger Catalogue and docking discipline

G.Core:4.3.1 - Definitions

G.Core:4.3.2 - Owner model

G.Core:4.3.3 - Authoring rules

G.Core:4.3.4 - Seed canonical catalogue (Phase‑2 minimum)

G.Core:4.3.4.1 - Canonical kind definitions (normative, minimal)

G.Core:4.3.4.2 - Canonical trigger sets (compression primitive)

G.Core:4.3.5 - Initial alias maps

G.Core:4.4 - Default Ownership Index

G.Core:4.4.1 - Definitions

G.Core:4.4.2 - Rules

G.Core:4.4.3 - Seed Default Ownership entries (Phase‑2 minimum)

G.Core:4.5 - ID continuity protocol (Δ‑discipline)

G.Core:4.6 - Explicit non-goals

G.Core:5 - Archetypal grounding

G.Core:6 - Bias-annotation (informative)

G.Core:7 - Conformance checklist (normative) — CC‑GCORE

G.Core:8 - Common anti-patterns and how to avoid them

G.Core:9 - Consequences

G.Core:10 - Rationale

G.Core:11 - SoTA alignment (informative)

G.Core:12 - Relations

G.Core:End

G.0:End

M1 — CG‑FrameContext Card (scope anchor)

M2 — SoTA_Set@CG‑Frame (harvester output card)

M3 — VariantPool (candidate inventory + emitter trace)

M4 — Shortlist (selector/assurer output)

M5 — CG‑FrameLibrary (published bindings index)

M6 — RefreshReadiness Card (telemetry hooks + wiring)

GPatternExtension — G.1:Ext.HarvesterWiring

GPatternExtension — G.1:Ext.ShortlistWiring

GPatternExtension — G.1:Ext.CreativityCHR

GPatternExtension — G.1:Ext.NQD

GPatternExtension — G.1:Ext.OpenEndedFamilyWiring

GPatternExtension — G.1:Ext.RefreshWiring

GPatternExtension — G.1:Ext.ShippingWiring

G.9 — Parity / Benchmark Harness

G.9:0 — Use this when

G.9:0.1 — What goes wrong if missed

G.9:0.2 — What this buys

G.9:1 — Intent

G.9:2 — Problem frame

G.9:3 — Forces

G.9:4 — Solution

G.9:4.0 — G.Core linkage (normative)

G.9:4.1 — Objects and surfaces

G.9:4.2 — Parity planning (design‑time / WorkPlanning)

G.9:4.3 — Execution protocol (run‑time / selector‑adjacent)

G.9:4.3a — Worked parity slice

G.9:4.9 — Extensions (pattern‑scoped; non‑core)

G.9:5 — Interfaces (minimal I/O; conceptual)

G.9:6 — Conformance Checklist (CC‑G9)

G.9:7 — Anti‑patterns and remedies

G.9:8 — Archetypal grounding (informative; SoTA‑oriented)

G.9:9 — Payload (what this pattern exports)

G.9:10 — Relations

G.9:11 — Working reading checks

G.9:End

GPatternExtension — G.10:Ext.QDArchiveShippingPins

GPatternExtension — G.10:Ext.OEEShippingPins

GPatternExtension — G.10:Ext.InteropCitation

G.10:End

G.11:Ext.LegacyTriggers

G.11:Ext.DecayAndDebt

G.11:Ext.QDRefreshWiring

G.11:Ext.OEERefreshWiring

G.11:Ext.SchedulingHeuristics (Phase-3 seed)

G.11:End

G.12 — DHC Dashboards (Discipline‑Health time‑series; lawful telemetry; generation‑first)

G.12:1 — Intent

G.12:2 — Problem frame

G.12:3 — Forces

G.12:4 — Solution — Compute and publish DHC series lawfully, with RSCR‑ready telemetry

G.12:4.0 — G.Core linkage (normative)

G.12:4.1 — Objects (LEX heads; twin‑register discipline)

G.12:4.2 — Method‑of‑Obtaining Output (generation‑first; design‑time → run‑time)

G.12:4.9 — Extensions (pattern‑scoped; non‑core)

G.12:Ext.SoTAPalette — SoTA palette & DHC alignment hooks (optional)

G.12:Ext.PortfolioTelemetry — selector/portfolio integration panel

G.12:Ext.QDTelemetry — illumination / archive telemetry panel

G.12:Ext.OpenEndedTelemetry — open‑endedness / transfer telemetry panel

G.12:Ext.MaturityLadderPanel — maturity ladder view (optional)

G.12:Ext.PackInclusion — shipping inclusion stub (optional)

G.12:Ext.ViewFamilySeed — advanced view families (Phase‑3 seed; owner TBD)

G.12:5 — Interfaces (conceptual; kit surface)

G.12:6 — Conformance checklist (CC‑G12, normative)

G.12:7 — Bias‑Annotation (informative)

G.12:8 — Consequences

G.12:9 — Relations

G.12:10 — Author’s quick checklist

G.12:11 — Worked micro‑examples (informative; SoTA‑oriented)

G.12:End

G.13:End

Part H – Glossary & Definitional Pattern Index

Part I – Annexes & Extended Tutorials

Part J – Indexes & Navigation Aids

Part K – Lexical debt

Mandatory replacement map for measurement terms

Migration debt from A.2.6 (Scope, ClaimScope, WorkScope)

Deprecations (normative)

Affected locations and required edits (normative)

Migration playbook (informative)

Backwards compatibility (informative)

Change Log (normative migration record)

Preface›Part A – Kernel Architecture Cluster›A.5:End

A.5:End

Preface node heading:a-5-end:6554

Last Updated:

Previous pageA.4:End Next pageCluster A.IV.A - Signature Stack & Boundary Discipline (A.6.\)*

#A.5:End

A.5:End