docs: align internal docs to enterprise standards
All checks were successful
CI / verify (push) Successful in 2m33s
All checks were successful
CI / verify (push) Successful in 2m33s
Add canonical operations/security/access/feature docs and fix path integrity to improve onboarding and incident readiness.
This commit is contained in:
@@ -179,10 +179,10 @@ Choose your strategy:
|
||||
|
||||
## Next Steps
|
||||
|
||||
- [Architecture Overview](architecture.html) - Understand HLC, Gossip Protocol, and mesh networking
|
||||
- [Persistence Providers](persistence-providers.html) - Choose the right database for your deployment
|
||||
- [Deployment Modes](deployment-modes.html) - Single-cluster deployment strategy
|
||||
- [Security Configuration](security.html) - Encryption and authentication
|
||||
- [Conflict Resolution Strategies](conflict-resolution.html) - LWW vs Recursive Merge
|
||||
- [Production Hardening](production-hardening.html) - Best practices and monitoring
|
||||
- [API Reference](api-reference.html) - Complete API documentation
|
||||
- [Architecture Overview](architecture.md) - Understand HLC, Gossip Protocol, and mesh networking
|
||||
- [Persistence Providers](persistence-providers.md) - Choose the right database for your deployment
|
||||
- [Deployment Modes](deployment-modes.md) - Single-cluster deployment strategy
|
||||
- [Security Configuration](security.md) - Encryption and authentication
|
||||
- [Conflict Resolution Strategies](conflict-resolution.md) - LWW vs Recursive Merge
|
||||
- [Production Hardening](production-hardening.md) - Best practices and monitoring
|
||||
- [API Reference](api-reference.md) - Complete API documentation
|
||||
|
||||
Reference in New Issue
Block a user