1.4 KiB
Communication Principles
Status: Draft Phase: The Bedrock Phase
Overview
These principles govern how Open Engineer communicates its ideas — both within the standard's own documents and in any implementation or derivative work.
1. Observe, Don't Preach
Open Engineer does not seek to tell engineers what to think. It seeks to preserve how engineers arrive at understanding.
The standard documents process, not doctrine. It shows the path to understanding, not the destination as a fixed point.
2. Examples Carry Load
Examples are not decorations. They are transportation.
Every communication from Open Engineer should use examples to bridge from the unfamiliar to the familiar. A principle stated without an example is incomplete.
3. Structure Is Content
The arrangement of information is itself information. A well-structured document communicates not just through its words but through its architecture — the ordering of ideas, the nesting of concepts, the dependency relationships between sections.
4. Universality Through Translation
Open Engineer communicates in engineering language. It does not adopt the language of any particular philosophy, culture, or tradition. When it draws from a tradition, it translates the observation into universal engineering terms, making it accessible to all engineers regardless of background.