What you're trying to do
When multiple agents, teammates, branches, or repos each have their own .vouch/ directory, I want a deterministic way to reconcile them, because today the multi-agent story works best on one shared filesystem.
For example, Team A and Team B may both approve claims in separate repos, then later want to combine their reviewed knowledge. Right now that means bundle export/import or git merge, but conflicts still need manual interpretation and there is no first-class “what will happen if I merge these KBs?” workflow.
What you've tried
Existing bundle features help move a KB snapshot:
vouch exportvouch import-checkvouch import-apply
These are useful for portability, but they do not fully solve distributed KB convergence. They can identify new, identical, and conflicting files, but they do not provide a semantic merge workflow for diverged .vouch/ directories, decided proposals, superseded claims, contradictions, or audit implications.
Git merge is also possible, but it leaves vouch-specific conflict handling up to the user.
Suggested shape
Add a first-class sync/merge workflow, for example:
vouch sync-check <path-or-bundle>
vouch sync-apply <path-or-bundle> --on-conflict fail|skip|propose
What you're trying to do
When multiple agents, teammates, branches, or repos each have their own
.vouch/directory, I want a deterministic way to reconcile them, because today the multi-agent story works best on one shared filesystem.For example, Team A and Team B may both approve claims in separate repos, then later want to combine their reviewed knowledge. Right now that means bundle export/import or git merge, but conflicts still need manual interpretation and there is no first-class “what will happen if I merge these KBs?” workflow.
What you've tried
Existing bundle features help move a KB snapshot:
vouch exportvouch import-checkvouch import-applyThese are useful for portability, but they do not fully solve distributed KB convergence. They can identify new, identical, and conflicting files, but they do not provide a semantic merge workflow for diverged
.vouch/directories, decided proposals, superseded claims, contradictions, or audit implications.Git merge is also possible, but it leaves vouch-specific conflict handling up to the user.
Suggested shape
Add a first-class sync/merge workflow, for example: