Operations / Platform

Operations docs are for people deploying, debugging, recovering, or maintaining Wavemap environments.

These pages should make repeatable human decisions easier without hiding approval gates.

Wavemap currently has one shared cloud environment: Development. Its application host and persisted local data can survive ordinary stop/start, but the environment remains disposable by policy. Application delivery, database-affecting operator work, infrastructure change, and docs publication are separate human-selected paths.

Learn The Platform

Read these pages in order when learning the system:

1. Platform Orientation establishes the environment, ownership, authority, and source-reading model.
2. Testing Runtime And CI explains how an exact source revision earns CI confidence.
3. Private npm Supply Chain explains how local, CI, Docker, and publisher identities remain separate and recoverable.
4. Deployment Workflows follows application-only, operator, docs, and infrastructure paths.
5. Deployed Dev Environment explains the shared runtime and its value ownership.
6. Data Durability And Recovery explains the disposable-data boundary and future durability gate.
7. Infrastructure Change Policy explains Tendril-backed state and guarded Pulumi change.

Operate The Platform

• Deployment separates infrastructure provisioning, app release orchestration, and static docs publishing.
• Deployed Dev Environment records the current shared dev runtime and lifecycle posture.
• Deployed Dev Lifecycle records runtime, data, media, and teardown lifecycle boundaries.
• Data Durability And Recovery records disposable deployed-dev data posture, reset boundaries, backup learning drills, and future recovery gates.
• Deployment Workflows explains CI, deployed-dev CD, docs CD, smoke lanes, and command conventions.
• Private npm Supply Chain owns dependency-read credentials, trusted publication, rotation, offboarding, and npm incidents.
• Infrastructure Change Policy records Pulumi graph review and infrastructure mutation gates.
• Maps Provider Operations records browser key and map-ID ownership, restrictions, quota, attribution, CSP/privacy gates, provider smoke, and incident triage.
• Cloud Automation Permission Review records how to trace cloud API actions, target resources, trust boundaries, evidence, and explicit non-goals before automation runs.
• Docs Hosting records the live docs.wavemap.app static hosting, deploy, permission, and smoke boundaries.
• Infra Topology Processing explains the private capture, sanitized projection, review, and publication pipeline.
• Runbooks collects reviewed operator procedures and recovery paths.
• Generated Documentation defines the private-raw and reviewed-sanitized artifact boundary.

Private Planning Trail

• working-notes/SOPS.md
• working-notes/DEV_DEPLOYMENT_AND_CD_ROADMAP.md contains unresolved operations triggers only.
• working-notes/DEPLOYED_DEV_ENVIRONMENT.md is a historical index into current docs and source, not an environment contract.

Approval Gates

Live cloud mutation, permission changes, workflow deploy runs, and commits remain explicit human decisions. Docs should make those gates visible rather than replacing them with automatic instructions.