Nova Policy Advisor

Questions or comments?

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

AI-DRAFT. Seeded from the Nova Policy Advisor PRD v1.5 (Vanessa Gutierrez, PM; Ravindra Kumar, Lead Developer; July 9, 2026). Not yet reviewed by PM/EL against this repo's schema-first gate or Feature-Set conventions — treat scoping and the schema delta below as a starting point to react to, not a committed plan. Source doc kept at reference/Nova_Policy_Advisor_PRD_v1.5.docx for durability.

Business case

HR policy today is maintained the way most shared documents are: redlines in a Word doc here, a tracked-changes copy there, a PDF exported for a meeting. When a policy changes, it's often unclear which copy is actually current — and updating a document isn't the same as updating the system of record. Someone still has to make the corresponding change inside the platform for an agreed change to actually take effect in the workflows and automation that depend on it, and it's often unclear who's responsible for that step or whether it happened at all.

HR Policy Owners and Compliance Analysts feel this most directly: they have no fast way to check whether a new or proposed policy is consistent with existing policy or applicable regulation before publishing it, and no governed, auditable place to keep policy content current and review-ready. The measurable cost: HR staff time lost figuring out which version of a document is current; inconsistent guidance when different people work from different copies of the same policy; and operational/compliance risk when the platform's system of record lags behind what was actually agreed to, with no reliable way to confirm the update ever took effect.

This isn't just an internal-tooling problem — because published policy content also determines how other Nova agents behave at runtime, an out-of-sync or unauditable KB directly threatens every agent governed by that policy, not only the humans reading it.

Goal

Give HR Operations (policy owners, compliance analysts, and other HR decision-makers) a single governed place to author, collaboratively edit, publish, and question policy — with every publish automatically re-syncing the advisor's retrieval index, and every advisor conversation persisted for audit. Concretely, a customer-recognizable outcome: an HR Policy Owner updates a policy once, in one governed editor, and from that moment every HR staffer and every other Nova agent governed by that policy is reading the same, current, versioned content — with a defensible, auditable trail of every question asked against it along the way.

Explicitly out of scope for this Feature Set (per the source PRD): this is not an employee- or people-manager-facing self-service tool — access is scoped to HR Operations only, since published policy content also governs other Nova agents' runtime behavior. Advisor-suggested policy edits ("policy edit suggestions in chat mode") are a roadmap item flagged in the source PRD's April 2026 status deck, not a shipped capability — the advisor currently only answers from what's already published and cannot edit or publish policy itself. Clickable links from an advisor answer to the underlying government regulation text (as opposed to the internal KB article) are explicitly a Codex Curator data-completeness dependency, not something this Feature Set can close on its own — see ../nova-codex-curator/concept.md.