Some collaborators can open the live AXP survey page. Others only have Google Sheets and OSF download access. This guide shows what each group can do with the access they already have.
Open the running questionnaire, submit a response, and use the current feedback view, guide, and share image actions.
Review wording, translations, options, version tabs, and the stable comparison-token registry in the shared questionnaire sheet.
Use the data examples page to inspect file shapes, field meanings, and export formats without needing live survey access.
Review how Google Sheets, MariaDB, public/private OSF exports, comparison tokens, and dose labels fit together.
Open the diagrams when you want a fast picture of how sheet edits, the running survey, and data examples fit together.
Open the public radial violin lab and adjust plot geometry, peer color, and scale direction in the browser.
Create a collaborator link that opens the survey in English and preselects Breathwork plus the Berlin Breathwork Days option.
Use Live Survey for a real run-through, Google Sheets for questionnaire wording and structure, Data Examples for file shapes, and Plot Lab for public feedback-plot tuning.
Use https://alteredxproject.com/... without www for new participant and test links. Older http or www links still work and redirect permanently while preserving their path and prefill parameters.
Stable questions keep the same item_id. English rows carry structure and scale_id. Scorable submissions must produce all 11 canonical ASC factor scores.
The live feedback controls only expose enabled rows from the comparison_tokens registry. Raw text and Other-style context can be stored for context, but they never belong in participant comparison dropdowns.
Routine OSF uploads now use append-only run folders. Public files keep safe canonical condition tokens; private files keep raw context for restricted review.
Adding a new induction or dose option to the questionnaire collects that answer. It does not make a new peer-comparison option until a stable token row is added and enabled in comparison_tokens.
Submitted responses include broad timing and operational metadata used to assess whether a response looks like a reasonable completed submission. This guide keeps the exact review criteria high-level so those signals remain useful.
Start every newly shared link with the canonical host https://alteredxproject.com. The compatibility variants using http or www redirect to this address, but using the canonical form directly avoids an unnecessary redirect.
Use the public participant link when responses should count as ordinary survey submissions:
https://alteredxproject.com/survey/?lang=en&induction=breathwork&dose=Berlin+Breathwork+Days+2026Use the dev link for collaborator testing. It opens the same live app with the same prefill values, but submissions made through /dev/ are marked as test submissions and excluded from analysis.
https://alteredxproject.com/dev/?lang=en&induction=breathwork&dose=Berlin+Breathwork+Days+2026lang=en opens the English version directly. Other public language values are de and es.induction=breathwork preselects Breathwork as the induction method.dose=Berlin+Breathwork+Days+2026 preselects Berlin Breathwork Days 2026 in the second field.+ signs stand for spaces in the URL./dev/ is only for collaborator testing. Do not share it as a participant collection link.General participant pattern:
https://alteredxproject.com/survey/?lang=en&induction=breathwork&dose=Your+Option+HereGeneral dev-test pattern:
https://alteredxproject.com/dev/?lang=en&induction=breathwork&dose=Your+Option+HereFor standard peer-comparison buckets, use canonical English tokens such as induction=psilocybin and dose=high. Include induction whenever you include dose, because the available second-field options depend on the selected induction. The current comparison dropdowns are controlled by the comparison_tokens sheet tab, not by every raw questionnaire option.
Use the live survey page.
Google Sheets access is usually enough for the edit itself. Keep one tab per version and keep translation rows aligned to the English structural rows.
Add or update the questionnaire option first, then add a stable row in comparison_tokens. Only rows with comparison_enabled=1 appear in the feedback comparison controls.
OSF access is enough to get the current bundle. Use the data stack page for public/private split rules and the data examples page for concrete file shapes.
You can still edit the questionnaire and use the downloads. Ask someone with live survey access to confirm the running flow after a structural change.
Decide whether you can open the running survey, edit the sheet, download from OSF, or some combination of those.
Use Live Survey for the running questionnaire, Google Sheets for questionnaire changes, and Data Examples when you need file structures, field formats, and export shapes.
That is enough to see whether the updated questionnaire was picked up. For structural or scoring changes, complete one full submit path and check that feedback renders.
Open the diagrams if you want a quick map of how sheet edits, the running survey, and data examples connect.