Vacancy Dependency Edge Map

Purpose

This map traces the real dependency edges around the current Vacancy backend. It separates:

• acceptable shared Kvary shell dependencies
• move-first vacancy-owned dependencies
• temporary compatibility edges
• unresolved public-read debt

Dependency Edges

| Source | Target | Dependency type | Verdict | Notes | | --- | --- | --- | --- | --- | | registerVacancyRoutes.ts | VacancyReadRepository | preferred read dependency | should move into Vacancy later | This is already the preferred route-time read path. | | registerVacancyRoutes.ts | VacancyCommandHandlers | command/write dependency | should move into Vacancy later | Core mutation dependency for postings and applications. | | registerVacancyRoutes.ts | VacancyRouteSupport | route-support dependency | should move into Vacancy later | Support contract is already vacancy-owned. | | VacancyRouteSupport builder | requireServiceAuth | auth ingress dependency | can remain shared after extraction | Shared shell auth ingress is expected to stay shared initially. | | VacancyRouteSupport builder | requireActivePrincipal | auth/principal dependency | can remain shared after extraction | Depends on shared auth/identity resolution behind /auth/me. | | VacancyRouteSupport builder | parsePositiveInt | shell parser dependency | can be wrapped later | Small shell helper; not a blocker. | | VacancyCommandHandlers | Postgres pool | persistence dependency | should move into Vacancy later | Core domain write dependency. | | VacancyCommandHandlers | applyVacancyDomainEventProjection | domain projection dependency | should move into Vacancy later | Projection upkeep is domain-owned. | | VacancyCommandHandlers | service outbox table via appendOutboxEvent | event/runtime dependency | should stay temporary for now | Uses shared outbox runtime pattern in current host. | | VacancyReadRepository | vacancy_postings, vacancy_applications | primary write-model read dependency | should move into Vacancy later | Owner/application reads already rely on vacancy-owned tables. | | VacancyReadRepository | vacancy_postings_view, vacancy_posting_detail_view, my_vacancy_applications_view, vacancy_applications_by_posting_view | projection/read-model dependency | should move into Vacancy later | These are real vacancy projections. | | VacancyReadRepository | legacy vacancies table | compatibility public-read dependency | unresolved | Main blocker for clean public discovery extraction. | | VacancyCompatibilityReadRepository | VacancyReadRepository | compatibility wrapper dependency | should stay temporary for now | Exists only for old root repository callers. | | VacancyCompatibilityApplicationRepository | VacancyReadRepository | compatibility wrapper dependency | should stay temporary for now | Same pattern for application reads. | | TendersRepository | vacancy compatibility wrappers | mixed root repository dependency | should stay temporary for now | Legacy hosting only; not the preferred runtime path anymore. | | server.ts | VacancyReadRepository, VacancyCommandHandlers, buildVacancyRouteSupport | shell composition dependency | should stay temporary for now | Normal while vacancy still lives inside svc-tenders. | | API vacancy routers | VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL | gateway service-target seam | can remain shared after extraction | This is already the intended shared seam. | | API vacancy routers | forwarded bearer token / x-intent-id | gateway auth/request propagation | can remain shared after extraction | Shared gateway contract, not vacancy-local ownership. | | Web portal/api.ts vacancy functions | API vacancy routes | client/service dependency | should become API/service contract | Good extraction boundary if DTO drift is controlled. | | Web portal/api.ts vacancy functions | VACANCY_CATALOG fallback | UI compatibility dependency | should stay temporary for now | Explicitly non-canonical fallback. | | Web vacancyCatalog.ts / vacancyDetail.ts | richer catalog/detail types | UI-only contract dependency | unresolved | Real duplication and enrichment beyond backend DTOs. | | Accommodation detail UI | vacancy list API results for nearby previews | cross-domain UI dependency | should stay temporary for now | Present in UI, but not a backend vacancy extraction edge. | | Map vacancy layer | mock vacancy data | UI-only dependency | should be removed before extraction claims | Not backend truth at all. |

Shared vs Must-Separate Summary

Acceptable to stay shared after extraction

• API gateway routing under services/api
• VACANCIES_SERVICE_URL ?? TENDERS_SERVICE_URL target resolution
• bearer-token auth ingress
• principal resolution behind /auth/me

Should move into Vacancy

• vacancy route registration
• vacancy route support contract and vacancy-local helpers
• vacancy command handlers
• vacancy domain aggregates
• vacancy projections
• vacancy read-model mapping
• vacancy preferred read repository
• vacancy-owned contracts and validation

Should stay temporary for now

• root repository compatibility wrappers
• current svc-tenders shell composition
• web fallback to VACANCY_CATALOG

Unresolved

• whether public /vacancies becomes fully projection-backed
• how much web vacancy detail/catalog duplication should be reduced before extraction
• migration ownership for vacancy-dominant vs mixed accommodation-context migrations

Main Dependency Conclusions

1. The gateway seam is already in good shape.
2. The shell auth dependency is real, but acceptable as a shared boundary.
3. The biggest non-shell blocker is not route wiring; it is the public read dependency on legacy vacancies.
4. The root repository is now mostly a compatibility burden for vacancy rather than a true dependency owner.