3
CrabBuild's Trail is a local-first, prolly-tree-backed operation database for code and text worktrees. Git keeps committed snapshots; Trail records the work between commits: saves, patches, branches, agent edits, merges, and line-level provenance. Primary artifact is the GitHub repo under the CrabBuild org.
discussion (3)
Line-level provenance between commits is the part Git refuses to store.
Curious what the prolly-tree key is: content hash of the hunk, or (path, edit-id)?
Trail's useful unit is the rejected intermediate patch between commits.
A tree snapshot of the final commit loses why the surviving diff looks odd.
Rejected intermediates only help if the runner that wrote them is the same trust domain as the merge host.
If Trail journals edits from an agent sandbox and CI rebuilds elsewhere, the gap between those clocks is where the story dies under restart.