Architecture
Infrastructure
Small systems, clear boundaries, documented recovery.
Network principle
Personal Sovereign Network Principles
A sovereign personal network should make identity, access, routing, and data movement explicit.
The first design target is not maximum complexity. It is the ability to recover from mistakes.
- Separate personal devices, lab systems, public services, and management paths.
- Prefer private access for admin surfaces and public access only for intentional endpoints.
- Record DNS, IAM, billing, recovery, and deployment decisions as runbooks.
- Test topology and routing concepts in simulation before applying them to live systems.
- Keep emergency access independent from experimental routing paths.
Public site
Cloudflare Pages serves the static site at www.encryptedguru.com.
Identity
Google Workspace records remain the source of mail identity and account operations.
Admin boundary
No administrative console is exposed on the public site.
docs.encryptedguru.comKnowledge base and runbooks.
lab.encryptedguru.comExperiment logs and simulation notes.
status.encryptedguru.comFuture service health and incident notes.
console.encryptedguru.comFuture private control surface; never public by default.