Project contribution
Contribute
DNA_CHECKS is intended to develop transparently, with room for scientific criticism, technical contributions and useful feature requests.
The source repository remains private during beta, but scientific criticism, bug reports, feature ideas and UX feedback are welcome through the public contact routes.
Contribute
Useful criticism is part of the project
A genetics interpretation tool benefits from being challenged on evidence quality, assumptions, wording and implementation.
Incorrect output, broken report behaviour or reproducible software problems.
Problems with source choice, interpretation, ancestry framing or clinical caution.
New inputs, traits, evidence sources, origins comparisons or report capabilities.
Readability, accessibility, navigation and explanation improvements.
Scientific contributions
Evidence should be inspectable
Scientific contributions are most useful when they identify the exact claim, source and change being proposed.
Examples include proposing a stronger primary source, identifying an outdated interpretation, challenging a population-genetic label, improving a phenotype explanation or showing where a report claim is more confident than the evidence warrants.
Technical contributions
Keep the analysis reproducible
Technical changes should preserve the separation between scientific evidence logic and narrative presentation.
Input adaptersAdd a provider without changing the downstream genome model.+
New consumer-array and sequencing formats should be normalised at the ingestion boundary so downstream clinical, PGx, traits and origins branches remain source-agnostic.
Evidence pipelinesScientific logic should remain testable and deterministic.+
Changes to evidence integration should include provenance, tests and explicit behaviour for missing or ambiguous data rather than relying on narrative inference.
Report presentationImprove readability without changing the underlying result.+
Report UX changes should preserve the locked scientific result while making evidence, limitations and technical detail easier to navigate.
Project status
How to contribute during beta
Public code contributions are not open during the beta, but feedback on the science, implementation and report experience is still useful and welcome.
Use the feature-request page for ideas and improvements, or contact DNA_CHECKS for bug reports, scientific criticism and other project feedback. Suspected vulnerabilities or data exposure should be sent privately to [email protected], not posted publicly. Please do not send raw DNA files by email.