Novaworks × ServiceNow HRSD + Employee Center Integration¶
Questions or comments?
Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.
Novaworks AI | scope/table prefix not stated in source material — see Open Questions
Note
Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.
Warning
The source PRD (reference/sn-integration-v1.md) is itself flagged, in its own header, as: "AI-DRAFT — v0.1 ... generated by Novaworks AI (Claude) as a first-pass outline PRD. All architectural assumptions are unverified. Sections marked NOTE require human review before this document advances to a reviewed draft." This concept inherits that same unreviewed status — it is a reverse-engineering of an already-unreviewed draft, not a reviewed source.
GitHub Issue Description (verbatim)¶
Issue #387, titled "[Feature Set] Servicenow Integrations":
Summary¶
Novaworks × ServiceNow HRSD + Employee Center Integration
Major Change History¶
| Version | Date | Author / Notes |
|---|---|---|
| 1 | 2026-08-11 | Seeded from GitHub issue #387 and sn-integration-v1.md — reverse-engineered, not yet reviewed by a PM. |
Business case¶
Reproduced verbatim from the source PRD's "Strategic Context" section.
This PRD serves two active company priorities simultaneously:
Priority 1 — Enterprise Side Car — Fast-to-adopt enterprise motion that keeps incumbent HCMs in place while inserting Novaworks as the AI orchestration layer. ServiceNow is both a co-sell partner and a native deployment environment. Data sync and Worker Activation features are the minimum viable integration surface for this motion.
Priority 2 — Mid-Market HCM (Ateko + Design Partners) — Proving the Novaworks constellation with real customers. Approval Hub and Slate surface exploration unlock workflows that design partners can experience natively inside ServiceNow, reducing change management friction.
The PRD does not separate this into the standard "what's broken / who has the problem / measurable cost / value to customers / value to Novaworks / Novaworks lens" structure — reproduced as the PRD itself frames it (by strategic priority) rather than force-fit into that structure.
Goal¶
Unable to find a single stated goal sentence in the source material —
the closest equivalent is the Strategic Context quoted above and the
per-Feature "Why we're building it" statements reproduced in each
Feature's own spec.md.
Scope¶
Reproduced verbatim from the source PRD's header.
Scope: Integration surface between Novaworks and ServiceNow HRSD and Employee Center (EC). CKM ticketing integration is explicitly out of scope — covered in a separate PRD.
Out of Scope (this PRD), verbatim:
- CKM ticketing integration → covered in Ticketing Integration PRD
- Outbound sync from HRSD to Novaworks in F-02 bidirectional mode (enterprise) deferred to confirmed deployment scenario
- Approval Hub UI customization
- Slate production integration (F-03 is PoC only)
Sources¶
- GitHub issue #387 and its 6 linked sub-issues (#388–#393).
reference/sn-integration-v1.md— "Outline PRD: Novaworks × ServiceNow HRSD + Employee Center Integration," v0.1, dated 2026-07-04, status "Draft — For Prioritization Only." Itself an AI-generated first-pass outline, not a reviewed PRD.
Related PRDs¶
The source PRD names two adjacent PRDs, verbatim: "CKM ticketing integration → covered in Ticketing Integration PRD" (matches the existing specs-superagent ticketing-integrations Feature Set) and references a "Ticketing Integration PRD" for the Worker Activation failure path (F-05). Neither is this repo's concern — noted for traceability only.
Who this is for¶
The PRD does not include a persona/friction/value table — unable to
find that content in the PRD. It does name roles implicitly per Feature
(HR admin, manager, employee, Novaworks agent) — see each Feature's own
spec.md for the "why it matters (customer)" quotes tied to that Feature.
What we are building¶
One Feature folder per linked GitHub sub-issue, matching the source PRD's F-01 through F-05 one-to-one (F-04 splits into two GitHub sub-issues, F-04a and F-04b).
| # | Feature | Folder |
|---|---|---|
| 1 | Employee Center Profile Write-Back (F-01, #388) | ec-profile-write-back/spec.md |
| 2 | Core HR Schema Sync (F-02, #389) | core-hr-schema-sync/spec.md |
| 3 | Employee Works Slate Framework — PoC (F-03, #390) | employee-works-slate-framework-poc/spec.md |
| 4 | Approval Hub Integration (F-04a, #391) | approval-hub-integration/spec.md |
| 5 | Automated Policy-Based Approvals (F-04b, #392) | automated-policy-based-approvals/spec.md |
| 6 | Worker Activation Integration (F-05, #393) | worker-activation-integration/spec.md |
Data Model (Conceptual)¶
No conceptual entity/relationship diagram is given anywhere in the source
material — unable to find that content in the PRD. The PRD does name
specific external ServiceNow tables each Feature reads from or writes to
(sn_employee_profile, sn_hr_core_profile, sys_user) — reproduced
per-Feature in each spec.md rather than diagrammed here, since no
relationship between them and any new Novaworks-side entity is described.
Table-Stakes & Differentiation¶
Unable to find this content in the PRD — no competitor names or
table-stakes framing appear anywhere in the source material. F-04b's
"Why we're building it" does frame Policy-as-Code as a differentiator
against ServiceNow's own native auto-approval feature — quoted in that
Feature's own spec.md rather than restated here.
UX & Interaction Design¶
Not found in the source material — no Figma/design link or UX flow
description appears anywhere in sn-integration-v1.md.
Open Questions¶
The source PRD has its own 8-item Open Questions list — reproduced verbatim below rather than re-derived, since these are the PRD author's own stated unknowns, not ones found during this reverse-engineering pass.
| # | Question | Blocks |
|---|---|---|
| 1 | Which ServiceNow entitlements (license tier, API scopes) are required for F-01, F-04a, F-05? | Feature 1, 4, 6 delivery |
| 2 | Is F-02 bidirectional mode required for Ateko go-live, or is inbound-only sufficient for the design partner phase? | Feature 2 scope |
| 3 | What is the Novaworks team's assessment of the new ServiceNow automated approval capability (F-04b) — is it compatible with an external policy engine? | Feature 5 scope |
| 4 | Who owns the Slate PoC (F-03) — Vivek's AI Differentiation team or a dedicated spike? | Feature 3 ownership |
| 5 | Does F-05 Worker Activation need to be production-ready for Ateko, or is Ateko's go-live scope limited to Core HR sync? | Feature 6 scope |
| 6 | Is F-01 (Novaworks Worker → sn_employee_profile) warranted at all? If F-02 is co-deployed, Group A fields project into EC automatically and F-01's only remaining write set is Group B (pronouns, bio, preferred name) — which are typically employee self-service. |
Feature 1 scope, possibly redundant with Feature 2 |
| 7 | Which sn_hr_core_profile fields does F-02 own vs. read from sys_user (directory/AD-mastered)? |
Feature 2 schema delta |
| 8 | What ServiceNow entitlements (license tier, API/ACL scope) are required for F-02 sn_hr_core_profile access (sensitive), and separately for F-01 sn_employee_profile write (lower-privilege fallback)? |
Feature 1 and 2 delivery |
| 9 | This entire concept was seeded from GitHub issue bodies (mostly empty placeholders) and one unreviewed AI-draft PRD, with no PM review yet — every section above needs a PM pass before this is treated as ready for Construction. | Everything downstream of this file. |
For internal engineering review only. Not for external distribution.
Novaworks AI | Confidential