PeopleOps Console
Quick Start
Every task follows this sequence:
- Open
<TASK_ENV_BASE_URL> in the browser-style fetch tool. Login with
ops.lead@peopleops.local / PeopleOps#2026 if the application requires
authentication.
- Read the task prompt to identify the task type, target record ID, and which
answer template fields are required.
- Fetch records from the relevant API endpoints, working from list endpoints
to detail endpoints.
- Apply the business rules for the task type (below).
- Produce a single JSON object matching the answer template. Every string
field that names an enum must use the exact allowed value from the template.
API Endpoints
See references/api_reference.md for the full
endpoint catalog, record field descriptions, and task-type-to-endpoint mapping.
Normalized Business Labels
See references/enum_reference.md for every
allowed value across all answer templates. Always match these exact strings.
Core Business Rules
Record Status Precedence
submitted > draft > superseded
- Only
submitted records are authoritative for decisions.
draft records must be excluded unless the task explicitly permits drafts.
superseded records were replaced by a newer submitted record; exclude them.
- When multiple submitted records exist for the same entity, use the most
recent.
Audit Scoping
- Each audit event has a
scope field and related_event_ids.
- When the task asks for leave-source decisions, use only audit events scoped
to leave precedence. Exclude document/notice or payroll audit events from
the leave decision, listing them in
excluded_audit_event_ids.
- When the task asks for document/notice decisions, use only audit events
scoped to document/notice findings. Exclude leave or payroll events.
- When the task asks for payroll readiness, use only payroll-scoped audit
events.
- A single audit event that covers the relevant scope serves as both the
primary
audit_event_id and the sole entry in
supporting_audit_event_ids.
Task Types
1. Onboarding Closeout
Verify leave and payroll setup for a given employee ID before approving
onboarding completion.
Leave verification:
- Fetch the employee from
/api/employees and the leave assignment ledger from
/api/payroll-ledgers.
- Identify all leave assignment records for the employee. Classify each as
submitted, draft, or superseded.
- The effective leave policy and annual days come from the most recent
submitted leave assignment. List draft and superseded leave assignment IDs
in
excluded_leave_ids.
- If the submitted assignment matches the current period, set
leave_source to leave_assignment_history and
leave_precedence_source to approved_assignment_current_period.
Payroll verification:
- From
/api/payroll-ledgers, identify all payroll assignment records for the
employee.
- The authoritative record is the most recent submitted payroll assignment.
Set
payroll_status and payroll_source_status to submitted.
- List any draft or superseded payroll assignment IDs in
excluded_payroll_ids.
- Extract
base_salary from the submitted assignment.
Closeout decision:
- If both leave and payroll records are clean (no drafts in authoritative
position, no missing records), set:
closeout_action: approve_onboarding_close
approval_closeout_gate: approval_sufficient_when_records_clean
final_control_result: approve_closeout
- If defects exist, choose the appropriate blocker action.
2. Case Folder and Notice Review
Review a case for folder readiness and formal notice quality.
Folder inspection:
- Fetch the case detail from
/api/cases/{case_id}.
- Check
folder_status for whether the folder is ready. Inspect listed
documents for required files. Any required file not present goes in
missing_files.
- Check
tags for the required tag. Set required_tag_present accordingly.
If the tag is already present, folder_required_tag_action is
no_tag_action; otherwise add_required_tag.
Notice inspection:
- Fetch notices from
/api/notifications and inspect the formal notice
packet.
- Check for defects: missing acknowledgement deadline, missing appeal
instructions, missing waitlist status, incorrect policy reference.
- Set
notice_quality to valid or defective and list any defect labels
in notice_defects.
- Set
notice_evidence_source to notice_packet_inspection.
Audit evidence:
- Fetch audit events from
/api/audit and /api/audit/{audit_id}.
- Find the audit event that covers document/notice findings. Use it for
audit_event_id and supporting_audit_event_ids.
- Set
audit_scope to document_notice_findings_only.
Evidence order: Follow approval_history_folder_notice_audit: read
approval history first, then folder, then notice packet, then audit detail.
Set evidence_source_order accordingly.
Decision:
- If both folder and notice are clean:
final_decision is approved or
approved_with_conditions.
- If folder has missing files or notice is defective:
final_decision is
held or approved_with_conditions (depending on approval record), and
list blockers in closeout_blockers.
- If notice is defective,
next_action is block_close_and_reissue_notice
and notice_remediation_action is reissue_defective_notices.
- If folder has missing files,
escalation_action is
open_records_remediation with records_remediation_owner set to
Records.
final_control_result is hold_for_folder_and_notice_defects when defects
exist.
3. Recruitment Reconciliation
Reconcile recruitment outcomes for an opening ID.
Candidate determination:
- Fetch
/api/recruitment for the opening. Inspect interview feedback and
offer records for each candidate.
- The selected candidate is the one with an accepted offer and committee
decision confirmation. Set
selected_offer_status to accepted.
- Waitlisted candidates: those with committee waitlist status but no accepted
offer. Put their IDs in
waitlisted_candidates.
- Rejected candidates: those with committee rejection. Put their IDs in
rejected_candidates.
- Set
candidate_status_source to interview_feedback_and_offer and
candidate_outcome_control to
committee_decision_with_offer_confirmation.
Offer and cost:
- Extract
offer_id and offer_base_salary from the selected candidate's
accepted offer.
- Sum all items from the recruitment cost ledger for
recruitment_cost_total.
Set cost_source to recruitment_cost_ledger.
Notice followup:
- Inspect notices from
/api/notifications. Set
notice_quality_source to notice_packet_inspection.
- For each waitlisted candidate without a valid waitlist notice, add to
notice_followup_required and set waitlisted_followup_action to
send_waitlist_notice.
- For each rejected candidate without a valid rejection notice, add to
notice_followup_required and set rejected_followup_action to
send_rejection_notice.
Payroll handoff:
- Only the selected candidate with an accepted offer triggers payroll handoff.
- Set
payroll_handoff_gate to accepted_offer_only.
- Set
payroll_assignment_status_required to
submitted_after_acceptance.
- Set
draft_payroll_allowed to false.
- Set
onboarding_handoff to create_payroll_precheck.
- Set
handoff_control_result to
submitted_handoff_required_after_acceptance.
- For waitlisted candidates, set
offer_exclusion_reason_for_waitlisted to
no_accepted_status_or_offer.
4. Leave Source Precedence
Determine which leave policy is authoritative when both an employee profile
summary and a leave assignment ledger exist.
Procedure:
- Fetch the employee from
/api/employees. Note the leave policy in the
profile summary.
- Fetch leave assignment records from
/api/payroll-ledgers.
- Fetch the policy document text from
/api/policies/{policy_id}.
- Fetch audit events from
/api/audit and inspect the leave-scope audit
detail from /api/audit/{audit_id}.
Rule: An approved (submitted) leave assignment for the current period
overrides a stale employee profile summary when the ledger, policy document,
and audit detail all confirm the approved assignment.
- If the submitted leave assignment matches the current period, set:
precedence_source: approved_assignment_over_profile
leave_precedence_source: approved_assignment_current_period
profile_policy_ignored: true
effective_leave_policy: the policy name from the assignment
assignment_id: the submitted assignment ID
balance_days: the balance from the assignment
audit_result: profile_summary_stale
next_action: update_employee_summary
- If no approved assignment exists for the current period, fall back to the
profile summary policy.
Audit scoping:
- Use only leave-scope audit events. Set
audit_scope to
leave_source_precedence_only.
- The primary leave-scope audit event becomes
audit_event_id and the sole
entry in supporting_audit_event_ids.
- List any document/notice or payroll-scope audit events in
excluded_audit_event_ids.
5. Payroll Assignment Readiness
Verify payroll assignment and accrual batch readiness for an employee.
Procedure:
- Fetch payroll assignment records from
/api/payroll-ledgers.
- Identify the most recent submitted assignment. Extract its ID, salary, and
effective date.
- Identify any draft or superseded assignments. List the draft assignment ID
in
excluded_assignment_id.
- Set
payroll_source_status to submitted and draft_exclusion_rule to
exclude_draft_assignment.
Accrual check:
- From the payroll ledger, check whether the accrual batch for the relevant
period is ready. Set
accrual_ready to true or false and provide the
accrual_batch_id.
Audit evidence:
- Fetch payroll-scope audit events. Set
audit_scope to
payroll_assignment_readiness.
- The payroll-scope audit event becomes
audit_event_id.
Control result:
- If the submitted assignment is valid and accrual is ready:
control_result is ready_with_monitoring.
- If defects exist, use the appropriate hold or block label.
Output Format
Return a single JSON object. No markdown fences, no explanatory text. Match
the answer template field-by-field:
- String fields where the template specifies an enum: use exactly one of the
allowed values.
- Integer/number fields: the numeric value from the API record.
- Boolean fields:
true or false.
- List fields: JSON arrays of strings (IDs or defect labels).
If the task provides an input/payloads/answer_template.json, read it first
to confirm the exact field names and allowed values.
1---2name: peopleops-console-113description: "PeopleOps HR console solver for employee onboarding closeout, case folder/notice review, recruitment reconciliation, leave source precedence, and payroll assignment readiness. Use when the task references PeopleOps Console, TASK_ENV_BASE_URL, ops.lead@peopleops.local, onboarding, leave policy, payroll assignment, case review, recruitment reconciliation, notice quality, or audit scoping."4metadata:5 source: https://skillmd.com/skills/prism-shadow/peopleops-console-116---78# PeopleOps Console910## Quick Start1112Every task follows this sequence:13141. Open `<TASK_ENV_BASE_URL>` in the browser-style fetch tool. Login with15 `ops.lead@peopleops.local` / `PeopleOps#2026` if the application requires16 authentication.172. Read the task prompt to identify the task type, target record ID, and which18 answer template fields are required.193. Fetch records from the relevant API endpoints, working from list endpoints20 to detail endpoints.214. Apply the business rules for the task type (below).225. Produce a single JSON object matching the answer template. Every string23 field that names an enum must use the exact allowed value from the template.2425## API Endpoints2627See [references/api_reference.md](references/api_reference.md) for the full28endpoint catalog, record field descriptions, and task-type-to-endpoint mapping.2930## Normalized Business Labels3132See [references/enum_reference.md](references/enum_reference.md) for every33allowed value across all answer templates. Always match these exact strings.3435## Core Business Rules3637### Record Status Precedence3839`submitted` > `draft` > `superseded`4041- Only `submitted` records are authoritative for decisions.42- `draft` records must be excluded unless the task explicitly permits drafts.43- `superseded` records were replaced by a newer submitted record; exclude them.44- When multiple submitted records exist for the same entity, use the most45 recent.4647### Audit Scoping4849- Each audit event has a `scope` field and `related_event_ids`.50- When the task asks for leave-source decisions, use only audit events scoped51 to leave precedence. Exclude document/notice or payroll audit events from52 the leave decision, listing them in `excluded_audit_event_ids`.53- When the task asks for document/notice decisions, use only audit events54 scoped to document/notice findings. Exclude leave or payroll events.55- When the task asks for payroll readiness, use only payroll-scoped audit56 events.57- A single audit event that covers the relevant scope serves as both the58 primary `audit_event_id` and the sole entry in59 `supporting_audit_event_ids`.6061## Task Types6263### 1. Onboarding Closeout6465Verify leave and payroll setup for a given employee ID before approving66onboarding completion.6768**Leave verification:**69- Fetch the employee from `/api/employees` and the leave assignment ledger from70 `/api/payroll-ledgers`.71- Identify all leave assignment records for the employee. Classify each as72 submitted, draft, or superseded.73- The effective leave policy and annual days come from the most recent74 *submitted* leave assignment. List draft and superseded leave assignment IDs75 in `excluded_leave_ids`.76- If the submitted assignment matches the current period, set77 `leave_source` to `leave_assignment_history` and78 `leave_precedence_source` to `approved_assignment_current_period`.7980**Payroll verification:**81- From `/api/payroll-ledgers`, identify all payroll assignment records for the82 employee.83- The authoritative record is the most recent submitted payroll assignment.84 Set `payroll_status` and `payroll_source_status` to `submitted`.85- List any draft or superseded payroll assignment IDs in86 `excluded_payroll_ids`.87- Extract `base_salary` from the submitted assignment.8889**Closeout decision:**90- If both leave and payroll records are clean (no drafts in authoritative91 position, no missing records), set:92 - `closeout_action`: `approve_onboarding_close`93 - `approval_closeout_gate`: `approval_sufficient_when_records_clean`94 - `final_control_result`: `approve_closeout`95- If defects exist, choose the appropriate blocker action.9697### 2. Case Folder and Notice Review9899Review a case for folder readiness and formal notice quality.100101**Folder inspection:**102- Fetch the case detail from `/api/cases/{case_id}`.103- Check `folder_status` for whether the folder is ready. Inspect listed104 documents for required files. Any required file not present goes in105 `missing_files`.106- Check `tags` for the required tag. Set `required_tag_present` accordingly.107 If the tag is already present, `folder_required_tag_action` is108 `no_tag_action`; otherwise `add_required_tag`.109110**Notice inspection:**111- Fetch notices from `/api/notifications` and inspect the formal notice112 packet.113- Check for defects: missing acknowledgement deadline, missing appeal114 instructions, missing waitlist status, incorrect policy reference.115- Set `notice_quality` to `valid` or `defective` and list any defect labels116 in `notice_defects`.117- Set `notice_evidence_source` to `notice_packet_inspection`.118119**Audit evidence:**120- Fetch audit events from `/api/audit` and `/api/audit/{audit_id}`.121- Find the audit event that covers document/notice findings. Use it for122 `audit_event_id` and `supporting_audit_event_ids`.123- Set `audit_scope` to `document_notice_findings_only`.124125**Evidence order:** Follow `approval_history_folder_notice_audit`: read126approval history first, then folder, then notice packet, then audit detail.127Set `evidence_source_order` accordingly.128129**Decision:**130- If both folder and notice are clean: `final_decision` is `approved` or131 `approved_with_conditions`.132- If folder has missing files or notice is defective: `final_decision` is133 `held` or `approved_with_conditions` (depending on approval record), and134 list blockers in `closeout_blockers`.135- If notice is defective, `next_action` is `block_close_and_reissue_notice`136 and `notice_remediation_action` is `reissue_defective_notices`.137- If folder has missing files, `escalation_action` is138 `open_records_remediation` with `records_remediation_owner` set to139 `Records`.140- `final_control_result` is `hold_for_folder_and_notice_defects` when defects141 exist.142143### 3. Recruitment Reconciliation144145Reconcile recruitment outcomes for an opening ID.146147**Candidate determination:**148- Fetch `/api/recruitment` for the opening. Inspect interview feedback and149 offer records for each candidate.150- The selected candidate is the one with an accepted offer and committee151 decision confirmation. Set `selected_offer_status` to `accepted`.152- Waitlisted candidates: those with committee waitlist status but no accepted153 offer. Put their IDs in `waitlisted_candidates`.154- Rejected candidates: those with committee rejection. Put their IDs in155 `rejected_candidates`.156- Set `candidate_status_source` to `interview_feedback_and_offer` and157 `candidate_outcome_control` to158 `committee_decision_with_offer_confirmation`.159160**Offer and cost:**161- Extract `offer_id` and `offer_base_salary` from the selected candidate's162 accepted offer.163- Sum all items from the recruitment cost ledger for `recruitment_cost_total`.164 Set `cost_source` to `recruitment_cost_ledger`.165166**Notice followup:**167- Inspect notices from `/api/notifications`. Set168 `notice_quality_source` to `notice_packet_inspection`.169- For each waitlisted candidate without a valid waitlist notice, add to170 `notice_followup_required` and set `waitlisted_followup_action` to171 `send_waitlist_notice`.172- For each rejected candidate without a valid rejection notice, add to173 `notice_followup_required` and set `rejected_followup_action` to174 `send_rejection_notice`.175176**Payroll handoff:**177- Only the selected candidate with an accepted offer triggers payroll handoff.178- Set `payroll_handoff_gate` to `accepted_offer_only`.179- Set `payroll_assignment_status_required` to180 `submitted_after_acceptance`.181- Set `draft_payroll_allowed` to `false`.182- Set `onboarding_handoff` to `create_payroll_precheck`.183- Set `handoff_control_result` to184 `submitted_handoff_required_after_acceptance`.185- For waitlisted candidates, set `offer_exclusion_reason_for_waitlisted` to186 `no_accepted_status_or_offer`.187188### 4. Leave Source Precedence189190Determine which leave policy is authoritative when both an employee profile191summary and a leave assignment ledger exist.192193**Procedure:**194- Fetch the employee from `/api/employees`. Note the leave policy in the195 profile summary.196- Fetch leave assignment records from `/api/payroll-ledgers`.197- Fetch the policy document text from `/api/policies/{policy_id}`.198- Fetch audit events from `/api/audit` and inspect the leave-scope audit199 detail from `/api/audit/{audit_id}`.200201**Rule:** An approved (submitted) leave assignment for the current period202overrides a stale employee profile summary when the ledger, policy document,203and audit detail all confirm the approved assignment.204205- If the submitted leave assignment matches the current period, set:206 - `precedence_source`: `approved_assignment_over_profile`207 - `leave_precedence_source`: `approved_assignment_current_period`208 - `profile_policy_ignored`: `true`209 - `effective_leave_policy`: the policy name from the assignment210 - `assignment_id`: the submitted assignment ID211 - `balance_days`: the balance from the assignment212 - `audit_result`: `profile_summary_stale`213 - `next_action`: `update_employee_summary`214- If no approved assignment exists for the current period, fall back to the215 profile summary policy.216217**Audit scoping:**218- Use only leave-scope audit events. Set `audit_scope` to219 `leave_source_precedence_only`.220- The primary leave-scope audit event becomes `audit_event_id` and the sole221 entry in `supporting_audit_event_ids`.222- List any document/notice or payroll-scope audit events in223 `excluded_audit_event_ids`.224225### 5. Payroll Assignment Readiness226227Verify payroll assignment and accrual batch readiness for an employee.228229**Procedure:**230- Fetch payroll assignment records from `/api/payroll-ledgers`.231- Identify the most recent submitted assignment. Extract its ID, salary, and232 effective date.233- Identify any draft or superseded assignments. List the draft assignment ID234 in `excluded_assignment_id`.235- Set `payroll_source_status` to `submitted` and `draft_exclusion_rule` to236 `exclude_draft_assignment`.237238**Accrual check:**239- From the payroll ledger, check whether the accrual batch for the relevant240 period is ready. Set `accrual_ready` to `true` or `false` and provide the241 `accrual_batch_id`.242243**Audit evidence:**244- Fetch payroll-scope audit events. Set `audit_scope` to245 `payroll_assignment_readiness`.246- The payroll-scope audit event becomes `audit_event_id`.247248**Control result:**249- If the submitted assignment is valid and accrual is ready:250 `control_result` is `ready_with_monitoring`.251- If defects exist, use the appropriate hold or block label.252253## Output Format254255Return a single JSON object. No markdown fences, no explanatory text. Match256the answer template field-by-field:257258- String fields where the template specifies an enum: use exactly one of the259 allowed values.260- Integer/number fields: the numeric value from the API record.261- Boolean fields: `true` or `false`.262- List fields: JSON arrays of strings (IDs or defect labels).263264If the task provides an `input/payloads/answer_template.json`, read it first265to confirm the exact field names and allowed values.