Architecture
Ownership, runtime coordination, authoritative data movement, and algorithm routes.
HEAD a63778eLoad only the missing decision:
| Question | Route |
|---|---|
| Which layer or public boundary may own this dependency? | Ownership and dependency direction |
| How does LLM- or human-authored ANSI text become editable Canvas cells and return to text? | LLM–Human Text Protocol |
| How does pasted ANSI, Markdown, or raw text become Canvas cells? | External text rendering |
| Does this belong to command, tool, keymap, extension, or Host coordination? | Editor runtime |
| Which state is authoritative, projected, persisted, synchronized, or undoable? | State and data flows |
| Which rule computes text cells, coordinates, rendering, selection, slides, or structured layout? | Algorithm routes |
| How are graph relationships mapped onto the Unicode cell grid? | CharGraph layout |
| Which business capability owns the change? | Domain reference |