Feature Sets

Each subfolder is one Feature Set — a themed goal, elaborated once at Inception, then fanned out into Features that repeat through Construction and Release.

A single Feature is a legitimate Feature Set on its own — the wrapper earns its place when it needs the schema-first gate, has its own business justification, and stands alone as a customer-announceable thing. If a proposed entry has no schema impact (or a trivial one) and no broader theme, it belongs in ../improvements/ instead, regardless of how it was initially framed — don't let "it's only one Feature" pull it into feature-sets/ on its own.

A Feature Set folder holds only what that set adds or changes relative to root — it is not a full copy of current state. Root (../schema/, ../adrs/, ../product/) is the single source of truth for "what's true now"; a Feature Set is a diff against it.

Index

Feature Set	Status	Notes
nova-policy-advisor	AI-DRAFT	Conversational compliance advisor, collaborative policy editor, KB governance, auditable conversation history. Seeded from the July 9, 2026 Policy Advisor PRD v1.5; not yet PM/eng reviewed.
nova-codex-curator	AI-DRAFT	Multi-jurisdiction regulatory ingestion pipeline, three-tier grounding model, four-state curation lifecycle, ops dashboard (proposed, not yet built), source classification and versioning. Seeded from the July 9, 2026 Codex Curator PRD v1.5; not yet PM/eng reviewed.
agent-accountability-framework	AI-DRAFT	Workforce-style identity, job profile, human supervision, audit, and escalation model for AI agents. Seeded from the June 2026 internal concept paper — earlier-stage than the other two (opportunity framing, not a shipped-feature PRD); expect heavier rework once scoped.

Status here reflects each Feature Set's own doc header, not the status: frontmatter field (which tracks delta-file lifecycle — see below — and currently reads draft for all Feature Sets regardless of how far along they are). Update this table when a Feature Set's status changes.

feature-sets/<feature-set-slug>/
  concept.md              # business case, justification (Inception) — owner, product-manager, issue-url
  schema-changes.md       # proposed delta to ../schema/ — status in frontmatter
  software-design/        # this set's overall design: design.md, adr-*.md, plus supporting files
  <feature-slug>/
    spec.md                # scope, value, acceptance — owner, product-manager, issue-url
    test-plan.md
    implementation-plan.md  # Nova Architect's output from the Feature Spec → implementation handoff

There is no checklist.md — the Feature Closure Checklist is enforced on the GitHub Issue itself (signed-off.dev), not as a repo file. See github-private/docs/ai-dlc/repo-convention.md's "No checklist.md file" note and its linked decision log.

Delta file status

schema-changes.md and files under software-design/ carry frontmatter:

---
feature_set: <slug>
status: proposed | applied | superseded
applied_date: <date or null>
supersedes: [<file>, ...]   # optional, if this delta revises an earlier one
---

These files are a permanent record — never deleted or moved once applied. proposed means not yet true; applied means it has been merged into root and is safe to treat as historical confirmation of current state; superseded means a later delta replaced it.

Starting skeletons live with the skills that generate them, not in this repo: skills-product/.claude/skills/nova-feature-set/templates/ (concept.md, schema-changes.md, software-design/adr-example.md) and skills-product/.claude/skills/nova-feature/templates/ (spec.md, test-plan.md). See github-private/docs/ai-dlc/repo-convention.md for the full convention this layout follows.