FEATURE SPEC¶

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Worker Activation Integration (Novaworks → HRSD Enterprise)¶

Parent Feature Set: ../concept.md.

Note

Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.

Important

To follow the AI-DLC process, fill this spec with PM assistance first.

GitHub Issue Description (verbatim)¶

Issue #393, titled "[Worker Activation] Worker Activation Integration (Novaworks → HRSD Enterprise)":

Summary¶

--

Acceptance Criteria¶

--

Expected Business Value¶

--

Additional Context¶

No response

All fields are placeholder — the GitHub issue itself carries no content beyond its title. Note the issue title is prefixed [Worker Activation], not [Feature] like its siblings — stated as an observed inconsistency, not corrected here.

Matching PRD Content¶

Reproduced verbatim from ../reference/sn-integration-v1.md, F-05.

Priority: High — Enterprise Side Car Direction: Novaworks → HRSD Deployment Target: Enterprise

Why we're building it (company): Worker Activation is one of the highest-value HR events in an enterprise — it triggers provisioning, system access, benefits enrollment, and onboarding workflows. A proper messaging and integration of Novaworks worker activation into broader HRSD Enterprise Life Cycle Events and Journeys is required when we get to enterprise customers.

Why it matters (customer): New hire onboarding that previously required manual HRSD entries or custom integrations gets handled by Novaworks agents — with policy enforcement applied before any record is written.

What it does: - Novaworks agent submits Worker Activation event to HRSD Enterprise via API on completion of onboarding workflow - Activation payload maps to HRSD worker record schema - Pre-submission policy check: Novaworks Policy Engine validates activation data before write - Activation status (success/failure) returned to Novaworks and surfaced to HR admin - Failure path: agent alerts HR agent or escalates via ticketing module (per Ticketing Integration PRD) - It should be possible for Novaworks worker activation to be part of the overall ServiceNow journey.

NOTE: HRSD Enterprise Worker Activation API schema and required entitlements must be confirmed. The policy enforcement step pre-write is a differentiator and should be preserved — not simplified away in v1.

Sources¶

GitHub issue #393
../reference/sn-integration-v1.md, F-05