FAQ
The questions this usually gets.
The premise, plainly: the intent is the durable artifact and the code is disposable.
Is it in my merge path?
No. It keeps the intent true; it does not gate your changes. Nothing in your CI has to move.
Does it review my code?
No. Source is read as evidence — never reported on, never edited.
Who decides what gets applied?
A person, always. The proposer is a model; every accept is one commit, reversible for five seconds.
Isn't this just git?
Git is underneath. What differs is sync at the turn boundary, grouping per agent, and a platform that reads the markdown.
Do findings work across files?
Detection is corpus-wide; each finding is anchored in one document. Where a fact belongs stays your judgment.
What if two agents write at once?
One atomic push per change, checked against the version it started from. A stale base is refused, not merged.
Does it work with my tool?
Tool-agnostic. It sits underneath the workflow tools. Any agent that writes files can push.
Does it slow my agents down?
No. Pull once before the first turn, push at the end of each. Nothing inside the reasoning loop.
Next step: point Syns at the documents your agents already read. What it finds on your corpus answers this better than a deck can.
Syns. Version control for AI agent reasoning · syns.dev