AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Quick Start Guide — LUCID Toolkit — GPT + Qualtrics Backend Welcome to the backend server powering the LUCID Toolkit — a research infrastructure for running controlled GPT-based chatbot interactions directly inside Qualtrics surveys. This code (Flask backend) serves as a secure proxy to the OpenAI API — allowing each researcher or research team to create their own isolated, privacy-preserving implementation of the LUCID system. ⚠️ Why Is a Separate Server Needed?檢視完整 README ↗
Welcome to the backend server powering the LUCID Toolkit — a research infrastructure for running controlled GPT-based chatbot interactions directly inside Qualtrics surveys.
This code (Flask backend) serves as a secure proxy to the OpenAI API — allowing each researcher or research team to create their own isolated, privacy-preserving implementation of the LUCID system.
It is not safe to embed an OpenAI API key directly in Qualtrics — whether in JavaScript, Survey Flow, or an HTML element. Survey participants (or anyone inspecting the page) could easily view and copy your key.
The LUCID backend solves this by securely handling GPT requests on your own private server. The API key is never visible to participants. And the best part?
You only need two accounts to get started:
An OpenAI API Key
A GitHub Account
(Optional) A printable version of our detailed setup guide containing all steps with screenshots 📄 Guide (.docx)
If you have all this, you're ready to get started.
To get started, click the following button:
You'll be taken to Vercel.
my-lucid-backend-code). This name will determine your default backend deployment URL that will be used by Qualtrics, so use a name you are comfortable with others (such a reviewers) potentially seeing.OPENAI_API_KEY:
OPENAI_API_KEY value field in Vercel.Visit Your Deployment: Once Vercel shows the deployment is complete ("Congratulations!"), click the image displayed that says in blue text "LUCID Backend Succesfully Deployed!".
Copy the URL: The resulting page you visit should display "LUCID Backend Successfully Deployed!". It will clearly show the exact URL needed for Qualtrics. Click the "Copy Backend URL" button (e.g., https://your-project-name.vercel.app/lucid). Keep this address handy for the Qualtrics setup.
Download your .QSF file from this repository:
LUCID_Qualtrics_Template_1_-One_Group_Design.qsf - A single condition design (e.g., for conducting an interview using the same chatbot for all participants)
LUCID_Qualtrics_Template_2_-Two_Group_Between_Subjects_Experiment.qsf - A 2-Group between subjects design (e.g., for conducting an experiment that manipulates chatbot behavior)
Garvey, Aaron M. and Simon J. Blanchard, (2025) "Generative AI as a Research Confederate: The LUCID Methodological Framework and Toolkit for Human-AI Interactions Research," MSI Working Paper. paper@ssrn
Blanchard, S. J., Duani, N., Garvey, A. M., Netzer, O., & Tae Oh, T. (2025). New Tools, New Rules: A Practical Guide to Effective and Responsible Generative AI Use for Surveys and Experiments in Research. Journal of Marketing, 89(6), 119-139. paper@Journal of Marketing
The code contents of this git repository are available for non-commercial use under Creative Commons BY-NC-SA (https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode.en).