KAI-VORAL-DRC-001 — Deployment Record
Template ID: TPL-08-06 | Stage: 08-Release-and-Deploy | Version: 0.3
Status: Project record created from the controlled template.
Purpose: Record what was actually deployed, when, by whom and with what result — the factual history of production.
Required inputs: Deployment plan; pipeline logs.
Document control
| Field |
Required entry |
| Document ID |
KAI-VORAL-DRC-001 |
| Template used |
TPL-08-06 Deployment Record 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-28 / 2026-10-28 / Pending |
| Applicable SOP and revision |
SOP-LC-08 v0.3 |
| Related issue, commit, requirement and evidence links |
KAI-VORAL-INF-001; KAI-VORAL-ENV-001 |
| Approver and decision record |
Pending |
Applicability and evidence baseline
Product / system boundary: Web app and API (dentalapp/), doctor/admin mobile app (mobile/), on-device models (mobile/assets/models/), 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. No controlled release has been recorded (OPEN-046). These records describe the release mechanism found in the code (mobile/eas.json, mobile/app.json), the builds measured in this documentation work, and the plan for the first controlled release.
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. Deployment identity
| Deployment ID |
Release |
Environment |
Operator |
Pipeline run |
EAS build 27bd4b8c… |
Android preview |
Internal distribution |
Developer via Claude Code |
Expo EAS (krinos_ai), 2026-10-22 |
EAS build 06f730e4… |
Android preview |
Internal distribution |
Developer via Claude Code |
Expo EAS (krinos_ai), 2026-10-23 |
EAS build 57de1cdb… |
Android preview |
Internal distribution |
Developer via Claude Code |
Expo EAS (krinos_ai), 2026-10-25 |
| Web production |
Not recorded |
Production |
Not recorded |
Not recorded — OPEN-022 |
2. Artifacts deployed
| Service |
Digest |
Matches approval? |
| Android APK |
Not recorded (APK not hashed) |
No approval existed |
3. Timeline
| Time (UTC) |
Event |
| 2026-10-22 |
Preview build finished (Measured) |
| 2026-10-23 |
Preview build finished (Measured) |
| 2026-10-25 |
Preview build finished (Measured) |
4. Deviations from plan
| Deviation |
Reason |
Approved by |
| Builds made without release approval |
No release process existed (OPEN-046) |
Not approved |
5. Outcome
| Outcome |
Link |
| Builds finished |
KAI-VORAL-INF-001 (INF-01 (change)); KAI-VORAL-FEA-001 |
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-022 |
Production hosting (Vercel vs Render), deployed version and dated integration checks for Clerk, MongoDB, R2, AWS, OpenRouter, Groq, Cashfree and Resend not recorded |
Tech Lead |
2026-11-30 (proposed) |
No |
Environment record (stage 05) with dated checks |
Open |
| OPEN-046 |
No release process: no Git tags, release approvals, deployment records or post-deployment checks; mobile builds are manual eas build runs and the web deployment is not recorded |
Tech Lead |
2026-11-30 (proposed) |
Yes |
Tagged release with approval, deployment record and verification |
Open |
Review and approval
| Review role |
Named individual |
Decision |
Date |
Signed / controlled record |
| Author |
Claude Code (drafted with Claude Code) |
Draft |
2026-10-28 |
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 |