tiara pre-empts AI merge conflicts before PRs hit GitHub

The tool emerged from a developer's experiment inspired by Anthropic's October 13, 2026 article "Redesigning source control at Anthropic," which argued that source-control burdens like rebasing and conflict handling should be carried by tooling rather than developers. The developer tested that idea at a small scale, finding that Git itself did not choke at a few AI agents producing a dozen or so pull requests per day, so replacing Git was unnecessary. Instead, the effective parts were predicting conflicts in advance, mechanically resolving what can be decided, and passing only the remainder to AI.

The design reflects that split: tiara uses git merge-tree for prediction to match GitHub's merge behavior, resolves only well-defined patterns such as insert-both additions and structured JSON/YAML changes, and otherwise emits a handoff with commit messages so an AI can see what each side intended. The developer describes tiara as a foundation rather than a finished product, version 0.1, meant to be adapted per team because repository layout, branch names, generated files, and test methods vary.