Platform
Platform docs own operational capabilities independent of providers. Services records how providers implement them.
| Capability | Current repository evidence | Canonical detail |
|---|---|---|
| CI / orchestration | Affected-workspace staging workflows and all-monorepo validation | CI |
| Environments / deployment / hosting | Local builds, Vercel previews and production apps, GitHub Pages docs | Deployment |
| Build orchestration / remote cache | Turbo task graph, remote caching enabled, CI credentials | Remote Build Cache |
| Dependency management | Renovate npm/custom managers and catalog/lockfile | Dependency Management |
| Notifications | PR, CI failure, preview and production Telegram routing | Telegram |
| Observability | App console logger and CI artifacts; no adopted central observability SDK found | See below |
Observability and recovery
Game Client src/logging/dev-logger.ts emits layer-controlled informational logs only in development, but logger.error remains active in production. There is no verified centralized error/log/metric/tracing pipeline in source. Data & Privacy owns permissible data/identifiers; Services tracks provider evaluation.
A formal release/versioning policy, incident response ownership, backup/recovery procedures and monitoring retention remain planned. Current production workflow triggers are documented as implemented, not as a completed release-management system. Do not invent service guarantees, alert coverage or rollback procedures from provider defaults.