# Open Engineer

**An open standard for preserving engineering context.**

Open Engineer is a methodology-neutral specification that preserves the reasoning, observations, decisions, and constraints that shape engineering work. It does not replace existing engineering methodologies or tools; it provides a common language for preserving engineering understanding across disciplines.

---

## The Missing Layer

> **Git preserves what changed.**
>
> **CI preserves what was built.**
>
> **Observability preserves what happened.**
>
> **Open Engineer preserves why the system became what it is.**

Engineering artifacts often survive.

Engineering understanding often does not.

Open Engineer exists to preserve that understanding.

---

# Read the Specification

If you are new to the project, begin with the specification.

The specification is the authoritative source.

References explain.

Examples illustrate.

Presentations communicate.

Implementations implement.

---

# Repository Structure

```text
spec/               Authoritative specification
reference/          Supporting explanations and background
examples/           Practical examples and demonstrations
case-studies/       Real-world applications and validation
laws/               Engineering and editorial constraints
rfc/                Design history and architectural evolution
schemas/            Shared data structures and future interoperability
presentation/       Communication and presentation specifications
implementations/    Reference implementations
website/            Static website implementation
tools/              Supporting utilities
```

Each directory has a single responsibility.

The repository is intentionally structured to minimize overlap and reduce ambiguity.

---

# Core Principles

Open Engineer is built upon a small number of enduring principles.

* Preserve engineering context.
* Translate, don't transplant.
* Reduce ambiguity without reducing meaning.
* Separate specification from implementation.
* Name enduring concepts rather than temporary technologies.
* Favor stewardship over ownership.
* Prefer observations over opinions.
* Treat examples as teaching tools, not authority.

---

# Project Philosophy

Open Engineer is not a software framework.

It is not a project management methodology.

It is not a development process.

It is an engineering specification for preserving context across disciplines, technologies, and generations.

The goal is simple:

Future engineers should inherit understanding, not merely artifacts.

---

# Methodology Neutral

Open Engineer intentionally avoids dependence on any specific engineering methodology.

Whether work originates from Agile, Waterfall, DevOps, Systems Engineering, Lean, Six Sigma, Kanban, ITIL, civil engineering, aerospace engineering, manufacturing, or future methodologies, Open Engineer seeks to preserve the engineering reasoning that produced the work rather than the methodology itself.

---

# Supplemental Overview

The specification is the authoritative source.

For readers who prefer a guided introduction, a supplemental overview video is available.

> **Supplemental Project Overview (Video)**
>
> *(Add the embedded video or repository link here.)*

The overview is intended to introduce the project.

It does not replace the specification.

---

# Contributing

Open Engineer values thoughtful refinement over rapid expansion.

Contributions should:

* Reduce ambiguity.
* Strengthen existing concepts.
* Preserve architectural consistency.
* Respect repository boundaries.
* Favor enduring concepts over temporary technologies.

Every contribution should improve the specification without increasing unnecessary complexity.

---

# Current Status

**Release Candidate:** RC3

Current focus:

* Editorial refinement
* Case studies
* Independent validation
* Practical demonstrations
* Long-term stewardship

The emphasis has shifted from creating concepts to refining language and validating the specification through real engineering work.

---

# License

See the repository license for usage and distribution terms.

---

*"Engineering understanding should be as durable as the systems it creates."*
