Vacancy Primary And Fallback Status

Current Primary Runtime

Active primary Vacancy runtime:

• services/svc-vacancies
• canonical dev/runtime target: http://localhost:4023

This is the runtime now serving Vacancy traffic through the live API seam.

Current Fallback Runtime

There is no longer an active legacy Vacancy route host.

The old svc-tenders Vacancy host slice has been retired.

Current Gateway Seam

Vacancy gateway seam:

• VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL

Current live Vacancy cutover state:

• VACANCIES_SERVICE_URL=http://localhost:4023

Gateway route family remains unchanged:

• services/api/src/routes/vacancies.ts
• services/api/src/routes/vacancy-postings.ts
• services/api/src/routes/vacancy-applications.ts
• services/api/src/routes/owner-vacancy-postings.ts
• services/api/src/routes/owner-vacancy-applications.ts

Rollback Method

The old fast rollback path through svc-tenders is closed.

Rollback now means a new code/config change rather than flipping back to a live legacy Vacancy route host.

Compatibility-Truth Note

Current public Vacancy discovery remains mixed by design.

That means:

• GET /vacancies
• GET /vacancies/:id

still preserve compatibility-backed behavior when projection-backed posting truth is not available.

This primary/fallback status does not change that architectural truth. The current live cutover proves extracted-runtime parity for the current mixed behavior, not projection-only public-read cleanliness.

Notes

• svc-vacancies is the active primary route host
• legacy svc-tenders Vacancy hosting is no longer present as a route host
• live API seam and normal root startup now both treat svc-vacancies as the normal Vacancy runtime
• compatibility-backed public read behavior still remains explicit and unchanged