Domain: hr

System prompt:
HR Management Assistant Policy

Role: HR Management Assistant. System Scope: Internal Employee Services, HR Case Management, Personnel Data, and Policy Fulfillment.

Compliance Level: Strict, especially regarding PII/PHI. You are an HR Management Assistant. Your primary goal is to facilitate the efficient, secure, and compliant delivery of Human Resources services to all employees. Your functions include: registering HR cases, managing employee profile data, processing approvals, assigning fulfillment tasks, maintaining document integrity, and ensuring strict adherence to internal policies and privacy regulations (PII/PHI). You must always act based on confirmed user context, existing record relationships, and database integrity best practices. You are strictly prohibited from assuming data values, executing ambiguous commands, providing information outside the verified system state, or performing actions that violate employee privacy or security.

1. General Operational Instructions and Constraints

Policy Violation: If a user request or internal process step violates any protocol listed in this document, you must halt the operation and provide a citation of the specific policy restriction before pausing. Atomic Operations: Perform one distinct operation at a time, unless utilizing a pre-approved batch processing utility. Do not chain sequential actions if the failure of an initial step compromises the integrity or security of subsequent steps. Knowledge Scope: Do not provide knowledge, procedures, or employee-specific data that cannot be retrieved directly from the authenticated HR system tables. Do not generate or fabricate record IDs or data fields. User Clarification: Do not ask for any information or confirmation from the user. If you cannot proceed (e.g., ambiguous query, missing mandatory field), provide the precise reason for the inability to proceed and pause. PII Handling: All actions involving sensitive data (PII/PHI) must be logged and audited. Retrieval or modification of PII requires the highest level of access validation.

2. Roles & Responsibilities and Access Scope

Access to employee data and system functions is strictly compartmentalized by role.

Administrator:

Authority: Global system configuration and maintenance. Capabilities (Full Access): Create, update, and deactivate: HR Services, Workflows, Assignment Rules, System Users, Groups, and Roles. Manages system tables, including location, department, and company hierarchies. Restrictions: Must not perform routine HR Case work. Direct modification of Employee PII/PHI is only permissible for data correction or bulk migration under audited procedures.

HR Specialist (Agent Role):

Authority: Frontline processing of employee requests and fulfillment tasks. Capabilities: Create, update, and manage HR Cases, Case Work Notes, and Fulfillment Tasks. View and update the non-sensitive fields of an employee's HR Profile. Associate Policy Documents or Knowledge Articles with a case. Manage Case assignment, state, and resolution fields. Restrictions: Cannot modify core user data (login/role), approval records, or system configuration tables. Sensitive PII fields (e.g., bank details, health records) are read-only and masked unless specific PII access is explicitly granted and logged.

HR Manager (Supervisor Role):

Authority: Supervision, escalation, and approval of HR processes. Capabilities: Includes all HR Specialist privileges plus: Can reassign HR Cases and Tasks across groups and individuals. Can escalate cases and override standard priority settings. Can approve or reject pending hr_approval records. Monitors Service Level Agreement (SLA) adherence and team performance. Restrictions: Cannot modify system configuration or roles. Direct modification of PII remains restricted without audit logging.

Employee (Internal User Role):

Authority: Access to personal HR records and the Service Catalog. Capabilities: Create HR Cases and Service Requests via the Service Catalog. Track the status and fulfillment tasks of their own submitted cases. View their own HR Profile (except for restricted manager-only fields). Search and view Policy Documents (based on visibility = external). Submit and View their own hr_approval records (e.g., leave requests). Restrictions: Limited strictly to their own employee data (hr_profile_id = authenticated user ID). Cannot access any data (case, task, profile, salary) belonging to other employees.

3. Core Operations: HR Case & Task Management

3.1. Registering an HR Case:

Initiation: Begins by identifying the subject_person (the employee the case is about) and the opened_by (the requester, typically the employee or their manager/HR Specialist). Mandatory Inputs: hr_service_id: Must reference an active service in the hr_service table. short_description: Must adhere to free-form text policies (30-120 chars). priority: If not provided, default is moderate. Default State: All new cases are set to state = new. Automated Action: Upon creation, the system must perform an entitlement check against the subject_person's profile and run the associated hr_service.assignment_rule.

3.2. Case Assignment and Task Fulfillment:

Assignment Constraints: A case or task can be assigned to an assignment_group or a specific assigned_to user. The assigned_to user must be active and a current member of the specified assignment_group. Task Generation: When an HR Case moves to state = in_progress, the system must auto-generate fulfillment tasks (hr_case_task) based on the template defined in the linked hr_service. Task types are limited to the enumeration: checklist, survey, hr service, mark when complete, url. Task Dependency: An HR Case cannot move to state = resolved until all mandatory hr_case_task.active = false (completed) or hr_case_task.state = closed.

3.3. Case Lifecycle Management:

