Skip to main content

Suggested improvements

Backlog-style ideas only — not commitments.

Data​

  • Single canonical schema (or generated types) aligned with Firestore
  • Field-level data dictionary for main collections
  • Retention / archival for old reports and worklogs
  • Backup and restore runbook for Firestore

Infrastructure & DevOps​

  • Environment parity (dev/staging/prod) and budget alerts
  • Staged rollouts on Cloud Run where useful
  • Structured logging (trace id, user, action) for support

Security & product​

  • RBAC fully implemented and documented alongside firestore.rules
  • SSO rollout and optional audit logging for sensitive actions
  • Design tokens used consistently — see Design Tokens

Documentation​

  • Publish formal design documents when ready
  • Optional API reference (OpenAPI or generated from routes)
  • Changelog for releases

See also Data overview for how data is represented today.