Local-First Sync Conflict Lab
Rehearse and explain three-way JSON sync conflicts with deterministic strategies, fingerprints, and JSON Pointer evidence.
The problem it solves
Local-First Sync Conflict Lab [](https://github.com/loganpendragonmultiverse/local-first-sync-conflict-lab/actions/workflows/ci.yml)
Who Local-First Sync Conflict Lab is for
- Developers and maintainers who need reviewable evidence before changing or releasing software.
- Users working with local-first, sync, conflict resolution who want the documented v1.0.0 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Rehearse and explain three-way JSON sync conflicts with deterministic strategies, fingerprints, and JSON Pointer evidence.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.0.0
Capabilities below come from the current project README and release documentation.
[](https://github.com/loganpendragonmultiverse/local-first-sync-conflict-lab/actions/workflows/ci.yml)
Simulate and explain a three-way synchronization merge from base, local, and remote JSON snapshots. The local CLI classifies same, local-only, remote-only, and both-changed values; records replayable input hashes; and can model manual, prefer-local, prefer-remote, or newest-snapshot policies.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
Platforms and implementation
The public release claims only the cataloged platforms and technologies.
Supported platforms
- Windows
- macOS
- Linux
Built with
- Python
Quick start
The shortest documented path into the current release.
python -m pip install .
sync-conflict-lab examples/base.json examples/local.json examples/remote.json
sync-conflict-lab examples/base.json examples/local.json examples/remote.json --strategy prefer-local --format json --output result.jsonExit code 1 means manual conflicts remain unresolved, 0 means the selected policy produced a complete simulated result, and 2 means the inputs or command were invalid. Existing reports are never overwritten.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
Everything runs locally without accounts, telemetry, storage, or network requests. Reports may reproduce conflicting input values so they can contain sensitive data and must be protected accordingly.
This is a deterministic policy simulator, not a production synchronization engine or CRDT. It does not infer identities inside arrays, validate an application's schema, guarantee convergence across repeated real-world operations, contact a server, or write merged data back into an application.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
Everything runs locally without accounts, telemetry, storage, or network requests. Reports may reproduce conflicting input values so they can contain sensitive data and must be protected accordingly.
This is a deterministic policy simulator, not a production synchronization engine or CRDT. It does not infer identities inside arrays, validate an application's schema, guarantee convergence across repeated real-world operations, contact a server, or write merged data back into an application.
License and release
Local-First Sync Conflict Lab is published under MIT. The current cataloged release is v1.0.0, published 2026-08-03.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Local-First Sync Conflict Lab v1.0.0
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical local repository. Fingerprint: 20df158235efc353.