Documentation

• Docs index
• Core framework API
• Configuration & inheritance
• Task: SFT
• Task: PM
• Task: NBack
• Task: Bricks
• Task: Stroop
• Task: Tracking
• Bricks runtime config schema

Structure

• packages/core: shared runtime, selection, config, scheduler, integration utilities
• apps/web: selection-aware browser shell
• tasks/sft: SFT (DotsExp) task adapter
• tasks/pm: PM task adapter
• tasks/bricks: Bricks (DiscoveryProject) task adapter
• tasks/stroop: Stroop task adapter
• tasks/tracking: continuous tracking task adapter
• configs/*: core + task-specific presets

URL selection

Supported query params:

• task: task id (sft, pm, nback, bricks, stroop, tracking)
• variant: variant id within task
• config: optional task config path override
• overrides: URL-encoded JSON override

Participant params:

• PROLIFIC_PID, STUDY_ID, SESSION_ID, SONA_ID, participant, survey_code

Dev

npm install
npm run dev

Auto-responder launch example:

http://localhost:5173/?task=sft&variant=default&auto=true

Long-run JATOS auto-responder (headless, focus-independent):

npm run autoresponder:url -- \
  --url "https://<your-jatos-host>/jatos/run?..." \
  --max-minutes 130 \
  --done-text "Thank you very much for participating"

Notes:

• If auto is missing in the URL, the runner injects auto=true by default.
• For JATOS publix start pages that require a launch click, pass --start-selector "button:has-text('Start')" if needed.
• Artifacts are written to temp/autoresponder-runs/<timestamp>/ (result.json, screenshot, HTML).

Design stance

The common framework is the source of truth. Task adapters run natively inside this workspace and do not redirect into external experiment folders.