Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

E.5 - Four Guard‑Rails of FPF

Status: Stable

E.5:1 - Problem frame

Use this pattern when authoring or revising Core concepts or their Tooling and Pedagogy forms. Four recurring risks require different checks:

  1. Implementation language — concept prose acquires tool-specific terms.
  2. Notation lock-in — one diagram style becomes the only way to express a concept.
  3. Reverse dependencies — a local convenience makes Core depend on an outer layer.
  4. Disciplinary bias — domain-specific assumptions enter rules intended for several domains.

These risks undermine Pillars P-1 Cognitive Elegance, P-4 Open-Ended Kernel and P-5 FPF Layering. Use E.5.1–E.5.4 for the corresponding detailed rules.

E.5:2 - Problem

Core definitions can become tied to transient tools or one notation, acquire dependency cycles, or present domain-specific assumptions as universal. Authors need constraints that preserve reusable meanings while allowing concrete examples and different forms of expression.

E.5:3 - Forces

ForceTension
Abstraction vs Concrete UseKeep concept definitions stable while illustrating them with useful examples from real situations.
Universality vs ConventionA familiar notation can be convenient, but tying a cross-domain rule to that notation limits its use elsewhere.
Modularity vs IntegrationKeep layers independent despite the temptation to cross-link them for speed.
Cross-Domain Use vs PerspectiveClaims intended for several domains can reflect contributors’ disciplinary and cultural assumptions.

E.5:4 - Solution — the Four Guard‑Rails

Every Core, Tooling, and Pedagogy artefact must obey these four guard-rails at its own layer.

Scope. These guard-rails regulate concepts, claims and their relations. Abstract Core definitions exclude incidental tools, formats and workflows.

A rule about a named publication form, protocol or grammar may retain the syntax necessary for that subject under E.5.1, with its edition/use boundary.

Linting and automation remain outside Core and are optional unless a separate operational contract requires them. They preserve the governed conditions rather than define the concepts.

#Guard‑RailProtects against
GR‑1DevOps Lexical FirewallPull of implementation, governance, automation, and DevOps concerns
GR‑2Notational IndependenceNotation lock‑in
GR‑3Unidirectional DependencyConvenience cycles
GR‑4Cross‑Disciplinary Bias AuditDisciplinary monoculture

For the detailed rule behind each guard-rail, see E.5.1 – E.5.4.

E.5:5 - Archetypal Grounding (System / Episteme)

Guard‑RailU.System exampleU.Episteme example
GR‑1Definition of U.System never cites file formats or build scripts.Definition of U.Episteme avoids naming specific proof engines.
GR‑2A meaning-preserving mapping between text and diagram retains the pump boundary invariant.A meaning-preserving mapping between algebraic and graph expressions retains F‑G‑R semantics.
GR‑3A sizing helper imports Core invariants. Core never imports helper tutorials.A learning guide cites the R‑score. Core does not derive its semantics from the guide.
GR‑4Bias audit removes thermo‑mechanical jargon from a “universal” pattern.Audit replaces physics‑centric metaphors in a trust pattern.

E.5:6 - Conformance Checklist

IDRequirementPurpose
CC‑GR.1A Core pattern SHALL name the guard-rails whose interpretation, realization or interaction changes its design or use, and explain that relation.Makes material rule interactions recoverable.
CC‑GR.2Core, Tooling and Pedagogy respect GR-1 through GR-4 at their own layer. Implementation and runnable teaching remain in their sources. Necessary subject-defining syntax follows E.5.1 and interpretation/mapping follows E.5.2.Preserves both portability and applicable concrete-subject rules.
CC‑GR.3A change to a guard-rail’s governing meaning REQUIRES an E.9 Design-Rationale Record stating the reason and Pillar impact under the E.3 precedence model.Grounds a changed constitutional obligation while preserving E.9’s ordinary editorial branch.
CC‑GR.4The aggregate of guard‑rail rules MUST remain internally consistent and acyclic. No guard‑rail may override another without explicit precedence edges.Preserves deterministic governance.
CC‑GR.5Every Core pattern MUST make its primary EntityOfConcern or primary relation recoverable at first mention. Declare CHR:ReferencePlane (`worldconcept

All CC‑GR duties are conceptual. Any automated checks are informative only and live in Tooling/Pedagogy.

E.5:7 - Consequences

BenefitsTrade‑offs / Mitigations
Long‑term integrity – stops slow drift of the Core toward jargon, notation lock‑in, and hidden cycles.Authors must check the applicable guard-rails before submission.
Stable yet evolvable ecosystem – Core meanings can remain stable while Tooling and Pedagogy change independently.Contributors may find the guard-rails restrictive in the early stages of a contribution. Examples in the Pedagogical Companion show how to work within them.
Trust & auditability – readers can inspect the declared meaning, dependency and bias boundaries.Review adds work. The four rules identify what the review covers.

E.5:8 - Rationale

The four guard-rails turn abstract Pillars into constraints on wording, notation, dependency and bias. Grouping them here gives newcomers one entry to the applicable rule, identifies any needed amendment, and supplies shared requirements for optional automated checks.

They instantiate Pillars P-1, P-2, P-4 and P-5 and follow the precedence order defined in E.3.

E.5:9 - Relations

  • Comprises:
    • pat:guard/devops‑firewall (E.5.1) – GR‑1
    • pat:guard/notational‑independence (E.5.2) – GR‑2
    • pat:guard/unidirectional‑dependency (E.5.3) – GR‑3
    • pat:guard/bias‑audit (E.5.4) – GR‑4
  • Depends on:
    • pat:constitution/pillars (E.2)
    • pat:constitution/principle‑taxonomy (E.3)
  • Constrains: every Core, Tooling, and Pedagogy artefact and all DRRs.

E.5:End

Referenced in the corpus

17 literal mentions in other sections. Read their context to establish the relation.