Skip to content

KrinosAI — Documentation Impact Assessment

Template ID: TPL-06-07 | Stage: 06-Build-and-Document | Version: 0.3
Record: KAI-VORAL-DOC-001 — retrospective draft for Visionary Oral. Not approved.

Purpose: For a change, identify every document that must be updated and confirm it was updated before merge or release.

Required inputs: PR or change request; document inventory.

Document control

Field Required entry
Document ID KAI-VORAL-DOC-001
Template used TPL-06-07 Documentation Impact Assessment 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-06 v0.3
Related issue, commit, requirement and evidence links KAI-VORAL-PR-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. 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. Observed in code and Git at a6b4429. The feature, PR, review and documentation-impact records describe the most recent change set (offline access limit and suspension, commits 0cd7a01, bbeeabc, a6b4429), which was made without a PR or recorded review. 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. Affected requirements and architecture

Record Affected? Update
KAI-VORAL-SRS-001 Yes REQ-007, REQ-009, REQ-026 written
KAI-VORAL-HLD-001, KAI-VORAL-LLD-001 Yes DES-101, DES-109, DES-110

2. Impacted SOPs design and API docs

Document Affected? Update
KAI-VORAL-APC-001, KAI-VORAL-APII-001 Yes New routes listed
Admin SOP (stage 09 runbooks) Yes Suspension and offline-limit procedures

3. User guide and training changes

Document Affected? Update
Doctor guide (offline limit, suspension message) Yes Not written — OPEN-042

4. Regulatory risk and labeling impacts

Item Affected? Reviewer
Intended use / labelling No —
Risk screen Yes (new suspension behaviour) Qualified regulatory reviewer (name to be assigned)
Document Link Reviewer
Lifecycle records suhanijn02/Visionary_Oral_docs Tech Lead (name to be assigned)

6. PR gate decision

Decision By Date
Merged without docs gate (retrospective) Not recorded —

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-042 No project tracker, sprint history, PR descriptions or code-review records exist for past work Tech Lead 2026-12-15 (proposed) No Tracker and PR workflow in use from now on 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 Tech Lead (name to be assigned) Pending Pending Pending