0001 - ATON Vision
Status
Accepted
Date
2026-07-19
Context
Modern engineering relies on a large number of specialized tools for requirements management, systems modeling, testing, project management, risk management and documentation.
Although these tools often describe the same system, they maintain separate data models and repositories.
This fragmentation leads to
- duplicated engineering knowledge
- inconsistent traceability
- disconnected workflows
- vendor lock-in
- limited interoperability
A common engineering foundation is required.
Decision
ATON shall be developed as an Open Engineering Operating System (EOS).
The Kernel provides domain-independent engineering services.
Engineering capabilities are implemented as extensions built upon the Kernel.
The central data model of the Engineering Operating System is the versioned Engineering Knowledge Graph.
Rationale
Separating the engineering infrastructure from engineering capabilities
- provides a stable Kernel
- enables reuse across engineering disciplines
- encourages extensibility
- reduces duplicated functionality
- supports long-term maintainability
The Engineering Operating System becomes the common platform upon which engineering capabilities are built.
Consequences
Positive
- Clear separation between infrastructure and capabilities
- Stable architectural foundation
- Consistent engineering services
- Extensible plugin architecture
- Shared Engineering Knowledge Graph
Negative
- Requires a well-defined Kernel architecture
- Requires strict separation between Kernel and Capabilities
Architectural Principle
The Kernel provides generic engineering infrastructure.
Capabilities provide engineering functionality.
Capabilities depend on the Kernel.
The Kernel never depends on Capabilities.
Notes
ATON is not intended to replace every engineering tool.
Its purpose is to provide a common engineering platform based on a versioned Engineering Knowledge Graph.
ATON is an Open Engineering Operating System built around a versioned Engineering Knowledge Graph.