PeopleOps Console
Verify HR lifecycle records by fetching data from the REST API, applying business-policy rules, and returning structured JSON.
Quick Start
- Read the task prompt for the
<TASK_ENV_BASE_URL> and credentials.
- Fetch all relevant API collections in parallel:
/api/employees, /api/cases, /api/policies, /api/payroll-ledgers, /api/recruitment, /api/documents, /api/messages, /api/audit.
- Drill into specific records (single case, policy, audit event, attachment) only when needed.
- Apply the business rules from references/business_rules.md and use only the normalized enum values from references/enum_catalog.md.
- Return a single JSON object matching the answer template in the payload.
API Reference
All endpoints and data shapes are in references/api_reference.md. Fetch that file before making any API calls.
Business Rules
Core decision rules for each domain are in references/business_rules.md. Read it after fetching data to map raw records to normalized conclusions.
Enum Catalog
Every allowed enum value across all answer-template fields is listed in references/enum_catalog.md. Scan it before populating any enum field — never invent a label.
Workflows
Onboarding Closeout
Examine an employee's leave and payroll ledger records, then apply source-precedence rules.
Steps:
- Fetch employee list and find the target employee by ID.
- Fetch payroll-ledgers; filter by employee_id.
- Leave: Pick the record with status
Approved for the current period. Mark any Superseded or Draft leave records as excluded. Use the policy_name and approved_leave_days from the approved record.
- Payroll: Pick the record where
record_type is Salary assignment and status is Submitted. Mark any Draft salary assignment as excluded. Use base_salary from the submitted record.
- Set
leave_source to leave_assignment_history, leave_precedence_source to approved_assignment_current_period, payroll_status / payroll_source_status to submitted.
- If leave and payroll records are clean (no draft/superseded contamination), set
approval_closeout_gate to approval_sufficient_when_records_clean, closeout_action to approve_onboarding_close, and final_control_result to approve_closeout.
Policy Case Folder and Notice Review
Review a case's folder checklist and formal notice for defects.
Steps:
- Fetch the case detail:
GET /api/cases/{case_id}. This returns approvals, attachments (checklist), and audit events.
- From the folder checklist attachment (
kind: Checklist): compare files against required_files to find missing entries. Compare tags against required_tags.
- From messages (
GET /api/messages): find the matching case_id, read quality and defects. If quality is defective, list the defect codes.
- From approvals: identify the final approval step (largest
decided_at or step named Final approval) and extract decision and approver.
- From audit events with matching
case_id: use the one whose scope matches documents/notices.
- Set
evidence_source_order to approval_history_folder_notice_audit when all sources are used. Set notice_evidence_source to notice_packet_inspection when using messages.
- If any required file is missing, add
missing_required_files to closeout_blockers. If any tag is missing, add missing_required_tags. If notice is defective, add defective_formal_notice.
- When blockers exist: set
approval_closeout_gate to approval_not_sufficient_when_folder_or_notice_defective, final_control_result to hold_for_folder_and_notice_defects, and choose the appropriate next_action and escalation_action.
Recruitment Reconciliation
Reconcile a recruitment opening's candidates, offers, costs, and notices.
Steps:
- Fetch recruitment data:
GET /api/recruitment. Find the target opening_id.
- From
candidates: read committee_decision for each. Selected → selected_candidate. Waitlisted → waitlisted_candidates. Rejected → rejected_candidates.
- From
offer_register: find the offer with candidate_id matching the selected candidate. Extract offer_id, base_salary, and status.
- From
cost_ledger: sum all amount values across line items to compute recruitment_cost_total.
- From
notice_packets: identify candidates needing follow-up. Set notice_followup_required to their candidate_ids. Match notice_type to waitlisted_followup_action and rejected_followup_action.
- For payroll handoff: if the selected candidate's offer is
accepted, set onboarding_handoff to create_payroll_precheck and payroll_handoff_gate to accepted_offer_only. Set draft_payroll_allowed to false.
- Set
candidate_status_source to interview_feedback_and_offer, candidate_outcome_control to committee_decision_with_offer_confirmation, cost_source to recruitment_cost_ledger.
Leave Source Precedence
Determine which leave policy controls when profile and assignment conflict.
Steps:
- Fetch the employee and their payroll-ledger leave records.
- Fetch the relevant policy:
GET /api/policies/LEAVE-SRC-001 confirms that latest approved/submitted assignment controls.
- Compare the employee profile's
leave_balance_days and implicit policy against the approved leave assignment's policy_name and approved_leave_days.
- If the approved assignment exists for the current period: it controls. Set
precedence_source to approved_assignment_over_profile, leave_precedence_source to approved_assignment_current_period, profile_policy_ignored to true.
- Fetch audit events; find the one with matching
employee_id and event in leave.profile_mismatch. That becomes the primary audit_event_id and supporting event.
- Exclude any audit events whose scope is document/notice only (not leave-related) from
supporting_audit_event_ids.
- Set
audit_scope to leave_source_precedence_only, audit_result to profile_summary_stale, next_action to update_employee_summary.
Payroll Assignment Readiness
Verify which payroll assignment controls and whether accrual is ready.
Steps:
- Fetch payroll-ledgers and find salary assignments for the employee.
- Select the record with
status: Submitted. Extract ledger_id, base_salary, period (use first day as effective_date). Mark the Draft assignment as excluded.
- Check the submitted record for an
accrual_batch_id field. If present, set accrual_ready to true and use the batch id.
- Fetch audit events; find the one with matching
employee_id and event: payroll.ready.
- Set
payroll_source_status to submitted, draft_exclusion_rule to exclude_draft_assignment, audit_scope to payroll_assignment_readiness, control_result to ready_with_monitoring.
Important Rules
- Never guess enum values. Always look them up in references/enum_catalog.md.
- Draft records are always excluded from effective leave, payroll, and assignment decisions unless a policy explicitly allows them.
- Superseded records are excluded when a newer approved or submitted record exists for the same period.
- Source precedence chain: approved assignment > submitted assignment > profile summary > case summary only.
- Evidence source order: always prefer the richest chain: approval history + folder checklist + notice review + audit events. Narrow only when the task explicitly constrains scope.
- Audit scope isolation: when the task asks for leave-only or payroll-only findings, exclude document/notice audit events from the decision and their IDs from supporting lists.
- All dollar amounts and day counts come from the API data, not from the answer template or from inference.
1---2name: peopleops-console-63description: HR operations verification in the PeopleOps Console. Use when the task involves onboarding closeout, policy case folder/notice review, recruitment reconciliation, leave source precedence, payroll assignment readiness, or any PeopleOps lifecycle verification that requires cross-referencing employees, cases, policies, payroll ledgers, recruitment packets, documents, messages, and audit events through the REST API. Triggers on PeopleOps, People Ops, employee onboarding, policy case review, recruitment reconciliation, leave policy, payroll assignment, HR verification, or closeout workflows.4metadata:5 source: https://skillmd.com/skills/prism-shadow/peopleops-console-66---78# PeopleOps Console910Verify HR lifecycle records by fetching data from the REST API, applying business-policy rules, and returning structured JSON.1112## Quick Start13141. Read the task prompt for the `<TASK_ENV_BASE_URL>` and credentials.152. Fetch all relevant API collections in parallel: `/api/employees`, `/api/cases`, `/api/policies`, `/api/payroll-ledgers`, `/api/recruitment`, `/api/documents`, `/api/messages`, `/api/audit`.163. Drill into specific records (single case, policy, audit event, attachment) only when needed.174. Apply the business rules from [references/business_rules.md](references/business_rules.md) and use only the normalized enum values from [references/enum_catalog.md](references/enum_catalog.md).185. Return a single JSON object matching the answer template in the payload.1920## API Reference2122All endpoints and data shapes are in [references/api_reference.md](references/api_reference.md). Fetch that file before making any API calls.2324## Business Rules2526Core decision rules for each domain are in [references/business_rules.md](references/business_rules.md). Read it after fetching data to map raw records to normalized conclusions.2728## Enum Catalog2930Every allowed enum value across all answer-template fields is listed in [references/enum_catalog.md](references/enum_catalog.md). Scan it before populating any enum field — never invent a label.3132## Workflows3334### Onboarding Closeout3536Examine an employee's leave and payroll ledger records, then apply source-precedence rules.3738**Steps:**39401. Fetch employee list and find the target employee by ID.412. Fetch payroll-ledgers; filter by employee_id.423. **Leave:** Pick the record with status `Approved` for the current period. Mark any `Superseded` or `Draft` leave records as excluded. Use the policy_name and approved_leave_days from the approved record.434. **Payroll:** Pick the record where `record_type` is `Salary assignment` and status is `Submitted`. Mark any `Draft` salary assignment as excluded. Use base_salary from the submitted record.445. Set `leave_source` to `leave_assignment_history`, `leave_precedence_source` to `approved_assignment_current_period`, `payroll_status` / `payroll_source_status` to `submitted`.456. If leave and payroll records are clean (no draft/superseded contamination), set `approval_closeout_gate` to `approval_sufficient_when_records_clean`, `closeout_action` to `approve_onboarding_close`, and `final_control_result` to `approve_closeout`.4647### Policy Case Folder and Notice Review4849Review a case's folder checklist and formal notice for defects.5051**Steps:**52531. Fetch the case detail: `GET /api/cases/{case_id}`. This returns approvals, attachments (checklist), and audit events.542. From the folder checklist attachment (`kind: Checklist`): compare `files` against `required_files` to find missing entries. Compare `tags` against `required_tags`.553. From messages (`GET /api/messages`): find the matching `case_id`, read `quality` and `defects`. If `quality` is `defective`, list the defect codes.564. From approvals: identify the final approval step (largest `decided_at` or step named `Final approval`) and extract `decision` and `approver`.575. From audit events with matching `case_id`: use the one whose scope matches documents/notices.586. Set `evidence_source_order` to `approval_history_folder_notice_audit` when all sources are used. Set `notice_evidence_source` to `notice_packet_inspection` when using messages.597. If any required file is missing, add `missing_required_files` to `closeout_blockers`. If any tag is missing, add `missing_required_tags`. If notice is defective, add `defective_formal_notice`.608. When blockers exist: set `approval_closeout_gate` to `approval_not_sufficient_when_folder_or_notice_defective`, `final_control_result` to `hold_for_folder_and_notice_defects`, and choose the appropriate `next_action` and `escalation_action`.6162### Recruitment Reconciliation6364Reconcile a recruitment opening's candidates, offers, costs, and notices.6566**Steps:**67681. Fetch recruitment data: `GET /api/recruitment`. Find the target `opening_id`.692. From `candidates`: read `committee_decision` for each. `Selected` → selected_candidate. `Waitlisted` → waitlisted_candidates. `Rejected` → rejected_candidates.703. From `offer_register`: find the offer with `candidate_id` matching the selected candidate. Extract `offer_id`, `base_salary`, and `status`.714. From `cost_ledger`: sum all `amount` values across line items to compute `recruitment_cost_total`.725. From `notice_packets`: identify candidates needing follow-up. Set `notice_followup_required` to their candidate_ids. Match `notice_type` to `waitlisted_followup_action` and `rejected_followup_action`.736. For payroll handoff: if the selected candidate's offer is `accepted`, set `onboarding_handoff` to `create_payroll_precheck` and `payroll_handoff_gate` to `accepted_offer_only`. Set `draft_payroll_allowed` to `false`.747. Set `candidate_status_source` to `interview_feedback_and_offer`, `candidate_outcome_control` to `committee_decision_with_offer_confirmation`, `cost_source` to `recruitment_cost_ledger`.7576### Leave Source Precedence7778Determine which leave policy controls when profile and assignment conflict.7980**Steps:**81821. Fetch the employee and their payroll-ledger leave records.832. Fetch the relevant policy: `GET /api/policies/LEAVE-SRC-001` confirms that latest approved/submitted assignment controls.843. Compare the employee profile's `leave_balance_days` and implicit policy against the approved leave assignment's `policy_name` and `approved_leave_days`.854. If the approved assignment exists for the current period: it controls. Set `precedence_source` to `approved_assignment_over_profile`, `leave_precedence_source` to `approved_assignment_current_period`, `profile_policy_ignored` to `true`.865. Fetch audit events; find the one with matching `employee_id` and `event` in `leave.profile_mismatch`. That becomes the primary audit_event_id and supporting event.876. Exclude any audit events whose scope is document/notice only (not leave-related) from `supporting_audit_event_ids`.887. Set `audit_scope` to `leave_source_precedence_only`, `audit_result` to `profile_summary_stale`, `next_action` to `update_employee_summary`.8990### Payroll Assignment Readiness9192Verify which payroll assignment controls and whether accrual is ready.9394**Steps:**95961. Fetch payroll-ledgers and find salary assignments for the employee.972. Select the record with `status: Submitted`. Extract `ledger_id`, `base_salary`, `period` (use first day as effective_date). Mark the Draft assignment as excluded.983. Check the submitted record for an `accrual_batch_id` field. If present, set `accrual_ready` to `true` and use the batch id.994. Fetch audit events; find the one with matching `employee_id` and `event: payroll.ready`.1005. Set `payroll_source_status` to `submitted`, `draft_exclusion_rule` to `exclude_draft_assignment`, `audit_scope` to `payroll_assignment_readiness`, `control_result` to `ready_with_monitoring`.101102## Important Rules103104- **Never guess enum values.** Always look them up in [references/enum_catalog.md](references/enum_catalog.md).105- **Draft records are always excluded** from effective leave, payroll, and assignment decisions unless a policy explicitly allows them.106- **Superseded records are excluded** when a newer approved or submitted record exists for the same period.107- **Source precedence chain:** approved assignment > submitted assignment > profile summary > case summary only.108- **Evidence source order:** always prefer the richest chain: approval history + folder checklist + notice review + audit events. Narrow only when the task explicitly constrains scope.109- **Audit scope isolation:** when the task asks for leave-only or payroll-only findings, exclude document/notice audit events from the decision and their IDs from supporting lists.110- **All dollar amounts and day counts** come from the API data, not from the answer template or from inference.