weaver, documented.
Start with the introduction, then explore how weaver works — its architecture, the hard implementation problems, access control, and AI agent design — plus reference material and the decisions on record.
Get started
Architecture
Packages, document model, reactivity, plugin contract.
Block ModelBlock data structure, Loro mapping, Effect-TS SubscriptionRef stores, the layering rule.
Hard ProblemsThe eleven genuinely-hard implementation problems.
WASM StrategyFive concrete WASM uses; the Zero pattern stolen for read-models.
Framework CompatibilityWhich UI frameworks integrate with weaver, and the WASM + Effect-TS complexity that shapes each adapter.
AI AgentPeer model, streaming, tools, multi-agent.
MentionsTagging principals (people and agents) in-document: trigger UX, mention mark, debounced MentionCreated events.
Access ControlTokens, schemas, op validation, audit, threat model, gaps.
Reference
weaver vs Lexical, ProseMirror, Tiptap, BlockSuite, others.
Lexical ParityCatalog of Lexical features mapped to weaver primitives, with the v1 outcome rubric.
Implementation GuidelineEffect-TS pattern matching, tagged errors, state ownership — the code-level conventions a reviewer can block on.
BenchmarksWhat we measure, how, the v1 pass bars, and the outcome rubric.
PlaygroundStandalone demo webapp shipped to Cloudflare Pages — what it demos and how it ships.