Skip to main content

Recruitment Deployment and Startup

Purpose​

Describes source-backed startup and migration behavior.

Confirmed implementation​

Startup registers observability, messaging, persistence, gateways, application/compatibility services, authentication, health, and outbox relay. Development can auto-apply migrations and seed development data; Production migration is explicitly out-of-band.

Safe operational guidance​

Confirm approved configuration and migration approval. After deployment verify process health, tenant-safe reads, selected dependency scenarios, and outbox behavior. Do not run unapproved database commands.

Signals and evidence​

Process start, migration errors, health, service-info, startup logs, and sanitized smoke results.

Risks and escalation​

No readiness gate proves database, broker, Workflow, Employee, or Document availability. Production rollout/rollback and migration rollback ownership require confirmation.

Startup flow​

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/Dockerfile
  • microservices/src/recruitment-service/Infrastructure/Migrations

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly