FEATURE SPEC

Questions or comments?

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

Platform Data Pre-population

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 #471, titled "[Compliance& Filling] Platform Data Pre-population":

Summary

Feature no story

Acceptance Criteria

NA

Expected Business Value

Prepoulation to automate tasks

Additional Context

No response

Matching PRD Content

Reproduced verbatim from ../reference/Novaworks_PRD_Compliance_Filings_v2.docx, §4 (Feature Specifications) and §3 (Data Coverage Constraint).

Data gathering — platform fields — For each filing, the system identifies required form fields and gathers values from Novaworks platform data (PERSON, WORKER, JOB_ASSIGNMENT, LEGAL_ENTITY, COREHR_AUDIT tables) where available. Each gathered field displays its source table and as-of date. Acceptance criteria: Pre-populated fields display source table name and as-of date; data reflects the correct reporting period; jurisdiction routing logic applied automatically.

Data gathering — manual fields — Fields that cannot be gathered from platform data display a 'Manual entry required' indicator with the field definition and a note indicating which future module will supply this data when available. Acceptance criteria: Manual entry required indicator displays in amber; field definition shown; phase reference note included; count of manual fields surfaced in filing list row as a readiness indicator.

Platform boundary disclosure — The detail sheet displays a persistent note: 'Novaworks gathers and presents the data required for this filing. The form must be completed and submitted in the external agency portal. Marking as Filed here reflects status tracking only.' Acceptance criteria: Note is visible before and after a filing is marked Filed; note cannot be dismissed or hidden; language is fixed.

Data Coverage Constraint — Of the full catalog of compliance reports across US, Canada, and India, the platform data currently available in Novaworks is sufficient to gather required fields for a limited subset of filings. Many reports require payroll, benefits, talent acquisition, or leave data that Novaworks does not yet carry. This is expected and documented — it does not prevent v1 from shipping, because the platform surfaces all obligations with a clear field-by-field breakdown of what can be gathered from platform data vs. what requires manual input. The requirement gate for catalog expansion: before any new filing type is published as fully supported in the catalog, data availability for all required fields must be verified against the current Novaworks data model.

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

Sources

• GitHub issue #471
• ../reference/Novaworks_PRD_Compliance_Filings_v2.docx, §3 and §4