Skip to main content

Recruitment Operational Checklist

Purpose​

Provides source-supported, non-destructive review checks.

Confirmed implementation​

Checks cover startup, health, approved migration handling, tenant-safe reads, dependencies, public routes, relay, compatibility routing, and documentation.

Safe operational guidance​

Use approved environments and synthetic data only. Mark unavailable checks Requires confirmation rather than improvising recovery.

Signals and evidence​

Preserve sanitized status categories, source revision, correlation evidence, and owner decisions.

Risks and escalation​

This is not an approved production runbook; authority, rollback commands, objectives, and emergency changes require confirmation.

Checklists​

Pre-deployment​

  • Configuration categories and approved migration plan reviewed.
  • Workflow mode, HTTP dependencies, gateway/public impact, and messaging ownership identified.

Post-deployment and regular​

  • Process health and tenant-safe read succeed.
  • Correlation evidence is present.
  • Outbox progresses without persistent unexplained failure.
  • Approved synthetic smoke scenarios pass.

Incident, cutover, and rollback​

  • Classify dependency or platform boundary.
  • Collect sanitized evidence and avoid direct repair.
  • Confirm cutover/rollback and reconciliation with owners.
  • Review documentation after resolution.

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/scripts/smoke-recruitment.ps1
  • microservices/src/recruitment-service/recruitment-service.http
  • microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs

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