Docs

Baseline

EncryptedGuru Infrastructure v0.1

The initial system uses Google Workspace for identity, encryptedguru.com for naming, Cloudflare Pages for the public static site, Google Cloud for deployable infrastructure, and NVIDIA DSX Air for network simulation. The first objective is not scale. The first objective is clarity.

• Every service should have a named owner, purpose, and recovery path.
• Every public endpoint should be documented before it becomes important.
• Secrets should not appear in notebooks, screenshots, logs, or public repositories.
• Automation should remain observable and reversible.
• Public pages should stay static unless dynamic behavior has a clear operational purpose.

Verification

Production Verification

Public infrastructure is treated as valid only after live checks pass from outside the deployment environment. The current production checks verify the canonical redirect, security headers, security.txt freshness, sitemap contents, and Google Workspace DNS records.

Runbook

First operating rules

• Use domain-based email for infrastructure accounts.
• Keep billing, operations, contact, and security aliases separate.
• Use static public pages before adding dynamic systems.
• Simulate network changes before deploying them to real infrastructure.
• Keep marketing, analytics, and tracking disabled until there is a clear reason.
• Prefer boring recovery over clever architecture.

Change control

How public changes ship

A release starts with a small written intent, then source review, then deployment, then live verification. The goal is to make every change reversible, explainable, and boring enough to repeat under pressure.

• Keep public pages static unless a dynamic system earns its operational cost.
• Commit content, headers, redirects, and runbooks together when behavior changes.
• Record production cutovers so future failures start with known facts.
• Stop immediately if DNS, mail authentication, or account recovery becomes ambiguous.