FEATURE SPEC

Questions or comments?

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

Nova Compliance Alerts

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 #477, titled "[Compliance& Filling] Nova Compliance Alerts":

Summary

Feature, no story here

Acceptance Criteria

NA

Expected Business Value

Visibility

Additional Context

No response

Matching PRD Content

Reproduced verbatim from ../reference/Novaworks_PRD_Compliance_Filings_v2.docx, §5 (Nova Integration) and §6 (Flow 4).

Nova Integration (Approval-Gated and Assistive) — Nova operates in two modes within Compliance & Filings. In assistive mode, Nova answers practitioner questions about filing requirements, deadlines, and form field definitions using the filing catalog as a knowledge base. In approval-gated mode, Nova proactively surfaces compliance signals — flagging a VETS-4212 obligation triggered by a headcount threshold crossing, or alerting that a deadline is entering the Due Soon window. Nova never files on behalf of the practitioner and never completes a form autonomously. All submission actions and form completion occur outside the platform.

Flow 4: Nova Threshold Alert — Obligation Triggered - Entry: Nova surfaces a compliance alert: 'VETS-4212 obligation triggered — covered establishment headcount exceeded 50 on [date].' - Action: User clicks alert, navigating to VETS-4212 in the filing list (Status: Due soon). - System: Detail sheet shows gathered fields (EIN, legal entity, headcount by job category — sourced from WORKER and JOB_ASSIGNMENT tables) and the September 30 deadline. Nova adds context: 'Triggered by worker record update on [date]. Confirm legal entity scope before submitting.' - Action: User reviews gathered data, marks as In Progress. - Exit: Status updates; HR Ops completes and submits the form in the VETS portal using the gathered data.

AI Feedback Loop — Explicit: Thumbs up / thumbs down on Nova-generated compliance alerts to signal accuracy of threshold detection. 'Incorrect obligation' flag on any auto-surfaced filing to indicate an employer was incorrectly identified as subject to a given report. Implicit: Click-through rate on Nova compliance alerts — high dismissal rates on a specific obligation type signal threshold logic needs recalibration.

No Acceptance Criteria were provided on the GitHub issue itself (marked "NA") — stating that fact rather than inventing criteria.

Sources

• GitHub issue #477
• ../reference/Novaworks_PRD_Compliance_Filings_v2.docx, §5 and §6