25 lines
1016 B
Markdown
25 lines
1016 B
Markdown
# RFC-0000: Purpose
|
|
|
|
**Status:** Proposed
|
|
**Phase:** The Bedrock Phase
|
|
|
|
## Abstract
|
|
|
|
This RFC establishes the foundational purpose of the Open Engineer standard and the process by which all subsequent RFCs shall be written and evaluated.
|
|
|
|
## Motivation
|
|
|
|
Before any individual RFC is accepted, the project must agree on what an RFC is for and what it must accomplish. This RFC answers that question at the highest level.
|
|
|
|
## Proposal
|
|
|
|
The purpose of an RFC in the Open Engineer project is to propose, justify, and specify a change to the standard. Every RFC must demonstrate:
|
|
|
|
1. **Observation** — What was observed that prompted this proposal?
|
|
2. **Engineering Principle** — What principle does this proposal establish or extend?
|
|
3. **Reasoning** — Why is this principle valid and necessary?
|
|
4. **Relationship to Existing Concepts** — How does this connect to or extend the existing body of the standard?
|
|
|
|
## Scope
|
|
|
|
This RFC defines the meta-framework for all subsequent RFCs. It is the root of the RFC tree. |