Problem
Imported evidence, local edits, and LLM proposals can conflict; disconnected clients must not lose or silently overwrite user intent.
Python · web/Android · offline-first · reliable synchronization
Imported evidence, local edits, and LLM proposals can conflict; disconnected clients must not lose or silently overwrite user intent.
Imported evidence, local edits, and LLM proposals can conflict; disconnected clients must not lose or silently overwrite user intent.
Offline clients replay commands after restarts; external observations, local state and model proposals must not share mutation authority.
Separated external observations, canonical state, and derived plans; client operation IDs and atomic server records make offline replay idempotent. Feasibility requires validated witnesses and preserves UNKNOWN where proof is missing.
Browser and native Android clients, migrations and device/release checks; the signed Android 0.8.3 release workflow passed on 10 Oct 2026. External adoption has not been established.
Operation IDs and atomic server records, explicit lifecycle conflicts, witness validation, emulator/device checks and signed APK provenance.
Canonical/evidence/projection boundaries, offline command replay, feasibility witnesses, LLM intent limits and native Android release path.