Problem
Guarantee that every row arriving via Electric sync was written by its legitimate owner, and that the state converges correctly when that owner writes from multiple devices.
The owner is responsible for ordering their own writes. The receiving peer only needs to verify authenticity and apply the owner’s stated ordering — it does not need to reason about time independently.
> Evolved into:
> - Integrity — the integrity triad (deleted_flag, owner_timestamp, sign_b64), trust bootstrap, PoP relationship
> - Data Versioning — hash-linked version chains, two-table pattern
Solution
Every piece of information in the system has an owner (author), who is eligible to update/delete it.
Data can be unversioned (integrity triad only) or versioned (integrity triad + hash-linked history chain in a two-table layout).
See the evolved design docs for field-level details, schemas, examples, and algorithms.
