FEATURE SPEC

Questions or comments?

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

Event-Triggered Reports

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 #618, titled "[Reporting] Event-Triggered Reports":

Summary

Feature set

No Acceptance Criteria, Expected Business Value, or Additional Context sections were present on this issue — stating that fact rather than inventing content.

Matching PRD Content

Reproduced verbatim from ../reference/Reporting_PRD_v3_2026-07-17.docx, §3 (Three-Mode Reporting Engine) and §4 (Flows 5–6).

Event-Triggered Reports — Fire automatically when a defined threshold or HR event is detected — headcount crossing a compliance threshold, a filing deadline entering the warning window. Nova detects the trigger, assembles the report, and delivers it proactively with a notification and CTA. The user receives the finding, not a blank screen to navigate to.

Use case example (HR Operations Specialist): No input required — event-triggered. Nova detects headcount in a covered establishment crossing 50 in the JOB_ASSIGNMENT table and delivers a notification: 'VETS-4212 obligation likely triggered — headcount reached 51 on [date]. Review required.' CTA opens a pre-populated Canvas view with affected legal entity, filing deadline, and relevant data fields. Practitioner reviews and confirms or dismisses.

Flow 5 — Event-Triggered Delivery: A compliance threshold is crossed in the data layer. Nova detects the trigger, assembles the report, and delivers a notification to the relevant persona with a CTA. The practitioner clicks through to a pre-populated Canvas view showing the finding, affected entity, filing deadline, and relevant data fields. Practitioner reviews and confirms or dismisses — no action is taken autonomously.

Flow 6 — Scheduled Report Delivery: Fourteen days before a compliance filing deadline, Nova generates a pre-populated compliance readiness report per the Scheduled Reports cadence. The HR Ops Specialist receives a notification, opens the report in Canvas, reviews the data, identifies any gaps, and marks the report as In Progress. Filing is completed in the Compliance & Filings workspace and submitted via the external agency portal.

Flow 6 (Scheduled Report Delivery) is included here because it's the closest PRD content to the "Routine (Scheduled) Reports" mode — see the parent concept.md's Open Question about whether Scheduled Reports needs its own Feature/sub-issue rather than being folded into this one.

Sources

• GitHub issue #618
• ../reference/Reporting_PRD_v3_2026-07-17.docx, §3 and §4