Architecture
Ownership, runtime coordination, authoritative data movement, and algorithm routes.
HEAD a63778eLoad only the missing decision:
| Read this page when | A change crosses a layer, state boundary, rendering boundary, or execution boundary. |
|---|---|
| First answer | Which architectural question is unresolved? |
| Owner | The route below owns the decision; the linked source and tests own implementation and verification. |
| Boundary | This page routes architecture questions; it does not duplicate the selected contract. |
| Follow-up | Choose one question below, then stop when its authority resolves the 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 |
| How does Canvas read, search, and write the original Cell surface? | Canvas reading, Canvas searching, and Canvas writing |
| How are live Canvas tools composed and discovered by browser agents? | WebMCP |
| How are retired Blackboard and Structured documents converted or retained? | Blackboard retirement |
| 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 |