Roadmap from prototype to launch
Milestones, acceptance gates and observable deliverables
Edition: October 2026
Phase 1 — secure integration
Qualify frontend, NestJS, QDIP boundaries, identity, tenant isolation and rollback.
Exit: reproducible builds, authorized real API flows, security negatives and QA integration evidence.
Phase 2 — research design
Define hypotheses, prediction baselines, abstention criteria, harm safeguards, metrics, consent and data protocol.
Exit: registered evaluation protocol, reproducible synthetic baseline comparisons, risk and ethical review.
Phase 3 — human feasibility
Recruit appropriately consented participants/partners and evaluate usability, acceptability and data quality in a bounded study.
Exit: feasible workflow and transparent findings; any required ethics approval obtained before real participant research.
Phase 4 — DI evaluation
Compare policy approaches using suitable data and preregistered metrics for calibration, harms, explanation and decision usefulness.
Exit: auditable report including confidence intervals, limitations and negative findings.
Phase 5 — controlled launch
Prepare production monitoring, support, data policy, deployment gates and a sustainable operating model.
Exit: go/no-go review, production E2E and credible operating plan. Dates depend on budget and partnership commitments.
How to interpret this roadmap
Phases are milestone order, not committed calendar dates. Starting/ending TRL, headcount, time estimates and costs should be call-specific and evidence-backed.
Only mark a phase done when its explicit acceptance evidence is available.
Evidence and source documents
These sources establish scientific context and engineering work, not real-world effectiveness of Dzvin.co.
Discuss funding for the next verifiable development stage.
Discuss funding