dcosnet
/
openengineer
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
openengineer/ROADMAP.md

2.1 KiB
Executable File
Raw Blame History

Roadmap

Current Phase: The Bedrock Phase

Every sentence accepted during this phase is intended to support everything built above it. The specification leads. Everything else follows.

RC2 Objective

Reduce ambiguity without reducing meaning.

RC2 is compression, not expansion. Every refinement should either eliminate ambiguity or strengthen traceability.

RC2 Exit Criteria

RC2 is complete when:

  1. Every top-level directory has exactly one responsibility.
  2. Every canonical term has one definition (in OE-0002).
  3. Every definition survives the Enduring Concept test (Law 5).
  4. Every example passes the Self-Fading Example principle.
  5. Every implementation derives from a specification rather than inventing one.
  6. An independent reviewer can reconstruct the architecture without speaking to the project authors.

Specification Dependency Tree

Charter (OE-0000)
  -> Foundation (OE-0001)
    -> Core Vocabulary (OE-0002)
      -> Engineering Context (OE-0003)
        -> Observation (OE-0004)
          -> Survey (OE-0005)
            -> Understanding (OE-0006)
              -> Verification (OE-0007)
                -> Decisions (OE-0008)
                  -> Stewardship (OE-0009)
                    -> Inheritance (OE-0010)
                      -> Amendment (OE-0011)

Nothing later may redefine an earlier layer. Only extend it.

Change Workflow

Observe -> Draft -> Review -> Accept -> Freeze (RC) -> Reference

Document status lifecycle: Draft -> Proposed -> RC -> Accepted -> Deprecated (defined in OE-0000).

Future Phases

  • Implementation Phase — Interchange formats, context record tooling, presentation layers
  • Integration Phase — Context record systems for specific engineering domains
  • Community Phase — Open contributions, discipline-specific extensions

Constitutional Governance

OE-0011 (Amendment) defines a two-tier amendment process. Technical content follows the standard change workflow. Governance content (Laws, Editorial Principles, Status Lifecycle) requires additional constraints including independent review. See OE-0011 for details.