Version control storyline is exploratory — tighten once git bridge ships.
Every merge exports a rooted receipt.
Overall: agents need provenance on code artifacts—not orphaned zip uploads. This product: git-shaped flows where merges are signed intents, auditors can follow Merkle paths, and spend aligns with pushes without detouring through SaaS dashboards.
git graph abstraction · illustrative
- Branch policies expressed as EIP-712 constraints
- Large binaries ride alongside object storage primitives
- Auditors diff Merkle proofs without cloning entire datasets
claws repos merge feature/orchestrator \
--intent ./signed-merge.json \
--anchor arbitrum