Cohort validation summary
A machine-readable export of the repository's passing served-core verification output, including cohort sizes, metrics, scope, source hash, and limits.
Evidence ledger · updated 20 July 2026
Publish the proof we have. Name the proof we do not.
The cohort-level verification export is available below. A full accession-linked public-sample input/output bundle is not. The guided demo is therefore labeled as an interface walkthrough, never as validation evidence.
Public-sample run
No cleared bundle currently joins a source accession and license, full transformed input, current served-core identity, output, and reproduction steps. An anonymized internal example is not a substitute for that chain.
Guided demo
The demo uses fictional, canned profiles and results to teach the interface and abstention behavior. It does not call the model, read an uploaded file, or support a performance claim.
Publication gate
What the first public-sample bundle must contain
The status will move to available only when the complete evidence chain can ship together.
- Source and permission. A public accession, source cohort, tissue label, and redistribution or linking basis that can be checked.
- Exact input provenance. The transformation from source data to a complete accepted profile, including identifiers, normalization, and checksums.
- Current model identity. A served version identifier and reproducibility record sufficient to show which core produced the result, without publishing model weights.
- Unedited outputs. Machine-readable output and human-readable report with abstention, uncertainty, limitations, and timestamps intact.
- Reproduction instructions. A documented command or approved API flow, expected response, and checksum so the linkage can be rechecked.
Not an independent audit. The downloadable summary is authored by Provotics from repository verification output. It should be read with the model card, distribution limits, and known failure modes on the Validation page.
Evaluate Provenance-2 in context
Review product maturity, validation, and input compatibility before starting an access application.