Visionary Oral — Lifecycle Documentation¶
Internal and confidential
KrinosAI internal documentation. Keep this repository private and do not publish the site. The records name files, fields and environment variables only — never their values or any patient data.
Lifecycle records and SOPs for Visionary Oral (product code VORAL), written with the KrinosAI
krinos-sdlc documentation skills (repository AI-Dental-Project/Claude_document_skills).
What this covers¶
| Product | Visionary Oral — guided dental photo scans with AI findings and a printable report: web app and API (dentalapp/), doctor/admin mobile app (mobile/), PDF Lambda |
| Source repository | AI-Dental-Project/Visionary_Oral, branch app_dev |
| Pinned commit | a6b4429e3165 (2026-10-25) — every statement cites code at this commit |
| Mode | Retrospective — documents what the code does today. History that was never written down is marked Not recorded, not reconstructed. |
| Status | Draft. Nothing here is approved. Each record's approval table stays Pending until a named reviewer signs it. |
Progress¶
All ten stages are drafted (75 records), each following its stage Execution SOP.
| Stage | Records | Status |
|---|---|---|
| 01 Start Project | All 7 records of SOP-LC-01 |
Drafted 2026-10-27 — awaiting review |
| 02 Requirements | 8 records: PRD, use case, user story, SRS (36 requirements), acceptance criteria, DPIA, RTM, change request | Drafted 2026-10-27 — awaiting review |
| 03 Design | 7 records: HLD, data flow, LLD, database schema (18 collections), API contract (97 operations), threat model, ADRs | Drafted 2026-10-27 — awaiting review |
| 04 Planning | 8 records: Work breakdown, cost estimate, resource plan, RACI, risk register, quality plan, project plan, sprint plan | Drafted 2026-10-27 — awaiting review |
| 05 Development-Setup | 7 records: Repository, coding standards, access and secrets, environments, infrastructure change, CI/CD, SBOM | Drafted 2026-10-27 — awaiting review |
| 06 Build-and-Document | 8 records: Feature task, pull request, code review, API inventory, API documentation, README, change log, documentation impact | Drafted 2026-10-27 — awaiting review |
| 07 Test-and-Validate | 9 records: Test plan, test cases (33; 201 automated tests pass), API contract test, bugs, dataset datasheet, model card, validation plan, UAT, verification report | Drafted 2026-10-28 — awaiting review |
| 08 Release-and-Deploy | 7 records: Release readiness, rollback plan, deployment plan, release notes, release approval, deployment record, post-deployment verification | Drafted 2026-10-28 — awaiting review |
| 09 Operate-and-Maintain | 9 records: Operational handover, monitoring, runbook, incident, root cause analysis, complaint, AI drift, change control, backup-restore test | Drafted 2026-10-28 — awaiting review |
| 10 Close-and-Retire | 5 records: Closure, service retirement, API retirement, data archival and disposal, infrastructure decommission (components inside the live product; the product is not retired) | Drafted 2026-10-28 — awaiting review |
Read first¶
- 01 Start Project — completeness report: what is done, open items by owner, and what blocks the stage gate.
- Urgent security items: OPEN-007 (credential files committed to Git), OPEN-008 (database backups with personal data committed to Git), OPEN-026 (20 API routes with no authentication, incl. patient and doctor emails), OPEN-033 (public admin sign-up route) and OPEN-037 (critical dependency vulnerabilities) — see the Threat Model.
How to read a record¶
- Each record starts with a document control table (ID, template, pinned commit, status).
- Every row carries a label: Observed (seen in code at the pinned commit, cited as
file:line), Measured, Stated (by a named person, dated) or Not recorded. - Every gap is an
OPEN-item with a named owner, due date and the evidence needed to close it.OPEN-IDs are project-wide: one gap keeps one ID in every record. - Values marked Proposed (Claude Code, for confirmation) are drafts for the named owner to confirm. People are named by role ("name to be assigned") until OPEN-001 is closed; approvals stay Pending.
- Diagrams (Mermaid) are drawn from the tables of the record they sit in.
- Records end with Open issues and Review and approval.