A public-safe explanation of how TESS connects education pages, asteroid/comet data, observatory operations, infrastructure status, and automation into one planetary-defense mission system.
This page intentionally describes the system at a high level. Credentials, internal-only endpoints, private keys, and operational secrets are not published.
The website is the public command surface: homepage, Mission Control, Earth/Moon/Mars pages, observatory pages, downloads, learning modules, and live NEO tools. Links are host-relative where possible so alternate domains and failover origins stay coherent.
--, never fabricated.TESS operations create rollback artifacts, verify origin and public responses, and document full source in Obsidian so the mission system remains recoverable and auditable.
The architecture is designed to expand toward observatory telemetry, Asteroid Watch Network node reports, public education kits, and future citizen-science submissions.
Public pages explain the mission without exposing secrets. Credentials stay server-side; public UI receives only sanitized, minimal outputs needed for education and status awareness.
Primary and failover origins are kept aligned for public routes. Rollback directories preserve exact previous files before changes, allowing rapid recovery if a deployment needs to be reversed.