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 21:55:20 UTC

E.5.1 - DevOps Lexical Firewall

Status: Stable

E.5.1:1 - Problem frame

Use this pattern when Core prose mentions an implementation detail, such as a file format, build command or runtime flag. Determine whether that detail is incidental to the concept or necessary to the conformance rule for a named publication form, protocol or grammar.

E.5.1:2 - Problem

An incidental tool dependency can force a Core concept to be revised when the tool changes, even though the concept does not. It can also make earlier editions harder to interpret. A blanket ban on concrete syntax causes a different loss when the syntax defines how to test the subject’s conformance.

E.5.1:3 - Forces

ForceTension
ContinuityConcepts must survive tool turnover.
Pedagogic clarityExamples need concrete detail, but too much hard-codes a technology.
Cross‑domain reachPhysical‑system engineers and knowledge‑theorists use different stacks.

E.5.1:4 - Solution

Apply the Lexical Firewall to the subject the text governs:

  1. Keep abstract definitions independent of incidental machinery. A Core definition SHALL NOT make an unrelated tool, file format, command or deployment arrangement necessary to identify or use its conceptual subject. Describe that subject directly. Place the implementation in Tooling.

  2. Retain the syntax needed to test conformance of a concrete subject. When a rule governs a publication form, protocol or grammar, it MAY state the exact syntax needed to apply that subject’s conformance condition. Name the subject and its edition or use boundary. The exception applies only where replacing the syntax with a conceptual alias would remove an operative condition.

    A heading marker in a heading grammar qualifies. An unrelated build command does not. Calling executable code a grammar example supplies no exception.

  3. Keep executable teaching in its teaching or Tooling source. A Core concept needing a runnable illustration cites the teaching or Tooling artifact by conceptual name. Runnable teaching programs, concrete execution paths and commands remain there. A subject-defining syntax fragment under item 2 is not a runnable illustration merely because it appears in a code span or block.

    Mathematical expressions follow E.5.2: explain their interpretation, operation and prerequisites, with semantic mapping when compared or translated.

  4. Use aliases where they preserve the rule. An incidental technical term can be defined in a Tooling Glossary and cited by conceptual alias. Preserve necessary spelling under item 2 when the concrete subject’s condition would otherwise become untestable.

Non‑normative automation. Machine checks MAY exist in Tooling. They are advisory and MUST NOT be imported into the Core.

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

ScenarioU.System exampleU.Episteme example
Normative text“Identify the system’s actual constituents and the relations by which they form the whole.” (No modelling-language syntax.)“Identify the claim content, the entity it concerns, and the effective reference scheme.” (No proof-engine syntax.)
Illustrative linkA modelling profile resides in the Tooling family. Core cites it as “the reference system‑profile”.A linting routine lives in Tooling. Core cites it as “the reference episteme‑checker”.

E.5.1:5.1 - Four placement decisions

Role of the detail in the rule or examplePlacement and first action
E.8 H-1/H-2/H-6/H-9 govern this edition’s Markdown pattern headings: level-2 ##, the identifier/title separator shown in <FullId> - <Title>, and ### <PatternId>:End.Keep those necessary syntax fragments in E.8. The author can write and check the heading and sentinel. Using “the reference heading mark” would lose the condition. The rule is about this publication form, not the ontology of the described System.
An unrelated abstract System definition requires a container-build command.Move the command and its operational prerequisites to Tooling. Recover the System definition independently of that implementation.
A runnable program demonstrates a conceptual method.Keep the program in its teaching/Tooling source and cite its conceptual role from Core. Calling it a grammar example does not change its role.
A Euclidean construction expression supplies a reasoning step under the subject Method.Keep the expression where its meaning, construction operation and prerequisites are supplied under E.5.2. Treat it as a step in the reasoning. When comparing expressions, establish or retain the mapping that preserves the meaning used in the comparison.

E.5.1:6 - Conformance Checklist

IDRequirement
CC‑LFW.1A Core pattern excludes incidental implementation dependence. Exact syntax is allowed only when necessary for the conformance condition of its named publication form, protocol or grammar, under a stated edition/use boundary.
CC‑LFW.2Executable illustrations are cited by conceptual name and kept in their teaching/Tooling source. A necessary subject-defining syntax fragment follows §4 item 2. Keep it when an alias would lose the condition.
CC‑LFW.3Core pedagogical examples may describe behavior. Runnable teaching code remains outside Core. Mathematical expressions retain E.5.2 interpretation/operation duties. A label such as “example” alone grants no syntax exception.

E.5.1:7 - Consequences

BenefitsTrade‑offs / Mitigations
Core definitions avoid incidental dependence on a tool generation.Move incidental implementation details and runnable teaching code to Tooling or Pedagogy. Retain necessary governed-subject syntax under §4 item 2 and operative mathematics under E.5.2.
A token scan can locate places to inspect.Judge conformance by the subject and its operative condition. An allow-list alone cannot tell you whether the implementation dependence is incidental.

E.5.1:8 - Rationale

Keeping incidental implementation details outside abstract definitions supports P-1 Cognitive Elegance, P-2 Didactic Primacy and P-5 FPF Layering. The subject-sensitive boundary keeps abstract concepts portable while allowing a form-specific rule to state the syntax that its reader must use.

E.5.1:9 - Relations

  • Parent umbrella: pat:constitution/guard‑rails (E.5)
  • Constrains: every pattern in Conceptual Core
  • Instantiates pillars: P‑1, P‑2, P‑5

E.5.1:End

Referenced in the corpus

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