Wavemap Docs

This site is a curated documentation surface for Wavemap. As the platform takes shape and architectural decisions around areas such as authorization and authentication come together, working notes, roadmaps, decision logs, etc… are synthesized and graduated up to being organized into this documentation website.

The goal is not to publish every note in the repository. Instead, we seek to keep a stable admin, developer, and operations guidance in focused pages while active planning and proof history stay in working notes.

Main Sections

• Admin / Content is for individuals managing Wavemap content concepts and future CMS workflows.
• Developer is for those changing the platform, applications, packages, and docs site.
• Operations / Platform is for those deploying, debugging, recovering, or maintaining the hosting environments that support the system.

Developers will often read all three sections. Admin docs should remain usable without deep platform knowledge, and operations docs should keep approval gates visible instead of hiding them behind quick commands.

Current Scope

• Provide a stable information architecture around admin, developer, and operations reader jobs.
• Publish durable summaries, references, runbooks, and reviewed generated assets when their boundaries have settled.
• Keep raw working notes, proof evidence, cloud inventories, and private operational artifacts out of the public docs site.
• Keep versioned docs, preview docs, generated API documentation, and private-docs access control deferred until audience need justifies the machinery.

First Reading Path

1. Developer explains the platform-facing docs surface.
2. Operations / Platform points to deployment, runbooks, generated artifacts, and cloud-operation gates.
3. Admin / Content starts with the current content model without pretending the future CMS is complete.
4. Docs Content Model explains what moves into the docs app and what stays in working notes.