Overview
The existing database live demo uses demo-only Postgres/MySQL mappings. It is accessible without login, billing, API key, or account creation.
The demo story is intentionally conservative: Postgres/MySQL remains the source of truth, Synapsor reads selected rows through least-privilege live-read mappings, records evidence and query audit, stages risky changes as proposals, and keeps writeback behind a trusted worker boundary.
Before a run, the page shows a source-data access preview: seeded Postgres/MySQL rows on one side, then Synapsor-visible mapped fields, denied fields, trusted SESSION values, and generated context/capability/workflow safety-contract names on the other.
After each run, the demo starts with a plain result summary: source, rows read, tables touched, kept-out review fields, whether the agent had SQL access, whether the source database changed, proposal/writeback status, and replay availability.
Readable evidence rows, query-audit records, proposal diff, writeback boundary, and replay status are shown before advanced technical handles. Handles stay collapsed until a developer wants to inspect them.
The public MySQL lane is read-only in the seeded visitor experience. It still demonstrates source mapping, safe live reads, evidence, query audit, and replay. Signed-in workspaces can configure reviewed MySQL proposal writeback mappings separately.
The public page shows the review states and trusted writeback preview, but public visitors cannot approve or apply writeback. Real approval/writeback happens from an authenticated workspace or customer worker.
CDC/mirrored subsets are not part of this public demo. CDC remains private preview/dev-test/soak work until production monitoring, retention cleanup, restore semantics, fail-closed operations, and signoff are complete.
Existing DB plus Synapsor
The database you already run stays in place. Synapsor adds the reviewed agent boundary.
- customer data
- contracts/invoices/orders/payments
- normal app transactions
- ORM and migrations
- source-of-truth write path
- live-read mapping
- hidden tenant/session scope
- reviewed capabilities
- evidence bundle
- query audit
- write proposal
- replay/writeback status
Developer notes
- Use the public /demo/existing-db page for the seeded visitor experience.
- Use live-read mappings for current customer setup; do not present CDC as the public connector path.
- Do not expose source credentials, admin URLs, secret refs, or raw SQL tools to the model.
- Treat proposal writeback as a trusted worker step after approval, not an automatic model write.
- Keep Postgres/MySQL as the source of truth unless a customer deliberately migrates data later.