API sync reliability
Bidirectional state without duplicate chaos.
A deterministic proof for Craft.do ↔ Todoist-style synchronization. It focuses on the hard part: stable identity mapping, idempotent reruns, state propagation, collisions, and repair behavior.
Verified locally
7/7 tests passing
What it demonstrates
- Stable source/target ID mapping
- Duplicate prevention
- Bidirectional completion updates
- Collision rejection and repair path
Proof policy ──────────── • Self-directed portfolio work • No invented client attribution • Tests must pass before publication • Buyer-specific claims remain scoped • Live integrations are verified against current APIs before production use