openengineer/spec/oe-0003-engineering-context.md

1.9 KiB

OE-0003: Engineering Context

Status: Draft Depends on: OE-0002 (Core Vocabulary) Phase: The Bedrock Phase

Overview

This may be the single sentence that defines the project:

Open Engineer is an open standard for preserving engineering context.

Everything else extends from that.

Definition

Engineering context is the full set of information required to understand why an engineering decision was made, what alternatives were considered, and what constraints shaped the outcome.

Context is not merely background information. It is the decision-shaped record of an engineering process. Without context, a decision is an isolated artifact — understandable in isolation but disconnected from the reasoning that produced it.

Components of Engineering Context

Engineering context includes, but is not limited to:

  • The observations that prompted the work
  • The constraints (technical, environmental, temporal, economic) within which decisions were made
  • The alternatives that were considered and rejected, and why
  • The assumptions that were made explicit and implicit
  • The verification methods used to confirm the outcome
  • The relationship of this work to prior and subsequent work

Why Context Matters

When context is lost, engineers must re-derive understanding from first principles every time. This is wasteful and error-prone. Preserving context means that future engineers can begin where their predecessors left off, rather than starting over.

This is the thread made concrete. Context is the substance that the thread carries.

Context as the Unit of Preservation

If Open Engineer has a unit of measurement, it is the context. Not the document. Not the specification. The context — a complete, self-contained record of engineering reasoning.

Every other element of the standard serves the goal of capturing, preserving, and transmitting engineering context.