Skip to content
Wavemap Docs

Architecture

Architecture pages should explain durable system boundaries and components after the working roadmaps have proven them.

Stable Pages

Section titled “Stable Pages”
  • Platform Orientation establishes the environment, Tendril/product ownership, authority, evidence, and strategic source-reading model before the deeper architecture pages.
  • Monorepo Map records the current workspace areas and the boundaries between apps, shared packages, the CLI, typed operations, infrastructure, and docs.
  • API Contracts records the shared route, DTO, envelope, query, permission, and domain-code boundary between Wavemap apps and packages.
  • Authentication And Authorization records the current auth model, enforcement layers, frontend and backend route-access patterns, the and role/permission contract which defines what a user can see and do before and after they’ve logged in.
  • Configuration And Secrets records source ownership, visibility boundaries, and verification rules for environment variables, runtime config, build inputs, secrets, and deploy-facing values.
  • Media Storage And Delivery records the media model, provider/runtime separation, storage adapter rules, local execution modes, and ingest/delivery posture.
  • Domain Relationships records association-row modeling and relationship-management surfaces.
  • Query Controls And Browsing State records query-control contracts, data-heavy browsing pages, URL state, and saved-view boundaries.
  • Public Entity Identifiers records the public ID, slug, URL, DTO, and collision-retry convention for public entities.
  • Content Entity Governance records the row lifecycle, provenance, ownership/control, and audit-trail vocabulary for primary content entities.
  • i18n explains the localization package layers, runtime boundaries, generated asset flow, and automated guardrails.
  • Deployed Dev Environment records the current shared cloud-backed dev environment architecture.
  • Data Durability And Recovery records deployed-dev disposable data posture, reset boundaries, backup learning drills, and future recovery gates.
  • Infrastructure Change Policy records the AWS-first, provider-aware infrastructure mutation posture.

Source Trail

Section titled “Source Trail”

Start with code-owned boundaries before historical notes:

  • packages/api-contracts/src for shared route, DTO, envelope, role, permission, and domain-code contracts.
  • apps/wavemap-back-end/src and apps/wavemap-front-end/src for the application implementations of those contracts.
  • packages/i18n/src and packages/i18n/locales for localization ownership and source resources.
  • packages/cli/src/wavemap-cli, infra/operations/src, and bin for public routes, typed operations, and external execution.
  • infra/pulumi/index.ts and infra/pulumi/src/providers/aws for the Wavemap workload resource graph.
  • working-notes only for active follow-ups and historical proof after the current implementation is understood.

Near-Term Pages To Extract

Section titled “Near-Term Pages To Extract”
  • Full ADRs for candidate decisions listed in ADRs once their tradeoffs outgrow focused reference pages.

Keep Out of This Document

Section titled “Keep Out of This Document”
  • Raw provider resource inventories.
  • Secret values and secret names beyond documented public contracts.
  • Live cloud evidence that belongs in private workflow artifacts.
  • Hand-drawn topology diagrams that are not generated from deterministic sources.