E.5:4 - Solution — the Four Guard‑Rails
FPF establishes four architecturally enforced guard‑rails that every Core, Tooling, and Pedagogy artefact must obey. They function as an “immune system” resisting each entropic pull. Scope note (conceptual, not lint). These guard‑rails regulate the architecture of thought—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‑Rail | Protects against |
|---|---|---|
| GR‑1 | DevOps Lexical Firewall | Pull of implementation, governance, automation, and DevOps concerns |
| GR‑2 | Notational Independence | Notation lock‑in |
| GR‑3 | Unidirectional Dependency | Convenience cycles |
| GR‑4 | Cross‑Disciplinary Bias Audit | Disciplinary monoculture |
Concrete rules for each rail live in patterns E.5.1 – E.5.4.