Files
CBDDC/docs/adr/0001-peer-mesh-topology.md
Joseph Doherty ce727eb30d
All checks were successful
CI / verify (push) Successful in 2m33s
docs: align internal docs to enterprise standards
Add canonical operations/security/access/feature docs and fix path integrity to improve onboarding and incident readiness.
2026-02-20 13:23:55 -05:00

20 lines
504 B
Markdown

# ADR 0001: Peer Mesh Topology
## Status
Accepted
## Context
CBDDC requires local-first synchronization without a central coordinator in LAN-focused deployments.
## Decision
Adopt a peer mesh topology with gossip-based synchronization and per-node oplog tracking.
## Consequences
- Improves resilience when individual nodes disconnect.
- Requires strong operational tooling for lag, peer lifecycle, and pruning controls.
- Increases importance of clear runbook and troubleshooting documentation.