architecture-diagramlisted

# Drawing the architecture diagram Ensemblr keeps an architecture diagram of every workspace at **`.ensemblr/architecture.json`**, committed alongside the code it describes. The user opens it from the tab strip. **Nothing derives it.** The app ships no scanner: a workspace nobody has drawn has no diagram at all, and its pane shows an empty state whose button opens a fresh chat and asks for one — which may well be how you got here. Producing it is entirely your work, and what you store is what the user sees until somebody stores something else. Read and write it through the two ops below rather than by editing the file directly — they validate the document, and the update op refreshes any diagram tab the user has open. So the job is one of two, depending on what the read answers: **draw one from the codebase** when there is none, or **edit the one that exists** when there is. Either way the target is a drawing a maintainer would make, not a dump of the folder tree. ## It is a drawing for people, not a map for you The diagram exists so a human can see the shape of the repository at a glance. It is **not a source of truth about the code, and you must never treat it as one.** You curate it; you do not consult it. Concretely: never answer a question about the codebase from the diagram, never decide what to edit or where something lives because a node says so, and never report its contents as fact. It is lossy by design — nodes are dropped as noise, edges are omitted, labels