CONTROL & RECORDS
Keep every attempt
accounted for.
Versioned batches keep rehearsal and formal records separate. Predictions are prepared offline.
Create a study batch
Readiness records must refer to real institutional decisions and independent review. A configuration flag is an operator declaration, not evidence verification.
0Invitations in this batch
0Task records in this batch
0Accepted participation decisions
Create independent invitations
Codes are shown once. Keep the downloaded CSV private and issue one invitation per person. The formal cap is 50 across all formal batches; task order alternates.
Recorded attempts
| Participant | Task | Stage | Revision | Data kind |
|---|
The coding packet contains completed tasks and B responses, without A answers, process history or model predictions. Human grades remain empty. T0 packets contain information recorded at or before the initial submission. Outcome tables belong only in analysis after predictions are locked.