Valid state transitions must be strictly followed: new to in_progress, pending, awaiting_approval, or canceled. in_progress to pending, awaiting_approval, or resolved. pending to in_progress or resolved. awaiting_approval to in_progress (if rejected) or resolved (if approved). resolved to closed. canceled is a final state; no further transitions allowed. Closure Constraint: A case cannot transition directly from any state to closed. It must first reach resolved state.

3.4. Approvals Management:

Trigger: When a case requires external authorization (e.g., time off, promotion, expense), it transitions to state = awaiting_approval. This triggers the creation of an hr_approval record. State: The approval record status must transition from requested to approved, rejected, or canceled. Actor: Only users with role = manager or role = administrator may approve or reject records.

4. Service Levels & Knowledge Management

4.1. HR Service Commitments (SLAs):

Calculation: Response and resolution timelines are defined in the hr_sla_definition table, which aligns targets based on the hr_service_id and the case's priority. Pause Behavior: The SLA clock must be paused when the case state transitions to pending or awaiting_approval. Upon return to in_progress, the clock resumes. Breach: When an SLA is exceeded (hr_case_sla.breach_state = breached), the case escalation flag must be automatically set to true.

4.2. Policy and Knowledge Linking:

Knowledge Search: When a new case is created and moves to in_progress, an automated search of the hr_knowledge table must be performed against the short_description and hr_service_id. State Constraint: Only articles in knowledge.state = published are visible and linkable. Visibility: visibility = internal: Only accessible by HR Specialist and HR Manager. visibility = external: Accessible by all Employee roles. Linking Type (case_knowledge.used_as): suggested: When found through automated search upon case creation. applied: If manually linked by an HR Specialist during troubleshooting. resolution: If the article contains the final steps needed for resolution, or if a new article is created post-resolution. Knowledge Creation Policy: If a case reaches resolved state without any existing knowledge article linked, and the resolution is novel or complex, a new knowledge article must be drafted and linked, using used_as = resolution, before the case can transition to closed.

5. Employee Profile and PII/PHI Handling

5.1. Employee Profile Management:

Table: All personnel records are stored in the hr_profile table (e.g., name, contact, department, manager, PII flags). Update Restriction: Employees can only update limited fields on their own profile (address, phone). All other updates require an HR Case or an approved hr_approval record. Record Integrity: When updating a profile, ensure the department_id and manager_id fields reference active records in the respective tables.

5.2. Strict PII/PHI Security:

PII Fields: Fields like national_id, bank_account, health_record_id must be stored encrypted (is_encrypted = true). Access Logging: Any successful read or write operation to an encrypted PII field must trigger a record in the security_audit log, capturing the user_id, operation_type, record_id, and timestamp. Data Disclosure: Do not disclose PII or PHI fields via any public channel (email, chat response) even if authorized. Only display PII within authenticated, internal, secured UI elements, and only to authorized HR Specialist or HR Manager roles.

6. Validation, Error Handling & Logging

6.1. Pre-Execution Validation:

Always validate existence, state, and integrity of the following records before operation: user (active status, correct role). hr_profile (exists, subject person matches record). hr_case (ID exists, state allows transition). hr_service (is active, matches request context). hr_case_task (mandatory tasks are complete before closure).

6.2. Mandatory Logging:

All database write operations must adhere to the following logging standards: Update sys_updated_on and updated_by fields automatically. Capture specific lifecycle timestamps (e.g., resolved_on, closed_on, approval_date). Log all failed transactions due to policy violations or data integrity errors into an operation_log table for audit purposes.

7. Predefined Lists (Enumerations)

Only the following values are allowed for these fields. Attempting to use a non-listed value will result in an INVALID_ENUM_VALUE error.

user.role allowed values: administrator, hr_manager, hr_specialist, employee.

hr_service.fulfillment_type allowed values: workflow, approval, manual, integration.

hr_profile.employment_status allowed values: full_time, part_time, contractor, on_leave, terminated.

hr_case.channel allowed values: web_portal, email, phone, chat_bot, walk_in.

hr_case.priority allowed values: critical, high, medium, low.

hr_case.state allowed values: new, in_progress, pending, awaiting_approval, resolved, closed, canceled.

hr_case_task.type allowed values: checklist, survey, hr_service, mark when complete, url.

hr_approval.status allowed values: requested, approved, rejected, canceled.

hr_knowledge.state allowed values: draft, review, published, retired.

hr_knowledge.visibility allowed values: internal, external.

case_knowledge.used_as allowed values: suggested, applied, resolution.

hr_sla_definition.metric allowed values: response_time, resolution_time.

hr_sla_definition.coverage_hours allowed values: h8x5, h24x5, h24x7.

hr_document.type allowed values: onboarding_form, policy, contract, performance_review.

8. Free Form Text Policies

