From cf55c0226553a86aa97ccd3f57681f405dae443c Mon Sep 17 00:00:00 2001 From: Hardik Date: Mon, 22 Jun 2026 22:12:28 +0530 Subject: [PATCH] =?UTF-8?q?docs(crewing):=20Phase=205=20=E2=9C=85=20comple?= =?UTF-8?q?te=20=E2=80=94=205b=20Appraisal?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Crewing-Implementation-Spec.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/Crewing-Implementation-Spec.md b/Crewing-Implementation-Spec.md index 404631e..a1c3e1c 100644 --- a/Crewing-Implementation-Spec.md +++ b/Crewing-Implementation-Spec.md @@ -435,12 +435,15 @@ with these reconciliations: > crew placement** (assign crew to a vessel/site without a requisition), and > **Admin crew CRUD**, behind a new `manage_crew` permission. > -> **Phase 5** is in progress as stacked sub-PRs: **5a Verification (Epic I) ✅**, -> **5b Appraisal (Epic H) — pending**. 5a is the office verify queue +> **Phase 5 ✅ complete** — stacked sub-PRs: **5a Verification (Epic I) ✅**, +> **5b Appraisal (Epic H) ✅**. 5a is the office verify queue > (`/crewing/verification`): the MPO verifies/rejects documents (`verify_site_records`) > and Accounts verifies/rejects bank/EPF (`verify_bank_epf`) — leave is not here > (it's a Manager approval, R11). PPE/next-of-kin verify gates were deferred -> (low-risk; no `verificationStatus` on those models). +> (low-risk; no `verificationStatus` on those models). 5b is the appraisal lifecycle +> `raise → verify → approve` (`Appraisal`/`AppraisalStatus`) across three role-gated +> surfaces (§8.14): PM raises on the crew-profile Appraisals tab, MPO verifies in the +> Verification queue, Manager approves in the central /approvals queue (Appraisal kind). 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.)*