Architecture model
Stable IDs, hierarchy, relations, and the desired-state contract.
The Architecture model separates semantic identity from presentation. A node ID remains stable while its name, parent, or owning repository changes. Canvas positions are computed by the graph and never written into the desired-state model.
Stable node identity
- id: host-resource-monitoring
name: Resource Monitoring
kind: feature
parent: devbox-host-control
owner: DotNaos/devboxMoving this responsibility changes only parent. Renaming it changes only name. Consumers should join data and documentation through id, never through a label or filesystem path.
Validation
The repository rejects duplicate node IDs, missing parents, parent cycles, duplicate relations, and relations whose endpoints do not exist. The JSON schema defines the storage shape; semantic validation covers the constraints that need knowledge of the complete graph.