Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- The seed YSQL node owns the common cluster contract and node initialization boundary; role/schema provisioning is an authorized separate responsibility.
- Multiple logical nodes on a single VPS do not establish independent physical fault domains.
Verification still required
- Prove real cluster quorum and application-role identity, not just static topology or mocked probes.
- Coordinate additive schema/seed/readiness changes with migrate and node2/node3 without importing other services’ code.
How to update
When the owner changes implementation or contract behavior, update this page and the relevant service interfaces. For cross-service changes, also update the platform interface map or decision register. State the actual verification performed; do not inherit historical pass claims without fresh evidence.