6  User Stories & Acceptance Criteria

Engineering-facing delivery companion to the Kav AI PRD

Published

June 19, 2026

7 Purpose

This is the execution companion to the PRD. The PRD owns the what and why and keeps the Feature Summary (Appendix A) as the master index of requirements. This document owns the how it behaves: user stories and testable acceptance criteria, organised by milestone.

To keep the PRD from growing, every story here references an FR ID rather than restating the requirement. If a story has no FR, add the FR to the PRD first, then write the story here.

8 Conventions

  • Story format: As a [persona], I want [capability] so that [benefit].
  • Acceptance criteria: Given / When / Then, covering the happy path, at least one error or empty state, and any negative case (“must not…”).
  • Traceability: each story is tagged with its FR ID(s) and the FR’s current status (Delivered / In Progress (Q2) / Q3 Target / Q4 Target), taken from PRD Appendix A.
  • IDs: US-<milestone>-<n> (e.g. US-M3-01).

9 Personas

Persona Who they are
Integrity Engineer (IE) Reviews and validates findings; owns sign-off on Critical findings and Remaining Life.
Design Engineer (DE) Engineering-design counterpart to the IE; co-owns the IE & DE persona sign-off.
Data Explorer Manages organizations and campaigns; explores and triages campaign data.
On-call Integrity Engineer Works the triage dashboard; confirms / dismisses / reclassifies anomalies.
Operations Supervisor Consumes audit and shift-handover records.

10 Milestones

Extend per milestone as FRs move into active development; retire stories to the release notes once shipped and verified.