SRS → Capability Map → Build Order

Overwatch v1.0 · Capability Views

The whole programme on one page: four capability clusters · SRS coverage proof · build order. Click any diagram on any page to open in lightbox.

The model · four mutually exclusive clusters · every SRS req lands in exactly one
Platform Floor
Shared backbone 9 buckets
Identity, persistence, secrets, sessions, email, scan, observability. Every other cluster consumes from here. Slip the floor and everything slips.
Product Surface
User-facing 2 buckets
Frontend shell (C14) and document editor / export (C9). What the user sees and touches.
Integration Surface
Outbound plumbing 2 buckets
Connector framework (C10) and security check libraries (C11). Read-only into tenant cloud, SCM, IdP, vuln feeds.
Ops Surface
How it ships & runs 1 bucket
Deployment, packaging, backup, upgrade (C13). One image, three topologies: single-node · multi-node · air-gap.
Step 1
See the buckets
→ 01 Overview · 02–05 zooms
→
Step 2
Prove SRS coverage
→ 06 Traceability · 17 × 14
→
Step 3
See the build order
→ 07 Dependencies · 08 Gantt
Deep dive · all 8 pages
01 · Overview
Four clusters
MECE boundary · all four side-by-side.
02 · Zoom
Platform Floor
9 buckets · C1–C8, C12.
03 · Zoom
Product Surface
2 buckets · C9 · C14.
04 · Zoom
Integration Surface
2 buckets · C10 · C11.
05 · Zoom
Ops Surface
1 bucket · C13 · 3 topologies.
06 · Matrix
SRS × Capability
17 modules · 14 buckets · 3 views.
07 · Graph
Critical path + parallels
Spine · branches · 6 gates.
08 · Gantt
W0 → W12 timeline
Core W0–W8 · Extended W9–W12.