[amabito]

The Markdown-over-database choice makes sense for document-shaped output.

The harder problem seems to be concurrent semantic edits. Git-style merging works for code because conflicts are syntactic. With prose, two agents can produce logically conflicting conclusions without triggering a merge conflict.

How does Sayou reason about semantic divergence when Agent A updates a research note while Agent B is drafting against an older snapshot?

[syumpx]

Current approach is last-write-wins with version history - simple but doesn’t solve concurrent edits.

I don’t think auto-merge is the right default for prose/research (unlike code where Git’s merge works). When Agent A writes strategic memo concluding X while Agent B writes concluding NOT-X, merging both is worse than surfacing the conflict.

Thinking the right model is: ∙ Optimistic writes (current behavior) for most cases ∙ Explicit locks for high-stakes docs agents know they’re collaborating on ∙ Diff tooling for post-hoc resolution when conflicts do occur

thanks for asking a great question. whats your thoughts?