katrix-engine: sync pipeline — sliding-sync + v2 sources, reducer, in-memory stores #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The M0 core loop per §3.3/§10.3: SyncSource implementations for sliding sync and v2 fallback with capability-negotiated selection (§3.3, §10.3.2, §4); reducer committing facts + cursor in one store transaction, cursor last (CR-1); in-memory store-port impls (§3.5); change bus post-commit; quarantine for malformed events; delivery policy AtLeastOnce/AtMostOnce. CRs binding: CR-1, CR-2 (source equivalence), CR-3 (unknown events undropped), CR-17 (cancellation never corrupts/advances), CR-4 (sync loop honors server delay). Tests reference CR ids.