SOP → Nx Targets & Generators Mapping

This turns the SOP into mechanical execution.

Phase 1–2: Workspace & Spine

Nx usage

• create-nx-workspace
• nx graph
• Root project.json for global commands (setup, dev, test)

Rule: no handwritten structure until Nx exists

Phase 3: Architecture Enforcement

Nx usage

• ESLint module-boundary rules
• Tag libs (domain, application, infra, ui)
• Enforce allowed dependency edges

Rule: architecture violations fail lint, not review

Phase 4: Local Runtime Stack

Nx usage

• nx run-commands targets:

  • infra:up
  • infra:down
  • infra:reset
  • infra:flags-up (start Flipt binary)
  • infra:flags-down (stop Flipt)
  • infra:flags-check (validate features.yaml)
• One Nx target = one lifecycle action
• Feature flags via OpenFeature SDK + Flipt provider

Rule: infra is treated like code

Phase 5: Observability (ADR-029)

Nx usage

• Shared libs/observability lib containing:
  • OTel SDK bootstrap (Node.js + Python)
  • Logfire configuration
  • Semantic context helpers
• Nx run-commands targets:
  • infra:otel-up (start OTel Collector)
  • infra:otel-down (stop OTel Collector)
  • infra:otel-validate (validate config)
• Apps import observability lib at bootstrap

Stack: OpenTelemetry SDK → OTel Collector → OpenObserve + Vanta

Rule: apps don’t roll their own telemetry; all signals via OTel

Phase 6: Contracts

Nx usage

• contracts lib

• Targets:

  • contracts:generate
  • contracts:check
• CI fails on drift

Rule: contracts are source of truth

Phase 7: Generators

Nx usage

• Built-in generators for apps/libs

• Custom generators:

  • nx g bounded-context
  • nx g adapter
  • nx g api-surface

Rule: if you repeat structure twice, make a generator

Phase 8: Testing (Vitest + Playwright)

Nx usage

• @nx/vite plugin infers test target from vite.config.ts
• Targets:
  • nx test <project> — Vitest unit/integration
  • nx affected -t test — Only test changed projects
  • nx e2e <app>-e2e — Playwright E2E
• Python: just test-python (pytest)

Rule: test scope matches change scope; integration tests use Testcontainers

Phase 9: Vertical Slices

Nx usage

• One feature = changes across domain/app/infra/UI libs
• Feature flags injected via config lib

Rule: slices cross layers, not projects

Phase 10–11: Flags & CI

Nx usage

• Feature flags consumed via libs/config (OpenFeature client)
• Flipt provider registered at app bootstrap
• CI uses nx affected:*
• CI runs infra:flags-check to validate features.yaml

Rule: shipping ≠ enabling

Phase 12: Hardening

Nx usage

• Dedicated hardening tasks (load tests, audits)
• Scheduled CI jobs

Rule: hardening is continuous, not a phase at the end