Benchmarks and results
Collaborate and preserve a reproducible experiment record
Invite collaborators, keep owner billing intact, lock manifests, preserve source revisions, and retain an auditable run history.
The basic idea
Collaboration should not blur responsibility. The experiment creator remains the billing owner; invited users gain access to that experiment but cannot silently become owners or rewrite locked scientific definitions.
A principal investigator creates and funds a benchmark experiment, invites a collaborator to run it, and preserves the protocol, outcome definitions, benchmark revision, sample seed, attempts, scores, and costs.
How to do it
- 1
Create the experiment under the account that should own billing and data controls.
- 2
Invite collaborators by their verified account email.
- 3
Review and lock outcome and protocol manifests before confirmatory execution.
- 4
Record benchmark source revision, filters, seed, option-order mode, failures, exclusions, token use, and final scoring.
What to watch for
- Collaborator runs charge the original owner’s balance.
- Unlocking is recorded and must occur before a changed protocol can be saved.
- Deleting an experiment removes its associated workspace record, so export needed evidence first.
What a useful result looks like
The resulting record makes it possible to explain who ran what, under which locked design, against which data revision, and at what cost.