A hypothetical staffing company builds a post-hire onboarding checklist system for its multi-tenant HR platform. Named system owner: the company's VP of HR operations. Named proposer: recruiter assigned to the new hire. Named independent approver: authorized HR records owner at the client tenant. All targets are hypothetical and illustrative.
Prelaunch fixtures.
hr_cur_1: New hire H-501 at Tenant T-300, hiring decision made by authorized hiring manager, onboarding checklist version V4, recipient HR coordinator assigned
hr_cur_2: Recruiter prepares onboarding task draft with document list, benefits packet and IT provisioning request, queued for HR records owner approval
hr_stale_1: Task draft referencing onboarding template V2 when current is V4 (stale version)
hr_unknown_1: Task draft for candidate not found in ATS for Tenant T-300 (unknown candidate)
hr_inelig_1: Task draft for candidate whose offer was rescinded (no longer eligible for onboarding)
hr_unauth_role_1: Receptionist attempting to approve onboarding task distribution (requires HR records owner role)
hr_unauth_tenant_1: Recruiter from Tenant T-400 attempting to access Tenant T-300 candidate records
hr_unavail_1: ATS temporarily unreachable for candidate status verification
Disjoint held-out setup. 11 synthetic onboarding records. Positive cohort (5: ONB-001 through ONB-005): valid hiring decision, current template, authorized recruiter, qualified HR records owner, recipient assigned. Negative cohort (6: ONB-006 through ONB-011): stale template, unknown candidate, rescinded offer, wrong role, wrong tenant, ATS unavailable. The held-out total (11: 5 positive and 6 negative) excludes the named recovery-only revocation fixture (ONB-101) and private-restore test fixture. Training and tuning data separated from held-out fixtures; held-out cohorts are never used to train or tune system behavior. All hypothetical.
Allowed workflow (hr_1). ONB-001: recruiter prepares onboarding draft for H-501 at Tenant T-300. System verifies: candidate exists in ATS with confirmed post-hire status (started, not merely accepted offer), current onboarding template V4 and recipient version confirmed, recipient HR coordinator assigned within T-300. HR records owner reviews: candidate status confirmed, template current, recipient authorized. Approves. System distributes checklist tasks to recipient (business effect: recipient task queue shows new items, verified independently). No AI hiring, ranking, eligibility or automated employment decisions. I-9 task assigned as a checklist item; actual I-9 verification by employer's authorized reviewer is separate. 5 of 5 positive onboardings distributed.
Denied: stale template (hr_2a). ONB-006: references V2, current is V4. Version mismatch. Deferred. 0 distributions on stale templates.
Denied: unknown candidate (hr_2b). ONB-007: candidate not in T-300 ATS. Cannot verify. 0 distributions for unknown candidates.
Denied: rescinded offer (hr_2c). ONB-008: offer rescinded. No longer eligible. 0 onboardings for ineligible candidates.
Denied: unauthorized role (hr_2d). ONB-009: receptionist attempts approval. Requires HR records owner. 0 unauthorized approvals.
Denied: cross-tenant (hr_2e). ONB-010: T-400 recruiter, T-300 records. Isolation enforced. 0 cross-tenant access.
Denied: ATS unavailable (hr_2f). ONB-011: ATS unreachable. Queued, not distributed. 0 distributions without verified status (fail closed).
Idempotency and duplicate detection (hr_3). Operation A: recruiter drafts ONB-001, HR records owner approves, key op:hr_A_001. Recipient task insertion for ONB-001 confirmed (verified independently by reading task store: entry for ONB-001 present with correct recipient, post-hire step reference and assigned team). Replay of A with same key op:hr_A_001: rejected, 0 duplicate task insertions, prior log preserved. Operation B: recruiter drafts distinct ONB-002, HR records owner separately reads fresh hire record and team assignment and approves, key op:hr_B_002. Recipient task insertion for ONB-002 confirmed (verified independently by reading task store). 2 of 3 applied (A and B), acceptance target 0 duplicates, not observed. Test acceptance targets.
Ambiguous first response (hr_3b). Fixture hr_ambig_1: recruiter submits ONB-003, key op:hr_A_003. Network interruption. Before any repeat: (1) read distribution log for key; (2) read recipient task queue for ONB-003 tasks; (3) read current ATS post-hire status for candidate H-501 (confirmed started/post-hire, not merely accepted offer); (4) read current onboarding template version and recipient assignment/version; (5) check exact task queue for pending/inflight. Log found, tasks distributed, ATS confirms post-hire: complete, no repeat. Log found, tasks missing: STOP. VP of HR operations investigates. Log not found, tasks exist: reconcile without replay. Log not found, no tasks AND no pending/inflight AND current ATS post-hire status confirmed (started) AND current role/tenant/template version/recipient assignment verified AND HR records owner re-approves with fresh read: resubmit with identical key. Recruiter assignment revoked: fail closed. I-9 document review and employment eligibility verification remain entirely separate from this workflow. 0 duplicates. Test acceptance targets.
Distribution logging and access control (hr_4). Write-once log: onboarding ID, candidate ID (not SSN), tenant, template version, recruiter, HR records owner, recipient, timestamp. No raw personal identifiers beyond internal IDs. Scoped read for HR records and compliance. Retention owner: HR records owner per applicable retention schedule.
Revoked recruiter assignment before reconnect (hr_5a). Fixture hr_revoked_1: recruiter queued onboarding task draft for ONB-101 with key op:hr_R_101 while Tenant T-300 assignment was current and HR records owner had approved the draft. Before task insertion completed, VP of HR operations (named revoker) revoked recruiter's Tenant T-300 assignment. On delayed result/reconnect: system reads current recruiter assignment: Tenant T-300 absent. Queries pending task queue: op:hr_R_101 present but not committed. Reads task store: no entry for ONB-101. Reads committed effects from prior distributions (ONB-001 through ONB-003): preserved, no modification. Fail closed: no task distribution, no checklist delivery, no recipient notification, no replay. 0 effects after revoked assignment. Test acceptance target.
Staged restore (hr_5b). After ATS restored: stage the prior stable version privately with no real writes to recipient task queues, onboarding checklists or production distribution pipeline. Named fixture hr_restore_1: queued onboarding draft for candidate H-502 at Tenant T-300, key op:hr_R_502, template V4, recipient HR coordinator assigned, HR records owner role grant current. In private staging: (a) test authorized route: verify VP of HR operations authority accepted, current recruiter Tenant T-300 assignment valid, HR records owner role grant active, ATS confirms candidate post-hire status (started), template V4 current, recipient assignment current, and each independently confirmed distribution effect from before the outage (recipient task queue entry) is still present and consistent; (b) test revoked/denied route: recruiter whose Tenant T-300 assignment was revoked during outage attempts to submit a queued draft and system denies (zero distributions after revoked assignment, revoked access never resurrected). Reconcile exact queued drafts against current ATS candidate status and onboarding templates. Preserve each independently committed effect: already-distributed checklists from manual fallback preserved. Require two named signoffs: VP of HR operations verifies data integrity, HR records owner verifies onboarding correctness. Both approve before production restore. Named manual fallback during outage: recruiters hold checklists manually with candidate ID, tenant, template version and recruiter signature; reconciles upon restore. Named fallback owner: VP of HR operations; queue reconciliation and two-role restart.
Tablet and keyboard access plan (hr_6). On iPad at 820 by 1180, recruiter attempts 3 tasks: (1) review draft queue (pass: fits viewport; fail: truncated; error: queue loads but template-version column hidden), (2) open candidate onboarding detail with ATS post-hire status and recipient assignment (pass: scrollable with complete data; fail: data hidden; error: detail opens but ATS status stale), (3) tap Submit for HR Records Owner Review (pass: visible, draft not distributed; fail: unreachable; error: submit fires with no feedback). On desktop at 1280 by 800, keyboard-only HR records owner attempts 3 tasks: (1) navigate queue (pass: focus ring; fail: no indicator; error: focus skips), (2) open detail (pass: focus to panel with candidate/template/recipient; fail: nothing; error: panel opens, focus stays), (3) approve or defer with keyboard (pass: accessible, announced; fail: inaccessible; error: approval distributes without ATS re-check). Residual risk: if ATS post-hire status changes between recruiter draft and HR records owner approval, the stale status may not refresh, causing approval for a candidate whose offer was rescinded. All outcomes are test acceptance targets. Test plan; results not claimed.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.