STEP 01
BRING THE WORK
Intake
Share the queue, the rubric, the reviewers, and what a successful pilot has to prove.
→HUMAN DATA OS · PILOT
Bring one queue. Keep the proof.
Pick one queue you already run — annotation, RLHF, red-team, or eval. We scope it, run it on your data in your tenant, and hand back a signed result you keep. First batch in weeks, not quarters.
BRING ONE QUEUE
One queue in
Annotation, RLHF, red-team, or eval — a queue you already run, on your data, in your tenant.
KEEP THE PROOF
A signed result
Every reviewed case, override, and regression carries who created it, who reviewed it, and under what rights.
TIMELINE
Weeks, not quarters
First batch reviewed in weeks. Then a clear decision to expand or stop.
HOW A PILOT RUNS
Intake. Scope. Sign.
One queue in. A standardized review loop on your data. A signed result out — and a clear decision to expand or stop.
STEP 02
RUN IT ON YOUR DATA
Scope
We run a standardized review loop on your data, in your tenant, with the reviewers and rubric your team trusts. Never pooled.
→STEP 03
KEEP THE PROOF
Sign
First batch reviewed. Regressions captured. A signed packet — identity-verified consent attached to each case — that survives an examiner and an EU AI Act audit.
WHY NOW
Three reasons a pilot can't wait.
A pilot is how you prove a neutral, audit-ready second source on your own work — before you have to.
A NEUTRAL SECOND SOURCE
Your largest source got absorbed
When the biggest data vendor was bought by one of the labs it served, its other customers needed an independent source they could defend under audit. A pilot is how you prove one.
SUPPLY-CHAIN GOVERNANCE
A competitor lost four terabytes
Including who its workers were. Identities were pooled in one place and leaked. We verify identity, attach consent to each datapoint, and never pool your data.
EU AI ACT · AUGUST 2026
The provenance clock is running
78% of orgs can't validate their training data and 77% can't trace its origin. Enforcement begins August 2026. You need provenance attached to the data, not a dashboard about it.
WHAT “SIGNED” MEANS
An identity-verified chain of consent, attached to the datapoint itself. Your reviewers sign each call. The packet runs in your tenant and is never pooled, so it survives an examiner and an EU AI Act audit. A frontier AI lab ran this pilot and kept the packet for examination.
WHAT A PILOT COMMITS TO
A first batch in units and a price band up front. A robotics pilot is $25K–$100K for 100–500 reviewed episodes. We scope the human-data batch the same way, so you know what you are committing to before you send the form.
Human Data OS · Pilot intake
Scope the pilot.
Tell us the queue, the timeline, and what you want to prove. You get a reply in one business day with a scoped pilot, the deliverable defined, and the terms to expand or stop. No generic sales call.
Bring the work · Keep the proof
Start a pilot.
Two doors, one loop. Bring an expert human-data queue, or bring an operational workflow from your field and keep the tuned weights. Same Intake, Scope, Sign either way.
Pilot intake
Accepting
Starts fromOne queue you already run
Leaves withSigned packet · regression cases
PathIntake → Scope → Sign
OwnerHuman Data pilot desk