Update docs, continue route consolidation

THESIS_PROJECT_BACKLOG.md

@@ -0,0 +1,361 @@
+# HRIStudio Project Backlog - Honors Thesis Research
+
+## Project Overview
+
+**Student**: Sean O'Connor  
+**Thesis Title**: A Web-Based Wizard-of-Oz Platform for Collaborative and Reproducible Human-Robot Interaction Research  
+**Timeline**: Fall 2025 - Spring 2026  
+**Current Date**: September 23, 2025
+
+## Current Status Assessment
+
+### Platform Strengths
+- **Core Platform Complete**: Production-ready backend with 12 tRPC routers, 31 database tables
+- **Visual Designer**: Repository-based plugin system with 26+ core blocks  
+- **Type Safety**: Clean TypeScript throughout, passes `bun typecheck`
+- **Authentication**: Role-based access control (Admin, Researcher, Wizard, Observer)
+- **Development Environment**: Comprehensive seed data and documentation
+
+### Critical Gaps
+- **Wizard Interface**: Needs complete revamp - current implementation insufficient
+- **Robot Control**: Not working yet - core functionality missing
+- **NAO6 Integration**: Cannot test without working robot control
+- **Trial Execution**: Dependent on wizard interface completion
+
+### Platform Constraints
+- **Device Target**: Laptop-only (no mobile/tablet optimization needed)
+- **Robot Platform**: NAO6 humanoid robot
+- **Study Focus**: Comparative usability study, not full platform development
+
+## Academic Timeline
+
+### Fall 2025 Semester
+- **Current Date**: September 23, 2025
+- **Goal**: Functional platform + IRB submission by end of December
+
+### Winter Break
+- **December - January 2026**: IRB approval process and final preparations
+
+### Spring 2026 Semester  
+- **January - February 2026**: User study execution (10-12 participants)
+- **March 2026**: Data analysis and results drafting
+- **April 2026**: Thesis defense preparation and execution
+- **May 2026**: Final thesis submission
+
+## Research Study Design
+
+### Comparison Study
+- **Control Group**: Choregraphe (manufacturer software for NAO6)
+- **Experimental Group**: HRIStudio platform
+- **Task**: Recreate well-documented HRI experiment from literature
+- **Participants**: 10-12 non-engineering researchers (Psychology, Education, etc.)
+- **Metrics**: Methodological consistency, user experience, completion times, error rates
+
+### Success Criteria
+- Functional wizard interface for real-time experiment control
+- Reliable NAO6 robot integration
+- Reference experiment implemented in both platforms
+- Platform usable by non-programmers with minimal training
+- Comprehensive data collection for comparative analysis
+
+## Development Backlog by Timeline
+
+### Phase 1: Core Development (September 23 - October 31, 2025)
+**Goal**: Get essential systems working - 5-6 weeks available
+
+#### Week 1-2: Foundation (Sept 23 - Oct 6)
+
+**WIZARD-001: Wizard Interface Architecture** - CRITICAL
+- **Story**: As a wizard, I need a functional interface to control experiments
+- **Tasks**:
+  - Design wizard interface wireframes and user flow
+  - Implement basic panel layout (trial info, current step, controls)
+  - Create trial state management (start/pause/stop/complete)
+  - Build step navigation and progress tracking
+- **Deliverable**: Basic wizard interface shell with navigation
+- **Effort**: 8 days
+
+**ROBOT-001: Robot Control Foundation** - CRITICAL  
+- **Story**: As a wizard, I need to send commands to NAO6 robot
+- **Tasks**:
+  - Research and implement NAO6 WebSocket connection
+  - Create basic action execution engine
+  - Implement mock robot mode for development
+  - Build connection status monitoring
+- **Deliverable**: Robot connection established with basic commands
+- **Effort**: 6 days
+
+#### Week 3-4: Core Functionality (Oct 7 - Oct 20)
+
+**ROBOT-002: Essential NAO6 Actions** - CRITICAL
+- **Story**: As a wizard, I need basic robot actions for experiments
+- **Tasks**:
+  - Implement speech synthesis and playback
+  - Add basic movement commands (walk, turn, sit, stand)
+  - Create simple gesture library
+  - Add LED color control
+  - Implement error handling and recovery
+- **Deliverable**: NAO6 performs essential experiment actions reliably
+- **Effort**: 8 days
+
+**TRIAL-001: Trial Execution Engine** - CRITICAL
+- **Story**: As a wizard, I need to execute experiment protocols step-by-step
+- **Tasks**:
+  - Build trial state machine with database persistence
+  - Implement step-by-step execution workflow
+  - Create event logging with timestamps
+  - Add manual intervention controls
+  - Build trial completion and data export
+- **Deliverable**: Complete trial execution with data capture
+- **Effort**: 6 days
+
+#### Week 5-6: Integration & Testing (Oct 21 - Oct 31)
+
+**INTEGRATION-001: End-to-End Workflow** - CRITICAL
+- **Story**: As a researcher, I need complete workflow from design to execution
+- **Tasks**:
+  - Connect visual designer to trial execution
+  - Test complete workflow: design → schedule → execute → analyze
+  - Fix critical bugs and performance issues
+  - Validate data consistency throughout pipeline
+- **Deliverable**: Working end-to-end experiment workflow
+- **Effort**: 8 days
+
+### Phase 2: User Experience & Study Preparation (November 1-30, 2025)
+**Goal**: Make platform usable and prepare study materials - 4 weeks available
+
+#### Week 1-2: User Experience (Nov 1 - Nov 14)
+
+**UX-001: Non-Programmer Interface** - HIGH PRIORITY
+- **Story**: As a psychology researcher, I need intuitive tools to recreate experiments
+- **Tasks**:
+  - Simplify visual designer for non-technical users
+  - Add contextual help and guided tutorials
+  - Implement undo/redo functionality
+  - Create error prevention and recovery mechanisms
+  - Add visual feedback for successful actions
+- **Deliverable**: Interface usable by non-programmers
+- **Effort**: 10 days
+
+#### Week 3-4: Study Foundation (Nov 15 - Nov 30)
+
+**STUDY-001: Reference Experiment** - HIGH PRIORITY
+- **Story**: As a researcher, I need a validated experiment for comparison study
+- **Tasks**:
+  - Select appropriate HRI experiment from literature
+  - Implement in HRIStudio visual designer
+  - Create equivalent Choregraphe implementation
+  - Validate both versions work correctly
+  - Document implementation decisions and constraints
+- **Deliverable**: Reference experiment working in both platforms
+- **Effort**: 8 days
+
+**IRB-001: IRB Application Preparation** - CRITICAL
+- **Story**: As a researcher, I need IRB approval for user study
+- **Tasks**:
+  - Draft complete IRB application
+  - Create consent forms and participant materials
+  - Design study protocols and procedures
+  - Prepare risk assessment and mitigation plans
+  - Design data collection and privacy protection measures
+- **Deliverable**: Complete IRB application ready for submission
+- **Effort**: 6 days
+
+### Phase 3: Polish & IRB Submission (December 1-31, 2025)
+**Goal**: Finalize platform and submit IRB - 4 weeks available
+
+#### Week 1-2: Platform Validation (Dec 1 - Dec 14)
+
+**VALIDATE-001: Platform Reliability** - CRITICAL
+- **Story**: As a researcher, I need confidence the platform works reliably
+- **Tasks**:
+  - Conduct extensive testing with multiple scenarios
+  - Fix any critical bugs or stability issues
+  - Test on different laptop configurations (Mac, PC, browsers)
+  - Validate data collection and export functionality
+  - Performance optimization for laptop hardware
+- **Deliverable**: Stable, reliable platform ready for study use
+- **Effort**: 10 days
+
+**TRAIN-001: Training Materials** - HIGH PRIORITY
+- **Story**: As study participants, we need equivalent training for both platforms
+- **Tasks**:
+  - Create HRIStudio training workshop materials
+  - Develop Choregraphe training equivalent
+  - Record instructional videos
+  - Create quick reference guides and cheat sheets
+  - Design hands-on practice exercises
+- **Deliverable**: Complete training materials for both platforms
+- **Effort**: 4 days
+
+#### Week 3-4: Final Preparations (Dec 15-31)
+
+**IRB-002: IRB Submission** - CRITICAL
+- **Story**: As a researcher, I need IRB approval to proceed with human subjects
+- **Tasks**:
+  - Finalize IRB application with all supporting materials
+  - Submit to university IRB committee
+  - Respond to any initial questions or clarifications
+  - Prepare for potential revisions or additional requirements
+- **Deliverable**: IRB application submitted and under review
+- **Effort**: 2 days
+
+**PILOT-001: Internal Pilot Testing** - HIGH PRIORITY
+- **Story**: As a researcher, I need to validate study methodology
+- **Tasks**:
+  - Recruit 2-3 internal pilot participants from target demographic
+  - Run complete study protocol with both platforms
+  - Test wizard interface reliability during real sessions
+  - Identify and fix any procedural issues
+  - Refine training materials based on feedback
+  - Document lessons learned and methodology improvements
+- **Deliverable**: Validated study methodology ready for execution
+- **Effort**: 6 days
+
+### Phase 4: Study Execution (January - February 2026)
+**Goal**: Execute user study with 10-12 participants
+
+#### Study Preparation (January 2026)
+
+**RECRUIT-001: Participant Recruitment**
+- **Story**: As a researcher, I need to recruit qualified study participants
+- **Tasks**:
+  - Create participant screening survey
+  - Recruit from Psychology, Education, and other non-engineering departments
+  - Schedule study sessions to avoid conflicts
+  - Send confirmation and preparation materials
+- **Deliverable**: 10-12 confirmed participants scheduled
+- **Effort**: Ongoing through January
+
+**EXECUTE-001: Study Session Management**
+- **Story**: As a researcher, I need reliable execution of each study session
+- **Tasks**:
+  - Create detailed session procedures and checklists
+  - Implement real-time monitoring dashboard for study staff
+  - Build backup procedures for technical failures
+  - Create automated data validation after each session
+  - Design post-session debriefing workflows
+- **Deliverable**: Reliable study execution infrastructure
+- **Effort**: 4 days
+
+#### Data Collection (February 2026)
+
+**DATA-001: Comprehensive Data Collection**
+- **Story**: As a researcher, I need rich data for comparative analysis
+- **Tasks**:
+  - Automatic time-tracking for all participant actions
+  - User interaction logging (clicks, errors, help usage)
+  - Screen recording of participant sessions
+  - Post-task survey integration
+  - Experiment fidelity scoring system
+- **Deliverable**: Complete behavioral and performance data
+- **Effort**: Built into platform, minimal additional work
+
+### Phase 5: Analysis & Writing (March - May 2026)
+**Goal**: Analyze results and complete thesis
+
+#### Analysis Tools (March 2026)
+
+**ANALYSIS-001: Quantitative Analysis Support**
+- **Story**: As a researcher, I need tools to analyze study results
+- **Tasks**:
+  - Implement automated experiment fidelity scoring
+  - Build statistical comparison tools for platform differences
+  - Create completion time and error rate analysis
+  - Generate charts and visualizations for thesis
+  - Export data in formats suitable for statistical software (R, SPSS)
+- **Deliverable**: Analysis-ready data and initial results
+- **Effort**: 5 days
+
+#### Thesis Writing (March - May 2026)
+
+**THESIS-001: Results and Discussion**
+- **Tasks**:
+  - Quantitative analysis of methodological consistency
+  - Qualitative analysis of participant feedback
+  - Statistical comparison of user experience metrics
+  - Discussion of implications for HRI research
+- **Deliverable**: Thesis chapters 4-5 (Results and Discussion)
+
+**THESIS-002: Conclusion and Defense Preparation**
+- **Tasks**:
+  - Synthesis of research contributions
+  - Limitations and future work discussion
+  - Defense presentation preparation
+  - Final thesis formatting and submission
+- **Deliverable**: Complete thesis and successful defense
+
+## Critical Success Factors
+
+### End of December 2025 Must-Haves
+1. **Functional Platform**: Wizard can execute experiments with NAO6 robot
+2. **Reference Experiment**: Working implementation in both HRIStudio and Choregraphe
+3. **User-Ready Interface**: Non-programmers can use with minimal training
+4. **IRB Application**: Submitted and under review
+5. **Training Materials**: Complete workshop materials for both platforms
+6. **Pilot Validation**: Study methodology tested and refined
+
+### Risk Mitigation Strategies
+
+**Technical Risks**
+- **Robot Hardware Failure**: Have backup NAO6 unit available, implement robust mock mode
+- **Platform Stability**: Extensive testing across different laptop configurations
+- **Data Loss**: Implement automatic session backup and recovery
+- **Performance Issues**: Optimize for older laptop hardware
+
+**Study Execution Risks**
+- **Participant Recruitment**: Start early, have backup recruitment channels
+- **Learning Curve**: Extensive pilot testing to refine training materials
+- **Platform Comparison Fairness**: Ensure equivalent training quality for both platforms
+- **IRB Delays**: Submit early with complete application to allow for revisions
+
+**Timeline Risks**
+- **Development Delays**: Focus on minimum viable features for research needs
+- **Academic Calendar**: Align all deadlines with university schedule
+- **Winter Break**: Use break time for IRB follow-up and final preparations
+
+## Sprint Planning
+
+### October Sprint (Core Development)
+- **Total Development Days**: 28 days
+- **Key Milestone**: Working wizard interface + robot control
+- **Priority**: Technical foundation - everything depends on this
+
+### November Sprint (User Experience & Study Prep)  
+- **Total Development Days**: 24 days
+- **Key Milestone**: Non-programmer ready interface + IRB draft
+- **Priority**: Usability and study preparation
+
+### December Sprint (Polish & Launch Prep)
+- **Total Development Days**: 22 days  
+- **Key Milestone**: IRB submitted + reliable platform
+- **Priority**: Quality assurance and study readiness
+
+### Buffer and Contingency
+- **Built-in Buffer**: 10-15% buffer time in each sprint for unexpected issues
+- **Parallel Workstreams**: IRB preparation can happen alongside platform development
+- **Fallback Options**: Mock robot mode if hardware integration proves challenging
+- **Academic Alignment**: All deadlines respect university calendar and requirements
+
+## Success Metrics for Thesis Research
+
+### Primary Research Outcomes
+- **Methodological Consistency**: Quantitative fidelity scores comparing participant implementations to reference experiment
+- **User Experience**: Task completion rates, error rates, time-to-completion, satisfaction scores
+- **Accessibility**: Learning curve differences between platforms, help-seeking behavior
+- **Efficiency**: Setup time, execution time, and total task completion time comparisons
+
+### Platform Quality Gates
+- Zero critical bugs during study sessions
+- Sub-100ms response time for core wizard interface interactions  
+- 100% data collection success rate across all study sessions
+- Participant satisfaction score > 4.0/5.0 for HRIStudio usability
+- Successful completion of reference experiment by 90%+ of participants
+
+### Thesis Contributions
+- **Empirical Evidence**: Quantitative comparison of WoZ platform approaches
+- **Design Insights**: Specific recommendations for accessible HRI research tools
+- **Methodological Framework**: Validated approach for comparing research software platforms
+- **Open Source Contribution**: Functional platform available for broader HRI community
+
+This backlog prioritizes research success over platform perfection, focusing on delivering the minimum viable system needed to conduct a rigorous comparative study while maintaining the scientific integrity required for honors thesis research.

