KrinosAI — User Story
Template ID: TPL-02-03 | Stage: 02-Requirements | Version: 0.3
Record: KAI-VORAL-UST-001 — retrospective draft for Visionary Oral. Not approved.
Purpose: Express one small unit of user value that a team can build and verify in a sprint, linked to its requirements.
Required inputs: PRD capabilities; use cases; SRS requirement IDs.
Document control
| Field |
Required entry |
| Document ID |
KAI-VORAL-UST-001 |
| Template used |
TPL-02-03 User Story v0.3 |
| Product / project / software version or commit SHA |
VORAL (Visionary Oral) / PRJ-001 / a6b4429e3165 (branch app_dev of AI-Dental-Project/Visionary_Oral) |
| Record status and version |
Draft v0.1 |
| Author / technical reviewer / quality reviewer |
Claude Code (drafted with Claude Code for KrinosAI) / Tech Lead (name to be assigned) / Security & Privacy Officer (name to be assigned) |
| Created / updated / approved dates |
2026-10-27 / 2026-10-27 / Pending |
| Applicable SOP and revision |
SOP-LC-02 v0.3 |
| Related issue, commit, requirement and evidence links |
KAI-VORAL-BRF-001, KAI-VORAL-IRS-001, KAI-VORAL-CHR-001, KAI-VORAL-DEC-001; KAI-VORAL-SRS-001; KAI-VORAL-UCS-001 |
| Approver and decision record |
Pending |
Applicability and evidence baseline
Product / system boundary: Web app and API (dentalapp/), doctor/admin mobile app (mobile/), PDF Lambda (dentalapp/pdf-lambda/) at a6b4429e3165, and the external services they call (see KAI-VORAL-IRS-001).
Related approved requirements, risks and change records: None approved. Related drafts are listed in document control.
Retrospective record? Yes — follows the Retrospective Documentation Protocol (KrinosAI lifecycle pack, 05-References/). Items are labelled Observed (code or Git at a6b4429), Measured (dated run), Stated (named person, dated) or Not recorded. Story US-01 restates the main implemented flow; no backlog tool or historical stories were available.
Acceptable evidence: an implementation reference (file:line at a commit SHA), a dated test record, a signed decision, a vendor agreement, or another independently verifiable artifact. Never invent approvals, clinical results, measurements or performance data.
1. Story statement
| Story ID |
Statement |
Persona |
| US-01 |
As a doctor, I want to take a 3-photo scan of my patient and see a report with findings, so that I can advise the patient to see a dentist. |
PER-01 |
2. Linked requirements and design
| Story ID |
CAP |
REQ |
Design |
| US-01 |
CAP-04, CAP-06, CAP-07 |
REQ-012, REQ-013, REQ-017, REQ-020, REQ-022 |
Stage 03 records — OPEN-032 |
3. Preconditions, trigger and exception paths
| Item |
Entry |
| Preconditions |
Active doctor account; patient exists |
| Trigger |
New scan on the patient |
| Exceptions |
Retake, offline, detector timeout, suspension (KAI-VORAL-UCS-001 §4) |
4. Acceptance criteria and negative cases
| AC ID |
Given / When / Then |
| AC-01 (ACR) |
Given an active doctor and a patient, when three accepted photos are captured, then a report with three photos and findings is shown |
| AC-02 (ACR) |
Given a blurred photo, when it is captured, then a retake is requested |
| AC-05 (ACR) |
Given a suspended account, when the app re-checks status, then the account-suspended screen is shown |
5. Estimate, priority and definition of done
| Story ID |
Estimate |
Priority |
Definition of done |
| US-01 |
Not recorded (already built) |
Must |
All ACs pass on a reference Android phone; report identical on reopen; no unauthenticated data access (REQ-034) |
Open issues and decisions
| ID |
Specific gap or decision |
Responsible owner |
Due date |
Blocks gate? |
Evidence required |
Status |
| OPEN-001 |
Tracker project ID, named requester and sponsor, and named reviewers are not recorded |
Product Owner |
2026-11-10 (proposed) |
Yes |
Tracker entry; names with roles |
Open |
| OPEN-032 |
Design (DES) and test (TC) links for requirements are added by stages 03 and 07; requirements without them stay open |
Tech Lead |
2026-12-15 (proposed) |
No |
RTM with DES and TC links |
Open |
Review and approval
| Review role |
Named individual |
Decision |
Date |
Signed / controlled record |
| Author |
Claude Code (drafted with Claude Code) |
Draft |
2026-10-27 |
This file at the commit that adds it |
| Technical reviewer |
Tech Lead (name to be assigned) |
Pending |
Pending |
Pending |
| Quality / regulatory reviewer (if applicable) |
Qualified regulatory reviewer (name to be assigned) |
Pending |
Pending |
Pending |
| Authorized approver |
Product Owner (name to be assigned) |
Pending |
Pending |
Pending |