turnset

What exactly are you licensing?

Real human sessions with agents, licensed with the rights attached.

Every contributor is paid for each session that finalizes. The people in the data chose to be there, and were paid for it. No scraping, no telemetry reads, no zipped-up history folders.

How is that different from an exported log?

Recorded live, not reconstructed after the fact.

Most workflow data on offer is an export. Someone finishes the work, finds the log file, uploads it and ticks a box. The left column is what that can tell you. The right column is what being there at the time can tell you.

An exported logA Turnset trace
Consent collected after the work, when a file gets uploadedConsent recorded before the session existedThe contributor starts each capture session on purpose. The trace carries the terms version in force at that moment. Nothing arrives by default.
No way to tell a person from a scriptEvidence a person was at the keyboardTurn timing, the corrections in the transcript, and for the top tier a repository and a test run.
Clean one-shot examples that resolve on the first tryThe failures and the recovery after themWhat broke, what the error said, and how the person redirected the agent. Reward models and RL need these turns. They cannot be synthesized, and public data has almost none of them.
Text with no evidence the work succeededOutcome signals from the session itselfTest runs, exit codes, retries, commits, and whether the task resolved.
Rights asserted by whoever uploaded the fileA rights boundary enforced at capturePersonal, open-source and sandbox work only, stated before they start and checked against the trace.
Scrubbing applied to a file that already left the machineRedaction before the data exists anywhere elseSecrets are removed on the contributor's own machine. Each trace carries the scrub version that ran and what it removed.

Why the human half matters. Model output is abundant and getting cheaper. What stays scarce is a competent person deciding what to ask for next, judging a wrong answer, and steering an agent through a task that did not go straight. That decision sequence is what a trace preserves.

What are the tiers?

Licensed per trace, by tier.

A trace enters the tier its artefacts qualify it for. You pay for the tier you need, and only for the traces you license.

Conversation
Multi-turn dialogue between a person and an agent on a real task, with the human turns marked. For SFT, evals, and user simulators trained on how people actually talk to agents.
Trajectory
Agentic trajectories: tool calls with their results, a checkable step inside the trace, and human corrections after the agent started working. For RL, reward modelling, failure analysis, and preference pairs drawn from real corrections.
Verifiable
A task instance with a verifiable outcome: repository and start commit, state at exit, the final diff, and tests that ran after the last edit. For RL with verifiable rewards, SWE-bench-style evals, and environments seeded from work that happened.

Every trace records the harness, the models it called, and tokens and latency per call. Packages carry the provenance record for every trace, the scrub version that ran, and the tier evidence. Raw captures are never delivered, and there is no browser over individual contributors.

What is written down, and when?

Written down while it happens.

A reconstruction is a claim rather than a record. Being in the capture path is what lets us hand you the record.

Consent
Recorded per session, not assumed once. Contributors accept the terms, then choose which sessions to capture. Each trace carries the terms version from the moment of capture.
Rights
Asserted at capture, not inferred later. Personal, open-source and sandbox work only. Employer code, client code and anything under NDA are out. Stated before they start, not certified afterwards.
Processing
Recorded, not asserted. Collector version, scrub version and what it removed, the host allowlist in force, and timestamps for capture, window close and finalization. A chain you can audit, per trace.
Removal
Runs forward, never backward. Every trace sits visible to its contributor for 24 hours and can be excluded free, so packages only contain what passed. Later withdrawal drops it from all future packages. Delivered packages are not recalled.
Secrets
Removed on the contributor's machine. Tokens, keys and identifying paths are scrubbed before the data exists anywhere else. The result is privacy-preserved. Traces this rich cannot honestly be called anonymized.

Can a contributor withdraw data after we license it?

Not from a delivered package. Every trace sits with its contributor for 24 hours before it can be licensed, so packages contain only what passed that window. A later withdrawal removes the trace from future packages and nothing else.

How do you know a person did the work?

The session was started by the contributor through our collector, on their machine, under terms accepted first. Turn timing, the corrections in the transcript, and for the verifiable tier a repository and a test run all come from the wire, not from a form.

What about secrets and personal information?

Keys, tokens and identifying paths are removed on the contributor's machine before anything is written to disk. Each trace records which scrub version ran and what it removed. We describe the result as privacy-preserved; traces this rich cannot honestly be called anonymized.

Is this data already in public training corpora?

The sessions are captured on the contributor's machine and are not published anywhere. Code in an open-source repository can be public; the session that produced it, with its turns, tool calls and corrections, is not.

Whose code is in a trace?

Personal, open-source and sandbox work only. Employer code, client code and anything under NDA are outside the pilot's scope, stated to the contributor before they start and checked against the trace before payment.

How is it priced?

Per trace, by tier. You pay for the traces you license. Tell us the coverage you need and we quote against it. Datasets are licensed under a written agreement, not click-through terms.

Tell us what you need it to cover. Supply is being built cohort by cohort, so the shape of what we collect is open to influence.