Skip to content

Watchlist Phase Schedule

Purpose: - Map Scalability_Security_Watchlist.md items into implementation phases and ops tracks. - Provide explicit execution order and ownership evidence for readiness gating.

Last updated: 2026-02-23

Scheduling Map

  1. Notification delivery durability beyond Redis Pub/Sub
  2. Target phase: Post-beta reliability
  3. Owner group: Platform + Notification

  4. Track: operations/Parallel_Ops_Track.md item 9

  5. Data growth guardrails (usage/ledger/audit)

  6. Target phase: Scale milestone (>= 10M rows)
  7. Owner group: Platform + Infra/SRE

  8. Track: operations/Parallel_Ops_Track.md item 6

  9. Security key management and rotation runbooks

  10. Target phase: Pre-beta blocking
  11. Owner group: Security + Platform

  12. Track: operations/Parallel_Ops_Track.md item 4

  13. WS token replay/concurrency hardening tests

  14. Target phase: Pre-beta blocking
  15. Owner group: Backend + QA

  16. Track: Implementation_Roadmap.md test hardening workstream

  17. Abuse controls beyond RPM

  18. Target phase: Pre-beta hardening
  19. Owner group: Security + Backend

  20. Track: operations/Parallel_Ops_Track.md item 7

  21. Policy cache invalidation across pods

  22. Target phase: Pre-beta hardening
  23. Owner group: Platform

  24. Track: Implementation_Roadmap.md policy workstream

  25. Encryption envelope specification

  26. Target phase: Pre-phase security (blocking)
  27. Owner group: Security + Backend

  28. Track: completed baseline in code/docs; remaining key-source rollout tracked in Execution_Progress.md

  29. Rate-limit fail-open observability

  30. Target phase: Pre-beta hardening
  31. Owner group: Security + SRE

  32. Track: operations/Parallel_Ops_Track.md items 1 and 7

  33. JWKS compromise break-glass

  34. Target phase: Pre-beta hardening
  35. Owner group: Security + Platform

  36. Track: operations/Parallel_Ops_Track.md item 4

  37. Node probe SSRF guardrails

  38. Target phase: Pre-production
  39. Owner group: Security + Backend

  40. Track: provisioning/inventory hardening slice

  41. Idempotency response-body sanitization

  42. Target phase: Pre-beta hardening
  43. Owner group: Backend + Security

  44. Track: middleware hardening slice

  45. Notification channel namespace extensibility

  46. Target phase: completed MVP baseline
  47. Owner group: Notification service owner

  48. Track: packages/services/notification/channels.go

  49. Scheduler metadata encryption rule

  50. Target phase: before scheduler backend implementation
  51. Owner group: Security + Provisioning

  52. Track: Phase-2 scheduler enablement

  53. Temporal execution-path parity

  54. Target phase: ongoing (active)
  55. Owner group: Platform + Backend

  56. Track: Inter_Service_Communication.md baseline + worker runtime updates

  57. Outbox payload data minimization

  58. Target phase: pre-beta hardening
  59. Owner group: Backend + Security

  60. Track: event contract review cycles

  61. Storage path-safety algorithm lock

  62. Target phase: completed MVP baseline
  63. Owner group: Storage service owner
  64. Track: packages/shared/storagepath

Notes

  • This schedule complements, not replaces, owner execution status in Parallel_Ops_Track.md.
  • Launch gates remain defined in Parallel_Ops_Track.md and Phase_Readiness_Tracker.md.