farstic/ai-servicenow-architect / .claude/skills/hrsd-specialist
hrsd-specialist
VerifiedMandatory gateway for HR Service Delivery — HR case lifecycle, Lifecycle Events (LE), HR Profile, Employee Center and Employee Center Pro, HR document templates, HR data policies, HR Knowledge. Produces the 5-Part Constraint Envelope.
| File | Kind | Size |
|---|---|---|
| EXAMPLES.md | markdown | 30.8 KB |
| SKILL.md | skill md | 50.7 KB |
EXAMPLES.md
View on GitHub# HRSD Specialist v2.0 — Worked Examples
Three examples exercising each §1.1 verdict path. Each shows the full 5-Part Constraint Envelope for a realistic HRSD dispatch. Read alongside `SKILL.md`.
---
## Example 1 — Verdict A (Fully Baseline)
### Dispatch input
**Source:** Chief Architect, routing from a user request.
**User request:** *"We need an Internal Transfer Lifecycle Event. When an employee transfers between departments, we need to: notify the new manager, send a welcome packet, update HR Profile, create an IT task to reprovision access, and schedule a 30-day check-in. Show me how to design this."*
**Module:** HRSD
**Workspace:** HR Agent Workspace + Employee Center
**Volume:** ~150 internal transfers/year
**Sensitivity:** PII (employee record updates)
### Gateway Response
```markdown
# HRSD Specialist Gateway Response
**Request:** Implement an Internal Transfer Lifecycle Event with five activities.
**Domain Expert:** HRSD Specialist v2.0
**Release family:** Australia (HRSD published as Employee Service Management)
---
## Part 1 — OOB Process Map
The baseline HRSD Lifecycle Events framework handles structured employee journeys via the activity-set library. The OOB flow for any LE:
1. **LE trigger** — typically a record producer in Employee Center ("Initiate Internal Transfer") or an HR agent action, or a scheduled trigger (e.g., effective-date-driven).
2. **Lifecycle Event Case creation** — a new `sn_hr_le_case` record is created (extends `sn_hr_core_case`), with a reference to its Lifecycle Events Type (`sn_hr_le_type`; the field is not documented in the bundled corpus — verify on the instance) pointing to the configured LE type. When an HR service's **Fulfillment type** is Lifecycle Event (Enterprise Onboarding and Transition only), its own **Lifecycle Event Type** field names the lifecycle event that fulfills it *(citation: `markdown/employee-service-management/hr-service-delivery/configure-hr-service.md`)*; an HR service whose lifecycle event type is the same as the LE type used in an LE activity can create a loop that causes memory issues *(citation: `markdown/employee-service-management/lifecycle-events/create-hr-service-for-lifecycle-event.md`)*.
3. **Activity Set retrieval** — `sn_hr_le_activity_set` records linked to the LE type fire in defined order.
4. **Activity execution** — each `sn_hr_le_activity` runs:
- Notifications fire via the HR notification engine
- HR tasks are created on `sn_hr_core_task`
- Document generation fires from Document Template [`sn_doc_template`]
- Subflow invocations fire from Flow Designer
- Wait-for-condition steps gate downstream activities
5. **LE Case progression** — `sn_hr_le_case.state` advances as activities complete. Sub-state (`sub_state` — not documented in the bundled corpus — verify on the instance) tracks LE-specific stage if needed.
6. **Closure** — when all activity sets complete, `sn_hr_le_case.state` advances to Closed Complete.
For an Internal Transfer specifically, baseline HRSD ships activity-set templates for transfer scenarios that engagements typically tailor (not customise into new tables).
(citation: markdown/employee-service-management/index.md — Lifecycle Events section)
## Part 2 — Data Model Alignment
**Primary baseline tables:**
| Table | Purpose |
|---|---|
| `sn_hr_le_case` | The LE case record (extends `sn_hr_core_case`) |
| `sn_hr_le_activity_set` | The set of activities for an LE type |
| `sn_hr_le_activity` | Individual activities within a set |
| `sn_hr_core_profile` | Employee data updated by the LE |
| `sn_hr_core_task` | Tasks generated by activities (e.g., manager check-in) |
| `sn_doc_template` | Document templates (welcome packet); HR Document Templates is deprecated as of Australia *(citation: `markdown/employee-service-management/hr-service-delivery/reference-doc-templates.md`, `markdown/employee-service-management/hr-service-delivery/migration-hrdt-dt.md`)* |
**Critical baseline fields on `sn_hr_le_case`:**
| Field | Type | Purpose |
|---|---|---|
| `subject_person` | Reference to `sys_user` | The transferring employee |
| `opened_for` | Reference to `sys_user` | Who initiated (often the employee or HRBP) |
| (the LE type reference — field not documented in the bundled corpus — verify on the instance) | Reference to `sn_hr_le_type` | Links to the Internal Transfer LE definition; on the HR service, when its **Fulfillment type** is Lifecycle Event, the **Lifecycle Event Type** field selects the lifecycle event that fulfills it (Enterprise Onboarding and Transition only) *(citation: `markdown/employee-service-management/hr-service-delivery/configure-hr-service.md`)* |
| `state` | Choice (inherits from `sn_hr_core_case`) | Lifecycle state |
| `sub_state` | Choice | Use for transfer-specific stages if needed; not documented in the bundled corpus — verify on the instance |
**For IT task creation (reprovision access):** the LE activity can create an `sc_request` / `sc_req_item` via baseline Service Catalog integration, or call an HR-to-IT subflow. No new table needed.
(citation: markdown/employee-service-management/index.md — HR Case data model)
## Part 3 — §1.1 Baseline-First Verdict
**Verdict: A — Fully covered by baseline.**
The Internal Transfer LE is fully satisfied by baseline HRSD constructs:
1. **Create a new `sn_hr_le_activity_set` record** named "Internal Transfer Activity Set".
2. **Define five `sn_hr_le_activity` records** under that activity set:
- Activity 1: Notification — new-manager welcome (uses HR notification engine; template references `subject_person`, `sn_hr_core_profile.manager`, `sn_hr_core_profile.department`)
- Activity 2: HR Task — "Send Welcome Packet" assigned to HR coordinator (creates `sn_hr_core_task`); document generation via existing `sn_doc_template`
- Activity 3: HR Profile update — write `manager`, `department`, `location` on `sn_hr_core_profile` (baseline HR Profile update action available in activity-set library)
- Activity 4: IT task creation — Service Catalog record producer for "Internal Transfer — Access Reprovisioning" creates `sc_request` / `sc_req_item` for IT (reuses existing IT-facing catalog item)
- Activity 5: Wait-for-condition + HR Task — 30 days after transfer effective date, create check-in task
No custom table. No custom scoped app. No custom flow. Pure configuration of the baseline activity-set library.
(citation: markdown/employee-service-management/index.md — Activity sets and activities)
## Part 4 — Routing Recommendation
**PROCEED — baseline configuration only.**
No Technical Designer dispatch needed. The configuration path:
1. HR Admin creates new `sn_hr_le_activity_set` record for Internal Transfer.
2. HR Admin defines the five activities in the set.
3. HR Admin links the activity set to an LE type record (either a new Internal Transfer LE type or reuses an existing baseline transfer LE type).
4. HR Admin creates the Employee Center record producer "Initiate Internal Transfer" (or repurposes an existing one).
5. HR Admin tests end-to-end in a sub-prod instance.
Optional Developer involvement: only if Activity 4's IT task creation needs custom Service Catalog variable handling. Minor — fits in a small Business Rule or Script Include. Code Reviewer fires per §6.2.
Consult flags:
- **Security & GRC** — minor consult since HR Profile fields are PII-classified. Baseline ACLs cover this; consult is informational only.
- **Integration Specialist** — only if the IT task creation involves a non-baseline external IT system; not the case here.
## Part 5 — Anti-Patterns to Block
- **Do not create a `u_internal_transfer_case` table.** `sn_hr_le_case` covers it; this would be a §1.1 violation.
- **Do not write a custom Flow Designer flow that orchestrates the five activities outside the activity-set library.** Use `sn_hr_le_activity_set` + `sn_hr_le_activity` records. The activity-set library is the baseline orchestration mechanism.
- **Do not create a custom HR Profile extension table to track the transfer history.** `sn_hr_core_profile` audit history (`sys_history_set`) tracks manager/department/location changes natively.
- **Do not extend `sn_hr_le_case.state` with new transfer-specific states.** Carry a variant in a field, or in the sub-state where the instance has one (see the field table above).
- **Do not duplicate the welcome-packet document in a custom template table.** Use `sn_doc_template`.
- **Do not hardcode IT-task creation logic in a Business Rule on `sn_hr_le_case`.** The activity-set library has a dedicated activity type for cross-application task creation.
## Open Questions
OQ-EV-1. **Existing baseline Internal Transfer LE template** — does the engagement's release ship a baseline Internal Transfer LE type that can be tailored, or does a new LE type need to be created? Verify in the Lifecycle Events Type [`sn_hr_le_type`] table *(citation: `markdown/employee-service-management/lifecycle-events/components-installed-with-enterprise-onboarding-and-transitions.md`)*.
OQ-EV-2. **IT-task catalog item** — is there an existing "Internal Transfer — Access Reprovisioning" record producer in the engagement's IT catalog, or does one need to be created? If yes-needs-creating, ITSM Specialist consult is appropriate.
OQ-EV-3. **30-day check-in scheduling** — the wait-for-condition activity needs a clear trigger (transfer effective date + 30 days). Confirm whether the effective date is captured on the LE case directly or sourced from HR Profile.
---
*End of HRSD Specialist Gateway Response.*
```
---
## Example 2 — Verdict B (Baseline Extension)
### Dispatch input
**Source:** Chief Architect.
**User request:** *"On our internal transfer LE cases, we want to record the target role title (the new role the employee is moving into). Currently we use the existing `subject_person`'s new `sn_hr_core_profile.position` field, but for the LE we need to capture the *intended* title before the transfer is effective, separate from the current profile position."*
**Module:** HRSD
**Volume:** ~150 transfers/year (continues from Example 1)
**Sensitivity:** Internal HR data, PII context
### Gateway Response
```markdown
# HRSD Specialist Gateway Response
**Request:** Capture a "target role title" attribute on Internal Transfer LE cases, distinct from current HR Profile position.
**Domain Expert:** HRSD Specialist v2.0
**Release family:** Australia (HRSD published as Employee Service Management)
---
## Part 1 — OOB Process Map
The Internal Transfer LE flow (per Example 1 envelope) creates `sn_hr_le_case` records. The HR Profile (`sn_hr_core_profile`) for the subject_person carries the *current* position via `sn_hr_core_profile.position`. The transfer activity-set eventually writes the new position to HR Profile when the transfer becomes effective.
The user wants to capture the *intended* (future) position on the LE case itself — separate from current HR Profile. This represents pre-effective transfer data: the answer to "what role is the employee moving INTO" while the case is still in flight.
(citation: markdown/employee-service-management/index.md — HR Profile and LE Case interaction)
## Part 2 — Data Model Alignment
**Primary baseline table:** `sn_hr_le_case` (extends `sn_hr_core_case`, which extends `task`)
**Existing baseline fields evaluated for this need:**
| Field | Coverage |
|---|---|
| `sn_hr_le_case.subject_person.sn_hr_core_profile.position` | Current position (will become old position after transfer). Does NOT carry the intended future title. |
| `sn_hr_le_case.short_description` / `description` | Free text — agents could type the target title here, but it's not structured and not reportable. |
| `sn_hr_le_case.work_notes` | Free text — same limitation. |
No baseline field on `sn_hr_le_case` (or its parents) captures the *intended target* role title. The semantic is genuinely missing in baseline.
(citation: markdown/employee-service-management/index.md — sn_hr_le_case field model)
## Part 3 — §1.1 Baseline-First Verdict
**Verdict: B — Requires baseline extension.**
The smallest viable extension:
**Add a single String field on `sn_hr_le_case`:**
- **Field name:** `sn_hr_le_case.u_target_role_title` (open question 1 covers how the platform names it)
- **Type:** String, length 100
- **Mandatory:** No (transfer LE cases may exist before target title is finalised)
- **ACL:** Inherits `sn_hr_le_case` field ACLs
- **Form layout:** Surface in the HR Agent Workspace LE case form near `subject_person` and the LE type reference
This is Verdict B because:
- The semantic is genuinely missing from baseline `sn_hr_le_case` (verified in Part 2).
- One field is the smallest possible extension — no new table, no new scoped app, no state-model change.
- The field is at the top of §1.1's preference hierarchy (field on baseline table).
(citation: markdown/employee-service-management/index.md — HR Case form extensibility)
## Part 4 — Routing Recommendation
**PROCEED — dispatch to Technical Designer with constraints.**
Technical Designer's deliverable:
1. **Field definition** — `sn_hr_le_case.u_target_role_title` (String, 100, mandatory=No)
2. **Form layout update** — surface field in HR Agent Workspace, in the Transfer LE variant form
3. **Record producer update** — if the "Initiate Internal Transfer" record producer collects target title from the requesting manager, add a variable for it and map to the new field on case create
4. **Reporting** — direction to Reporting & Analytics for any "Transfers by target title" indicators (not Technical Designer's deliverable)
5. **No new ACLs** — explicit confirmation
6. **No code** — pure configuration unless record producer mapping needs a small Catalog Client Script
Consult flags:
- **Reporting & Analytics** — downstream, non-blocking
- **Security & GRC** — minor consult; field contains role information which is generally non-sensitive but engagement-specific classification may differ
## Part 5 — Anti-Patterns to Block
- **Do not write `u_target_role_title` to `sn_hr_core_profile.position` early.** That field captures the *current* position; overwriting it pre-effective creates audit confusion and breaks Employee Center "my profile" display.
- **Do not create a `u_target_role` table.** One field on the baseline LE case table is enough.
- **Do not extend `sn_hr_le_case.state` with new "Target Title Set" / "Target Title Confirmed" states.** State is lifecycle progress, not a data-presence flag. Use a separate field, or the sub-state where the instance has one, if pre-effective sub-stages are needed.
- **Do not duplicate the title into HR Profile via a custom Business Rule** before the transfer is effective. The activity-set library handles HR Profile updates at the right step.
- **Do not name the field with engagement-scope prefix if engagement convention uses dictionary-level extension on baseline tables.** Coordinate with App Engine Specialist on naming.
## Open Questions
OQ-EV-1. **Engagement field-naming convention** — on `sn_hr_le_case` the platform names a new field by where it is created: in the table's own scope it takes no prefix, so `u_target_role_title` is the engagement's mark for a custom field; created from global, the platform adds `u_`; from a scoped app, that app's namespace, `x_<vendor>_<app>_target_role_title` *(citation: `markdown/platform-administration/table-administration-and-data-management/r_DictionaryEntryForm.md`)*. Confirm with Chief Architect / App Engine Specialist.
OQ-EV-2. **Record producer variable** — does the existing "Initiate Internal Transfer" record producer already collect this attribute (perhaps under a different name)? If yes, the field may need a rename consultation; if no, the variable definition is part of the same configuration change.
OQ-EV-3. **Target title vs target position record** — is the target a free-text title, or should it be a reference to a position table (Position [`sn_hr_core_position`] *(citation: `markdown/employee-service-management/hr-service-delivery/components-installed-with-case-and-knowledge-management.md`)*)? If reference, escalates the design — possible Verdict B+ with a join consideration. Verify Discovery output on position-table presence.
---
*End of HRSD Specialist Gateway Response.*
```
---
## Example 3 — Verdict C (§1.1 Halt)
### Dispatch input
**Source:** Chief Architect.
**User request:** *"We need to extend HR Profile with engagement-specific PII fields: passport number, work-permit expiry, dependants (number and ages), security-clearance level and expiry, and emergency-contact full details (relationship, full address, phone, alternative phone). These fields must be stored separately from the main `sn_hr_core_profile` so we can apply COE-specific read ACLs (e.g., only the Mobility COE can read passport and work-permit; only the Security COE can read clearance fields)."*
**Module:** HRSD
**Volume:** ~5K active employees across global offices
**Sensitivity:** Special-category PII (passport, security clearance), country-specific HR data law applicability
### Gateway Response
```markdown
# HRSD Specialist Gateway Response
**Request:** Add multiple categories of sensitive HR data with COE-specific access controls.
**Domain Expert:** HRSD Specialist v2.0
**Release family:** Australia (HRSD published as Employee Service Management)
---
## Part 1 — OOB Process Map
`sn_hr_core_profile` is the baseline HR Profile table — a single denormalised record per employee carrying employment data, manager hierarchy, location, employment status, dates. Baseline HRSD adds field-level audit and supports dictionary-level extension for additional employment attributes.
Field-level access controls in HRSD operate at two layers:
1. **Table-level ACLs** on `sn_hr_core_profile` — gate which roles can read/write the profile at all
2. **Field-level ACLs** on individual fields — gate finer-grained access within the profile (e.g., a role can read profile but not see compensation field)
For COE-specific data isolation, baseline HRSD ships the **Human Resources Scoped App: Security** plugin (`com.snc.hr.scoped_security`) *(citation: `markdown/employee-service-management/hr-service-delivery/activate-case-and-knowledge-management-scoped.md`)* which provides:
- `subject_person`-based ACL conditions (an HR agent only sees profiles for employees in COEs they belong to)
- Restricted-notes pattern (sensitive HR notes hidden from non-COE agents)
- Group-based ACL inheritance
The user's request describes *five distinct categories of sensitive data* with *three distinct access-control patterns* (Mobility-only for two fields, Security-only for two fields, and presumably broader read for emergency contact). This is a non-trivial ACL design AND a data-organisation design.
(citation: markdown/employee-service-management/index.md — HR Profile, Scoped HR Security)
## Part 2 — Data Model Alignment
**Primary baseline table:** `sn_hr_core_profile`
**Existing baseline fields evaluated:**
| Field | Coverage |
|---|---|
| `sn_hr_core_profile` (existing fields) | None of the proposed fields exist baseline. Passport, work-permit, dependants and clearance are absent; emergency contacts are a baseline related list (next row). |
| Dictionary extension on `sn_hr_core_profile` | Possible — but field-level ACLs would need to be configured per field with COE-specific conditions. |
| `sys_user.country` | Exists but covers nationality at user level, not passport details. |
| Emergency contacts | Baseline and structured: the HR profile's Emergency Contacts list, records in `sn_hr_core_contact`, one designated primary and the others alternates *(citation: `markdown/employee-service-management/hr-service-delivery/t_CreateOrModifyAUserProfile.md`, `markdown/employee-service-management/hr-service-delivery/document-template-scripts.md`)*. A documented template script reads `name`, `mobile_phone`, `relation_to_employee`, `priority` and `date_of_birth` from these records *(citation: `markdown/employee-service-management/hr-service-delivery/document-template-scripts.md`)*, and the HR Contact form takes the contact's name and telephone numbers, in the plural *(citation: `markdown/employee-service-management/hr-service-delivery/t_Contacts.md`)*, so a relationship and a phone are covered; a full address, and the field that would hold an alternative phone, are not documented in the bundled corpus — verify on the instance. |
**Related baseline constructs:**
- **Scoped HR Security plugin** — provides the ACL machinery for COE-based access control on profiles and notes.
- **Field-level ACLs (`sys_security_acl`)** — provide per-field gating.
- **`sn_hr_core_profile` audit** — `sys_history_set` captures field-level changes, but does NOT provide field-level encryption-at-rest.
The user's request spans:
- Multiple new data attributes (5 categories, ~12 fields total)
- Multiple sensitivity tiers (passport / work-permit = Mobility; clearance = Security; emergency = broader)
- Country-specific compliance (passport data subject to country-specific HR data laws)
This is beyond a single field extension. It is a data-model design question with ACL implications.
(citation: markdown/employee-service-management/index.md — HR Profile data model, Scoped HR Security)
## Part 3 — §1.1 Baseline-First Verdict
**Verdict: C — Requires custom object. §1.1 HALT.**
```
🚨 OPEN QUESTION — CUSTOM OBJECT PROPOSAL (§1.1 Blocking)
Before any specialist may be dispatched, §1.1 requires honest evaluation. This proposal halts dispatch until Chief Architect decision is received.
1. Baseline options evaluated [citations REQUIRED]:
a. Extend `sn_hr_core_profile` directly via dictionary (add fields to baseline table)
- Covers: storage of all 12 proposed fields on the existing HR Profile record
- Falls short: field-level ACLs with COE-specific conditions become complex and brittle (12 fields × 3 COE-tier patterns = 36 ACL conditions to maintain). Risk: ACL gap on field exposes sensitive data. Performance: each profile-form load runs all field ACLs.
- Citation: markdown/employee-service-management/ (HR Profile dictionary extension)
b. Use the baseline emergency contacts (`sn_hr_core_contact`) for emergency contact, dictionary-extend `sn_hr_core_profile` for everything else
- Covers: emergency contact, structured, with a primary and alternates
- Falls short: the other fields still need extension on `sn_hr_core_profile` with the same ACL complexity.
- Citation: `markdown/employee-service-management/hr-service-delivery/t_CreateOrModifyAUserProfile.md` (Emergency Contacts)
c. Use the baseline Scoped HR Security plugin + dictionary extension + field-level ACLs
- Covers: COE-based access control mechanism is baseline (scoped HR security plugin)
- Falls short: still requires 12 fields on `sn_hr_core_profile` with per-field ACL — same brittleness as option (a). Plugin handles subject_person isolation, not COE-tiered field-level access.
- Citation: markdown/employee-service-management/ (Scoped HR Security)
d. Defer storage to HRIS (e.g., Workday) and read into ServiceNow via integration
- Covers: separation of concern — sensitive data lives in HRIS where it belongs
- Falls short: requires HRIS integration design; doesn't satisfy "store in ServiceNow" requirement; may not align with engagement's data-sovereignty stance
- Citation: n/a (architecture pattern)
2. Custom object proposed (smallest viable scope):
- Objects: two new tables, one per restricted tier — `sn_hr_core_profile_mobility` (proposed — not baseline) and `sn_hr_core_profile_security` (proposed — not baseline). Emergency contacts stay in the baseline `sn_hr_core_contact` (Part 2), so there is no third table.
- Kind and place in the §1.1 hierarchy: new tables extending a baseline table, in the baseline `sn_hr_core` scope — the "acceptable" rung. Fields on the baseline profile were weighed first and rejected: access by sensitivity tier is the failure mode, not storage. A top-level table or a new scoped app is not justified.
- What they would hold, in the request's words: "passport number, work-permit expiry" for the Mobility COE, and "security-clearance level and expiry" for the Security COE, "stored separately from the main `sn_hr_core_profile`".
3. Consequences of approval:
- **Data model:** two new child tables in `sn_hr_core` scope, whose namespace a table in that scope begins with *(citation: `markdown/application-development/r_ExampleNamespaceIdentifiers.md`)*. Each extends the baseline profile.
- **Deployment:** ships in HRSD update set; no new scoped app cadence.
- **Support cost:** medium — two new tables to administer; ACLs simpler than 12-field ACL design but still three patterns to maintain.
- **Platform-upgrade risk:** medium — the tables extend a baseline table. Upgrade risk if ServiceNow ships its own sensitive-data-extension pattern in a future release (currently no announced roadmap).
- **Compliance:** opens explicit conversation with engagement's HR-data-protection officer / DPO. Passport storage is in scope for GDPR / country-specific laws — encryption-at-rest may be required (separate Security & GRC consult).
4. Alternatives if rejected:
- **Alternative A: Pure dictionary extension on `sn_hr_core_profile` with per-field ACLs** (option (a) above). Accept the ACL-brittleness risk. Documented as a known-risk pattern. Acceptable if engagement has mature ACL governance and the field count stays small.
- **Alternative B: Defer to HRIS integration** (option (d) above). Read passport/clearance/emergency from Workday/SAP/etc. via integration. Cleanest separation but breaks "store in ServiceNow" requirement.
- **Alternative C: Hybrid** — keep emergency contacts in baseline `sn_hr_core_contact` (broad access tier, simple ACL), but defer passport and clearance to HRIS or a sealed scoped-app integration with column-level encryption (advanced security pattern, requires GRC consult).
Decision required from Chief Architect before any specialist is dispatched.
Recommendation if approved: dispatch Technical Designer + Security & GRC + Integration Specialist in parallel for the two-child-table design + ACL strategy + HRIS upstream check.
Recommendation if rejected: adopt Alternative C (hybrid). Surface to user that pure dictionary extension is acceptable only if engagement accepts the ACL-brittleness risk.
```
(citation: markdown/employee-service-management/index.md — HR Profile; markdown/platform-security/ — ACL design patterns)
## Part 4 — Routing Recommendation
**HALT — §1.1 custom-object proposal in Part 3 requires Chief Architect decision.**
No specialist is dispatched until proposal is approved, rejected, or replaced.
If approved: dispatch Technical Designer + Security & GRC Specialist + Integration Specialist (parallel). Discovery may need a follow-up consult on country-specific HR data law applicability.
If rejected: adopt Alternative A, B, or C from Part 3.
## Part 5 — Anti-Patterns to Block
(Surfaced now in case the proposal is approved.)
- **Do not store all 12 fields on `sn_hr_core_profile` directly without explicit ACL governance.** Field-level ACL complexity is the failure mode.
- **Do not put passport numbers in `work_notes` for "audit" purposes.** PII in journal fields bypasses scoped HR security; severe §1.1 + governance violation.
- **Do not disable the Scoped HR Security plugin** to "simplify" ACL design. The plugin is the baseline data-isolation mechanism; disabling it removes engagement-wide HR data protection.
- **Do not duplicate emergency contacts outside baseline `sn_hr_core_contact`.** Single source of truth: the HR profile's Emergency Contacts list.
- **Do not create the two child tables in a new scoped app** when `sn_hr_core` scope is appropriate. New scoped app is over-escalation per §1.1.
- **Do not store passport image attachments in the child table without explicit GRC review.** Attachment ACLs are separate from field ACLs; engagement must explicitly govern.
- **Do not skip Security & GRC consult.** This request is fundamentally a security architecture question; HRSD Specialist cannot ratify the ACL strategy alone.
- **Do not assume country-specific HR data law is the same across all engagement geographies.** Passport and work-permit storage may be legal in some countries and restricted in others; verify per-geography.
## Open Questions
OQ-EV-1. **Country-specific HR data law applicability** — Passport, work-permit, security-clearance storage may be subject to different regulations per country (GDPR vs APPI vs LGPD vs local employment laws). Discovery follow-up required on engagement's geographic footprint and per-country compliance posture.
OQ-EV-2. **Encryption-at-rest requirement** — Does engagement's DPO require column-level encryption for passport/clearance fields? Affects design pattern (custom-table with encryption vs sealed scoped-app integration).
OQ-EV-3. **HRIS authoritative source** — Is the engagement's HRIS (Workday/SAP/BambooHR) the authoritative source for any of these fields? If yes, ServiceNow becomes a read-only consumer, simplifying the storage question.
OQ-EV-4. **Dependants — PII or special-category?** Family member data may be special-category in some jurisdictions. Clarify whether storage in ServiceNow is acceptable at all.
OQ-EV-5. **Emergency contact — do the baseline records carry all four attributes?** Baseline emergency contacts (`sn_hr_core_contact`) are structured: a documented template script reads their `relation_to_employee` and `mobile_phone` *(citation: `markdown/employee-service-management/hr-service-delivery/document-template-scripts.md`)*, and the HR Contact form takes telephone numbers, in the plural *(citation: `markdown/employee-service-management/hr-service-delivery/t_Contacts.md`)*; confirm a full address and the field for the alternative phone, which are not documented in the bundled corpus — verify on the instance.
OQ-EV-6. **Mobility COE membership model** — How is "Mobility COE" membership represented in `sys_user_group` in the engagement? ACL conditions need to reference the membership pattern correctly.
---
*End of HRSD Specialist Gateway Response.*
```
---
## Reading these examples
- **Example 1 (Verdict A)** — pattern for HR LE configuration via the baseline activity-set library. PROCEED — baseline configuration only. No Technical Designer dispatch.
- **Example 2 (Verdict B)** — pattern for single-field extension on `sn_hr_le_case`: one field on a baseline table, the one schema addition Verdict B allows, with no §1.1 halt. PROCEED — Technical Designer dispatch with envelope as constraints.
- **Example 3 (Verdict C)** — pattern for §1.1 halt on sensitive-data architecture. Four baseline alternatives evaluated honestly, three sensitivity tiers requiring different ACL patterns, country-specific compliance flagged. HALT — Chief Architect decision required.
The §6.2 post-build review fires after Technical Designer returns a spec for Verdict B and Verdict C (approved). The Domain Expert re-validates against the envelope before Developer is dispatched.
---
*End of HRSD Specialist EXAMPLES.md v2.0.*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |