DTRACDTRAC Project is the starting point for documentation about the builder and its agents. It separates the workspaces used to author research and collection settings from the execution roles that support that work. This is a guide to the current code structure, not a complete installation or operations manual or a claim of deployment readiness.
How the three products relate
| Product | Documentation scope |
|---|---|
| DTRAC Project | Research app configuration and builder/agent structure |
| DTRAC Android | Conditions, data, and development of the collection app on participant devices |
| DTRAC SDK | The roadmap for offering collection modules to other Android apps |
The Android documentation explains participant-device runtime behavior. The SDK documentation separates reusable modules from remaining integration work; it does not describe a released unified SDK.
Where to start
- Builder structure & workspaces: identify the current UI entry point and the boundaries between research, collection, and design work.
- Agents & execution roles: distinguish runtime agents, pipeline capabilities, and compatibility prompts.
Documentation baseline
This guide reflects the September 17, 2026 working tree. The default renderer entry point connects main.tsx to StudioShell. Agent classification follows agentTaxonomy.mjs. The existence of older stage-based screens or files does not establish that they are the current default UI.
New guides and integration examples can be added to this product after their behavior and execution conditions have been checked. Whether a project configuration produces a deployable Android app, and what validation an external study requires, need separate verification.
Architecture reference
Refer to DTRAC architecture — Assurance tab alongside the builder and agent structure. This link opens the external architecture reference with the Assurance tab selected.
The reference site currently requires ChatGPT sign-in.