Researcher onboarding

What a researcher can do

Four capabilities beyond a normal teacher account:

1. Observe across the whole cohort — every teacher's classes, activities, engagement and cost.
2. Help a teacher directly — open any teacher's class or activity and change it: rename the class, add or create an activity in it, mint a join code, share or unshare an activity. An activity you create inside a teacher's class belongs to them — it appears in their own library and they can edit it without you. You cannot delete a teacher's class.
3. Maintain the teaching approaches — edit the seven published approaches that tutors teach with, and see which tutor teaches with what.
4. Experiment with rubrics — author and version the judge prompts (lenses) used to score student sessions, and run a judge over a captured session.

When you edit something you do not own, the page tells you whose it is, and the teacher's page afterwards says who last edited it and when. Every such edit is also recorded for audit.

Getting access

The researcher role is a claim an administrator sets on your account (via aiplatform users grant-researcher <uid>). Once granted, sign out and back in so your session picks up the new role. You will then see the extra controls described below — scope switches on Classes and Activities, extra tabs under Insights, extra tabs under Tutors (account menu), and a Programme item in the sidebar. The account menu shows your role as a line under your name (Role: researcher). Without the role, these surfaces show a "Researcher access required" message.

With the role, the screens default to English. To read them in Danish, use the DA | EN switch in the account menu (top right); your choice is remembered in this browser.

Cross-teacher observation

• Research view (activities) — on Activities, an All teachers tab beside Mine and Shared by colleagues opens a scan of every teacher's activities, in every state (Draft / Private / Shared), with the owner shown. Use it to see what is being built across the cohort. Open one to see exactly what the teacher configured and, if needed, change it on their behalf — the editor says whose it is.
• Research view (classes) — on Classes, a Your classes / All teachers' classes switch changes the list to every teacher's classes; selecting a class's name opens it with the same controls the teacher has.
• Insights across all teachers — Insights opens on Lessons. On its All classes tab, the same Your classes / All teachers' classes switch widens the comparison of engagement and spend to the whole cohort.
• Conversations — a researcher-only tab under Insights: every student conversation, grouped by the teaching approach that produced it, with the transcript one click away (Read). The transcript shows the group's workspace work — table entries, writing, checklist ticks, simulation events — between the turns where it happened, and What they ended with beside it shows the group's final saved work on that activity. Export (CSV or JSONL) downloads the turns under the selected approach.
• Cost — a researcher-only Cost tab under Insights breaks cross-class spend down by cohort, model, voice (speech-to-text / text-to-speech) and class, over a period you choose.

Teaching approaches and tutors

Open Tutors from the account menu (top right). As a researcher you get four tabs:

• Approaches — the seven published approaches. Edit teaching approach changes an approach's constructs; the tutor's prompt is rebuilt from them, so it stays traceable to the source paper. Below them are the custom approaches teachers and researchers have written.
• Tutors — build tutors (the same panel teachers have); then What each tutor teaches with, where you change which approach a tutor teaches with, in every class that uses it; then Faces and voices.
• Try them — ask two tutors the same question side by side, and see what each was told.
• Research tools — Everything that teaches, and how much it is used (every approach, who wrote it, how many tutors use it and how many turns it has taught), Corrections as a calibration set, and the Judge lenses (see Rubric experimentation below).

The Tutor co-pilot on this page proposes constructs for an approach and can search the papers held in the private literature corpus; citations stay yours to vouch for.

Writing a custom approach and building a tutor on it does not need the researcher role — any teacher can, on Approaches (under Your own teaching approaches) and Tutors (guide T1, Make your own tutor). Only editing the seven published approaches is researcher-only.

Rubric experimentation

On Tutors → Research tools, the Judge lenses panel is where you shape and test how student sessions are scored (it used to sit under Settings, which now points here):

• Judge lenses — for each lens you can enable/disable it, choose the judge model, inspect the default prompt, and write a judge prompt override. Saving an override bumps its version, so you can iterate on the wording and keep the history. Reset to default reverts it.
• Experiment — score a captured session — paste a session id, pick a lens, and Run judge to see the score profile that lens produces on real data (or an "Abstained" result when the lens declines to score).

This is the workflow for developing the capability-floor rubrics: change a lens prompt, run it against known sessions, compare the profiles, and promote a version when it behaves.

Next steps

• The teacher-facing surfaces work as documented in T1–T4; the researcher views sit alongside them.