Roadmap

This page records intended direction, not a commitment or release schedule. Items are provisional and may change as implementation and security review clarify priorities.

Intended direction

• Improve documentation and examples around CRDT conflict modeling, authoritative projections, persistence, and bounded document growth.
• Continue hardening sync, room behavior, reconnect handling, and application validation through focused tests.
• Explore phase-3 wallet-to-wallet work that could address authenticated identity and E2E network integration; generic E2E wiring is not complete today.
• Keep fork, merge, persistence, and compaction behavior explicit at epoch boundaries.

Explicitly provisional

Collaborative Canvas, Virtual Tabletop, and Planning Board are recipes, not scheduled shipped products. Marketplace, privacy, and fair-shuffle features should not be inferred from the current examples. In particular, Cuttle's honest-dealer model is not intended to become a fairness guarantee without a separate protocol and review.

Changes should preserve the single engine.dispatch() mutation path, strict TypeScript settings, and the Apache 2.0 licensing model.