HFA's framework for how every dataset is created, documented, and delivered, so engineering, legal, and compliance teams can review where the data came from and confirm they received exactly what was licensed.
Every full HFA dataset is traceable to its source and verifiable at delivery.
Every file traces to its recording session: performer, technique, signal chain, and capture parameters. Performers assign full rights in writing, with AI training disclosed explicitly.
Per-file SHA-256 checksums are delivered with licensed data, so any file can be verified against the master at any point in a pipeline.
An optional technique that may support identification in disputed-provenance cases. Not required in v0.9 and not relied upon for consent, provenance, or integrity guarantees.
Every licensed dataset ships with the same core package.
High-fidelity files captured to one consistent standard and structure.
Standard metadata for each file, such as labels, session context, and technique taxonomy, depending on the dataset.
Per-file SHA-256 checksums to confirm every file matches what HFA delivered.
Clear dataset versions for reproducibility and change tracking across releases.
Orpheus Suite adds optional metadata built to a buyer's need, such as
instruction-tuning labels or MIDI data. Checksums verify with standard tools like
sha256sum, with no proprietary software required. Free previews are
built for evaluation; the full Proteus documentation comes with licensed datasets.
Proteus is built for transparency, not control.
It places no restrictions on how licensed teams use data inside their own pipelines.
Verification uses standard, widely available tools. Nothing proprietary is required.
Proteus favors transparent, reviewable signals over claims of invisible marks that survive any transformation.
HFA can map Proteus documentation to your organization's security, legal, or compliance review as part of licensing.