Why I built it
Raw genetics exports are difficult to interpret, but health-risk language creates serious correctness and privacy obligations.
What exists
The private Django app contains ingestion, variant matching, prevalence views, reports, and retrieval-assisted explanations. Its health-risk logic and data lifecycle are not suitable for public or clinical use.
How it works
Uploaded genotype data feeds parsing and heuristic matching, reports, cached results, and external retrieval services.
- Private genotype-file ingestion
- Variant and prevalence views
- Report generation
My role
Built the Django application, ingestion and reporting flows, visual explanations, and retrieval-assisted learning surfaces.
What I checked
- risk-reviewPrivacy, caching, heuristic, and testing gaps documented
What stays bounded
- Synthetic data only in public material
- No medical claim or clinical validity
- No DNA files, screenshots, or source link are public
What is missing
- Clinical correctness, privacy, deletion, security, and health-pipeline tests require reconstruction.
Next
None scheduled; preserve safely as earlier work.
Later ideas, not current features
- Remain private unless specialist review and a new governance model are funded