Evidence register and development readiness

A route, test, runnable API, end-to-end release and externally validated intervention are different levels of evidence.

The matrix below references public engineering and methodological sources. It does not certify all features as safely activated for every account.

The web repository contains personal check-in, history, exercise and self-support components and related roadmap tasks.

Status: code artifacts available; a full live identity/backend/browser E2E is not independently certified by this dossier.

There are company routes, roles, team analytics and manager decision-support code, but secure multi-tenant access and data migration remain launch gates.

Status: partially implemented, guarded activation, no verified enterprise customers or field impact.

Research Workspace covers projects, cohorts, inspection, datasets, export requests and audit; formal methodology work is documented.

Status: software/research baseline, not external validation or completed ethics-reviewed trial.

The public QDIP research narrative describes hybrid rules/models, policy governance, explanations, risk signals and evaluation.

Status: conceptual and engineering foundations; a statistically demonstrated advantage within Dzvin is pending.

An upgrade to 'validated' requires date, artifact/commit, environment, explicit test or study protocol, and accountable sign-off.

A marketing claim or mocked test cannot substitute for the actual evidence level.