FEATURE SPEC¶
Questions or comments?
Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.
Employee Works Slate Framework (Proof of Concept)¶
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 #390, titled "[Feature] Employee Works Slate Framework (Proof of Concept)":
Summary¶
POC
Acceptance Criteria¶
--
Expected Business Value¶
--
Additional Context¶
No response
Matching PRD Content¶
Reproduced verbatim from ../reference/sn-integration-v1.md, F-03.
Priority: Low — Multi-Surface Agent Strategy Direction: Outbound surface (Novaworks agents surfaced in Slate) Deployment Target: Enterprise
Why we're building it (company): ServiceNow launched Employee Slate (Moveworks-powered) in May 2026 — which provides a new framework for AI native interface also called AIUX. Novaworks needs to understand how to surface our components into Slate so that an enterprise customer who standardized on Moveworks/Slate will not see Novaworks as an overlapping functionality.
Why it matters (customer): Enterprises already invested in ServiceNow Employee Center get Novaworks agent capabilities without leaving their existing employee experience layer.
What it does: - Surface at least one Novaworks agent interaction natively inside the Slate UI - Test Slate's extensibility model against Novaworks' MCP/A2A proxy architecture - Document: what Slate allows, what it blocks, where Novaworks' identity model fits or conflicts - Deliverable is a PoC report and feasibility assessment — not a production feature
NOTE: This is explicitly scoped as discovery. Success is defined as a written assessment of integration feasibility, not a shipped feature. Scope must not expand mid-PoC.
Sources¶
- GitHub issue #390
../reference/sn-integration-v1.md, F-03