Review and update the questionnaire in the shared sheet.

Current questionnaire contract

Use comparison_tokens to promote stable peer buckets.

The questionnaire tab and the comparison registry have different jobs. The questionnaire tab decides what participants can select and submit. The comparison_tokens tab decides which stable buckets can appear in the feedback comparison controls.

Columns to maintain

• kind: use induction or dose.
• token: stable internal value, for example breathwork or berlin_breathwork_days_2026.
• label_en, label_de, label_es: participant-facing labels for comparison controls.
• induction_token: optional for dose rows; use it when a dose belongs under one induction, for example breathwork.
• aliases: semicolon-separated old labels and alternate spellings that should map to the same token.
• comparison_enabled: set to 1 to show the row in comparison controls; set to 0 to keep it mapped but hidden.
• sort_order: stable display order.

Example rows

kind,token,label_en,induction_token,aliases,comparison_enabled,sort_order
induction,cannabis,Cannabis,,weed;marijuana,1,10
induction,breathwork,Breathwork,,breath work;breathing,0,50
dose,low,Low,,low dose;microdose,1,10
dose,berlin_breathwork_days_2026,Berlin Breathwork Days 2026,breathwork,Berlin Breathwork Days,0,120

Safe workflow

1. 1
   Add or rename the questionnaire option.

   This changes what participants can submit in the running survey.

2. 2
   Add or update the matching registry row.

   Choose a stable token. Do not change that token later just because the visible label changes.

3. 3
   Keep new buckets hidden until they are intended for comparison.

   Use comparison_enabled=0 while collecting or testing. Switch to 1 only when collaborators agree it should appear publicly in the comparison controls.

4. 4
   Notify the app maintainer after token or alias changes.

   The peer-plot cache should be rebuilt after mapping changes so historical rows use the updated canonical tokens.

Google Sheets workflow

1. 1
   Open the current shared questionnaire tab.

   Confirm you are working in the intended version before changing anything.

2. 2
   Make the content change.

   Update wording, translations, options, or structural rows in the stacked table. Keep the same columns across language blocks.

3. 3
   Keep stable questions stable.

   Keep the same item_id when the question is still the same underlying question, and keep scorable English rows mapped through canonical scale_id values.

4. 4
   Update comparison_tokens when comparison eligibility changes.

   Do this only when an induction or dose should map to a stable peer bucket. New questionnaire options do not automatically become comparison options.

5. 5
   Let the sheet enforcer sync the tab.

   If the Google Sheets Apps Script is installed, it will auto-sort language blocks, keep the expected header shape, and apply the row formatting the questionnaire uses.

6. 6
   Create a new dated tab when the version truly changes.

   Use a new dated version when the questionnaire definition should be tracked separately.

7. 7
   Open the running survey once if you want confirmation.

   That is enough to see whether the latest sheet version was picked up. For response logic or scoring changes, complete one submit path and confirm that feedback renders.

8. 8
   Tell download users if files may change.

   If the change affects the meaning of later exports or codebooks, let OSF users know what to expect.

What the Google Sheets enforcer does

• If installed, the Apps Script runs on edit and is also available from the AXP Sheet menu as Sync questionnaire sheet.
• It keeps the questionnaire tab in the expected header order and auto-sorts each language block by the English row order.
• It colors and formats rows from the English structural metadata, including active state and scale_id.
• It checks that explicit induction_method_N, dose_options_N, and dose_label_override_N triplets are structurally complete before syncing.
• It helps keep the sheet structurally valid and readable, but it is not a separate publish step. The running survey still reads the questionnaire from the sheet itself.