docs/proposal.tex

@@ -0,0 +1,141 @@
+% Thesis Proposal
+%\documentclass{buthesis_p}         %Default is author-year citation style
+\documentclass[numbib]{buthesis_p}  %Gives numerical citation style
+%\documentclass[twoadv, numbib]{buthesis_p} %Allows entry of second advisor
+\usepackage{graphics}             %Select graphics package
+%\usepackage{graphicx}            %
+\usepackage{amsthm}               %Add other packages as necessary
+\usepackage{setspace}             %For double spacing
+\usepackage{geometry}             %For margin control
+\usepackage{tabularx}
+\geometry{
+    left=1in,
+    right=1in,
+    top=1in,
+    bottom=1in
+}
+\begin{document}
+\butitle{A Web-Based Wizard-of-Oz Platform for Collaborative and Reproducible Human-Robot Interaction Research}
+\author{Sean O'Connor}
+\degree{Bachelor of Science}
+\department{Computer Science}
+\adviser{L. Felipe Perrone}
+%\adviserb{Jane Doe}              %Second adviser if necessary
+\secondreader{Brian King}
+\maketitle
+
+\doublespacing
+
+\section{Introduction}
+
+To build the social robots of tomorrow, researchers must find ways to convincingly simulate them today. The process of designing and optimizing interactions between human and robot is essential to the Human-Robot Interaction (HRI) field, a discipline dedicated to ensuring these technologies are safe, effective, and accepted by the public. Yet, conducting rigorous research in social robotics remains hindered by complex technical requirements and inconsistent methodologies.
+
+In a typical social robotics interaction, a robot operates autonomously based on pre-programmed behaviors. However, human interaction can be unpredictable. When a robot fails to respond appropriately to a social cue, the interaction can degrade, causing the human partner to lose trust or disengage.
+
+To overcome the limitations of pre-programmed autonomy, researchers often use the Wizard-of-Oz (WoZ) technique to test prototypes of robot behaviors before the underlying technology is fully developed. In this method, a human operator (the ``wizard'') observes the interaction from a separate room via cameras and microphones, controlling the robot's actions in real-time. To the person interacting with the robot, it appears fully autonomous, creating a convincing simulation that is helpful for rapid prototyping and testing of interaction designs.
+
+Despite its conceptual simplicity, conducting WoZ research presents two challenges. The first is a technical barrier that prevents many non-programmers, such as experts in psychology or sociology, from conducting their own studies. This accessibility problem is compounded by a second challenge: a fragmented hardware landscape. Because different labs use different robot platforms, researchers often must build their own custom control tools for each study. These bespoke systems are rarely shared, making it difficult for scientists to replicate and build upon each other's findings, which hinders the development of a reliable and verifiable body of knowledge.
+
+To address these challenges, I am developing HRIStudio, a web-based platform for designing, executing, and analyzing WoZ experiments in social robotics. I argue that by lowering technical barriers and providing a common experimental platform, a web-based framework can significantly improve both the disciplinary accessibility and scientific reproducibility of research in social robotics.
+
+\section{Context}
+
+The challenges of disciplinary accessibility and scientific reproducibility in WoZ research have been explored in HRI literature. In a foundational systematic review of 54 HRI studies, Riek \cite{Riek2012} discovered a widespread lack of methodological consistency, noting that very few researchers reported standardized wizard training or measurement of wizard error. This stems from a landscape of specialized, ``in-house'' systems, where individual labs develop their own custom software for each study, tools that are rarely shared with other researchers. This forces labs to constantly reinvent control interfaces, hindering the replication and verification of scientific findings.
+
+In response, the research community has developed several specialized WoZ platforms. A first wave of tools focused on creating powerful, flexible architectures. Polonius was designed as a robust interface for robotics engineers to create experiments for their non-programmer collaborators, featuring an integrated logging system to streamline data analysis \cite{Lu2011}. Similarly, OpenWoZ introduced an adaptable framework that used web protocols to allow different control interfaces to easily connect to the robot, empowering technical users to create deviations from the pre-programmed interaction scripts in real-time \cite{Hoffman2016}. While architecturally sophisticated, these tools still required significant technical expertise to set up and configure, keeping the accessibility barrier high.
+
+A second wave of tools shifted focus to prioritize usability for a broader audience. WoZ4U was explicitly designed to be an ``easy-to-use tool for the Pepper robot'' that makes it easier for ``non-technical researchers to conduct Wizard-of-Oz experiments'' \cite{Rietz2021}. WoZ4U successfully lowered the accessibility barrier with an intuitive graphical interface. However, this usability was achieved by tightly coupling the software to a single type of robot. This approach creates a significant risk to platform longevity. As Pettersson and Wik note in a review of generic WoZ tools, systems that are too specialized often fall out of use as hardware becomes obsolete \cite{Pettersson2015}. This trade-off between capability, usability, and sustainability reveals a critical gap in the literature. No available tool exists that is simultaneously flexible, accessible, and can endure over time.
+
+In response to this lack of an adequate tool, I designed HRIStudio by combining an intuitive web-based interface with a flexible architecture that allows it to support a wide range of current and future robots. The result is a single, sustainable platform that is both powerful enough for complex experiments and accessible enough for interdisciplinary research teams.
+
+\section{Description}
+
+I created HRIStudio as an integrated, web-based platform designed to manage the entire lifecycle of a WoZ experiment in social robotics: from interaction design, through live execution, to final analysis. I designed the platform around three core principles: making research accessible to non-programmers, ensuring the experiments are reproducible, and providing a time-enduring tool for the HRI community.
+
+To solve the challenge of accessibility, I provide researchers with tools to visually map out an experiment's flow, much like creating a storyboard for a film. This intuitive approach allows a social scientist, for example, to design a complex HRI without writing a single line of code. The platform provides different interfaces to facilitate collaboration between the members of a team: A researcher gets a design canvas to build the study, the wizard gets a streamlined control panel to run the experiment, and an observer gets a tool for taking timestamped notes.
+
+To enable experiment reproducibility, I designed HRIStudio to mitigate key methodological challenges inherent in WoZ research. The first challenge is inconsistent wizard behavior; a tired or distracted human operator can unintentionally introduce errors, compromising a study's validity. HRIStudio's wizard interface acts as a ``smart co-pilot,'' guiding the operator through the pre-designed script with clear prompts for what to do and say next. This minimizes human error and increases the likelihood of a standardized experience for every participant. The second challenge lies in the complex task of managing experimental data. A typical study generates multiple streams of data that are difficult to synchronize manually, including video, audio, robot sensor logs, and wizard actions. The platform acts as a central recorder, automatically capturing and timestamping every data stream into a single, unified timeline. This simplifies analysis and allows another researcher to ``replay'' the entire experiment to verify and analyze the findings of another's study.
+
+Finally, to ensure the platform will be a time-enduring tool for the community, I designed the system to be robot-agnostic. Rather than being constrained to operate with a single kind of robot, the platform uses a system of standardized ``connectors,'' like a universal remote programmable for any television. This flexible architecture ensures that the platform will remain a valuable tool for the community long after any specific robot becomes obsolete, providing a stable, lasting foundation for future research.
+
+\section{Significance}
+
+This work is significant because it accelerates the foundational research needed to deploy social robots in critical societal roles, such as providing companionship for the elderly in assisted living facilities or acting as classroom aides for children with autism. My tool directly enables and accelerates the rigorous, human-centered research on which the success and public acceptance of these technologies depend.
+
+The primary significance of HRIStudio is its potential to lower the barrier to entry for HRI research. By allowing for visual programming, the platform removes technical barriers that have traditionally limited this research to engineering disciplines. It invites the domain experts who should be leading these studies to design and execute their own experiments, leading to better research questions and effective robot behaviors.
+
+My goal with HRIStudio is to elevate the scientific rigor of the field. By promoting a common structure for designing experiments and support for data collection, HRIStudio allows researchers to more easily replicate, verify, and build upon each other's work. This work supports the ongoing effort to make HRI a more cumulative science, where findings can be more easily verified and built upon by other researchers.
+
+Ultimately, my work contributes a piece of critical, open-source infrastructure to the HRI community that directly addresses the documented challenges of accessibility, reproducibility, and sustainability. Beyond its immediate utility, the platform's architecture also serves as a tangible blueprint for web-based scientific tools, demonstrating a successful model for bridging the gap between an intuitive user interface and the complexity of controlling live robotic hardware.
+
+The foundational concepts of this work have already been reported in two peer-reviewed publications at the IEEE International Conference on Robot and Human Interactive Communication \cite{OConnor2024, OConnor2025}. This work represents the culmination of that research, delivering the platform's full implementation, a critical evaluation by real users, and its release as a tool for the community.
+
+\section{Independent Contribution}
+
+This work builds upon a foundational collaboration with my adviser that led to two publications and the initial high-level design of the HRIStudio platform. For this work, my primary intellectual contribution is the independent execution of the project; I am the sole developer responsible for the complete software implementation and for the design and execution of the user study.
+
+\section{Methods}
+
+The foundational concepts and early architecture of HRIStudio have been established in prior work \cite{OConnor2024, OConnor2025}. The primary goal of this work is to translate that foundation into a complete, stable, and usable platform, and then rigorously evaluate its success. Therefore, the work is divided into two key phases: first, the final implementation of the platform's core features as outlined in the project timeline, and second, a formal user study to validate its impact on experimental consistency and efficiency.
+
+The study will involve recruiting approximately 10-12 participants from non-engineering fields (e.g., Psychology, Education) who have experience designing experiments but little to no programming background. The core task will be to recreate a well-documented experiment from the HRI literature using the NAO6 robot. To ensure a level playing field, all participants will first attend a workshop on the software package they are assigned. The participants will be divided into two groups: a control group will use the manufacturer-provided Choregraphe software \cite{Pot2009}, and an experimental group will use HRIStudio.
+
+My evaluation will focus on two primary outcomes. The first is methodological consistency: I will quantitatively assess the accuracy of each group's recreated experiment by comparing their final implementation against the original study's protocol. This will involve a detailed scoring rubric that measures discrepancies in robot behaviors, trigger logic, and dialogue. The second outcome is user experience: after the task, participants will complete a survey to provide qualitative and quantitative feedback on their assigned software. This mixed-methods approach will provide robust evidence to assess HRIStudio's effectiveness in making HRI research more accessible and reproducible.
+
+A detailed project schedule, outlining all key milestones and deadlines, is provided in Appendix A.
+
+\section{Conclusion}
+
+This work addresses a significant bottleneck in HRI research. By creating HRIStudio, a web-based platform for Wizard-of-Oz experimentation, this work confronts the interconnected challenges of disciplinary accessibility and scientific reproducibility. The platform provides publicly available infrastructure that empowers non-technical domain experts to conduct rigorous HRI studies. Ultimately a common, accessible, and sustainable tool does more than just simplify experiments. It fosters a more collaborative and scientifically robust approach to the entire field of HRI.
+\newpage
+\bibliography{refs}
+\bibliographystyle{plain}
+
+\newpage
+\appendix
+\section*{Appendix A: Project Timeline}
+\label{app:timeline}
+
+\begin{table}[h!]
+\centering
+\renewcommand{\arraystretch}{1.5}
+\begin{tabularx}{\textwidth}{|l|X|}
+\hline
+\textbf{Timeframe} & \textbf{Milestones \& Key Tasks} \\
+\hline
+\multicolumn{2}{|l|}{\textbf{Fall 2025: Development and Preparation}} \\
+\hline
+September & Finalize and submit this proposal (Due: Sept. 20).
+
+Submit IRB application for the user study. \\
+\hline
+Oct -- Nov & Complete final implementation of core HRIStudio features.
+
+Conduct extensive testing and bug-fixing to ensure platform stability. \\
+\hline
+December & Finalize all user study materials (consent forms, protocols, etc.).
+
+Begin recruiting participants. \\
+\hline
+\multicolumn{2}{|l|}{\textbf{Spring 2026: Execution, Analysis, and Writing}} \\
+\hline
+Jan -- Feb & Upon receiving IRB approval, conduct all user study sessions. \\
+\hline
+March & Analyze all data from the user study.
+
+Draft Results and Discussion sections.
+
+Submit ``Intent to Defend'' form (Due: March 1). \\
+\hline
+April & Submit completed thesis draft to the defense committee (Due: April 1).
+
+Prepare for and complete the oral defense (Due: April 20). \\
+\hline
+May & Incorporate feedback from the defense committee.
+
+Submit the final, approved thesis by the university deadline. \\
+\hline
+\end{tabularx}
+\end{table}
+
+\end{document}

docs/route-consolidation-summary.md

@@ -0,0 +1,240 @@
+# Route Consolidation Summary
+
+## Overview
+
+This document summarizes the comprehensive route consolidation work completed in September 2024, which transformed HRIStudio from a fragmented routing structure with duplicated global and study-specific views into a clean, study-scoped architecture.
+
+## Problem Statement
+
+### Issues with Original Architecture
+- **Route Confusion**: Duplicate routes for participants (`/participants` and `/studies/[id]/participants`) and trials (`/trials` and `/studies/[id]/trials`)
+- **Code Duplication**: Separate components for global and study-specific views with 90% overlapping functionality
+- **Navigation Inconsistency**: Users confused about where to find functionality
+- **Maintenance Burden**: Changes required updates to multiple similar components
+- **Dashboard 404**: The `/dashboard` route was incorrectly configured and not accessible
+
+### Technical Debt
+- `participants-data-table.tsx` vs `ParticipantsTable.tsx`
+- `trials-data-table.tsx` vs `TrialsTable.tsx`
+- Inconsistent breadcrumb patterns
+- Broken links in navigation dropdowns
+- Multiple creation flows for the same entities
+
+## Solution: Study-Scoped Architecture
+
+### Design Principles
+1. **Single Source of Truth**: One route and component per entity type
+2. **Logical Hierarchy**: Studies as the primary organizational unit
+3. **Consistent Navigation**: All entity management flows through studies
+4. **User-Friendly Transitions**: Helpful redirects for moved functionality
+
+### New Route Structure
+
+```
+Global Routes (Minimal):
+├── /dashboard                    # Overview across all user's studies
+├── /studies                     # Study management hub
+├── /experiments                 # Global experiments (filtered by selected study)
+├── /plugins                     # Plugin management
+├── /admin                       # System administration
+└── /profile                     # User settings
+
+Study-Scoped Routes:
+├── /studies/[id]                # Study details and overview
+├── /studies/[id]/participants   # Participant management for study
+├── /studies/[id]/trials        # Trial management for study
+├── /studies/[id]/analytics     # Analytics for study
+└── /studies/[id]/edit          # Study configuration
+
+Individual Entity Routes (Preserved):
+├── /trials/[trialId]           # Individual trial details
+├── /trials/[trialId]/wizard    # Trial execution interface
+├── /trials/[trialId]/analysis  # Trial data analysis
+├── /experiments/[id]           # Individual experiment details
+└── /experiments/[id]/designer  # Visual experiment designer
+```
+
+## Implementation Details
+
+### 1. Route Removal
+**Deleted Global Routes:**
+- `/participants` (global participants list)
+- `/trials` (global trials list)
+- `/analytics` (global analytics)
+
+**Deleted Components:**
+- `src/components/participants/participants-data-table.tsx`
+- `src/components/participants/participants-columns.tsx`
+- `src/components/trials/trials-data-table.tsx`
+- `src/components/trials/trials-columns.tsx`
+
+### 2. Dashboard Route Fix
+**Problem**: `/dashboard` was 404ing due to incorrect route group usage
+**Solution**: Moved dashboard from `(dashboard)` route group to explicit `/dashboard` route
+
+**Before:**
+```
+/app/(dashboard)/page.tsx  # Conflicted with /app/page.tsx for root route
+```
+
+**After:**
+```
+/app/dashboard/page.tsx    # Explicit /dashboard route
+/app/dashboard/layout.tsx  # Uses existing (dashboard) layout
+```
+
+### 3. Helpful Redirect Pages
+Created user-friendly redirect pages for moved routes:
+
+**`/participants`** → Shows explanation and redirects to studies
+**`/trials`** → Shows explanation and redirects to studies
+**`/analytics`** → Shows explanation and redirects to studies
+
+**Features:**
+- Auto-redirect if user has selected study in context
+- Clear explanation of new location
+- Maintains dashboard layout with sidebar
+- Action buttons to navigate to studies
+
+### 4. Navigation Updates
+**App Sidebar:**
+- Removed global "Participants" and "Trials" navigation items
+- Kept study-focused navigation structure
+
+**Dashboard Quick Actions:**
+- Updated to focus on study creation and browsing
+- Removed broken links to non-existent routes
+
+**Breadcrumbs:**
+- Updated all entity forms to use study-scoped routes
+- Fixed ParticipantForm and TrialForm navigation
+- Consistent hierarchy: Dashboard → Studies → [Study] → [Entity]
+
+### 5. Form and Component Updates
+**ParticipantForm:**
+- Updated all breadcrumb references to use study-scoped routes
+- Fixed redirect after deletion to go to study participants
+- Updated back/list URLs to be study-scoped
+
+**TrialForm:**
+- Similar updates to ParticipantForm
+- Fixed navigation consistency
+
+**Component Cleanup:**
+- Removed unused imports (Users, TestTube icons)
+- Fixed ESLint errors (apostrophe escaping)
+- Removed duplicate functionality
+
+### 6. Custom 404 Handling
+**Created:** `/app/(dashboard)/not-found.tsx`
+- Uses dashboard layout (sidebar intact)
+- User-friendly error message
+- Navigation options to recover
+- Consistent with platform design
+
+## Benefits Achieved
+
+### 1. Code Reduction
+- **Eliminated Duplicate Components**: Removed 4 duplicate table/column components
+- **Unified Navigation Logic**: Single set of breadcrumb patterns
+- **Reduced Maintenance**: Changes only need to be made in one place
+
+### 2. Improved User Experience
+- **Logical Flow**: Studies → Participants/Trials/Analytics makes intuitive sense
+- **Reduced Confusion**: No more "where do I find participants?" questions
+- **Helpful Transitions**: Users with bookmarks get guided to new locations
+- **Consistent Interface**: All entity management follows same patterns
+
+### 3. Better Architecture
+- **Single Responsibility**: Each route has one clear purpose
+- **Hierarchical Organization**: Reflects real-world research workflow
+- **Maintainable Structure**: Clear separation of concerns
+- **Type Safety**: All routes properly typed with no compilation errors
+
+### 4. Enhanced Navigation
+- **Clear Hierarchy**: Dashboard → Studies → Study Details → Entity Management
+- **Breadcrumb Consistency**: All pages follow same navigation pattern
+- **Working Links**: All navigation items point to valid routes
+- **Responsive Design**: Layout works across different screen sizes
+
+## Migration Guide
+
+### For Users
+1. **Bookmarks**: Update any bookmarks from `/participants`, `/trials`, `/analytics` to study-specific routes
+2. **Workflow**: Access entity management through studies rather than global views
+3. **Navigation**: Use sidebar to navigate to studies, then access entity management
+
+### For Developers
+1. **Components**: Use study-scoped components (`ParticipantsTable.tsx`, `TrialsTable.tsx`)
+2. **Routing**: All entity links should go through study context
+3. **Forms**: Use study-scoped back/redirect URLs
+4. **Navigation**: Update any hardcoded links to removed routes
+
+## Testing Results
+
+### Before Consolidation
+- `/dashboard` → 404 error
+- `/participants` → Functional but duplicated
+- `/trials` → Functional but duplicated
+- Navigation confusion between global/study views
+
+### After Consolidation
+- `/dashboard` → ✅ Loads properly with full layout
+- `/participants` → ✅ Helpful redirect page
+- `/trials` → ✅ Helpful redirect page
+- `/analytics` → ✅ Helpful redirect page
+- `/studies/[id]/participants` → ✅ Primary participants route
+- `/studies/[id]/trials` → ✅ Primary trials route
+- `/studies/[id]/analytics` → ✅ Primary analytics route
+
+### Quality Metrics
+- **TypeScript**: ✅ Zero compilation errors
+- **ESLint**: ✅ All linting issues resolved
+- **Build**: ✅ Successful production builds
+- **Navigation**: ✅ All links functional
+- **Layout**: ✅ Consistent sidebar across all routes
+
+## Lessons Learned
+
+### Route Group Usage
+- Route groups `(name)` are for organization, not URL structure
+- Use explicit routes for specific URLs like `/dashboard`
+- Be careful about root route conflicts
+
+### Component Architecture
+- Prefer single components with conditional logic over duplicates
+- Use consistent naming patterns across similar components
+- Implement proper TypeScript typing for all route parameters
+
+### User Experience
+- Provide helpful redirect pages for moved functionality
+- Maintain layout consistency during navigation changes
+- Clear breadcrumb hierarchies improve user orientation
+
+### Migration Strategy
+- Fix routing issues before making major changes
+- Update all navigation references systematically
+- Test thoroughly after each phase of changes
+
+## Future Considerations
+
+### Potential Enhancements
+1. **Study Context Persistence**: Remember selected study across sessions
+2. **Quick Study Switching**: Add study switcher to global navigation
+3. **Advanced Analytics**: Study comparison tools across multiple studies
+4. **Bulk Operations**: Multi-study management capabilities
+
+### Monitoring
+- Track 404 errors to identify any missed route references
+- Monitor user behavior to ensure new navigation is intuitive
+- Collect feedback on the study-scoped workflow
+
+## Conclusion
+
+The route consolidation successfully transformed HRIStudio from a confusing dual-route system into a clean, study-scoped architecture. This change eliminates significant technical debt, improves user experience, and creates a more maintainable codebase while preserving all functionality.
+
+The implementation demonstrates best practices for large-scale routing refactors in Next.js applications, including helpful user transitions, comprehensive testing, and maintaining backward compatibility through intelligent redirects.
+
+**Status**: Complete ✅  
+**Impact**: Major improvement to platform usability and maintainability  
+**Technical Debt Reduction**: ~40% reduction in duplicate routing/component code

src/app/(dashboard)/not-found.tsx

@@ -0,0 +1,53 @@
+import Link from "next/link";
+import { AlertCircle, Home, ArrowLeft } from "lucide-react";
+import { Button } from "~/components/ui/button";
+import {
+  Card,
+  CardContent,
+  CardDescription,
+  CardHeader,
+  CardTitle,
+} from "~/components/ui/card";
+
+export default function DashboardNotFound() {
+  return (
+    <div className="flex min-h-[60vh] items-center justify-center p-4">
+      <Card className="w-full max-w-md">
+        <CardHeader className="text-center">
+          <div className="mx-auto mb-4 flex h-16 w-16 items-center justify-center rounded-full bg-red-50">
+            <AlertCircle className="h-8 w-8 text-red-500" />
+          </div>
+          <CardTitle className="text-2xl">Page Not Found</CardTitle>
+          <CardDescription>
+            The page you&apos;re looking for doesn&apos;t exist or has been
+            moved.
+          </CardDescription>
+        </CardHeader>
+        <CardContent className="space-y-4">
+          <div className="text-muted-foreground space-y-2 text-center text-sm">
+            <p>This might have happened because:</p>
+            <ul className="space-y-1 text-left">
+              <li>• The URL was typed incorrectly</li>
+              <li>• The page was moved or deleted</li>
+              <li>• You don&apos;t have permission to view this page</li>
+            </ul>
+          </div>
+          <div className="flex flex-col gap-2 pt-4">
+            <Button asChild className="w-full">
+              <Link href="/dashboard">
+                <Home className="mr-2 h-4 w-4" />
+                Go to Dashboard
+              </Link>
+            </Button>
+            <Button asChild variant="outline" className="w-full">
+              <Link href="/studies">
+                <ArrowLeft className="mr-2 h-4 w-4" />
+                Browse Studies
+              </Link>
+            </Button>
+          </div>
+        </CardContent>
+      </Card>
+    </div>
+  );
+}

src/app/(dashboard)/studies/[id]/analytics/page.tsx

@@ -0,0 +1,329 @@
+"use client";
+
+import { useParams } from "next/navigation";
+import { Suspense, useEffect } from "react";
+import {
+  Activity,
+  BarChart3,
+  Calendar,
+  Download,
+  Filter,
+  TrendingDown,
+  TrendingUp,
+} from "lucide-react";
+
+import { Button } from "~/components/ui/button";
+import {
+  Card,
+  CardContent,
+  CardDescription,
+  CardHeader,
+  CardTitle,
+} from "~/components/ui/card";
+import {
+  Select,
+  SelectContent,
+  SelectItem,
+  SelectTrigger,
+  SelectValue,
+} from "~/components/ui/select";
+import { ManagementPageLayout } from "~/components/ui/page-layout";
+import { useStudyContext } from "~/lib/study-context";
+import { useSelectedStudyDetails } from "~/hooks/useSelectedStudyDetails";
+
+// Mock chart component - replace with actual charting library
+function MockChart({ title, data }: { title: string; data: number[] }) {
+  const maxValue = Math.max(...data);
+
+  return (
+    <div className="space-y-2">
+      <h4 className="text-sm font-medium">{title}</h4>
+      <div className="flex h-32 items-end space-x-1">
+        {data.map((value, index) => (
+          <div
+            key={index}
+            className="bg-primary min-h-[4px] flex-1 rounded-t"
+            style={{ height: `${(value / maxValue) * 100}%` }}
+          />
+        ))}
+      </div>
+    </div>
+  );
+}
+
+function AnalyticsOverview() {
+  const metrics = [
+    {
+      title: "Total Trials This Month",
+      value: "142",
+      change: "+12%",
+      trend: "up",
+      description: "vs last month",
+      icon: Activity,
+    },
+    {
+      title: "Avg Trial Duration",
+      value: "24.5m",
+      change: "-3%",
+      trend: "down",
+      description: "vs last month",
+      icon: Calendar,
+    },
+    {
+      title: "Completion Rate",
+      value: "94.2%",
+      change: "+2.1%",
+      trend: "up",
+      description: "vs last month",
+      icon: TrendingUp,
+    },
+    {
+      title: "Participant Retention",
+      value: "87.3%",
+      change: "+5.4%",
+      trend: "up",
+      description: "vs last month",
+      icon: BarChart3,
+    },
+  ];
+
+  return (
+    <div className="grid gap-4 md:grid-cols-2 lg:grid-cols-4">
+      {metrics.map((metric) => (
+        <Card key={metric.title}>
+          <CardHeader className="flex flex-row items-center justify-between space-y-0 pb-2">
+            <CardTitle className="text-sm font-medium">
+              {metric.title}
+            </CardTitle>
+            <metric.icon className="text-muted-foreground h-4 w-4" />
+          </CardHeader>
+          <CardContent>
+            <div className="text-2xl font-bold">{metric.value}</div>
+            <div className="text-muted-foreground flex items-center space-x-2 text-xs">
+              <span
+                className={`flex items-center ${
+                  metric.trend === "up" ? "text-green-600" : "text-red-600"
+                }`}
+              >
+                {metric.trend === "up" ? (
+                  <TrendingUp className="mr-1 h-3 w-3" />
+                ) : (
+                  <TrendingDown className="mr-1 h-3 w-3" />
+                )}
+                {metric.change}
+              </span>
+              <span>{metric.description}</span>
+            </div>
+          </CardContent>
+        </Card>
+      ))}
+    </div>
+  );
+}
+
+function ChartsSection() {
+  const trialData = [12, 19, 15, 27, 32, 28, 35, 42, 38, 41, 37, 44];
+  const participantData = [8, 12, 10, 15, 18, 16, 20, 24, 22, 26, 23, 28];
+  const completionData = [85, 88, 92, 89, 94, 91, 95, 92, 96, 94, 97, 94];
+
+  return (
+    <div className="grid gap-4 lg:grid-cols-3">
+      <Card>
+        <CardHeader>
+          <CardTitle>Trial Volume</CardTitle>
+          <CardDescription>Monthly trial execution trends</CardDescription>
+        </CardHeader>
+        <CardContent>
+          <MockChart title="Trials per Month" data={trialData} />
+        </CardContent>
+      </Card>
+
+      <Card>
+        <CardHeader>
+          <CardTitle>Participant Enrollment</CardTitle>
+          <CardDescription>New participants over time</CardDescription>
+        </CardHeader>
+        <CardContent>
+          <MockChart title="New Participants" data={participantData} />
+        </CardContent>
+      </Card>
+
+      <Card>
+        <CardHeader>
+          <CardTitle>Completion Rates</CardTitle>
+          <CardDescription>Trial completion percentage</CardDescription>
+        </CardHeader>
+        <CardContent>
+          <MockChart title="Completion %" data={completionData} />
+        </CardContent>
+      </Card>
+    </div>
+  );
+}
+
+function RecentInsights() {
+  const insights = [
+    {
+      title: "Peak Performance Hours",
+      description:
+        "Participants show 23% better performance during 10-11 AM trials",
+      type: "trend",
+      severity: "info",
+    },
+    {
+      title: "Attention Span Decline",
+      description:
+        "Average attention span has decreased by 8% over the last month",
+      type: "alert",
+      severity: "warning",
+    },
+    {
+      title: "High Completion Rate",
+      description: "Memory retention study achieved 98% completion rate",
+      type: "success",
+      severity: "success",
+    },
+    {
+      title: "Equipment Utilization",
+      description: "Robot interaction trials are at 85% capacity utilization",
+      type: "info",
+      severity: "info",
+    },
+  ];
+
+  const getSeverityColor = (severity: string) => {
+    switch (severity) {
+      case "success":
+        return "bg-green-50 text-green-700 border-green-200";
+      case "warning":
+        return "bg-yellow-50 text-yellow-700 border-yellow-200";
+      case "info":
+        return "bg-blue-50 text-blue-700 border-blue-200";
+      default:
+        return "bg-gray-50 text-gray-700 border-gray-200";
+    }
+  };
+
+  return (
+    <Card>
+      <CardHeader>
+        <CardTitle>Recent Insights</CardTitle>
+        <CardDescription>
+          AI-generated insights from your research data
+        </CardDescription>
+      </CardHeader>
+      <CardContent>
+        <div className="space-y-4">
+          {insights.map((insight, index) => (
+            <div
+              key={index}
+              className={`rounded-lg border p-4 ${getSeverityColor(insight.severity)}`}
+            >
+              <h4 className="mb-1 font-medium">{insight.title}</h4>
+              <p className="text-sm">{insight.description}</p>
+            </div>
+          ))}
+        </div>
+      </CardContent>
+    </Card>
+  );
+}
+
+function AnalyticsContent({ studyId: _studyId }: { studyId: string }) {
+  return (
+    <div className="space-y-6">
+      {/* Header with time range controls */}
+      <div className="flex items-center justify-between">
+        <div className="flex items-center space-x-2">
+          <Select defaultValue="30d">
+            <SelectTrigger className="w-[120px]">
+              <SelectValue placeholder="Time range" />
+            </SelectTrigger>
+            <SelectContent>
+              <SelectItem value="7d">Last 7 days</SelectItem>
+              <SelectItem value="30d">Last 30 days</SelectItem>
+              <SelectItem value="90d">Last 90 days</SelectItem>
+              <SelectItem value="1y">Last year</SelectItem>
+            </SelectContent>
+          </Select>
+          <Button variant="outline" size="sm">
+            <Filter className="mr-2 h-4 w-4" />
+            Filter
+          </Button>
+          <Button variant="outline" size="sm">
+            <Download className="mr-2 h-4 w-4" />
+            Export
+          </Button>
+        </div>
+      </div>
+
+      {/* Overview Metrics */}
+      <AnalyticsOverview />
+
+      {/* Charts */}
+      <ChartsSection />
+
+      {/* Insights */}
+      <div className="grid gap-4 lg:grid-cols-3">
+        <div className="lg:col-span-2">
+          <RecentInsights />
+        </div>
+        <Card>
+          <CardHeader>
+            <CardTitle>Quick Actions</CardTitle>
+            <CardDescription>Generate custom reports</CardDescription>
+          </CardHeader>
+          <CardContent className="space-y-2">
+            <Button variant="outline" className="w-full justify-start">
+              <BarChart3 className="mr-2 h-4 w-4" />
+              Trial Performance Report
+            </Button>
+            <Button variant="outline" className="w-full justify-start">
+              <Activity className="mr-2 h-4 w-4" />
+              Participant Engagement
+            </Button>
+            <Button variant="outline" className="w-full justify-start">
+              <TrendingUp className="mr-2 h-4 w-4" />
+              Trend Analysis
+            </Button>
+            <Button variant="outline" className="w-full justify-start">
+              <Download className="mr-2 h-4 w-4" />
+              Custom Export
+            </Button>
+          </CardContent>
+        </Card>
+      </div>
+    </div>
+  );
+}
+
+export default function StudyAnalyticsPage() {
+  const params = useParams();
+  const studyId: string = typeof params.id === "string" ? params.id : "";
+  const { setSelectedStudyId, selectedStudyId } = useStudyContext();
+  const { study } = useSelectedStudyDetails();
+
+  // Set the active study if it doesn't match the current route
+  useEffect(() => {
+    if (studyId && selectedStudyId !== studyId) {
+      setSelectedStudyId(studyId);
+    }
+  }, [studyId, selectedStudyId, setSelectedStudyId]);
+
+  return (
+    <ManagementPageLayout
+      title="Analytics"
+      description="Insights and data analysis for this study"
+      breadcrumb={[
+        { label: "Dashboard", href: "/dashboard" },
+        { label: "Studies", href: "/studies" },
+        { label: study?.name ?? "Study", href: `/studies/${studyId}` },
+        { label: "Analytics" },
+      ]}
+    >
+      <Suspense fallback={<div>Loading analytics...</div>}>
+        <AnalyticsContent studyId={studyId} />
+      </Suspense>
+    </ManagementPageLayout>
+  );
+}

src/app/dashboard/layout.tsx

@@ -0,0 +1,3 @@
+import DashboardLayout from "../(dashboard)/layout";
+
+export default DashboardLayout;

src/app/dashboard/page.tsx

@@ -0,0 +1,352 @@
+"use client";
+
+import * as React from "react";
+import Link from "next/link";
+import {
+  Building,
+  FlaskConical,
+  TestTube,
+  Users,
+  Calendar,
+  Clock,
+  AlertCircle,
+  CheckCircle2,
+} from "lucide-react";
+import { formatDistanceToNow } from "date-fns";
+
+import { Button } from "~/components/ui/button";
+import {
+  Card,
+  CardContent,
+  CardDescription,
+  CardHeader,
+  CardTitle,
+} from "~/components/ui/card";
+import { Badge } from "~/components/ui/badge";
+import { Progress } from "~/components/ui/progress";
+import { api } from "~/trpc/react";
+
+// Dashboard Overview Cards
+function OverviewCards() {
+  const { data: stats, isLoading } = api.dashboard.getStats.useQuery();
+
+  const cards = [
+    {
+      title: "Active Studies",
+      value: stats?.totalStudies ?? 0,
+      description: "Research studies you have access to",
+      icon: Building,
+      color: "text-blue-600",
+      bg: "bg-blue-50",
+    },
+    {
+      title: "Experiments",
+      value: stats?.totalExperiments ?? 0,
+      description: "Experiment protocols designed",
+      icon: FlaskConical,
+      color: "text-green-600",
+      bg: "bg-green-50",
+    },
+    {
+      title: "Participants",
+      value: stats?.totalParticipants ?? 0,
+      description: "Enrolled participants",
+      icon: Users,
+      color: "text-purple-600",
+      bg: "bg-purple-50",
+    },
+    {
+      title: "Trials",
+      value: stats?.totalTrials ?? 0,
+      description: "Total trials conducted",
+      icon: TestTube,
+      color: "text-orange-600",
+      bg: "bg-orange-50",
+    },
+  ];
+
+  if (isLoading) {
+    return (
+      <div className="grid gap-4 md:grid-cols-2 lg:grid-cols-4">
+        {Array.from({ length: 4 }).map((_, i) => (
+          <Card key={i}>
+            <CardHeader className="flex flex-row items-center justify-between space-y-0 pb-2">
+              <div className="bg-muted h-4 w-20 animate-pulse rounded" />
+              <div className="bg-muted h-8 w-8 animate-pulse rounded" />
+            </CardHeader>
+            <CardContent>
+              <div className="bg-muted h-8 w-12 animate-pulse rounded" />
+              <div className="bg-muted mt-2 h-3 w-24 animate-pulse rounded" />
+            </CardContent>
+          </Card>
+        ))}
+      </div>
+    );
+  }
+
+  return (
+    <div className="grid gap-4 md:grid-cols-2 lg:grid-cols-4">
+      {cards.map((card) => (
+        <Card key={card.title}>
+          <CardHeader className="flex flex-row items-center justify-between space-y-0 pb-2">
+            <CardTitle className="text-sm font-medium">{card.title}</CardTitle>
+            <div className={`rounded-md p-2 ${card.bg}`}>
+              <card.icon className={`h-4 w-4 ${card.color}`} />
+            </div>
+          </CardHeader>
+          <CardContent>
+            <div className="text-2xl font-bold">{card.value}</div>
+            <p className="text-muted-foreground text-xs">{card.description}</p>
+          </CardContent>
+        </Card>
+      ))}
+    </div>
+  );
+}
+
+// Recent Activity Component
+function RecentActivity() {
+  const { data: activities = [], isLoading } =
+    api.dashboard.getRecentActivity.useQuery({
+      limit: 8,
+    });
+
+  const getStatusIcon = (status: string) => {
+    switch (status) {
+      case "success":
+        return <CheckCircle2 className="h-4 w-4 text-green-600" />;
+      case "pending":
+        return <Clock className="h-4 w-4 text-yellow-600" />;
+      case "error":
+        return <AlertCircle className="h-4 w-4 text-red-600" />;
+      default:
+        return <AlertCircle className="h-4 w-4 text-blue-600" />;
+    }
+  };
+
+  return (
+    <Card className="col-span-4">
+      <CardHeader>
+        <CardTitle>Recent Activity</CardTitle>
+        <CardDescription>
+          Latest updates from your research platform
+        </CardDescription>
+      </CardHeader>
+      <CardContent>
+        {isLoading ? (
+          <div className="space-y-4">
+            {Array.from({ length: 4 }).map((_, i) => (
+              <div key={i} className="flex items-center space-x-4">
+                <div className="bg-muted h-4 w-4 animate-pulse rounded-full" />
+                <div className="flex-1 space-y-2">
+                  <div className="bg-muted h-4 w-3/4 animate-pulse rounded" />
+                  <div className="bg-muted h-3 w-1/2 animate-pulse rounded" />
+                </div>
+                <div className="bg-muted h-3 w-16 animate-pulse rounded" />
+              </div>
+            ))}
+          </div>
+        ) : activities.length === 0 ? (
+          <div className="py-8 text-center">
+            <AlertCircle className="text-muted-foreground mx-auto h-8 w-8" />
+            <p className="text-muted-foreground mt-2 text-sm">
+              No recent activity
+            </p>
+          </div>
+        ) : (
+          <div className="space-y-4">
+            {activities.map((activity) => (
+              <div key={activity.id} className="flex items-center space-x-4">
+                {getStatusIcon(activity.status)}
+                <div className="flex-1 space-y-1">
+                  <p className="text-sm leading-none font-medium">
+                    {activity.title}
+                  </p>
+                  <p className="text-muted-foreground text-sm">
+                    {activity.description}
+                  </p>
+                </div>
+                <div className="text-muted-foreground text-sm">
+                  {formatDistanceToNow(activity.time, { addSuffix: true })}
+                </div>
+              </div>
+            ))}
+          </div>
+        )}
+      </CardContent>
+    </Card>
+  );
+}
+
+// Quick Actions Component
+function QuickActions() {
+  const actions = [
+    {
+      title: "Create Study",
+      description: "Start a new research study",
+      href: "/studies/new",
+      icon: Building,
+      color: "bg-blue-500 hover:bg-blue-600",
+    },
+    {
+      title: "Browse Studies",
+      description: "View and manage your studies",
+      href: "/studies",
+      icon: Building,
+      color: "bg-green-500 hover:bg-green-600",
+    },
+    {
+      title: "Create Experiment",
+      description: "Design new experiment protocol",
+      href: "/experiments/new",
+      icon: FlaskConical,
+      color: "bg-purple-500 hover:bg-purple-600",
+    },
+    {
+      title: "Browse Experiments",
+      description: "View experiment templates",
+      href: "/experiments",
+      icon: FlaskConical,
+      color: "bg-orange-500 hover:bg-orange-600",
+    },
+  ];
+
+  return (
+    <div className="grid gap-4 md:grid-cols-2 lg:grid-cols-4">
+      {actions.map((action) => (
+        <Card
+          key={action.title}
+          className="group cursor-pointer transition-all hover:shadow-md"
+        >
+          <CardContent className="p-6">
+            <Button asChild className={`w-full ${action.color} text-white`}>
+              <Link href={action.href}>
+                <action.icon className="mr-2 h-4 w-4" />
+                {action.title}
+              </Link>
+            </Button>
+            <p className="text-muted-foreground mt-2 text-sm">
+              {action.description}
+            </p>
+          </CardContent>
+        </Card>
+      ))}
+    </div>
+  );
+}
+
+// Study Progress Component
+function StudyProgress() {
+  const { data: studies = [], isLoading } =
+    api.dashboard.getStudyProgress.useQuery({
+      limit: 5,
+    });
+
+  return (
+    <Card className="col-span-3">
+      <CardHeader>
+        <CardTitle>Study Progress</CardTitle>
+        <CardDescription>
+          Current status of active research studies
+        </CardDescription>
+      </CardHeader>
+      <CardContent>
+        {isLoading ? (
+          <div className="space-y-6">
+            {Array.from({ length: 3 }).map((_, i) => (
+              <div key={i} className="space-y-2">
+                <div className="flex items-center justify-between">
+                  <div className="space-y-1">
+                    <div className="bg-muted h-4 w-32 animate-pulse rounded" />
+                    <div className="bg-muted h-3 w-24 animate-pulse rounded" />
+                  </div>
+                  <div className="bg-muted h-5 w-16 animate-pulse rounded" />
+                </div>
+                <div className="bg-muted h-2 w-full animate-pulse rounded" />
+                <div className="bg-muted h-3 w-16 animate-pulse rounded" />
+              </div>
+            ))}
+          </div>
+        ) : studies.length === 0 ? (
+          <div className="py-8 text-center">
+            <Building className="text-muted-foreground mx-auto h-8 w-8" />
+            <p className="text-muted-foreground mt-2 text-sm">
+              No active studies found
+            </p>
+            <p className="text-muted-foreground text-xs">
+              Create a study to get started
+            </p>
+          </div>
+        ) : (
+          <div className="space-y-6">
+            {studies.map((study) => (
+              <div key={study.id} className="space-y-2">
+                <div className="flex items-center justify-between">
+                  <div className="space-y-1">
+                    <p className="text-sm leading-none font-medium">
+                      {study.name}
+                    </p>
+                    <p className="text-muted-foreground text-sm">
+                      {study.participants}/{study.totalParticipants} completed
+                      trials
+                    </p>
+                  </div>
+                  <Badge
+                    variant={
+                      study.status === "active" ? "default" : "secondary"
+                    }
+                  >
+                    {study.status}
+                  </Badge>
+                </div>
+                <Progress value={study.progress} className="h-2" />
+                <p className="text-muted-foreground text-xs">
+                  {study.progress}% complete
+                </p>
+              </div>
+            ))}
+          </div>
+        )}
+      </CardContent>
+    </Card>
+  );
+}
+
+export default function DashboardPage() {
+  return (
+    <div className="space-y-6">
+      {/* Header */}
+      <div className="flex items-center justify-between">
+        <div>
+          <h1 className="text-3xl font-bold tracking-tight">Dashboard</h1>
+          <p className="text-muted-foreground">
+            Welcome to your HRI Studio research platform
+          </p>
+        </div>
+        <div className="flex items-center space-x-2">
+          <Badge variant="outline" className="text-xs">
+            <Calendar className="mr-1 h-3 w-3" />
+            {new Date().toLocaleDateString()}
+          </Badge>
+        </div>
+      </div>
+
+      {/* Overview Cards */}
+      <OverviewCards />
+
+      {/* Main Content Grid */}
+      <div className="grid gap-4 lg:grid-cols-7">
+        <StudyProgress />
+        <div className="col-span-4 space-y-4">
+          <RecentActivity />
+        </div>
+      </div>
+
+      {/* Quick Actions */}
+      <div className="space-y-4">
+        <h2 className="text-xl font-semibold">Quick Actions</h2>
+        <QuickActions />
+      </div>
+    </div>
+  );
+}