Facility Service — Service Readiness

Status: populated Owner: TBD Last updated: 2026-04-17 Companion: SERVICE_TEMPLATE §15 · DEFINITION_OF_DONE

1. Readiness gate (must be all green before production)

1.1 Documentation

• All 17 canonical docs populated
• EPICS.md, USER_STORIES.md populated with Jira-ready format
• Runbooks filed for top 3 alerts
• OpenAPI spec exported and published to developer portal

1.2 Code quality

• ESLint hexagonal import-restriction passes
• TypeScript strict mode, zero errors
• Line coverage ≥ 80 %, branch coverage ≥ 70 %
• All three mandatory integration tests green (tenant-isolation, outbox, inbox)
• Pact consumer tests green against broker
• Schema-registry conformance green for every facility.* event

1.3 Security

• Postgres RLS active on all tenant-scoped tables (verified)
• Access-policy guard active on every write
• Licensing guard active on every write
• No secrets in env default; all provided by secret manager
• Security review sign-off from platform-security

1.4 Observability

• OpenTelemetry traces visible in Grafana
• 4 mandatory dashboards published
• 8 alerts wired to on-call rotation
• SLO declared and tracked

1.5 Deploy & operations

• Canary 5% / 30m in staging completed
• Rollback verified
• HPA configured
• DR drill completed (region failover)
• On-call rotation assigned

1.6 Compliance

• Data residency verified per region
• Audit events flowing to audit-service
• No PHI stored (confirmed via data classification scan)

2. Readiness level

Level	Description	Target milestone
L2	Core graph + Location CRUD, manual monitoring	M0
L3	Contract tests, SLOs, memberships, automated HA	M1
L4	Chaos-tested, multi-region, import/export at scale	M3

3. Sign-off

Role	Name	Date
Tech lead	TBD	—
SRE	TBD	—
Security	TBD	—
Product	TBD	—