UAF‑Open is a tool‑neutral, ASCII‑stable reference architecture repository for expressing, validating, and tracing enterprise architectures from strategic intent through operational behavior to solution realization and actual deployed resources.
The goal of v0.1 is simplicity: a minimal but complete causal chain, two tiny examples, and a validator that enforces architectural correctness.
UAF‑Open provides:
- A minimal metamodel
- Typed relations
- Small, readable examples (goat + digital service)
- A machine‑checkable causal closure
- Basic validation rules
- Simple Mermaid rendering for diagrams
It is not a full UAF 1.3 implementation.
It is a minimal, working subset designed for clarity, portability, and correctness.
Every architecture model in this repository must satisfy:
Capability
→ OperationalActivity
→ Resource / Service (Realization)
→ ActualResource (Evidence)
This is enforced by the validator and expressed in the examples.
uaf-open/
├── README.md
├── metamodel/
│ ├── core.yaml
│ └── relations.yaml
├── examples/
│ ├── goat/
│ └── digital-service/
├── mappings/
│ └── causal-closure.yaml
├── validation/
│ └── rules.yaml
└── render/
└── mermaid/
Defines the minimal vocabulary:
- Capability
- OperationalActivity
- Service
- Resource
- Constraint
- Project
- ActualResource
Typed operators such as:
- supports
- realizes
- instantiates
- constrainedBy
Two minimal end‑to‑end architectures:
- Goat example
- Digital service example
Causal closure rules that enforce architectural correctness.
Rules that ensure:
- no dangling elements
- typed relations
- causal closure
- constraints propagate
- projects deliver realizations
A minimal Mermaid renderer with type grouping.
- Create a new model under
examples/. - Define elements in
elements.yaml. - Define relations in
relations.yaml. - Run the validator (external script or CI).
- Render diagrams using the Mermaid renderer.
This produces a portable, reviewable, tool‑neutral architecture.
- ASCII‑stable: no proprietary formats.
- Tool‑neutral: SysML, UML, ArchiMate, C4 are adapters, not sources of truth.
- Causally complete: every realization must justify itself.
- Minimal: only the essential UAF concepts.
- Extensible: Relationalism, formal methods, and adapters can be added later.
v0.1 is intentionally small.
Future versions may add:
- RDG substrate
- formal proofs
- additional viewpoints
- adapters for SysML‑v2, UML, ArchiMate
- richer examples
Future work: Plan RDG for v0.2