1.3 KiB
Executable File
Communication Principles
Status: Draft Version: 0.2.0-draft Phase: The Bedrock Phase
Overview
These principles govern how Open Engineer communicates. They are subordinate to the Engineering Laws (laws/engineering-laws.md) and the Editorial Principles (reference/editorial-principles.md). Where this document conflicts with either, those documents take precedence.
1. Structure Carries Meaning
The arrangement of information conveys meaning that the individual components do not. For the authoritative definition and engineering manifestations, see OE-0001 (Foundation), Section: Structure Carries Meaning.
2. Universality of Language
Open Engineer communicates in engineering language. When it draws from a domain outside engineering, it translates the observation into engineering terms (see reference/editorial-principles.md, Translation). The standard must be accessible to any engineer regardless of their cultural or philosophical background.
3. Precision Over Rhetoric
Specification documents use declarative, testable statements. Rhetorical techniques — negation lists, emphatic repetition, appeals to intuition — are not prohibited in examples or presentation layers, but they have no place in specification definitions. A definition must be testable, not evocative.