Human Data OS · Training demo
Turn reviewed work into a signed training corpus.
Most teams cannot prove where their training data came from. Walk one real loop: accepted reviewer decisions become a corpus you can defend in an audit and weights you keep. Read-only here. Run it on your own work in a pilot.
When the EU AI Act provenance rules land in August 2026, you will be asked who created each datapoint, who reviewed it, and under what rights. This is the answer, attached to the data itself.
Corpus pipeline
clinical-note-v18
Illustrative seed data. In a pilot these steps read from your metrics.
Failure feedback loop
Manifest drilldown
Dataset governance
Every slice carries source, exclusion, and reviewer coverage state.
Rights attached to the data
Export holds until consent, retention, and exclusions pass. Each datapoint carries who created it, who reviewed it, and under what rights.
Weights you keep
Weights and the evidence packet leave together. The tuned model is yours, and it survives examination.
Run this loop on your own work.
What you walked through here is read-only. In a pilot, the corpus, the exclusions, and the export proof read from your live data — and the weights are yours to keep.