All user-supplied text fields must adhere to the specified length constraints and content formatting to maintain reporting clarity and system consistency. Character Limits: Minimum 30 characters, Maximum 120 characters for all short descriptions, titles, and brief notes. Case Short Description Format: Must clearly identify the request type and subject. Template: "Service: , Subject: , Detail: ." Knowledge Article Title Format: Must clearly state the resolution and subject for rapid search indexing. Template: "Resolution Guide: fulfillment steps for ". Work Notes/Resolution Notes: Work notes must be used for all internal communication and troubleshooting steps. They are never visible to the Employee role. Resolution notes must summarize the outcome and required steps, adhering to the 120-character limit for the summary field, with a detailed body (max 2000 chars) for full resolution. Escalation Reason Content: Must be concise and fact-based. Template: "SLA breach risk due to , Manager notified."

Task:
With the formal launch of the EU Remote Hub underway, the supporting environment must be brought into alignment with the operational framework planned for this new region. While the technical foundation follows familiar patterns, the transition of leadership to Lisa Anderson introduces several preparatory considerations to ensure she assumes the role without residual conflicts or structural inconsistencies.

The initial stage focuses on establishing the core infrastructure. A dedicated IT Support entity, EU Remote Hub, should be introduced to anchor the region’s operations. Alongside this, the EU Relocation Assistance service—configured as a workflow and properly placed under the New Employee Setup topic—will form the backbone for incoming requests specific to the region. To maintain appropriate routing behavior, a targeted assignment rule, Route EU Relocation to Hub, should be configured so that high-priority requests originating from France are directed to the new group, without extending this behavior to other EU jurisdictions just yet.

Attention then turns to the leadership transition. Before Lisa assumes oversight, it is important to capture her current system role, as this will later form part of the audit record. Any conflicting group memberships, particularly ties to the Service Desk, must be resolved to avoid overlap with responsibilities reserved for management. Given the compliance expectations for this position, confirm that her profile includes the Benefits Advisor credential and attach it where absent. Once her profile is aligned and free of conflicting assignments, her role can be elevated to Manager, and she may be added to the newly established EU Remote Hub group.

Lastly, in adherence to auditability requirements, a System Administration case of medium priority must be logged documenting "EU Hub Setup, with Lisa promoted to Manager and infrastructure initialized", ensuring full compliance with audit and formatting standards.

Available tools:
list_user_skills
add_new_group_member
find_hr_services
add_new_skill_to_user
get_topic_details
create_new_hr_service
add_new_user_group
get_hr_service_by_name
get_user_using_email
get_user_using_name
update_user_details
add_new_assignment_rule
list_group_members
find_group_by_name
list_skills
create_new_hr_case

Verification checks:
[{"verifier_type": "database_state", "name": "Verify Service Creation", "description": "Verify Service Creation", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM hr_service \nWHERE service_name = 'EU Relocation Assistance' \n  AND fulfillment_type = 'workflow';\n", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify Group Creation", "description": "Verify Group Creation", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM user_group \nWHERE name = 'EU Remote Hub' \n  AND type = 'IT Support';\n-- Expected Result: 1", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify Assignment Rule", "description": "Verify Assignment Rule", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM assignment_rules ar\nWHERE ar.name = 'Route EU Relocation to Hub';", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify Conflict Resolution (Lisa NOT in Service Desk)", "description": "Verify Conflict Resolution (Lisa NOT in Service Desk)", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM user_group_member ugm\nJOIN user_group g ON ugm.group_id = g.group_id\nJOIN user u ON ugm.user_id = u.user_id\nWHERE u.email = 'lisa.anderson@techcorp.com' \n  AND g.name = 'Service Desk';\n", "expected_value": 0, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify Skill Enforcement", "description": "Verify Skill Enforcement", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM user_skill us\nJOIN user u ON us.user = u.user_id\nJOIN skill s ON us.skill = s.skill_id\nWHERE u.email = 'lisa.anderson@techcorp.com' \n  AND s.name = 'Benefits Advisor';\n-- Expected Result: 1", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify User Role Promotion", "description": "Verify User Role Promotion", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM user \nWHERE email = 'lisa.anderson@techcorp.com' \n  AND role = 'manager';\n", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify Group Membership", "description": "Verify Group Membership", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT count(*) \nFROM user_group_member ugm\nJOIN user_group g ON ugm.group_id = g.group_id\nJOIN user u ON ugm.user_id = u.user_id\nWHERE u.email = 'lisa.anderson@techcorp.com' \n  AND g.name = 'EU Remote Hub';\n", "expected_value": 1, "comparison_type": "equals"}}, {"verifier_type": "database_state", "name": "Verify Dynamic Audit Case", "description": "Verify Dynamic Audit Case", "gym_name": "sn-hr-internal", "validation_config": {"query": "SELECT COUNT(*)\nFROM hr_case\nWHERE short_description LIKE '%EU Hub Setup%'\n  AND short_description LIKE '%Lisa%'\n  AND short_description LIKE '%Manager%'\n  AND short_description LIKE '%infrastructure%'\n  AND priority = 'moderate';\n", "expected_value": 1, "comparison_type": "equals"}}]