What it is
Managed exactly like code
The industry settled this argument twenty years ago. Text in a repository can be branched, diffed, reviewed and rolled back by tools every engineer already has. Your architecture belongs in that same place, under those same tools.
See the format →# monday
strategy.arch element finance.goal.reduce-cost
# friday, after a reorganisation
domains/finance/
goals/q3.arch element finance.goal.reduce-cost
same id, same model, same diagrams. zero diff in meaning.
- Files, not recordsThe model is text in your repository. There is no other copy of it anywhere, and nothing to export.
- Move an element, a file, a whole treeCut a statement out of one file and paste it into another. Move a directory. Split one file into ten. The model does not notice, because identity is the name, never the path.
- Views move the same wayA view is a file too. Store it wherever it makes sense this quarter and every diagram it draws is unchanged.
- Reorganise as often as you likeThe structure of the repository is yours to keep tidy. It carries no meaning, so rearranging it costs nothing.