Loro

Route Common Tasks

• “Build a collaborative document model / choose data types / persist history”
  • Start with containers-and-encoding.md
  • Add sync-versioning-and-events.md if version/history behavior matters
• “Debug checkout / detached mode / missing imports / event timing”
  • Start with sync-versioning-and-events.md
• “Integrate ProseMirror, Tiptap, CodeMirror, or custom rich text”
  • Start with richtext-and-editors.md
  • Add sync-versioning-and-events.md if undo/version/event behavior matters
• “Model app state with loro-mirror or loro-mirror-react”
  • Start with mirror-and-react.md
  • Add containers-and-encoding.md if schema semantics depend on container choice
• “Change wasm bindings or debug pending event flushing”
  • Start with wasm-maintenance.md
• “Decide whether Loro is even the right tool / explain tradeoffs”
  • Start with fit-and-architecture.md
  • Add performance-and-research.md if benchmark or research context matters

Execute The Task

1. Classify the task before reading everything.
2. Load one primary chapter.
3. Load at most one secondary chapter for cross-domain work.
4. Keep solutions grounded in Loro semantics:
   • choose data types by merge behavior,
   • distinguish state version from history version,
   • keep ephemeral state out of persisted CRDT data,
   • respect the binding/runtime invariants in crates/loro-wasm.

Keep Guardrails

• Do not assume CRDTs are the right fit for hard invariants, exclusivity, or authorization-at-write-time problems.
• Do not model editable text as plain strings when user intent requires merged edits.
• Do not reuse peer IDs across concurrent sessions.
• Do not confuse detached documents with detached containers.
• Do not change wasm-exposed mutators without checking pending-event flushing behavior.