Operator journey
One continuous path: bring your agent, keep the work, and decide what becomes true.
01of the path
Your agent works. The work stays yours.
Bring the tools you already use. Synap gives their useful work a durable place to continue.
What Synap enables
- Context that survives the next session
- Work that stays as owned, linked records
- Changes that wait for your approval
Start with the surface you need
Three doors. One owned record.
All three connect to the same Data Pod.
02of the path
Bring anything in. Keep every source.
Notes, vaults, Notion, Drive, links, and agent results land raw in your Data Pod — ready to evolve with provenance still attached.
From outside in
Every path lands in one owned pod.
In-app capture, imports, connectors, and agent results — same pod.
03of the path
Bring any agent into the same context.
Cursor, Claude Code, ChatGPT or Codex, OpenClaw, Hermes—and the next tool you choose—can work from the same owned record.
04of the path
Your agent proposes. You decide what becomes true.
Signal becomes a reviewable proposal: structure stays outside truth until you approve it.
05of the path
One record. Many surfaces.
Open the same Atlas launch as a list, board, document, or workspace — the entities stay the same.
- LRLena RuizDesign leadWarm
- MCMarcus ChenEngineeringHot
- AOAya OkonkwoOperationsNew
- SOSam OkadaPartnerWarm
- PNPriya NairLegalHold
- JHJon HaleSalesHot
06of the path
Ask with the work already in the pod.
Your question carries project, sources, and decisions with it — not a blank chat.
What should we change before the Atlas launch?
07of the path
A hard question becomes a bounded session.
When one reply is not enough, promote the ask into a live goal, checkpoint, and scope you accept first.
What should we change before the Atlas launch?
Session · Atlas launch
Accept scope before the run starts.
08of the path
Watch the work happen—and bring another agent in.
Agents share one linked channel. Sources, generated cells, artifacts, and proposals stay visible while the session advances.
Atlas launch · live
One channel. Inspectable work.
09of the path
A finished session becomes a process you can run again.
Keep the approved steps and provenance. Next time starts from a playbook — with the same review points.
Session · Atlas launch · done
Launch readiness review
Playbook · ready to run again
Collect current evidence
Compare constraints
Propose changes
Review and publish
10of the path
Run it on your terms.
Install free, start managed, or self-host. The Data Pod is the same — the deployment choice does not change the journey.
Two doors. Same Data Pod.
Install, host, or build in the open with us.
Or self-host anytime — MIT, same pod model.
11of the path
Then build on top of it.
Your Data Pod is the substrate. Packages, apps, and open-source backends plug in — create anything on the same owned record.