Known issues & open questions

datadata is a prototype documented honestly. Rather than hiding the gaps behind a roadmap page, this site does two things:

• Flags issues in place. Every page that touches a known gap carries a callout at the point where you’d hit it.
• Aggregates them here, with the full write-ups.

The sections

• JSON Patch RFC issues — concrete problems we’ve hit applying RFC 6902 in a collaborative engine, and the workarounds baked into datadata’s design.
• Limitations — what’s missing, each classified as by design, not yet, or open question.
• Open questions — the things we’re genuinely unsure about. If you’ve solved one of these in your engine, we’d like to hear how.

Why publish this

Two reasons. Application developers evaluating a sync engine deserve the failure modes up front — discovering them in production is how trust in this whole category dies. And sync-engine developers are the people most likely to have useful opinions about exactly these gaps; consider every page in this section an invitation.