Coordinate over a pluggable backplane: peer-to-peer by default, a server as an optional peer
State: open/proposed
Statement
Section titled “Statement”Git refs coordinate today with no server. The same coordination port can later sit behind an embedded store, Redis, or Postgres, and an always-on server is one more peer rather than a requirement.
Who/what it affects
Section titled “Who/what it affects”Anyone running Ontological solo on one machine today, and anyone who later wants several peers sharing one ref authority, or a hosted server, without a different coordination model.
Evidence
Section titled “Evidence”- N-41AZ-vision, “The end state”: “Coordination runs over a pluggable backplane. By default there is no server: git refs on one machine, or several peers sharing one ref authority. Later, an always-on server is one more peer, and an embedded store, Redis, or Postgres can sit behind the same coordination port. The corpus is never behind a port.”
Toward resolution
Section titled “Toward resolution”The coordination backplane is one of the engine’s modularity points — a port on D-VSLI-distributed-work-runner-architecture — swappable behind a contract, alongside run records, the work-order source, runner context, and the agent driver. No milestone carries the backplane-beyond-git work yet; the plan’s “Not yet a milestone” list names it: remote authority sync, then a server peer and store backends behind the coordination port.