Development progress and limits

Dzvin is an in-development software prototype with a published documentation site and code for personal, organizational and research journeys.

There are no commercial customers or measured field outcomes. A passing website build does not prove every authenticated workflow is live.

The web code includes check-ins, journal, exercises, personal progress, goals and questionnaires. The product roadmap calls for a connected check-in → user-chosen support → feedback → history journey.

Production readiness still requires fully verified auth, privacy, real API and browser end-to-end flows.

Company administration, groups, permissions, analytics and manager decision support have frontend implementations.

Multi-tenant authorization, backend migrations, privileged access checks and real operator E2E are launch gates, not completed customer deployments.

There are project, membership, cohort, inspection, dataset, export-request and audit UI/API artifacts.

External study partners, ethics processes, real datasets and qualified research workflows remain pending.

Research documentation covers adaptive risk, explanation, policy control and scientific evaluation plans. Backend decision-support components exist.

Scientific advantage and integrated clinical/operational effectiveness have not been established in real settings.

A feature must pass the relevant authorization, privacy, end-to-end, operational and auditability checks in the target environment.

A milestone is evidence-based; a visible component or compiled source is not automatically launch-ready.