RCE-VC: Law of Version Control

RCE-VC is a version-control reference in the public repository openIE-dev/rce-vc, commit 8bf9c9af. It admits a change into one canonical, name-free repository state when a named checker accepts the post-state, and otherwise refuses it with a recorded reason. Changes whose dependency closures do not meet are admitted without coordination. A stated cost ranks admissible results, and accepted results, including resolved conflicts, are reused. The reference reads and writes ordinary Git history. It shares framing with the Reality Code Engine (a Form, a total step, a hash-chained log, name-free keys, and a gear ladder with the model last). It is not built on the Reality Code Engine language.

What the study claims and what it does not

  1. It quotes the Law of Version Control once, as the reference states it, and it says the reference is not the Reality Code Engine language.
  2. It reports milestones M0, M1 and M2 as implemented in that tree: persistent state, the gear ladder, reuse, and a Git projection. It names the tests the README gives for propositions VC1 to VC5. It does not re-run them.
  3. It reports measured wall time and admission-path shares from that build (release, one core). At 100,000 units the persistent state took 188 microseconds per submission. It labels receipt costs as the stated est_uj table, not a measurement.
  4. It does not claim a joule reading, a result on Merge-Bench or any other corpus, function-level units, or a score against any other version-control system. Parsing real source, packfiles, leases, and a meter are named as not done.
Measured admission-path shares for a 1,280-submission swarm, and measured wall time per submission from 400 units to 100,000 units, on the reference build. Not an energy figure.
Path shares and wall times printed for the reference build. Receipt costs are a stated table and are not on this figure.