Skip to content
How it works

How Synapse fits your delivery loop

Synapse links your org, workspaces, and Linear so delivery stays traceable.

Timeline diagram: Connect Linear, Distill tasks, Preview sync, Apply writeback, and Audit with correlation id.
Step 1

Connect Linear

OAuth per organization ties Linear to your billing tenant. One integration surface for the delivery org—not scattered personal tokens.

Step 2

Distill tasks

Issue text maps to distilled-task.v1 fields: summary, requirements, definition of done, and clarification questions.

Diagram: a vague Linear issue becomes structured distilled task fields through Synapse distillation with audit logging.

Bug triage from a vague client report

Riverside Retail (fictional)

Before — Linear issue

RIV-1842

checkout broken??

client says when they hit pay nothing happens. might be safari. ops saw it too last week. need fix before thursday launch — screenshot in slack thread

client-report

After — Distilled task

Fix silent checkout failure on Safari payment submit

Payment submit on checkout fails silently in Safari; users see no error and orders do not complete.

Bug · 4 pts · frontend, backend, qa

  • ·Failed payment shows user-visible error with support reference id
  • ·No silent no-op on pay click in Safari

2 clarification questions

Step 3

Sync with preview

Proposed Linear changes appear in a preview panel. Operators apply when ready; conflicts block silent overwrite.

Diagram: delivery workspace and client workspace under one organization with preview-then-apply status sync and preserved client-only fields.

Cross-workspace status alignment with preview

Northwind Studio (fictional)

Before — Linear issue

NWS-441

sync status to client board

when we mark done in delivery workspace it should show on client linear too. right now PM copies status by hand. don't overwrite client-only fields

syncworkflow

After — Distilled task

Preview status sync from delivery to client workspace

Sync task status from delivery workspace to client workspace via preview-then-apply, preserving client-only fields.

Revision · 4 pts · frontend, backend

  • ·Operator can preview and apply status sync in one flow
  • ·Conflicts block silent overwrite

1 clarification question

Step 4

Audit by default

Org actions and automation runs land in an immutable audit log with correlation IDs across HTTP and background jobs.

Timeline diagram: Connect Linear, Distill tasks, Preview sync, Apply writeback, and Audit with correlation id.

Ready to run delivery on one control plane?

Connect Linear, try distillation on the Free plan, and see sync preview before anything writes back.