From e8308304eee7c43718c2358e1cd5d1771f08beaf Mon Sep 17 00:00:00 2001 From: Hardik Date: Mon, 22 Jun 2026 19:28:28 +0530 Subject: [PATCH] =?UTF-8?q?docs(crewing):=20Phase=204=20underway=20?= =?UTF-8?q?=E2=80=94=204a=20Crew=20records=20&=20profile=20=E2=9C=85?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit §12 status note: Phase 4 in progress as stacked sub-PRs (4a ✅ records/profile/PPE, 4b leave/attendance pending, 4c sign-off/experience pending). Note 4a's server-side PII masking and the carried deferrals (own-site scoping, verify queue → Phase 5, pay-status → Phase 6). --- Crewing-Implementation-Spec.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Crewing-Implementation-Spec.md b/Crewing-Implementation-Spec.md index 42e7b64..d2b75cb 100644 --- a/Crewing-Implementation-Spec.md +++ b/Crewing-Implementation-Spec.md @@ -414,6 +414,15 @@ with these reconciliations: > `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**. +> +> **Phase 4** is in progress as stacked sub-PRs: **4a Crew records & profile + PPE +> (Epics E, F) ✅**, **4b Leave & attendance (Epic G) — pending**, **4c Sign-off & +> experience (Epic K) — pending**. 4a applies role-based PII masking server-side +> (bank/Aadhaar full only for Accounts; salary hidden from site staff, §6/§8.8). +> Deferrals carried in 4a: site-staff own-site scoping (needs a User↔Site link), +> the records **verify queue** (§8.11 → Phase 5), and the Pay-status tab beyond the +> salary structure (→ payroll, Phase 6). The leave-clash auto-backfill in 4b will +> reuse the Phase-2 `autoRaiseRequisition` helper. 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.)*