KrinosAI — Kickoff Minutes
Template ID: TPL-01-07 | Stage: 01-Start-Project | Version: 0.3
Record: KAI-VORAL-KOM-001 — retrospective draft for Visionary Oral. Kickoff not recorded. Not approved.
Purpose: Record the kickoff meeting: who attended, what was confirmed, decisions, and actions with owners.
Required inputs: Approved charter; stakeholder register; decision register.
Document control
| Field |
Required entry |
| Document ID |
KAI-VORAL-KOM-001 |
| Template used |
TPL-01-07 Kickoff Minutes 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) / Product Owner (name to be assigned) |
| Created / updated / approved dates |
2026-10-27 / 2026-10-27 / Pending |
| Applicable SOP and revision |
SOP-LC-01 v0.3 |
| Related issue, commit, requirement and evidence links |
KAI-VORAL-CHR-001, KAI-VORAL-STK-001, KAI-VORAL-DEC-001, KAI-VORAL-IRS-001 |
| Approver and decision record |
Pending |
Applicability and evidence baseline
Product / system boundary: As in KAI-VORAL-BRF-001: web app and API (dentalapp/), doctor/admin mobile app (mobile/), PDF Lambda (dentalapp/pdf-lambda/) at a6b4429e3165.
Related approved requirements, risks and change records: None approved.
Retrospective record? Yes — follows the Retrospective Documentation Protocol (KrinosAI lifecycle pack, 05-References/). No kickoff meeting, invite, attendance list, recording, slides or notes was available for this project. As the protocol requires, the minutes are not reconstructed: every section states Not recorded, and a new kickoff for the continuation of the product is proposed as an open item (OPEN-024). When that meeting is held, record it as KAI-VORAL-KOM-002 and keep this record as the historical "not recorded" entry.
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.
| Item |
Entry |
| Date and duration |
Not recorded. Development started no later than 2025-11-13 (Observed: first commit d55e801) |
| Facilitator |
Not recorded |
| Attendees |
Not recorded |
| Apologies |
Not recorded |
| Proposed continuation kickoff |
To be held after the charter is signed; attendees: the accountable roles in KAI-VORAL-CHR-001 §1 and §5 — Proposed (Claude Code, for confirmation): 2026-11-17, after charter signature |
2. Prior approvals and baseline reviewed
| Document |
Version |
| No approved documents were reviewed at any recorded kickoff (Not recorded) |
— |
Documents available for the proposed continuation kickoff: KAI-VORAL-BRF-001, KAI-VORAL-STK-001, KAI-VORAL-FEA-001, KAI-VORAL-IRS-001, KAI-VORAL-CHR-001, KAI-VORAL-DEC-001 |
Draft v0.1 each (2026-10-27), none approved |
3. Scope confirmed and unresolved boundaries
No scope was confirmed at a recorded kickoff. Open boundaries known now, each already an open item:
| Item |
Confirmed / open |
Follow-up |
| Intended use and patient population |
Open |
OPEN-004 |
| Target markets and device status |
Open |
OPEN-006 |
| 3 views vs 5 views; storage and AI vendors in the PRD vs code |
Open |
OPEN-005 |
| Which branch is the release line |
Open |
OPEN-023 |
| Production hosting and deployed version |
Open |
OPEN-022 |
4. Decisions with IDs and rationale
| Decision ID |
Summary |
| — |
No decisions were recorded at a kickoff. Project decisions found in ADRs, commits and dated requests are logged as DEC-001 to DEC-015 in KAI-VORAL-DEC-001; none was made at a kickoff meeting. |
5. Milestones owners and due dates
No milestones were confirmed at a recorded kickoff. The proposed milestones are in KAI-VORAL-CHR-001 §7 (M1–M7) and are to be confirmed at the continuation kickoff.
| Milestone |
Owner |
Due |
| M1 — Committed secrets and backups rotated and purged |
Security & Privacy Officer (STK-007) |
2026-10-31 (proposed, per KAI-VORAL-CHR-001 §7) |
| M2 — Named owners; intended use confirmed |
Product Owner (STK-002) |
2026-11-10 (proposed, per KAI-VORAL-CHR-001 §7) |
| M3 to M7 |
As in KAI-VORAL-CHR-001 §7 |
As in KAI-VORAL-CHR-001 §7 |
6. Safety privacy and regulatory escalations
No escalations were recorded at a kickoff. The escalations below were raised by this documentation work, outside any meeting:
| Escalation |
To |
Date |
| Credential files committed to Git (OPEN-007) |
Requesting KrinosAI team member, in the Claude Code session; Security & Privacy Officer to be named (OPEN-001) |
2026-10-27 |
| Database backups with personal data committed to Git (OPEN-008) |
Requesting KrinosAI team member, in the Claude Code session; Security & Privacy Officer to be named (OPEN-001) |
2026-10-27 |
| Medical-device status undetermined (OPEN-006) |
Qualified regulatory reviewer, once appointed — Qualified regulatory reviewer (proposed (claude code, for confirmation): appoint by 2026-11-10) |
2026-10-27 (raised in KAI-VORAL-IRS-001) |
7. Risks dependencies and actions
No actions were recorded at a kickoff. The one action this record creates:
| Action ID |
Action |
Owner |
Due |
| ACT-001 |
Hold the continuation kickoff once the charter is signed; record it as KAI-VORAL-KOM-002 |
Product Owner (STK-002) |
Proposed (Claude Code, for confirmation): 2026-11-17, after charter signature (after charter signature, milestone M3) |
8. Evidence links and review record
| Item |
Link / name |
| Recording |
Not recorded |
| Slides |
Not recorded |
| Reviewer of these minutes |
Not applicable — no meeting took place to attend; this "not recorded" entry is reviewed with the rest of stage 01 — Product Owner (name to be assigned) |
Open issues and decisions
| ID |
Specific gap or decision |
Responsible owner |
Due date |
Blocks gate? |
Evidence required |
Status |
| OPEN-001 |
Reviewers and accountable roles not named |
Product Owner |
2026-11-10 (proposed) |
Yes |
Names with roles |
Open |
| OPEN-004 |
Intended use not confirmed |
Product Owner with Qualified regulatory reviewer |
2026-11-10 (proposed) |
Yes |
Confirmed wording |
Open |
| OPEN-005 |
PRD vs code differences |
Tech Lead |
2026-11-30 (proposed) |
No |
Updated PRD or decision |
Open |
| OPEN-006 |
Device status undetermined |
Qualified regulatory reviewer |
2026-11-30 (proposed) |
Yes |
Written determination |
Open |
| OPEN-007 |
Committed credentials |
Security & Privacy Officer |
2026-10-31 (proposed) |
Yes |
Rotation and purge |
Open |
| OPEN-008 |
Committed patient-data backups |
Security & Privacy Officer |
2026-10-31 (proposed) |
Yes |
Purge and breach assessment |
Open |
| OPEN-022 |
Production hosting and deployed version not recorded |
Tech Lead |
2026-11-30 (proposed) |
No |
Environment record |
Open |
| OPEN-023 |
Release branch not defined |
Tech Lead |
2026-11-30 (proposed) |
No |
Branch policy |
Open |
| OPEN-024 |
No kickoff was ever recorded; a continuation kickoff has not been scheduled |
Product Owner |
After charter signature (proposed) |
Yes |
KAI-VORAL-KOM-002 with attendees, decisions and actions |
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 |
Sponsor (name to be assigned) |
Pending |
Pending |
Pending |