Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- The second YSQL node joins the seeded cluster; it does not create application databases, privileged login roles or cross-service secrets.
- Cluster membership must reject misconfigured peers, placement or unintended authority.
Verification still required
- Verify real three-node quorum and network connectivity with the seed and node3 before relying on cluster availability.
- Keep node-specific credentials and production storage controls outside this node’s static contract pages.
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.