KrinosAI — Resource Plan
Template ID: TPL-04-03 | Stage: 04-Planning | Version: 0.3
Record: KAI-VORAL-RES-001 — retrospective draft for Visionary Oral. Not approved.
Purpose: Show the people and skills needed, their availability, and how gaps are closed.
Required inputs: WBS; estimates; team rosters.
Document control
| Field |
Required entry |
| Document ID |
KAI-VORAL-RES-001 |
| Template used |
TPL-04-03 Resource Plan 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-04 v0.3 |
| Related issue, commit, requirement and evidence links |
KAI-VORAL-STK-001; KAI-VORAL-WBS-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. Planning records are forward-looking: they plan the corrective work found in stages 01–03. No past project plan, estimates or sprints were recorded (OPEN-042); effort, cost and dates are left to their owners (OPEN-020, OPEN-025).
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. Role and skill inventory
| Role |
Skills |
Needed for |
| Backend developer |
Next.js, MongoDB, Clerk, security |
WP-02, WP-03, WP-04, WP-08 |
| Mobile developer |
Expo/React Native, offline, ONNX |
WP-03, WP-11 |
| ML engineer |
YOLO/ONNX, evaluation |
WP-09 |
| Security & privacy officer |
Incident response, DPIA, DPAs |
WP-01, WP-05 |
| Regulatory reviewer |
Medical-device regulation (CDSCO, others) |
WP-06 |
| Clinical advisor (dentist) |
Clinical validation |
WP-09 |
2. Effort estimation method and ranges
| Role |
Effort (pd) |
Method |
| Backend developer |
WP-02, WP-03, WP-04, WP-08 → 23 / 38 / 63 pd |
Three-point estimate |
| Mobile developer |
WP-03, WP-11 (part) → 4 / 7 / 13 pd |
Three-point estimate |
| ML engineer |
WP-09 (part) → 15 / 20 / 30 pd |
Three-point estimate |
| Security & privacy officer |
WP-01, WP-05 → 12 / 18 / 30 pd |
Three-point estimate |
| Regulatory reviewer |
WP-06 → 5 / 10 / 20 pd |
Three-point estimate |
| Clinical advisor (dentist) |
WP-09 (part) → 15 / 25 / 40 pd |
Three-point estimate |
3. Availability and competing obligations
| Person (role) |
Availability |
Competing work |
Confirmed by |
| Contributors in Git (STK-004, STK-005) |
Proposed (Claude Code, for confirmation): named people confirmed by their managers when the plan is approved |
Not recorded |
Proposed (Claude Code, for confirmation): named people confirmed by their managers when the plan is approved |
4. Onboarding training and competency
| Person |
Training |
Status |
| All developers |
Secure coding and patient-data handling training |
Not recorded — OPEN-041 |
5. External contractor and supplier requirements
| Supplier |
Scope |
Contract / data access |
| Regulatory consultancy |
WP-06 |
Contract and NDA needed |
| Clinical study partner |
WP-09 |
Data-sharing agreement needed (OPEN-009) |
| Penetration tester |
After WP-02 |
Contract; test accounts only |
6. Capacity gaps and mitigation
| Gap |
Mitigation |
Owner |
| No named security/privacy, regulatory or clinical roles |
Appoint or contract (OPEN-001) |
Sponsor |
| No support/on-call |
Define rota (OPEN-019) |
Tech Lead |
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-007 |
Credential files committed to Git: dentalapp/google-credentials.json, dentalapp/mongoDb_usernamePassword (contents not opened) |
Security & Privacy Officer |
2026-10-31 (proposed) |
Yes |
Credentials rotated; files removed and purged from history; confirmation |
Open |
| OPEN-009 |
No DPIA |
Security & Privacy Officer |
2026-11-30 (proposed) |
Yes |
DPIA |
Open |
| OPEN-019 |
No named support team, support lead or on-call rota; capacity not confirmed |
Tech Lead |
2026-11-30 (proposed) |
No |
Support model accepted by a named team |
Open |
| OPEN-020 |
No budget ceiling, contingency or cost estimates |
Sponsor |
2026-11-30 (proposed) |
Yes |
Explicit numbers |
Open |
| OPEN-025 |
Milestone dates proposed only; no resources confirmed by their managers |
Sponsor |
2026-11-10 (proposed) |
Yes |
Committed dates and people |
Open |
| OPEN-041 |
No secrets vault, rotation schedule or access recertification; secrets live in host environment variables (and two were committed — OPEN-007) |
Security & Privacy Officer |
2026-11-30 (proposed) |
Yes |
Vault or managed secrets with rotation dates |
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 |
Sponsor (name to be assigned) |
Pending |
Pending |
Pending |