Interviews
A real person's slot will be filled from what they can tell us. The interviews are long sessions in the participant's own browser, and nothing leaves the browser until it has been sealed.
Not open yet · tested with fictional participants onlyA session
- 01
Consent
What the session is, what is kept, for how long, who processes it and how to withdraw. Every statement has to be ticked before the first question appears.
- 02
Questions
Each block opens with a core question and then asks every follow-up in its bank, in an order drawn for that person from a recorded seed. Any question can be skipped, and a closed tab resumes where it stopped.
- 03
Held-out questions
Decisions before and after new information, and the words a cue brings to mind. These are what the models will later have to predict, so they are kept apart.
- 04
Sealing
The browser seals the answers in two halves under two keys. The typed answers go to the team; the held-out half can only be opened by a separate evaluator account, after the predictions have been committed.
- 05
A code instead of a name
Each participant gets a random code such as r-3f9c2a1b. The session never asks for a name.
- 06
Afterwards
Withdrawal is possible at any time, without giving a reason. Everything is deleted at the end of a fixed retention period, and the consent says exactly what can and cannot be erased.
Safeguards
| Promise | How it is kept |
|---|---|
| No model runs while you answer | Every follow-up is asked. Models run afterwards, offline, so nobody waits and nothing is generated about you during the session. |
| Nothing leaves your browser unsealed | The session page's content policy forbids network access. Only the sealed file leaves. |
| The held-out half stays shut | It is sealed to an evaluator key held by a separate account, and opened only after the predictions are committed. |
| You know who processes your answers | The consent names every service that will handle them before the first question. |
Before the first participant
Six of the fourteen items on our checklist are done. Still open:
- a reviewed consent form, and a named contact for questions and withdrawal;
- encrypted storage, a place for the keys, and backups of both;
- a retest interval, and one complete dry run that includes a withdrawal;
- a final pass removing sensitive blocks from the interview script;
- a separate frozen configuration for the first real participants.
Test version
The first session, Everyday decisions, takes 45 to 60 minutes. Its test version is marked TEST and never sends anything anywhere. The keys it seals to were destroyed after the page was built, so nobody, including us, can open what is typed into it. Please do not use it for real answers.
Open the test sessionLater
This first session is deliberately small. The interviews will grow into a programme: more sessions, longer ones, repeated over months to see how answers change, and new kinds of task. Each new instrument gets its own consent text and its own frozen protocol before anyone sees it.