shad0w/pelagia-portal
1
0
Fork 0
Code Issues 11 Pull requests 2 Projects Releases 2 Packages Wiki Activity Actions

docs(crewing): Phase 3 complete — 3c Onboarding ✅ 

§12 status note: mark 3c Onboarding done (Phase 3 complete). Note onboarding
promotes the candidate to EMPLOYEE with a CRW- number and that SITE_STAFF login
creation for management ranks remains a deferred follow-up.
Hardik 2026-06-22 19:14:02 +05:30
parent 049b07a941
commit 1a78f10aa1
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Crewing-Implementation-Spec.md

@ -407,11 +407,13 @@ with these reconciliations:
> requisition it relies on is already built in Phase 2, so Epic K is purely
> additive when it arrives.
>
> **Phase 3** is delivered as three stacked sub-PRs: **3a Candidates (Epic B) ✅**,
> **3b Recruitment pipeline (Epic C) ✅**, **3c Onboarding (Epic D) — pending**.
> **Phase 3 ✅ complete** — delivered as three stacked sub-PRs: **3a Candidates
> (Epic B) ✅**, **3b Recruitment pipeline (Epic C) ✅**, **3c Onboarding (Epic D) ✅**.
> 3b's central-Approvals integration follows §8.13 R8 (Salary/Selection/Waiver
> gates surface in the unified Manager queue). `SalaryStructure` is attached to the
> `Application` during the pipeline and bound to the `CrewAssignment` at onboarding (3c).
> Onboarding promotes the candidate to `EMPLOYEE` with a `CRW-` number; **SITE_STAFF
> login creation for management ranks (`grantsLogin`) is a deferred follow-up**.
1. **Foundations** — `SITE_STAFF` role; crewing schema + enums; permissions; `CREWING_ENABLED` flag; nav scaffold; reference data (Ranks, RankDocRequirements).
2. **Requisitions + relief** (Epic A) — requisition lifecycle, relief requests, and the shared `autoRaiseRequisition` backfill helper. *(Epic K sign-off/experience originally sat here; moved to Phase 4 — see status note above, as it depends on the onboarding/assignment schema.)*