Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
Graphics and Canvas parity
Canvas Next implements the shared graphics foundation and the main local editing flows. It is the editor for all saved canvases and embeds, migrates older JSON at the host boundary, and shares edits through SyncService.
Current coverage
| Area | Status |
|---|---|
| Scene and transforms | Tree structure, grouping, ordering, rotation, resize, alignment, and distribution are implemented |
| Everyday editing | Selection, marquee, move, duplicate, clipboard, nudge, undo/redo, and context actions are implemented |
| Content | Shapes, pencil, rich text and labels, connectors, images, video, Macro entity cards, and document embeds are implemented |
| Presentation | Solid rendering, overlays, fit/pan/zoom, inspectors, and shared controls are implemented |
| Persistence | Versioned JSON import/export, single-winner shared initialization, snapshot/WAL recovery and live sync are connected |
| Collaboration | Production shared runtime and awareness are connected; three-peer and rendered collaboration tests exist; capacity is unmeasured |
Ownership
Graphics owns reusable document structure, geometry, commands, queries, shape contracts, and optional browser/Solid/Loro adapters. Canvas owns tools, shortcuts, Lexical, colors and defaults, assets, Macro content, permissions, persistence, migration, sharing, and product rollout.
Remaining priorities
- Expand legacy import coverage with explicit diagnostics for unsupported records.
- Lock down durable artwork colors separately from theme-driven application UI.
- Extend collaboration with character-level rich text, gesture rebasing, and measured multi-user capacity.
- Add high-value whiteboard gaps such as snapping, touch, crop, frames, export, and libraries as separate checkpoints.
- Measure mixed-content scenes before adding broad indexing or culling systems.
Do not block production integration on every optional parity feature, and do not copy the legacy or Excalidraw data model into the new transform tree. Each new renderer must preserve shared paint order, reverse hit order, and stable mounted identity.
See the Canvas architecture, legacy bridge, graphics README, and Canvas Next README.