Every project, on a single map.
Structure knowledge scattered across docs and chat, together with the history behind decisions. Understand the impact of changes and apply past decisions and their rationale to new ones.
Information keeps growing. What you can decide with does not.
Day to day, information accumulates in your documents. But what gets left behind is only the deliverable. The reasoning and context — “why was this change made?”, “what were we assuming?” — does not.
Change impact can't be traced
Change one spec, and the designs, tests, and procedures built on it sit somewhere in the project. Without recorded relationships, neither people nor AI can follow the trail.
No view of who's moving what
Which areas belong to whom, how far along they are, and where work has stalled — none of it is visible without asking around.
The reasoning behind decisions is lost
The discussion behind a decision scrolls away in chat; why it was decided survives only in someone's head.
Your everyday work becomes a map of your project.
There is no need to funnel all input into one place. We link the information your daily work produces to its relationships and history, building a map that informs decisions and action — behind the scenes.
- Your usual toolsDocs, chat, meetings, task management
- SynTopicLinks information to its relationships and history
- A map of your projectDecisions and actions draw on the same facts and context
* More tools coming
Structure information and context. Support decisions. Carry knowledge forward.
01 — Build the map
Information and context, in one unit.
Not just the information itself — its relationships, history, and the reasoning behind decisions, bound into one unit: a Topic. Connected together, Topics draw the entire project as a single map.
In the requirements, supported languages changed: Japanese only → Japanese and English. An estimate of "3 person-months of development" assumed the original scope. Is it still valid?
02 — The map comes to you
No need to go looking. The questions come to you.
When something changes, the map's relationships are traced to find where the impact may reach. Only what needs a decision arrives at the person who can make it, along with how it got there.
- No more chasing things down — focus on the decisions themselves
- Answers accumulate on the map as records, with their evidence
03 — Reuse the map
A map you built once becomes the next starting point.
The map, and the flow of checks running on it. A map that worked can be handed to the next project or another team as it is.
Your project, too, on a single map.
We'll send early-access invitations and product updates to those who register, in order.