Overview
Synapsor supports two branching modes. For data stored in Synapsor-native tables, branches and merges are real database operations inside Synapsor. For existing Postgres/MySQL sources, Synapsor does not branch or merge the external database. Instead, it creates a Synapsor review branch that stages the proposed change, evidence, query audit, approval state, replay record, and trusted writeback plan while the external database stays unchanged.
Rule of thumb: Synapsor-native data gets database branch/merge. Existing databases get review branches, proposals, and trusted writeback. Both flows give agents a safe place to propose changes before production changes.
Use precise labels in product UI and docs. Say Synapsor-native branch for hosted Synapsor data. Say Synapsor review branch or review branch inside Synapsor for external Postgres/MySQL proposals.
Two branch models
External Postgres/MySQL is the source of truth. Synapsor is the agent transaction and review layer.
For external database workflows, Synapsor gives users branch-like review benefits without pretending to branch their database: evidence snapshot, query audit, proposed row diff, review state, replay record, approval/policy state, trusted writeback plan, and conflict detection before writeback.
Synapsor-native tables
- Branch lives inside Synapsor as a real database branch.
- Proposed writes go to the isolated Synapsor branch.
- Settlement can approve, commit, and merge into Synapsor main.
- Synapsor applies the final merge operation.
Existing Postgres/MySQL
- Review branch lives inside Synapsor as proposal state.
- External database is not branched or merged by Synapsor.
- Policy can approve the proposal, not write directly to Postgres/MySQL.
- A customer-controlled trusted worker applies approved writeback.
Words to use
Use: Synapsor-native branch, Synapsor review branch, write proposal, approved for writeback, auto-approved by policy, trusted worker writeback, conflict-checked writeback, source database unchanged, external source remains source of truth.
Avoid claims that Synapsor creates physical customer-Postgres/customer-MySQL branches, performs direct external database merges, gives agents a Postgres branch to write into, merges external database branches, or treats green-lane external proposals as source-database merges.
Developer notes
- Show external source proposals as reviewable row diffs, not as writes already applied to Postgres/MySQL.
- Use approved for writeback for external proposals; reserve merge for Synapsor-native branches.
- For external writeback, keep source_database_mutated false until a trusted worker reports applied.
- For Synapsor-native writes, inspect branch, diff, settlement, commit, and merge state inside Synapsor.