That just sparked a thought. For a codebase, unit tests could be the pre-commit validation algorithm. Then, as authors continue to edit the piece, they both ad

That just sparked a thought. For a codebase, unit tests could be the pre-commit validation algorithm. Then, as authors continue to edit the piece, they both add unit tests, and merge the code. In the face of a merge, the tests could be the deciding factor between what emerges. Of course, unless you have conflicts in the tests themselves.