Use RV with clear roles, careful records, and safe research language.
This manual translates the platform research plan into day-to-day guidance for everyone who uses RV: invite recipients, vault users, viewers, monitors, judges, analysts, target managers, study stewards, data stewards, and system stewards.
Guidance for current RV workflows, privacy boundaries, and role workspaces.
Contents
Jump to a sectionI have an invitation
Redeem a one-time code, review consent when requested, and enter only the workspace your invitation unlocks.
I need my vault
Use the account vault for protected identity notes and context mapping. RV cannot recover lost vault recovery material for you.
I am running a session
Use Acquisition to follow the neutral cue, capture stage entries, record breaks, add sketches, and lock when complete.
I am judging
Review locked, anonymized packets and rank each choice set without seeing target identity or viewer identity.
I am managing a study
Create a study shell, lock the protocol plan, prepare target pools, assign participation slots, and preserve role boundaries.
All user types
What each role sees and doesStarts from a code and sees only the entry, consent, vault, or workspace pages made available by that code.
Captures raw impressions, stage notes, event tags, and sketches while remaining blind to target identity.
Keeps the session paced and neutral, records cue and break events, and helps prevent protocol drift.
Ranks locked packets against anonymized choices and submits confidence and notes before the score is sealed.
Reviews locked study data after acquisition and judging to prepare research summaries and chance comparisons.
Curates target records and pools, keeps metadata safe, and freezes pools before assignments are made.
Creates study shells, locks setup details, prepares assignments, and keeps participants in the right workflow lanes.
Handles audit review, controlled exports, retention summaries, and release boundaries without adding identifying details.
Maintains operational readiness and governance screens while respecting the same blinding and privacy boundaries.
What RV is for
Start here#what-rv-is-forRV is a structured, blinded research and training platform. It helps teams separate capture, judging, feedback, analysis, and governance so each step can be reviewed later.
What you do
- Use RV for research workflows, training cohorts, blinded acquisition, blind judging, and calibration over time.
- Keep training work, blinded research work, and exploratory group discussion clearly separated.
- Treat every locked artifact as a record of what was captured at that time, not something to reinterpret before review.
- Use feedback only when the study workflow allows it. In blinded research work, feedback waits until judging is complete.
What to expect
- The app keeps workspaces role-guided so each user sees the pages relevant to the active context.
- Most screens emphasize neutral cues, locked records, blind review, audit history, and cautious research summaries.
- The strongest workflow is: plan the study, freeze target materials, assign work, collect independent sessions, lock artifacts, judge blind, then release feedback.
Avoid
- Do not use RV outputs as a replacement for ordinary research review, emergency decisions, clinical care, legal process, or operational command.
- Do not discuss target guesses or peer artifacts before individual work is locked.
Access and invitation basics
Entry#access-invitationsMost work begins with an invitation code. A code opens a specific capability, such as a session, judging packet, study workspace, or governance page.
What you do
- Open Invitation entry and paste the code exactly as it was shared with you.
- Review consent if the app asks for it before continuing.
- Use the role card in the sidebar to understand the current privacy context.
- If you need to switch contexts, use Redeem another and enter the next code.
What to expect
- A code may be single-use or limited to a specific role and workspace.
- The sidebar changes after redemption so you can reach only the pages available to that context.
- The app may show a restricted context if your code is expired, missing consent, or does not include access to that area.
Avoid
- Do not post invitation codes in public channels.
- Do not reuse another person's workspace context.
Account vault and privacy
Privacy#account-vaultThe vault is where protected identity notes and cross-context reminders belong. It is designed so protected material stays under user-held recovery material rather than ordinary platform recovery.
What you do
- Open the vault from a trusted device when you need to store or review protected identity notes.
- Save your recovery material somewhere safe before relying on the vault.
- Keep direct identifiers, personal labels, and context mapping notes in the vault instead of workflow notes or target metadata.
- Use anonymous capability workspaces for study actions unless you specifically need the vault.
What to expect
- RV cannot recover protected vault content if you lose the recovery material.
- Anonymous workflow access does not automatically unlock your vault.
- Admins and operators should not need direct identity details to run normal study workflows.
Avoid
- Do not put names, private contact details, or cross-context identity notes in session entries, judging comments, target metadata, or exports.
- Do not assume hosting metadata disappears completely; use the vault and safe workflow habits to minimize identity exposure.
Roles at a glance
Who does what#roles-at-a-glanceRV separates responsibilities so the same person does not accidentally see information that could bias another step. Your sidebar shows the role currently active for you.
What you do
- Check the role card before you start work so you know which lane you are in.
- Use the role switcher only when you are intentionally changing hats for a permitted task.
- Keep Viewer, Monitor, Judge, Analyst, Target Manager, and Data Steward work separate when a study requires it.
- Ask a steward for a new invitation if the role or workspace shown does not match your task.
What to expect
- Viewer and Monitor work centers on acquisition sessions.
- Judge work centers on ranking locked packets.
- Analyst and Data Steward work happens after records are locked and ready for review.
- Target Manager work happens before assignments are made and before pools are frozen.
Avoid
- Do not use role switching to peek at information that should remain concealed for the current study phase.
- Do not copy concealed target or assignment details into notes visible to other roles.
Study setup and assignments
Study stewards#study-setupStudy setup turns a research plan into a locked workflow. The important goal is to make the study ready before viewers, monitors, and judges begin their work.
What you do
- Create the study shell with a clear title, mode, and short purpose statement.
- Complete setup before launch: target pool, scoring approach, exclusion notes, stopping rule, and analysis plan.
- Lock setup only when the plan is ready to be followed as written.
- Create participation slots and share invitation codes through a trusted out-of-band channel.
What to expect
- Locked setup helps later reviewers understand what was planned before data collection began.
- Slot codes open only the intended workspace and should be handled like temporary secrets.
- Assignments and study status guide what downstream users can do next.
Avoid
- Do not change the plan informally after viewers begin work; create a new version or new study when needed.
- Do not paste participant names or private identity notes into study setup fields.
Target corpus and pools
Target Managers#target-corpusThe target corpus holds target records and pool membership for later blinded assignment. Good target management keeps choices comparable and prevents accidental reveal clues.
What you do
- Create target records with neutral titles and safe metadata.
- Add media only when it is appropriate for the study and does not expose unnecessary identity details.
- Group targets into pools with matched choices for later judging.
- Freeze a pool when it is ready for assignment so membership stays stable.
What to expect
- Frozen pools support fairer assignment and later review.
- Artifact links are handled through controlled access instead of public file paths.
- Judges should see anonymized choices, not labels that reveal the intended target.
Avoid
- Do not put names, private locations, reveal keys, assignment mappings, or obvious answer clues in target metadata.
- Do not change pool membership after the study plan depends on that pool.
Acquisition workspace
Viewers and Monitors#acquisition-workspaceAcquisition is the structured capture area for a blinded session. It prioritizes quick entry, neutral prompts, stage tags, event records, sketches, and a final lock.
What you do
- Open the assigned session and read only the neutral cue shown on the page.
- Capture first impressions quickly, then continue through the stage prompts as appropriate for the protocol.
- Use event buttons for cue delivery, breaks, overlay, misses, and other session events.
- Add sketches or notes as they occur, then lock the session when the record is complete.
What to expect
- The target identity and decoy set remain concealed during the session.
- Entries are timestamped so the session can be reviewed in order later.
- After lock, the session moves forward for judging and feedback according to the study workflow.
Avoid
- Do not browse target pools, analysis pages, or peer packets before your own work is locked.
- Do not edit entries to make them fit a later guess; capture what you experienced at the time.
Blind judging
Judges#blind-judgingJudging compares a locked session packet with an anonymized choice set. The judge ranks the choices and submits confidence and notes without seeing which choice is intended.
What you do
- Open each ready packet and review the viewer artifacts before ranking.
- Rank all four choices from best fit to least fit using the study's rubric and your notes.
- Add brief comments about why the ranking fits the packet.
- Submit only when you are ready for the score to be locked.
What to expect
- The intended target choice is concealed during entry.
- Submitted scores become read-only so downstream summaries have a stable record.
- Feedback release depends on the study workflow and may wait until all required judging is complete.
Avoid
- Do not use file names, timestamps, labels, or outside hints as ranking shortcuts.
- Do not revise a rank after discussing the packet with others.
Analysis reports
Analysts#analysis-reportsAnalysis pages summarize locked study data after the relevant capture and judging steps. They are meant to support careful research review and calibration.
What you do
- Open Analysis after study records are locked and judging data is available.
- Review observed rates, rank distributions, exclusions, and notes in the context of the original study plan.
- Separate planned summaries from exploratory observations.
- Use cautious wording when sharing findings outside the platform.
What to expect
- Reports may compare observed results with chance expectations for a four-choice ranking task.
- Interim looks and exploratory notes should be treated as aids for learning and future planning.
- The platform supports calibration over repeated cohorts rather than one-off certainty.
Avoid
- Do not describe reports as proving an outcome or replacing ordinary decision processes.
- Do not mix post-hoc observations into planned summaries without labeling them clearly.
Governance, exports, and retention
Data Stewards#governance-exports-retentionGovernance pages help stewards review audit history, prepare controlled exports, and inspect retention summaries while keeping identity details out of research outputs.
What you do
- Use the audit view to review what changed, when it changed, and which role context performed the action.
- Prepare exports only for approved research, review, or release purposes.
- Check export manifests for identity-excluding language and safe bundle names.
- Review retention summaries before archival or removal work.
What to expect
- Export bundles should use local or bundle-specific pseudonyms rather than direct identity details.
- Retention views summarize lifecycle state and policy timing without asking stewards to expose private identity notes.
- Audit history supports reproducibility, dispute review, and release accountability.
Avoid
- Do not add names, emails, account IDs, or reveal mappings to export notes or manifest fields.
- Do not share raw bundles outside the approved release path.
Safe language and good practice
Use carefully#safe-practiceThe platform is most useful when people preserve blinding, protect identity details, and describe outputs as research records rather than certainty claims.
What you do
- Use phrases like observed pattern, research summary, exploratory note, chance comparison, or calibration result.
- Keep personal identifiers out of workflow notes, session entries, target metadata, judging comments, and exports.
- Lock only when you are ready for a record to become part of downstream review.
- Store vault recovery material carefully and treat invitation codes as temporary secrets.
- Preserve independence: individual work first, discussion only after lock.
What to expect
- Careful language protects users, reviewers, and future research readers.
- Cleaner records make later feedback, judging, analysis, and replication easier.
- If you are unsure whether a field should contain private identity material, use the vault or ask a Data Steward before entering it.
Avoid
- Avoid certainty claims, outcome promises, or language that suggests RV replaces ordinary professional processes.
- Avoid backfilling notes after feedback in a way that obscures what was captured before review.
Frequently asked questions
Common user concernsCan I use RV without an invitation?
You can read the overview, this manual, and the vault page publicly. Most study work requires an invitation or active role context so the platform can preserve workflow boundaries.
Why can I not see target details during a session?
Concealment protects the research workflow. Viewers and monitors should work from the neutral cue only until the session is locked and the study reaches the appropriate feedback step.
Can RV recover my vault if I lose recovery material?
No. Protected vault content depends on user-held recovery material. Store it carefully before relying on the vault for protected identity notes or context reminders.
Can I change a locked session or submitted score?
Locked records are meant to stay stable for downstream review. If something important needs correction, contact a study or data steward so it can be handled through the appropriate review path.
When is feedback available?
Feedback timing depends on the study mode and setup. In blinded research work, feedback usually waits until session artifacts and required judging steps are complete.
What should I do if I put private identity information in the wrong place?
Stop adding more detail and contact a Data Steward. Use the vault for protected identity notes, and ask for guidance before creating exports or sharing the affected record.
How should I describe analysis reports?
Use cautious research language: observed rate, chance comparison, calibration result, or exploratory note. Avoid certainty claims or promises about real-world decisions.