diff --git a/Auxiliary Files/webapp database model.drawio.png b/Auxiliary Files/webapp database model.drawio.png
new file mode 100644
index 00000000..e6cf02f8
Binary files /dev/null and b/Auxiliary Files/webapp database model.drawio.png differ
diff --git a/Design/Architecture.md b/Design/Architecture.md
new file mode 100644
index 00000000..f4c16f97
--- /dev/null
+++ b/Design/Architecture.md
@@ -0,0 +1,16 @@
+# Architecture
+## No updates were made prior to Update Design Items Assignment (10/26/23)
+
+Existing Peak Mind Structure:
+
+
+
+VR Data Visualization System:
+
+
+
+AWS API: Biometric sample data will be retrieved from Peak Mind’s AWS database.
+
+Unity data vis app: The data visualization app will obtain sample biometric data and convert it into VR modules.
+
+Web app dashboard iFrame: The visualizations will be sent to the web app dashboard and displayed via iFrame.
diff --git a/Design/BusinessRequirements.md b/Design/BusinessRequirements.md
new file mode 100644
index 00000000..b69fcfce
--- /dev/null
+++ b/Design/BusinessRequirements.md
@@ -0,0 +1,7 @@
+# Business Requirements
+## No updates were made prior to Update Design Items Assignment (10/26/23)
+
+* BR1. Reduce stress in the workforce
+ * This is Peak Mind’s primary business goal. The company was founded after Dr. Mckoy noticed a problem in workplace turnover and happiness. Peak Mind seeks to address this issue through their core technologies. The company does this using VR and biometric technologies to measure, remediate, and validate stress.
+* BR2. Validate that stress reduction techniques are effective
+ * Careful analysis of recorded data will allow Peak Mind to determine the effectiveness of stress reduction techniques described in BR5. By comparing biometrics before, during, and after stress reduction stimuli, Peak Mind will be able to look for statistically significant decreases in stress biometrics. Thus, the mathematical analysis of recorded data will validate the proposed effectiveness of the VR treatments.
diff --git a/Design/DomainModel.md b/Design/DomainModel.md
new file mode 100644
index 00000000..c47cce99
--- /dev/null
+++ b/Design/DomainModel.md
@@ -0,0 +1,21 @@
+# Domain Model
+## No updates were made prior to Update Design Items Assignment (10/26/23)
+
+
+
+Note that many of these components are likely already specified by the existing software. Our design will be adapted once we have access to the code.
+
+Recorder: The software responsible for connecting to and reading sensor data from the VRDevice.
+
+VRDevice: The VR headset itself, accessed via the applicable SDK.
+MomentaryData: A generic representation of a sensor reading at a single moment in time. The data it contains may be a frame of video, the current heart rate, or whatever else is being collected.
+
+WebUI: The frontend through which users and analysts may log in to access session data.
+
+Database: The storage method for collected session data. The database is hosted on AWS and thus is accessed over the network.
+
+Session: An aggregation of all the data collected over a single VR session. This class is associated with a six-digit access code, which is required for access by users. Each session is uniquely identified by its start time; this behavior may be adjusted in the case of collisions.
+
+User: A person who may log in to the WebUI in order to access session visualizations. They differ from analysts in that they must have the appropriate access code for any session they wish to access.
+
+Analyst: A person who may log in to the WebUI in order to access visualizations. They may access any session without the need for its access code, and may also access the session's raw data in addition to visualizations.
diff --git a/Design/Prototype.md b/Design/Prototype.md
new file mode 100644
index 00000000..6904e8d0
--- /dev/null
+++ b/Design/Prototype.md
@@ -0,0 +1,8 @@
+# Prototype
+## No updates were made prior to Update Design Items Assignment (10/26/23)
+
+Per discussion with our client, we are reusing their existing Figma prototype for the purposes of this project.
+
+[This link will lead to the prototype on Figma.](https://www.figma.com/file/1fNpgf7UKVJZiFxw7GPrn3/Dashboard-new-UIUX?type=design&node-id=49-874&mode=design&t=1KuLIpnsQsriXt3J-0)
+
+[Here is a link to a video on Youtube walking through the prototype.](https://youtu.be/mkMkjJ9EuP8)
diff --git a/Design/README.md b/Design/README.md
index 2a9d27f9..fad900c0 100644
--- a/Design/README.md
+++ b/Design/README.md
@@ -1,3 +1,4 @@
# Design
-Design documents here... Explain each folder/file in this readme file.
\ No newline at end of file
+## Existing documents
+Design documents from previous project located at [https://github.com/pfled/peak-visualization/tree/main] are still considered valid for the current work.
\ No newline at end of file
diff --git a/Design/Requirements.md b/Design/Requirements.md
new file mode 100644
index 00000000..e311abb1
--- /dev/null
+++ b/Design/Requirements.md
@@ -0,0 +1,11 @@
+# Functional Requirements
+* FR1. (Corresponds to BR2) (Priority: HIGH) When a user is using the VR device, the video feed from the device's face camera will be recorded.
+* FR2. (Corresponds to BR2) (Priority: HIGH) All recorded data will include timestamps so as to synchronize the individual feeds with each other for future playback.
+* FR3. (Corresponds to BR1) (Priority: LOW) A user may log in with a six-digit code to view a visualization of their collected data.
+* FR4. (Corresponds to BR2) (Priority: MEDIUM) Peak Mind analysts may access all collected data and associated visualizations.
+# Non-Functional Requirements
+* NR1. (Corresponds to BR1, BR2) (Priority: HIGH) The software will connect to the HP Omnicept VR device.
+* NR2. (Corresponds to BR1, BR2) (Priority: MEDIUM) The new software will extend the functionality of the existing software.
+* NR3. (Corresponds to BR2) (Priority: LOW) Recorded data will be stored via an AWS instance.
+* NR4. (Corresponds to BR1, BR2) (Priority: HIGH) Dr. Mckoy must have full access to and control over everything in the AWS account.
+* NR5. (Corresponds to BR1. BR2) (Priority: LOW) All collection, storage, and access of user data must comply with applicable regulations.
\ No newline at end of file
diff --git a/Design/RequirementsUpdated.md b/Design/RequirementsUpdated.md
new file mode 100644
index 00000000..b6d41877
--- /dev/null
+++ b/Design/RequirementsUpdated.md
@@ -0,0 +1,13 @@
+# Functional Requirements
+* FR1. (Corresponds to BR2) (Priority: HIGH) When a user is using the VR device, the video feed from the device's facial cameras will be recorded.
+* FR2. (Corresponds to BR2) (Priority: HIGH) All recorded data will include timestamps so as to synchronize the individual feeds with each other for future playback.
+* FR3. (Corresponds to BR1) (Priority: LOW) A user may log in with a six-digit code to view a visualization of their collected data.
+* FR4. (Corresponds to BR2) (Priority: MEDIUM) Peak Mind analysts may access all collected data and associated visualizations.
+* FR5. (Corresponds to BR2) (Priority: HIGH) Activate the mouth facial biometric camera.
+* FR6. (Corresponds to BR1) (Priority: MEDIUM) Display Peak Mind's stress reducing stimuli within the VR headset.
+# Non-Functional Requirements
+* NR1. (Corresponds to BR1, BR2) (Priority: HIGH) The software will connect to the HP Omnicept VR device.
+* NR2. (Corresponds to BR1, BR2) (Priority: MEDIUM) The new software will extend the functionality of the existing software.
+* NR3. (Corresponds to BR2) (Priority: LOW) Recorded data will be stored via an AWS instance.
+* NR4. (Corresponds to BR1, BR2) (Priority: HIGH) Dr. Mckoy must have full access to and control over everything in the AWS account.
+* NR5. (Corresponds to BR1. BR2) (Priority: LOW) All collection, storage, and access of user data must comply with applicable regulations.
diff --git a/Design/TechStack.md b/Design/TechStack.md
new file mode 100644
index 00000000..c66ec53e
--- /dev/null
+++ b/Design/TechStack.md
@@ -0,0 +1,20 @@
+# Tech Stack
+## No updates were made prior to Update Design Items Assignment (10/26/23)
+
+Note: We plan to carry over most, if not all, of the previous project's tech stack.
+## Web App
+* React (Link to https://reactjs.org)
+ * Peak Mind utilizes React for the portion of their web app that we will be working with.
+* JavaScript (Link to https://www.javascript.com)
+ * JavaScript was previously utilized by the last group of students who worked on the Web App because React is a JavaScript framework.
+* AWS (Link to https://aws.amazon.com)
+ * Peak Mind’s database operates as a cloud native system in AWS.
+* Docker (Link to https://www.docker.com)
+ * Docker will ensure that our code can run on any system. Our team is using a variety of machines with varying operating systems. A docker container will allow us to move the application into the AWS production environment.
+## VR Visualization
+* Unity (Link to https://unity.com)
+ * Unity was selected by the previous team for the purpose of connecting to the VR headset. The HP Omnicept SDK is compatible with Unity.
+* HP Omnicept SDK (https://developers.hp.com/omnicept/docs)
+ * Peak Mind uses HP Omnicept headsets, so the HP Omnicept SDK will be necessary to generate the visualization of obtained biometric data obtained via the headset.
+* AWS (https://aws.amazon.com)
+ * AWS will be necessary to reach Peak Mind’s biometric database and utilize sample data for the purpose of visualization. AWS is a client specified requirement.
diff --git a/Design/UseCases.md b/Design/UseCases.md
new file mode 100644
index 00000000..6b2a355f
--- /dev/null
+++ b/Design/UseCases.md
@@ -0,0 +1,21 @@
+# Use Cases
+* UC1. (Corresponds to BR1, BR2) Reduce employee stress by administering stress reducing stimuli
+ * We aim to reduce employee stress via the administration of stress reducing stimuli. This stimuli is most effective in VR format, thus employees of high stress demographics will utilize VR headsets to receive their stress reduction stimuli. The intended result is that employees will experience reduced stress during and after exposure to VR stress reduction stimuli.
+ * High Stress Employees
+ * Program Flow:
+ * Users access web app to request help with stress
+ * Backend evaluates user data to select appropriate response
+ * Response is provided via web app/VR device
+* UC2. (Corresponds to BR2) Access visualized employees stress biometric data for analysis
+ * Data analysts will want to be able to access both real time and recorded visualizations of employee stress biometric data. A live graph will be present, along with a recording of said graph as it evolves. A final chart will demonstrate how the graph changed over the duration of treatment/exposure.
+ * Data Analysts
+ * Program Flow:
+ * Participant data is collected via VR headset and stored in AWS backend
+ * Analysts request data via web app
+ * Data is retrieved from AWS backend, visualized, and displayed
+* UC3. (Corresponds to BR1, BR2) Identify most common workplace stressors
+ * The cumulative data collected and utilized by data analysts will allow the owner to determine the most common workplace stressors in each workplace that is analyzed. Recorded historic biometric data will play a key role in this identification process. Pattern analysis will certainly be necessary to accurately convey biometric data into real world, explainable stressors.
+ * Data Analysts
+ * Program Flow:
+ * Biometric data is collected from users via VR headset and stored in AWS backend
+ * Analysts evaluate data to identify common stressors
\ No newline at end of file
diff --git a/Design/UseCasesUpdated.md b/Design/UseCasesUpdated.md
new file mode 100644
index 00000000..19f77da8
--- /dev/null
+++ b/Design/UseCasesUpdated.md
@@ -0,0 +1,21 @@
+# Use Cases
+* UC1. (Corresponds to BR1, BR2) Detect biometric stressors through facial scanning and administer stress reducing stimuli
+ * We aim to reduce employee stress via the administration of stress reducing stimuli. This stimuli is most effective in VR format, thus employees of high stress demographics will utilize VR headsets to receive their stress reduction stimuli. The intended result is that employees will experience reduced stress during and after exposure to VR stress reduction stimuli.
+ * High Stress Employees
+ * Program Flow:
+ * Users access web app to request help with stress
+ * Backend evaluates user data to select appropriate response
+ * Response is provided via web app/VR device
+* UC2. (Corresponds to BR2) Access visualized employees stress biometric data for analysis
+ * Data Scientists will want to be able to access both real time and recorded visualizations of employee stress biometric data. A live graph will be present, along with a recording of said graph as it evolves. A final chart will demonstrate how the graph changed over the duration of treatment/exposure.
+ * Data Scientists
+ * Program Flow:
+ * Participant data is collected via VR headset and stored in AWS backend
+ * Analysts request data via web app
+ * Data is retrieved from AWS backend, visualized, and displayed
+* UC3. (Corresponds to BR1, BR2) Identify most common workplace stressors
+ * The cumulative data collected and utilized by data Scientists will allow the owner to determine the most common workplace stressors in each workplace that is analyzed. Recorded historic biometric data will play a key role in this identification process. Pattern analysis will certainly be necessary to accurately convey biometric data into real world, explainable stressors.
+ * Data Scientists
+ * Program Flow:
+ * Biometric data is collected from users via VR headset and stored in AWS backend
+ * Analysts evaluate data to identify common stressors
diff --git a/Design/image1.png b/Design/image1.png
new file mode 100644
index 00000000..8c1a02e1
Binary files /dev/null and b/Design/image1.png differ
diff --git a/Design/image2.png b/Design/image2.png
new file mode 100644
index 00000000..1a6f528e
Binary files /dev/null and b/Design/image2.png differ
diff --git a/Design/image3.png b/Design/image3.png
new file mode 100644
index 00000000..b03b4089
Binary files /dev/null and b/Design/image3.png differ
diff --git a/Discovery/Minutes.md b/Discovery/Minutes.md
new file mode 100644
index 00000000..0d62d78a
--- /dev/null
+++ b/Discovery/Minutes.md
@@ -0,0 +1,41 @@
+# Client Meeting on 10/2/2023
+## Meeting Start Time
+**2023/10/02/17:00**
+## Meeting End Time
+**2023/10/02/18:00**
+## Location/Medium
+Zoom
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan, Alicia
+## Minute Recorder
+Beethoven Meginnis
+## Topics Discussed
+We went over basic introductions. We discussed the basic tech stack. Set up zoom meeting for 5pm Wednesday 10/11.
+Will need a new AWS account and add Alicia in. (Give permissions to Alicia for everything we build)
+Peak Mind intends to lower stress in the workforce. Stress is the opposite of homeostasis. Peak intends to discover 150 of the most common workplace stressors and teach adults how to get out of stress and back into homeostasis. These 150 steps are stored in software. Intend to educate people on what workplace stressors look like as well as measure biometrics of stress. Measure, remediate, and validate.
+The HP headset has a face camera to do face computing. Look at face camera in conjunction with pupil dilation to tell us if we’re excited or in fear.
+***Alicia, requested that we email her to tell us about the dead code base repositories.
+The HP headset will require some permissions and plugins to make the camera work.
+***Eventually, schedule a meeting to physically test the headset.
+Tech Stack:
+Python3.8 Backend, Pipenv, PostgreSQL Database in AWS, JavaScript, TypeScript, HTML, CSS, Mako, Makefile, React Front End, and potentially Unity
+This product will be used on phones on computers. There is a backend and a frontend.
+Our primary objective is to get the face detection working in the existing software.
+The second objective is to get the web app working in a more complete manner. Deployed.
+Primarily, we just need to get the HP headset camera working.
+First Iteration:
+- Get Camera working (Big one for the first iteration)
+Second Iteration:
+- View data on frontend
+Third Iteration:
+- Visualize how we are replaying the data. We must be able to replay the camera. (Live video the whole time)
+Eventually get help from data science students to make mathematical equations to measure the difference between smiles and frowns.
+For design documents, replicate what is existing in the GitHub. Can use what we have.
+Can HP camera expert meet with us? Worked at HP Labs.
+This software aims to address the gap between doctor visits and therapy visits. Most Americans only visit their doctors on average for 30 minutes per year.
+SaaS – Software as a Service
+We use six digit codes when the user logs in for security. Only on the backend, do we see the true data.
+Virtual Reality Therapeutics are found to be 9 times more effective than just reading information. Cuts out all external stimuli.
+The peak mind website is joinpeakmind.com.
+## Things Clarified
+We established a follow up meeting for design documentation with our client on Wednesday (10/12) at 5:00pm. We also need to email her regarding the dead code base repositories to gain access to updated/migrated code bases. We need to send an of approximate dates for check in meetings and iterations.
\ No newline at end of file
diff --git a/Discovery/README.md b/Discovery/README.md
index cde548fc..9c3a56c6 100644
--- a/Discovery/README.md
+++ b/Discovery/README.md
@@ -1,3 +1,13 @@
# Discovery
-Discovery documents here. Explain each folder/file in this readme file.
\ No newline at end of file
+## Minutes.md
+Raw meeting minutes. Extensive meeting notes included, including business details, product details, and specifics for iterations.
+
+## Screenshot.png
+Screenshot from meeting on Zoom.
+
+## Participants
+Beethoven, Peter, Ethan, Tommy, Ryan, Alicia (Client)
+
+## Note:
+Drawings were ommited due to their presence in https://github.com/pfled/peak-visualization/tree/main. The client has instructed us to utilize existing design documentation in order to maintain consistency from previous groups.
diff --git a/Discovery/Screenshot.png b/Discovery/Screenshot.png
new file mode 100644
index 00000000..1af2da96
Binary files /dev/null and b/Discovery/Screenshot.png differ
diff --git a/Documentation/Deployment.md b/Documentation/Deployment.md
new file mode 100644
index 00000000..baba74ba
--- /dev/null
+++ b/Documentation/Deployment.md
@@ -0,0 +1,42 @@
+Note: As of 2023-11-11, this document has not been modified from its previous form.
+
+# Unity Application
+
+1. From the Unity editor with the project open. Click **File** in the top left of the editor window then select **Build Settings...**
+2. In the build setting window ensure that the `Scenes in build` table order is **Menu**, followed by **PeakVisualizationDashboard**, and finally **DataSave**.
+
+
+
+3. Press the build button. This is will open a prompt to choose where the build will be saved to. Go into the **Build** folder of the Unity project (this folder may not exist if you haven't run any builds before). While inside the **Build** folder create a new folder with whatever name you find most useful.
+
+
+
+
+
+4. Once the build is finished It will open the folder that contains all of the build products. The **PeakVisualization** application will be the main executable for the application.
+
+
+
+# Web Application
+
+## Frontend
+
+- To build the web application, open terminal at the project directory.
+
+- Then, run `npm run build` to create a build folder within the main directory.
+
+
+
+- Upload the build folder to a hosting service.
+
+## Backend
+
+- The backend is ready to run in a web server by running the shell script in the `bin/` folder: `bin/run.sh`.
+
+- In the environment you will have to set the environment variable `ENV` variable to `production`. Currently there is no production configuration so you will have to create an appropriate one in the `backend/api/config.py` file because it currently only has a configuration for development and testing.
+
+- The api is setup to run on the popular Python webserver flavor `Gunicorn`. so if that is not your preference for production you'll have to create a diffent setup for the api.
+
+- You can just take the code in the `backend` directory and run the setup shell script on a web server running Gunicorn or in a container and put on a cloud hosting service. To route traffic you will likely need some sort of load balancer to route http or https traffick to port 8080 (or the port you configured) on the web server.
+
+- When running the backend application on a webserver for the first time you will need to create the list of admins for the Peak Mind on the webserver it self. A custom Flask cli script was added to the backend so that admins can be created by running `flask create-admin --username --password`. If you are running the backend in a container service you will need to create a script to create these users otherwise you can connect to the web server via ssh to run this command whenever an Admin needs to be added.
\ No newline at end of file
diff --git a/Documentation/Development.md b/Documentation/Development.md
new file mode 100644
index 00000000..f7c80f24
--- /dev/null
+++ b/Documentation/Development.md
@@ -0,0 +1,217 @@
+# Development
+
+
+## Requirements for setup
+---
+
+- Our system requires [Unity](https://unity3d.com/get-unity/download) and the [HP Omnicept Developer SDK](https://developers.hp.com/omnicept/downloads). In order to download the HP Omnicept Developer SDK, first you must be a part of an organization with permission to access the SDK. You can create a organization within HP's developer portal [here](https://omnicept-console.hpbp.io/xr) once you do you can register an application as shown below.
+
+- For Unity, any up-to-date operating system is compatible including Windows 7 SP1+, 8, 10, 64-bit versions only; Mac OS X 10.12+; Ubuntu 16.04, 18.04, and CentOS 7.
+HP Omnicept SDK is only compatible with Windows and requires a workaround for other operating systems.
+
+- Unity Editor Version 2021.3.11f1 is required to open the project. Unity allows for any IDE to be used for scripting in C#; Visual Studio is recommended for Mac.
+
+## Downloading and setting up the SDK
+---
+
+- When on this [page](https://developers.hp.com/omnicept/downloads) click the button marked below to download the SDK
+
+
+
+- Then go find the executable that was downloaded and run it
+
+
+
+ - After going through the process of verification, the SDK can be accessed and the [documentation](https://developers.hp.com/omnicept/docs) can be followed for installation.
+
+ - Go through the setup up wizard and accept the terms of service. When you get the point where it asks you what to install keep all options except for the Unreal Engine plugin
+
+ 
+
+ - Then Finally click install
+
+ ## Setting up the project locally
+ ---
+
+The project follows Unity’s default folder structure: Assets, Packages, and ProjectSettings. A .gitignore and README.md are included at the root for version control and presentation. Within the Assets folder are files and folders for the HP Omnisept SDK called Glia.
+
+- To open this project locally, pull from this [repo](https://github.com/pfled/peak-vis-unity), open Unity Hub, then go to Open > Add project from disk. Then, select the folder of the cloned project.
+
+
+
+- The HP SDK assets for Unity Should be in the project already so to add your credentials there will be a tab in the Unity editor labeled HP Omnicept click that then click configure and a new window will pop up where you can add you Client ID and Access key from this [page](https://omnicept-console.hpbp.io/xr/application)
+
+
+
+]
+
+- In order to run the project, click the play button at the top of the Unity Editor pane. While playing, the HP SDK will create a separate pop-up that can be used to simulate user input such as a change in eye gaze or heart rate.
+
+
+
+- While you are running the application you can use the HP Omnicept Simulator that came with the SDK to send data to the application without needing a headset. The application can be found by searching in the Windows start menu. To actually begin to send information you need to hit "Send" or "Repeat" in the bottom left corner of the simulator
+
+
+
+- The following information regarding deployment is presumably correct, but not confirmed via testing at this point in time (10/26/23).
+
+- In order to actually save data to an AWS bucket you will have to add the base URL of the ApiGateway API created by running CDK deploy as explain in the [Deployment Documentation](./Deployment.md). However, this is not required for any kind of unit testing or changes that need to be made for any other part of the project only if you need to actually test the upload.
+
+
+
+- Running unit tests in Unity is done through the Unity Test Runner plugin. IMPORTANT - the HP provided prefab for the Omnicept SDK has caused frequent Unity crashes when running unit tests in `play mode` after the tests have ran, so it is recommended that you disable the HPGlia prefab in the scene before you run the unit tests.
+
+
+
+
+
+## Repicating via Docker
+---
+
+### Requirements
+
+- This project can be viewed in any IDE; Visual Studio Code is recommended.
+
+- Make you sure you have the correct version of [Docker Desktop](https://www.docker.com/products/docker-desktop/) installed.
+
+- Python 3.11 or higher is required for the backend
+
+- To open this project locally, pull from this [repo](https://github.com/pfled/peak-vis-webapp).
+
+- If you don't have make you can run the command listed in the `Makefile` which is `coverage run -m pytest && coverage report -m`.
+- If you want to run the unit tests without code coverage you can just run `pytest`.
+
+### Running the project
+- Open the project then open a terminal at the directory. You can run the project by running `docker compose up`. This will create a Docker container that has an image for a MySQL database, Backend, and Frontend When the container is running the output will look something like this. If you recieve and error about a missing .env file, you can create a blank .env file to temporarily relieve this issue. See below for the contents of the .env file.
+
+
+- The Frontend will run on port 3000, the Backend will run on port 8080, and the MySQL database will run on port 3306.
+ - To connect to the data do so through a socket connection with the username `peak-vis` and the password `dev`.
+ - If you recieve an error regarding port 3306, attempt to end task MySQL.exe in Task Manager, restart, and try again.
+
+- You can stop the container by pressing `Control + C` in the terminal instance where the compose up command was ran. Or by stopping it in the Docker Desktop application.
+ - If you are having issues with caching older versions of the code when restarting the Docker container after making changes you can run the command `docker compose up --build --force-recreate`. This should rebuild the container and ignore all caches in Docker when the container starts.
+
+### Frontend
+
+The web app follows React folder structure standards. There is a public folder, a src folder containing components and assets, and files necessary for package management and git tracking. The components folder contains JavaScript files that create different components throughout the application. This is a feature of React that makes frontend code modular and repeatable.
+
+- To run unit tests use `npm run test` in the root directory of the project.
+
+- You can view the fronte in your browser by connecting to http://localhost:3000.
+
+### Backend
+
+The api is built using Flask Python. To install all of the dependencies you can run `make install-dev` if you have and use `Make` or you could run the command in the make file: `pip install -r requirements/common.txt -r requirements/develop.txt` (you can replace `pip` with `pip3` if that is that Python package manager you prefer).
+
+If you recieve an error regarding building the wheels of MySQL Client, attempt to install [MariaDB Connector](https://mariadb.com/downloads/connectors/), product C Connector and latest version. After installing, copy bin, lib, and include folders of the install to a new folder that you will make called mariadb-connector in the root level of the C: Drive.
+
+The database can be initialized by running the commands `flask db migrate` then `flask db upgrade` in the command line in the Backend folder which use the `flask-migrate` package to automatically create the database schema defined by `Models` in the api code.
+
+The file structure for the project is as follows:
+```
+backend
+* api
+│ * __init__.py
+│ * config.py
+│ │
+│ * controllers
+│ │
+│ * models
+│ │
+│ * blueprints
+│ │
+│ └── utils
+│
+* requirements
+* bin (used for running api in web server)
+* migrations (auto generated)
+* tests
+* wgsi.py (used for running api in web server)
+└── setup.cfg (settings for flake8 linting)
+```
+ The `config.py` file contains the code for the main api and Flask settings and the `__init__.py` file in the `api` folder sets up the application. `controllers` is the folder that container the functional code for most of the api endpoints (routes). `utils` contains additional functional code for additional shared behaviour that don't belong in a single controller like checking if JWT tokens are blacklisted. `models` contain data classes that represent tables within the database it is also necessary to create database migrations. `blueprints` contain the files that define all of the endpoints (routes) in a blueprint which is a Flask construct.
+
+ To run the backend api completely you will need to add a `.env` file to the `backend` directory with these variables
+ ```
+DB_CONNECTION=
+DB_USERNAME=peak-vis
+DB_PASSWORD=dev
+DB_HOST=127.0.0.1
+DB_NAME=peak-visualization
+SECRET_KEY=
+S3_BUCKET_NAME=
+AWS_ACCESS_KEY_ID=
+AWS_SECRET_ACCESS_KEY=
+ ```
+
+The `S3_BUCKET_NAME`, `AWS_ACCESS_KEY_ID`, and `AWS_SECRET_ACCESS_KEY` should all be created and found on your AWS account. `DB_CONNECTION` is the database flavor that you will be using, currently we are using MySQL but you could use whatever other SQL flavor like `PostgreSQL`. Most of the `DB` variables are also set in the `docker-compose.yml` file when defining the database image.
+
+### Note
+
+When you first start after you run the docker compose project you will need to create an admin user if you want to test admin functionality on the frontend and create new users. To do so you will need to run a custom Flask command `flask creat-admin --email {your testing email} --password {development password}`
+
+## Linting
+---
+
+### Frontend
+- The frontend is setup with ESLint/Prettier
+- To run the code formatter i.e. Prettier type the command `npm format` in the root directory and this will run `prettier --write` on the entire project.
+- There are two main commands for ESLint `npm lint` which will just run the basic ESLint command and `npm lint:fix` which will run some automatted fixes.
+
+### Backend
+- The Backend uses Flake8 for linting
+- There are a couple ways to run the linter depending on preference
+ - If you have `Make` can run the command `make lint` the Flake8 command
+ - If you do not use `Make` you can just run the command in the file which is `flake8 api --count --show-source --statistics`
+ - This will lint only the `api` folder becasue it contains the main code for the api. If you want strictly enforce the linting rules on the entire backend directory you can just run `flake8` in the backend directory.
+
+### Unity Dashboard
+- The Unity dashboard implements Stylecop for formatting rules and SonarLint for linting.
+ - Both are implemented as NuGet packages that run in Visual Studio 2022.
+ - Neither implement auto-fix with a single command, but errors will be caught as they are typed and VS will provide warnings.
+ - Specific rules can be configured in the .editorconfig file.
+
+
+## Third party dependencies
+---
+
+### Frontend
+
+* react-pdf
+* rechars
+* eslint
+* html2canvas
+* isomorphic-fetch
+* jspdf
+* moment
+* prettier
+* react-dom
+* react-router-dom
+* react-router
+
+### Backend
+
+Production and dev
+
+* Flask
+* Gunicorn
+* Flask-Migrate
+* Flask-SQLAlchemy
+* PyJWT
+* flask-jwt-extended
+* mysqlclient
+* cmake
+* flask-bcrypt
+* boto3
+* JSONSchema
+* flask-cors
+
+Dev only
+
+* pytest
+* coverage
+* flake8
+* python-dotenv
+* moto
+* pytest-dotenv
diff --git a/Documentation/User.md b/Documentation/User.md
new file mode 100644
index 00000000..d6c1cb80
--- /dev/null
+++ b/Documentation/User.md
@@ -0,0 +1,138 @@
+# Unity application
+
+## Note for running the application the first time
+
+---
+
+By default users have to approve any application requesting data from the HP Omnicept for data collection. Normally a toast message will appear on Windows asking for approval, but if it doesn't or you have toast messages turned off you can open the **HP Omnicept Tray App** and approve the application as shown below.
+
+
+
+## Features
+
+---
+
+The primary use for this application is to display the data being collected from the HP Omnicept sensors while using the headset.
+
+### Eye tracking and pupilometry
+
+- On the side of the window there are two panels to display the data for the eye tracking and pupilometry sensors.
+- The top window will display the pupil dialation of each eye in millimeters and through a dot in that will change it's size depending on the user's dialation.
+- The bottom panel will display the combined gaze (roughly where a user is looking) in the form of a three-dimensional coordinate.
+
+
+
+### Heart Rate
+
+- In the center of the window is the smallest panel that displays the heart rate of the user (beats per minute).
+- The heart in the center will also pulse and change color depending on the user's heart rate.
+- If the user's heart rate is less than 75 the heart will pulse slow with a light blue color. If between 76 and 135, the heart will pulse a bit faster with a yellow color. If between 136 and 175, the heart will beat faster and with a light red color. Finally, if the user's heart rate is above 176, the heart will pulse faster than before and with a dark red color.
+
+
+
+
+### Cognitive load
+
+- On the right of window there is a panel that displays the cognitive load of a user in a range from 0.0 to 1.0.
+- The circle around the load number is a bar that will fill and change color depending on what the user's congitive load is.
+- If the user's cognitive load is less than 0.40, the bar would fill to the load with a light blue color. If the load is between 0.41 and 0.66, the bar would fill to the load with a yellow color. If the user's load is between 0.67 and 0.75 the bar would fill with a light red color. Finally, if the user's cognitive load is greater than 0.76, the bar would fill to the load point with a dark red color.
+- Cognitive load is a scientific tearm for a measurement of mental effort required to perform a task. Here is a [link](https://www.youtube.com/watch?v=2Sk2_4U58yg) to a video from HP explaining cognitive load in more detail.
+
+
+
+### Ending a session
+
+### Saving Data
+
+- After ending the session, the application will display options to add a note to the session, **Upload Session Data**, and **Save Session Data to Disk**.
+- Notes may be added by typing text into the provided text field and clicking the **Add Note** button.
+- When you press the **Save Session Data to Disk** button the user's data will ben saved to a folder on the local device. After the data has been saved, the file location will be displayed and a button will appear to automatically copy the location to the clipboard.
+- When you press the **Upload Session Data** button the user's data will then be uploaded to an AWS S3 bucket that stores the data by UserID and by timestamp of when uploaded.
+
+
+
+#### Mouth camera recording
+
+- Video from the integrated mouth camera is recorded automatically when a session is started and stopped when the session is ended. No preview of the collected video is displayed.
+- Recordings are saved alongside their associated session data on the local device. Note that recordings are saved locally _even if the *Save Session Data to Disk* button is not pressed!_
+- As of the time of writing, video data is not uploaded to any form of cloud storage, even if the **Upload Session Data** button is pressed.
+
+
+# Web application
+
+## Login
+
+Users can access their datasets by entering the email and password they created during registration.
+
+
+
+To get to registration click the link under the "LOGIN" button and create an account using your email on this page.
+
+
+
+## Features
+
+---
+
+### Select Dataset
+
+- The Simulation Results will appear on your dashboard. You can select which simulation's dataset to view.
+
+
+
+
+
+### Chart Details
+
+- You can see the value of specific points on the chart by hovering over them.
+
+
+
+### Filter Charts
+
+- You can filter which charts they want to view by clicking the pill toggles.
+
+
+
+
+
+### Add Dataset Notes
+
+- To add a note to a session dataset, click on any of the charts. A window will appear with the data and timestamp values automatically filled in, and more space to add a note.
+
+
+
+### View Dataset Notes
+- To view all saved notes for a given dataset, click "View Session Notes".
+
+
+
+### Export PDF
+
+- You can export the data to a PDF by clicking "Export PDF".
+
+
+
+
+
+### Export Raw Data
+
+- You can export the data to a JSON by clicking "Export Raw Data".
+
+
+
+
+
+### Admin Page
+
+- On the admin page, the user can perform executive functions such as creating and deleting organizations/users.
+
+
+
+
+
+### Manager Page
+
+- The manager page allows someone from the organization that is acting as a manager to access all the user's data that is in that organization. The manager can see a list of all users in the same organization, they can then click on the link and be taken to the individual's datasets to be reviewed.
+
+
\ No newline at end of file
diff --git a/Documentation/images/AdminDashboard.png b/Documentation/images/AdminDashboard.png
new file mode 100644
index 00000000..67ee2822
Binary files /dev/null and b/Documentation/images/AdminDashboard.png differ
diff --git a/Documentation/images/DisableHPGlia.png b/Documentation/images/DisableHPGlia.png
new file mode 100644
index 00000000..12957e6b
Binary files /dev/null and b/Documentation/images/DisableHPGlia.png differ
diff --git a/Documentation/images/DockerTerminalOutput.png b/Documentation/images/DockerTerminalOutput.png
new file mode 100644
index 00000000..abaa5f60
Binary files /dev/null and b/Documentation/images/DockerTerminalOutput.png differ
diff --git a/Documentation/images/FloatingNoteTaker.png b/Documentation/images/FloatingNoteTaker.png
new file mode 100644
index 00000000..8327d8be
Binary files /dev/null and b/Documentation/images/FloatingNoteTaker.png differ
diff --git a/Documentation/images/HpOmniSimulator.png b/Documentation/images/HpOmniSimulator.png
new file mode 100644
index 00000000..6c42097c
Binary files /dev/null and b/Documentation/images/HpOmniSimulator.png differ
diff --git a/Documentation/images/Iteration1CognitiveLoad.png b/Documentation/images/Iteration1CognitiveLoad.png
new file mode 100644
index 00000000..94d7df2d
Binary files /dev/null and b/Documentation/images/Iteration1CognitiveLoad.png differ
diff --git a/Documentation/images/Iteration1Hr.png b/Documentation/images/Iteration1Hr.png
new file mode 100644
index 00000000..aa6f713e
Binary files /dev/null and b/Documentation/images/Iteration1Hr.png differ
diff --git a/Documentation/images/Iteration1Pupil.png b/Documentation/images/Iteration1Pupil.png
new file mode 100644
index 00000000..1aca07d8
Binary files /dev/null and b/Documentation/images/Iteration1Pupil.png differ
diff --git a/Documentation/images/Iteration1SaveButton.png b/Documentation/images/Iteration1SaveButton.png
new file mode 100644
index 00000000..dccbd71a
Binary files /dev/null and b/Documentation/images/Iteration1SaveButton.png differ
diff --git a/Documentation/images/Iteration2CognitiveLoad.PNG b/Documentation/images/Iteration2CognitiveLoad.PNG
new file mode 100644
index 00000000..f9b5e0fd
Binary files /dev/null and b/Documentation/images/Iteration2CognitiveLoad.PNG differ
diff --git a/Documentation/images/Iteration2Hr.PNG b/Documentation/images/Iteration2Hr.PNG
new file mode 100644
index 00000000..4528fc11
Binary files /dev/null and b/Documentation/images/Iteration2Hr.PNG differ
diff --git a/Documentation/images/Iteration2Pupil.PNG b/Documentation/images/Iteration2Pupil.PNG
new file mode 100644
index 00000000..b2af96f4
Binary files /dev/null and b/Documentation/images/Iteration2Pupil.PNG differ
diff --git a/Documentation/images/Iteration2SaveDataButton.PNG b/Documentation/images/Iteration2SaveDataButton.PNG
new file mode 100644
index 00000000..07988331
Binary files /dev/null and b/Documentation/images/Iteration2SaveDataButton.PNG differ
diff --git a/Documentation/images/Iteration2UnityApp.PNG b/Documentation/images/Iteration2UnityApp.PNG
new file mode 100644
index 00000000..107489e5
Binary files /dev/null and b/Documentation/images/Iteration2UnityApp.PNG differ
diff --git a/Documentation/images/Iteration3CognitiveLoad.png b/Documentation/images/Iteration3CognitiveLoad.png
new file mode 100644
index 00000000..534991dd
Binary files /dev/null and b/Documentation/images/Iteration3CognitiveLoad.png differ
diff --git a/Documentation/images/Iteration3Hr.png b/Documentation/images/Iteration3Hr.png
new file mode 100644
index 00000000..aad806e3
Binary files /dev/null and b/Documentation/images/Iteration3Hr.png differ
diff --git a/Documentation/images/Iteration3Pupil.png b/Documentation/images/Iteration3Pupil.png
new file mode 100644
index 00000000..e37921ab
Binary files /dev/null and b/Documentation/images/Iteration3Pupil.png differ
diff --git a/Documentation/images/Iteration3SaveData.png b/Documentation/images/Iteration3SaveData.png
new file mode 100644
index 00000000..a9e25e03
Binary files /dev/null and b/Documentation/images/Iteration3SaveData.png differ
diff --git a/Documentation/images/ManagerPortal.png b/Documentation/images/ManagerPortal.png
new file mode 100644
index 00000000..1a1f5a28
Binary files /dev/null and b/Documentation/images/ManagerPortal.png differ
diff --git a/Documentation/images/NoUnrealPlugin.png b/Documentation/images/NoUnrealPlugin.png
new file mode 100644
index 00000000..308eafba
Binary files /dev/null and b/Documentation/images/NoUnrealPlugin.png differ
diff --git a/Documentation/images/NoteViewer.png b/Documentation/images/NoteViewer.png
new file mode 100644
index 00000000..578b3b04
Binary files /dev/null and b/Documentation/images/NoteViewer.png differ
diff --git a/Documentation/images/OmniceptTrayApp.png b/Documentation/images/OmniceptTrayApp.png
new file mode 100644
index 00000000..ea74cf07
Binary files /dev/null and b/Documentation/images/OmniceptTrayApp.png differ
diff --git a/Documentation/images/OpeningInUnityHub.png b/Documentation/images/OpeningInUnityHub.png
new file mode 100644
index 00000000..d568edfd
Binary files /dev/null and b/Documentation/images/OpeningInUnityHub.png differ
diff --git a/Documentation/images/SdkDownload.png b/Documentation/images/SdkDownload.png
new file mode 100644
index 00000000..dfb72914
Binary files /dev/null and b/Documentation/images/SdkDownload.png differ
diff --git a/Documentation/images/SdkSetupExe.png b/Documentation/images/SdkSetupExe.png
new file mode 100644
index 00000000..15252891
Binary files /dev/null and b/Documentation/images/SdkSetupExe.png differ
diff --git a/Documentation/images/UnityBuildExecutable.png b/Documentation/images/UnityBuildExecutable.png
new file mode 100644
index 00000000..5f9dd503
Binary files /dev/null and b/Documentation/images/UnityBuildExecutable.png differ
diff --git a/Documentation/images/UnityBuildFolder.png b/Documentation/images/UnityBuildFolder.png
new file mode 100644
index 00000000..e3084c19
Binary files /dev/null and b/Documentation/images/UnityBuildFolder.png differ
diff --git a/Documentation/images/UnityBuildSettingsIteration3.png b/Documentation/images/UnityBuildSettingsIteration3.png
new file mode 100644
index 00000000..9345dea9
Binary files /dev/null and b/Documentation/images/UnityBuildSettingsIteration3.png differ
diff --git a/Documentation/images/UnityBuildSubFolder.png b/Documentation/images/UnityBuildSubFolder.png
new file mode 100644
index 00000000..33293af2
Binary files /dev/null and b/Documentation/images/UnityBuildSubFolder.png differ
diff --git a/Documentation/images/UnityDataStoreUrl.png b/Documentation/images/UnityDataStoreUrl.png
new file mode 100644
index 00000000..42ae5ca7
Binary files /dev/null and b/Documentation/images/UnityDataStoreUrl.png differ
diff --git a/Documentation/images/UnityHpOmniTab.png b/Documentation/images/UnityHpOmniTab.png
new file mode 100644
index 00000000..f1f03a48
Binary files /dev/null and b/Documentation/images/UnityHpOmniTab.png differ
diff --git a/Documentation/images/UnityOmniCredentials.png b/Documentation/images/UnityOmniCredentials.png
new file mode 100644
index 00000000..d44d15c2
Binary files /dev/null and b/Documentation/images/UnityOmniCredentials.png differ
diff --git a/Documentation/images/UnityRun.png b/Documentation/images/UnityRun.png
new file mode 100644
index 00000000..6ac8ebe7
Binary files /dev/null and b/Documentation/images/UnityRun.png differ
diff --git a/Documentation/images/UnityTestRunner.png b/Documentation/images/UnityTestRunner.png
new file mode 100644
index 00000000..3816e9b1
Binary files /dev/null and b/Documentation/images/UnityTestRunner.png differ
diff --git a/Documentation/images/UserCreator.png b/Documentation/images/UserCreator.png
new file mode 100644
index 00000000..66a3197a
Binary files /dev/null and b/Documentation/images/UserCreator.png differ
diff --git a/Documentation/images/UserManager.png b/Documentation/images/UserManager.png
new file mode 100644
index 00000000..ee54d4be
Binary files /dev/null and b/Documentation/images/UserManager.png differ
diff --git a/Documentation/images/WebBuild.png b/Documentation/images/WebBuild.png
new file mode 100644
index 00000000..618d4266
Binary files /dev/null and b/Documentation/images/WebBuild.png differ
diff --git a/Documentation/images/WebDropdown.png b/Documentation/images/WebDropdown.png
new file mode 100644
index 00000000..69ee859b
Binary files /dev/null and b/Documentation/images/WebDropdown.png differ
diff --git a/Documentation/images/WebDropdown2.png b/Documentation/images/WebDropdown2.png
new file mode 100644
index 00000000..865e2094
Binary files /dev/null and b/Documentation/images/WebDropdown2.png differ
diff --git a/Documentation/images/WebExportData.png b/Documentation/images/WebExportData.png
new file mode 100644
index 00000000..1bc7d942
Binary files /dev/null and b/Documentation/images/WebExportData.png differ
diff --git a/Documentation/images/WebExportDataResult.png b/Documentation/images/WebExportDataResult.png
new file mode 100644
index 00000000..cfa3aee9
Binary files /dev/null and b/Documentation/images/WebExportDataResult.png differ
diff --git a/Documentation/images/WebExportPDF.png b/Documentation/images/WebExportPDF.png
new file mode 100644
index 00000000..3f699b0c
Binary files /dev/null and b/Documentation/images/WebExportPDF.png differ
diff --git a/Documentation/images/WebExportPDFResult.png b/Documentation/images/WebExportPDFResult.png
new file mode 100644
index 00000000..12000940
Binary files /dev/null and b/Documentation/images/WebExportPDFResult.png differ
diff --git a/Documentation/images/WebFilter.png b/Documentation/images/WebFilter.png
new file mode 100644
index 00000000..900b012d
Binary files /dev/null and b/Documentation/images/WebFilter.png differ
diff --git a/Documentation/images/WebFilter2.png b/Documentation/images/WebFilter2.png
new file mode 100644
index 00000000..1cbe5752
Binary files /dev/null and b/Documentation/images/WebFilter2.png differ
diff --git a/Documentation/images/WebHover.png b/Documentation/images/WebHover.png
new file mode 100644
index 00000000..649923b3
Binary files /dev/null and b/Documentation/images/WebHover.png differ
diff --git a/Documentation/images/WebLogin.png b/Documentation/images/WebLogin.png
new file mode 100644
index 00000000..924a8e2f
Binary files /dev/null and b/Documentation/images/WebLogin.png differ
diff --git a/Documentation/images/WebNoteTakerInterface.png b/Documentation/images/WebNoteTakerInterface.png
new file mode 100644
index 00000000..e901d01e
Binary files /dev/null and b/Documentation/images/WebNoteTakerInterface.png differ
diff --git a/Documentation/images/WebRegister.png b/Documentation/images/WebRegister.png
new file mode 100644
index 00000000..dcb677c7
Binary files /dev/null and b/Documentation/images/WebRegister.png differ
diff --git a/Documentation/images/WebSessionNotes.png b/Documentation/images/WebSessionNotes.png
new file mode 100644
index 00000000..541ce7f3
Binary files /dev/null and b/Documentation/images/WebSessionNotes.png differ
diff --git a/Documentation/images/WebShowSessionNotesButton.png b/Documentation/images/WebShowSessionNotesButton.png
new file mode 100644
index 00000000..117410aa
Binary files /dev/null and b/Documentation/images/WebShowSessionNotesButton.png differ
diff --git a/MeetingMinutes/ClientPartner/2019-09-30.md b/MeetingMinutes/ClientPartner/2019-09-30.md
deleted file mode 100644
index fa29e4c0..00000000
--- a/MeetingMinutes/ClientPartner/2019-09-30.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Client Meeting on 9/30/2019
-
-## Meeting Start Time
-
-Whatever the start of the meeting was in **YYYY/MM/DD/hh:MM** format. Just enter data in this format. Nothing else.
-
-## Meeting End Time
-
-Whatever the start of the meeting was in **YYYY/MM/DD/hh:MM** format. Just enter data in this format. Nothing else.
-
-## Location/Medium
-
-Wherever the meeting was.
-
-## Present
-
-Whoever were present in the meeting. Write only the first names of team members and clients. Each name should be separated by commas.
-
-## Minute Recorder
-
-Whoever was recording the minutes in the meeting. Write only the first name(s) of minute recorders. Each name should be separated by commas.
-
-## Topics Discussed
-
-Whatever discussed in this week.
-
-## Things Clarified
-
-Whatever the plan is for next week.
diff --git a/MeetingMinutes/ClientPartner/2023-10-02.md b/MeetingMinutes/ClientPartner/2023-10-02.md
new file mode 100644
index 00000000..0d62d78a
--- /dev/null
+++ b/MeetingMinutes/ClientPartner/2023-10-02.md
@@ -0,0 +1,41 @@
+# Client Meeting on 10/2/2023
+## Meeting Start Time
+**2023/10/02/17:00**
+## Meeting End Time
+**2023/10/02/18:00**
+## Location/Medium
+Zoom
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan, Alicia
+## Minute Recorder
+Beethoven Meginnis
+## Topics Discussed
+We went over basic introductions. We discussed the basic tech stack. Set up zoom meeting for 5pm Wednesday 10/11.
+Will need a new AWS account and add Alicia in. (Give permissions to Alicia for everything we build)
+Peak Mind intends to lower stress in the workforce. Stress is the opposite of homeostasis. Peak intends to discover 150 of the most common workplace stressors and teach adults how to get out of stress and back into homeostasis. These 150 steps are stored in software. Intend to educate people on what workplace stressors look like as well as measure biometrics of stress. Measure, remediate, and validate.
+The HP headset has a face camera to do face computing. Look at face camera in conjunction with pupil dilation to tell us if we’re excited or in fear.
+***Alicia, requested that we email her to tell us about the dead code base repositories.
+The HP headset will require some permissions and plugins to make the camera work.
+***Eventually, schedule a meeting to physically test the headset.
+Tech Stack:
+Python3.8 Backend, Pipenv, PostgreSQL Database in AWS, JavaScript, TypeScript, HTML, CSS, Mako, Makefile, React Front End, and potentially Unity
+This product will be used on phones on computers. There is a backend and a frontend.
+Our primary objective is to get the face detection working in the existing software.
+The second objective is to get the web app working in a more complete manner. Deployed.
+Primarily, we just need to get the HP headset camera working.
+First Iteration:
+- Get Camera working (Big one for the first iteration)
+Second Iteration:
+- View data on frontend
+Third Iteration:
+- Visualize how we are replaying the data. We must be able to replay the camera. (Live video the whole time)
+Eventually get help from data science students to make mathematical equations to measure the difference between smiles and frowns.
+For design documents, replicate what is existing in the GitHub. Can use what we have.
+Can HP camera expert meet with us? Worked at HP Labs.
+This software aims to address the gap between doctor visits and therapy visits. Most Americans only visit their doctors on average for 30 minutes per year.
+SaaS – Software as a Service
+We use six digit codes when the user logs in for security. Only on the backend, do we see the true data.
+Virtual Reality Therapeutics are found to be 9 times more effective than just reading information. Cuts out all external stimuli.
+The peak mind website is joinpeakmind.com.
+## Things Clarified
+We established a follow up meeting for design documentation with our client on Wednesday (10/12) at 5:00pm. We also need to email her regarding the dead code base repositories to gain access to updated/migrated code bases. We need to send an of approximate dates for check in meetings and iterations.
\ No newline at end of file
diff --git a/MeetingMinutes/ClientPartner/2023-10-11.md b/MeetingMinutes/ClientPartner/2023-10-11.md
new file mode 100644
index 00000000..7a441b51
--- /dev/null
+++ b/MeetingMinutes/ClientPartner/2023-10-11.md
@@ -0,0 +1,21 @@
+# Client Meeting on 10/11/2023
+## Meeting Start Time
+**2023/10/11/17:00**
+## Meeting End Time
+**2023/10/11/18:00**
+## Location/Medium
+Zoom
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan, Alicia
+## Minute Recorder
+Beethoven Meginnis
+## Topics Discussed
+- Add a third actor, scientists, who look at percentages and what they mean in terms of emotion response.
+- Modify UC1 Program Flow to start with users put on the VR headset.
+- For UC2, think about how we can visualize the data differently between data scientists and users.
+- For UC3, keep in mind that there are only 8 customized avatars corresponding to emotion.
+- UC3 as currently stated may not be possible.
+- Potentially create more avatars or work on more of the frontend.
+- Change FR3 for a username and password because we are still in beta testing, not commercialization.
+## Things Clarified
+Send 2 emails to Dr. McKoy, one sending our presentation, and one with our followup meeting calendar notice on Outlook.
\ No newline at end of file
diff --git a/MeetingMinutes/ClientPartner/2023-11-04.md b/MeetingMinutes/ClientPartner/2023-11-04.md
new file mode 100644
index 00000000..78b56b7f
--- /dev/null
+++ b/MeetingMinutes/ClientPartner/2023-11-04.md
@@ -0,0 +1,18 @@
+# Client Meeting on 11/04/2023
+## Meeting Start Time
+**2023/11/04/12:00**
+## Meeting End Time
+**2023/11/04/13:00**
+## Location/Medium
+IRL
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan, Alicia
+## Minute Recorder
+Beethoven Meginnis
+## Topics Discussed
+- *Note, we had to meet with the client prior to our mentor meeting due to extremely limited time constraints for going to the client site in Indianapolis to get the headset facial camera working. There was no other option. This is simply how the timing worked out. We had to adapt to our circumstances.
+- We demonstrated the working first iteration software to Dr. McKoy. We demonstrated recording the facial camera data using the headset. We overcame hurdles regarding the physical access to the headset as well as the large volume of video data that had to be transferred. Dr. McKoy was pleased with our functional first iteration software. We were able to visually see our mouth’s moving on the facial camera as well. We recorded at least one video of this.
+- Dr. McKoy approved of our existing documentation and gave us the greenlight to continue creating our user.md and deployment.md.
+- For our second iteration features, Dr. McKoy wants us to primarily focus on the webapp. We will discuss specifics in a future meeting with her. She is highly confident in our development ability.
+## Things Clarified
+- We must meet with Dr. McKoy next Thursday when she is available, likely over a phone call meeting, to solidify second iteration features. She has given us the go ahead to work with what we have for now.
diff --git a/MeetingMinutes/ClientPartner/2023-11-21.md b/MeetingMinutes/ClientPartner/2023-11-21.md
new file mode 100644
index 00000000..ef87a864
--- /dev/null
+++ b/MeetingMinutes/ClientPartner/2023-11-21.md
@@ -0,0 +1,16 @@
+# Client Meeting on 11/21/2023
+## Meeting Start Time
+**2023/11/21/17:00**
+## Meeting End Time
+**2023/11/21/17:30**
+## Location/Medium
+Zoom
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan, Alicia
+## Minute Recorder
+Beethoven Meginnis
+## Topics Discussed
+Clarifications for iteration 2 features. Dr. Mckoy wants the video data uploaded to the AWS cloud. When save is selected, data must be saved locally and to the cloud. AWS is our biggest priority for iteration 2. The web app visualization will be deprioritized and focused on in iteration 3.
+
+## Things Clarified
+We will meet with Dr.Mckoy prior to our December 4th client meeting due date. We will send her our second iteration functional software over email to review.
diff --git a/MeetingMinutes/Mentor/2019-09-30.md b/MeetingMinutes/Mentor/2019-09-30.md
index d006256d..1b9ef2f7 100644
--- a/MeetingMinutes/Mentor/2019-09-30.md
+++ b/MeetingMinutes/Mentor/2019-09-30.md
@@ -1,29 +1,15 @@
-# Mentor Meeting on 9/30/2019
-
+# Mentor Meeting on 10/5/2023
## Meeting Start Time
-
-Whatever the start of the meeting was in **YYYY/MM/DD/hh:MM** format. Just enter data in this format. Nothing else.
-
+**2023/10/05/16:00**
## Meeting End Time
-
-Whatever the start of the meeting was in **YYYY/MM/DD/hh:MM** format. Just enter data in this format. Nothing else.
-
+**2023/10/05/16:30**
## Location/Medium
-
-Wherever the meeting was.
-
+Zoom
## Present
-
-Whoever were present in the meeting. Write only the first names of team members and clients. Each name should be separated by commas.
-
+Wyatt, Ethan, Beethoven, Peter, Tommy, Ryan
## Minute Recorder
-
-Whoever was recording the minutes in the meeting. Write only the first name(s) of minute recorders. Each name should be separated by commas.
-
+Beethoven
## Topics Discussed
-
-Whatever discussed in this week.
-
+We brought Wyatt up to speed with the data from our first client meeting. Wyatt highlighted the fact that creating an AWS account requires a credit card and stated that we should bring this up with Alicia. We also discussed our first iteration and the difficulty of turning on the camera. We need to ask Alicia in an email to send us the information of the HP camera expert. Wyatt told us that we need to collectively select our IDEs. We not to prioritize getting tools from our client as quickly as possible. We should set up code reviews. We thoroughly went through business requirements, use cases, requirements, architecture, domain model, tech stack, and prototype.
## Things Clarified
-
-Whatever the plan is for next week.
+We will not be able to meet with Wyatt next Thursday (10/12). We should be able to meet with Wyatt on Thursday (10/19).
diff --git a/MeetingMinutes/Mentor/2023-10-05.md b/MeetingMinutes/Mentor/2023-10-05.md
new file mode 100644
index 00000000..1b9ef2f7
--- /dev/null
+++ b/MeetingMinutes/Mentor/2023-10-05.md
@@ -0,0 +1,15 @@
+# Mentor Meeting on 10/5/2023
+## Meeting Start Time
+**2023/10/05/16:00**
+## Meeting End Time
+**2023/10/05/16:30**
+## Location/Medium
+Zoom
+## Present
+Wyatt, Ethan, Beethoven, Peter, Tommy, Ryan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We brought Wyatt up to speed with the data from our first client meeting. Wyatt highlighted the fact that creating an AWS account requires a credit card and stated that we should bring this up with Alicia. We also discussed our first iteration and the difficulty of turning on the camera. We need to ask Alicia in an email to send us the information of the HP camera expert. Wyatt told us that we need to collectively select our IDEs. We not to prioritize getting tools from our client as quickly as possible. We should set up code reviews. We thoroughly went through business requirements, use cases, requirements, architecture, domain model, tech stack, and prototype.
+## Things Clarified
+We will not be able to meet with Wyatt next Thursday (10/12). We should be able to meet with Wyatt on Thursday (10/19).
diff --git a/MeetingMinutes/Mentor/2023-10-19.md b/MeetingMinutes/Mentor/2023-10-19.md
new file mode 100644
index 00000000..63459dff
--- /dev/null
+++ b/MeetingMinutes/Mentor/2023-10-19.md
@@ -0,0 +1,19 @@
+# Mentor Meeting on 10/5/2023
+## Meeting Start Time
+**2023/10/19/16:00**
+## Meeting End Time
+**2023/10/19/16:30**
+## Location/Medium
+Zoom
+## Present
+Wyatt, Ethan, Beethoven, Peter, Tommy, Ryan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+- We began by discussing that for iteration 1, it would be nice to be able to focus solely on functionality; getting the camera working.
+- We discussed that we need to get the email sent to Dr. Mckoy requesting contact information for the HP VR headset expert.
+- We also discussed that we all need to individually email Dr. Mckoy for our temporary AWS logins.
+- We discussed that we should all probably use visual studio code.
+- Note from Wyatt: Get a greater understanding of what each repo handles and which repos specifically we should be working in.
+## Things Clarified
+We will meet with Wyatt at Thursday (10/26) at 4:00pm to go over our software and documentation that exists at that point in time.
\ No newline at end of file
diff --git a/MeetingMinutes/Mentor/2023-10-26.md b/MeetingMinutes/Mentor/2023-10-26.md
new file mode 100644
index 00000000..9577b574
--- /dev/null
+++ b/MeetingMinutes/Mentor/2023-10-26.md
@@ -0,0 +1,17 @@
+# Mentor Meeting on 10/26/23
+## Meeting Start Time
+**2023/10/26/16:00**
+## Meeting End Time
+**2023/10/26/16:30**
+## Location/Medium
+Discord
+## Present
+Wyatt, Ethan, Beethoven, Peter, Tommy, Ryan
+## Minute Recorder
+Ryan
+## Topics Discussed
+- We began by discussing how to create development.md
+- Talked about the common mistakes that come with a development.md
+- Discussed job hunting tips such as how to negotiate salary, interview tips, etc
+## Things Clarified
+We will continue using Discord for all meetings except Client Meetings.
diff --git a/MeetingMinutes/Mentor/2023-11-09.md b/MeetingMinutes/Mentor/2023-11-09.md
new file mode 100644
index 00000000..c71f91d0
--- /dev/null
+++ b/MeetingMinutes/Mentor/2023-11-09.md
@@ -0,0 +1,18 @@
+# Mentor Meeting on 11/9/23
+## Meeting Start Time
+**2023/10/26/16:00**
+## Meeting End Time
+**2023/10/26/16:30**
+## Location/Medium
+Discord
+## Present
+Wyatt, Ethan, Beethoven, Peter, Tommy, Ryan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+- We told Wyatt that we now have functional software for iteration 1.
+- We discussed what we need to accomplish for the second iteration, which will primarily revolve around the web app.
+- We discussed a hybrid/remote work environment and the pros and cons. We also discussed what work life looks like after school is finished.
+-We also briefly went over our the results of our successful client meeting.
+## Things Clarified
+-We will not meet with Wyatt next week. We will meet with Wyatt after Thanksgiving. We will be meeting with Wyatt at Yatts tonight to discuss further.
diff --git a/MeetingMinutes/Mentor/2023-11-21.md b/MeetingMinutes/Mentor/2023-11-21.md
new file mode 100644
index 00000000..74978bb2
--- /dev/null
+++ b/MeetingMinutes/Mentor/2023-11-21.md
@@ -0,0 +1,15 @@
+# Mentor Meeting on 11/21/23
+## Meeting Start Time
+**2023/10/26/16:00**
+## Meeting End Time
+**2023/10/26/16:30**
+## Location/Medium
+Discord
+## Present
+Wyatt, Ethan, Beethoven, Tommy, Ryan, Peter
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We discussed the project showcases as well as our iteration 2 goals. Wyatt asked about Dr. Mckoy's help setting up AWS. We discussed our primary iteration 2 goals being to set up AWS and the webapp. We are using S3 buckets. S3 buckets are similar to Azure data storage. Our video data will likely not work in a relational database. Wyatt advised us that we must get AWS set up and to demosntrate functionality, we must show that video can be found in AWS data storage. Video should be playable in the web app.
+## Things Clarified
+Thursday November 30th at 4pm will be our next mentor meeting.
diff --git a/MeetingMinutes/Mentor/2023-11-30.md b/MeetingMinutes/Mentor/2023-11-30.md
new file mode 100644
index 00000000..70046fc4
--- /dev/null
+++ b/MeetingMinutes/Mentor/2023-11-30.md
@@ -0,0 +1,15 @@
+# Mentor Meeting on 11/30/23
+## Meeting Start Time
+**2023/11/30/16:00**
+## Meeting End Time
+**2023/11/30/16:30**
+## Location/Medium
+Discord
+## Present
+Wyatt, Ethan, Beethoven, Tommy, Ryan, Peter
+## Minute Recorder
+Beethoven
+## Topics Discussed
+Wyatt went over our remaining goals for iteration 2 and confirmed that we were indeed setting up the AWS bucket. He approved that we were good to go in terms of meeting our extended deadline. He wished us a happy holidays and we did the same. We will miss him.
+## Things Clarified
+We clarified that this is likely our last mentor meeting. We will not be meeting again until next semester.
diff --git a/MeetingMinutes/Team/2019-09-30.md b/MeetingMinutes/Team/2019-09-30.md
deleted file mode 100644
index ba099130..00000000
--- a/MeetingMinutes/Team/2019-09-30.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Week of 9/30/2019 - 10/6/2019
-
-## Meeting Start Time
-
-Whatever the start of the meeting was in **YYYY/MM/DD/hh:MM** format. Just enter data in this format. Nothing else.
-
-## Meeting End Time
-
-Whatever the start of the meeting was in **YYYY/MM/DD/hh:MM** format. Just enter data in this format. Nothing else.
-
-## Location/Medium
-
-Wherever the meeting was.
-
-## Present
-
-Whoever were present in the meeting. Write only the first names of team members and clients. Each name should be separated by commas.
-
-## Minute Recorder
-
-Whoever was recording the minutes in the meeting. Write only the first name(s) of minute recorders. Each name should be separated by commas.
-
-## Topics Discussed
-
-Whatever discussed in this week.
-
-## Things Clarified
-
-Whatever the plan is for next week.
diff --git a/MeetingMinutes/Team/2023-09-26.md b/MeetingMinutes/Team/2023-09-26.md
new file mode 100644
index 00000000..214c88cf
--- /dev/null
+++ b/MeetingMinutes/Team/2023-09-26.md
@@ -0,0 +1,22 @@
+# Week of 9/24/2019 - 9/30/2023
+
+## Meeting Start Time
+2023/09/26/16:30
+
+## Meeting End Time
+2023/09/26/17:00
+
+## Location/Medium
+Zoom
+
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+
+## Minute Recorder
+Beethoven
+
+## Topics Discussed
+We discussed whether discord is a more viable meeting platform. We then began plotting possible meeting times for our client discovery meeting. We put together an email, with 3 possible time slots on Thursday (9/28), Friday (9/29), and Monday (10/2), mostly within business hours. We also used when2meet.com to figure out our collective availability in the future.
+
+## Things Clarified
+Next week, we plan to meet both on Tuesday and Thursday, likely on each day for at least 1 hour to knock out design details following our discovery meeting. We will be using discord for Team Meetings going forward. We will likely stick to Zoom for Client and potentially mentor meetings.
\ No newline at end of file
diff --git a/MeetingMinutes/Team/2023-10-02.md b/MeetingMinutes/Team/2023-10-02.md
new file mode 100644
index 00000000..dd5bc470
--- /dev/null
+++ b/MeetingMinutes/Team/2023-10-02.md
@@ -0,0 +1,17 @@
+# Week of 10/2/2023
+## Meeting Start Time
+2023/10/2/16:00
+## Meeting End Time
+2023/10/2/17:00
+## Location/Medium
+Zoom
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We discussed the previous year’s peak-visualization GitHub project as well as our next-gen emotion computing project. We discussed questions to ask the client, as well as assign roles for note taking, screenshot taking, and potential diagram drawing. We discussed recording software as well as how to upload our video. We discussed who should talk and when as well as established some basic group dynamics when engaging with the client. By roughly 16:40, we were more or less fully prepped to tackle the client meeting.
+## Things Clarified
+We discussed that we would meet for roughly 10-15 minutes following our client meeting at 17:00-18:00 to compile our meeting notes and submit to the GitHub discovery folder.
+## Tasks Distributed
+Ryan was tasked with sending the follow up email to the client. Tommy and Peter were tasked with beginning work on the business requirements and corresponding use cases. Ethan and Beethoven were tasks with beginning the architecture and domain model.
diff --git a/MeetingMinutes/Team/2023-10-11.md b/MeetingMinutes/Team/2023-10-11.md
new file mode 100644
index 00000000..f70296cd
--- /dev/null
+++ b/MeetingMinutes/Team/2023-10-11.md
@@ -0,0 +1,25 @@
+# Week of 10/11/2023
+## Meeting Start Time
+2023/10/11/16:00
+## Meeting End Time
+2023/10/2/17:00
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+- We revised our previous team meeting notes that lacked tasks distributed.
+- We talked about the topics that we would discuss with Dr. McKoy.
+- We broke down that Ryan would present the business requirements, Beethoven would present the use cases, Peter would present the functional requirements, Ethan would present the Domain Model, while Tommy would present the Prototype. We will then make appropriate modifications to our presentation, following Dr. McKoy’s feedback.
+## Things Clarified
+- We will briefly meet after our client meeting to discuss our presentation.
+- We will not meet again this week due to this being mid-terms week.
+- We will meet again on Tuesday of next week and this will likely be a doubled-up meeting, first our biweekly mentor meeting and after that, our own team meeting.
+## Tasks Distributed
+- Tommy will create the foundation for the presentation slides.
+- Ryan will email Dr.McKoy with a followup to ensure that she makes our client meeting.
+- Beethoven will work on meeting minutes for both meetings today.
+- Ethan will convert the google doc to markdown.
+- Peter will flesh out the presentation slide details.
\ No newline at end of file
diff --git a/MeetingMinutes/Team/2023-10-19.md b/MeetingMinutes/Team/2023-10-19.md
new file mode 100644
index 00000000..abf82527
--- /dev/null
+++ b/MeetingMinutes/Team/2023-10-19.md
@@ -0,0 +1,23 @@
+# Week of 10/11/2023
+## Meeting Start Time
+2023/10/19/16:30
+## Meeting End Time
+2023/10/19/18:00
+## Location/Medium
+Zoom
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We all shared our phone numbers together so that we can wake people up when needed. We spent time going through the previous group’s Development.md and installing the HP Omnicept SDK, Docket Desktop, and Unity. We troubleshooted issues such as .NET 3.5 not installing. We sent out 3 emails to Dr. Mckoy including getting the contact info of the HP Omnicept expert, requesting individual access to the AWS, and sending out presentation to her. Those who were unable to install certain applications on their machines were tasked with ensuring that they were able to install them come next meeting. Ethan also forked the repositories so that we can work in our own region now without worry of destroying the previous team’s work.
+## Things Clarified
+We will meet on Tuesday (10/24) at 4pm to continue working. This will be a team meeting. Going forward, we will need to meet at 4pm on Tuesdays and Thursdays, every single week in order to keep up with the workload.
+## Tasks Distributed
+Beethoven is handling meeting minutes as well as coordination of tasks. He will also pin the meeting upcoming meeting notices.
+Ryan is drafting and sending emails to Dr. Mckoy to show her our presentation as well as request the contact information of the HP Omnicept VR headset expert.
+Ethan will be forking the GitHub repo and setting up the development environment.
+Tommy will be writing down all changes that most be made to our design documents.
+Peter will be making the zoom meetings for next week.
+Everyone has been tasked with individually emailing Dr. Mckoy for their AWS login information.
+Everyone has been tasked with installing HP Omnicept SDK, Docker Desktop, and Unity.
\ No newline at end of file
diff --git a/MeetingMinutes/Team/2023-10-26.md b/MeetingMinutes/Team/2023-10-26.md
new file mode 100644
index 00000000..bcd3a18f
--- /dev/null
+++ b/MeetingMinutes/Team/2023-10-26.md
@@ -0,0 +1,21 @@
+# Week of 10/11/2023
+## Meeting Start Time
+2023/10/26/16:30
+## Meeting End Time
+2023/10/26/19:00
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Ryan
+## Topics Discussed
+- We talked about and updated our design documents according to the comments left by Dr. Ergin
+- We created our development.md file
+- Set up the development enviornment on each persons laptop.
+## Things Clarified
+We will continue meeting every Tuesday and Thursday at 4pm but are not meeting next Tuesday. Our next meeting is Thursday Nov 02
+## Tasks Distributed
+Ryan is in charge of creating the meeting notes and coordinating the tasks for the week.
+Ben and Tommy were tasked with updating the design documents with regards to Dr. Ergin's comments.
+Ethan, Peter, and Ryan were in charge of creating the development.md file
diff --git a/MeetingMinutes/Team/2023-11-03.md b/MeetingMinutes/Team/2023-11-03.md
new file mode 100644
index 00000000..c6c80d2f
--- /dev/null
+++ b/MeetingMinutes/Team/2023-11-03.md
@@ -0,0 +1,17 @@
+# Week of 10/30/2023
+## Meeting Start Time
+2023/11/2/16:00
+## Meeting End Time
+2023/11/2/19:00
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We communicated with Dr. Mckoy to figure out a time to meet with her in Indianapolis to utilize the headset. We evaluated that we are just waiting on the physical headset to collect real data to test our face camera code. We coordinated our schedules to effectively carpool on Saturday. We also planned additional meeting times next week. We dived into the Unity code and were able to find where the code talks to the headset and found the code that retrieves the image. We must still figure out how to display the code.
+## Things Clarified
+We will meet on Tuesday and Thursday of next week at 4pm. We will meet up at 10am on this Saturday to carpool together and meet Dr. Mckoy at 12pm at one of her offices.
+## Tasks Distributed
+All team members will meet on Saturday to utilize the limited time window in which we have the headset. All team members must be present to take advantage of this opportunity. All team members must bring their laptops and be prepared to code and test on site. We will all be meeting at Ryan’s house at 10am on Saturday. Ryan will be driving us down to Indianapolis and back up to Muncie.
diff --git a/MeetingMinutes/Team/2023-11-06.md b/MeetingMinutes/Team/2023-11-06.md
new file mode 100644
index 00000000..207c12fc
--- /dev/null
+++ b/MeetingMinutes/Team/2023-11-06.md
@@ -0,0 +1,20 @@
+# Week of 11/06/2023
+## Meeting Start Time
+2023/11/09/16:00
+## Meeting End Time
+2023/11/09/19:00
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We primarily worked on the presentation slides in this meeting. We coordinated our efforts to draft our second iteration features. We discussed the need to rehearse this presentation to aid in a smoother presentation in class. We also discussed the responsibility of each team member to memorize the information that will be discussed on each slide so that we can have a lower word count per slide overall. This should aid in visual clarity and a concise viewer experience.
+## Things Clarified
+We will meet over discord on Monday to rehearse our presentation for roughly 30 minutes.
+## Tasks Distributed
+Tommy and Peter will finish up the presentation slides.
+Ryan will review the presentation slides to ensure that all requirements are met.
+Beethoven and Ethan will work on 1st iteration documentation as well as second iteration features.
+
diff --git a/MeetingMinutes/Team/2023-11-09 _DURING-CLASS-TIME.md b/MeetingMinutes/Team/2023-11-09 _DURING-CLASS-TIME.md
new file mode 100644
index 00000000..a743b3c9
--- /dev/null
+++ b/MeetingMinutes/Team/2023-11-09 _DURING-CLASS-TIME.md
@@ -0,0 +1,14 @@
+## Meeting Start Time
+2023/11/09/9:30
+## Meeting End Time
+2023/11/09/10:50
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Tommy
+## Things Clarified
+We are planning to finish the presentation slides for next class and meet up in the library from 4:30pm to 8pm. We will have our mentor meeting at 4pm. We will meet in person in the library to collaborate together. We need to work on our Deployment.md tonight.
+## Progress Made
+We completed presentation slides 1-6. We finished implementing the code for the video encoding using the MediaEncoder class. Additionally, we began taking pictures for our step-by-step user.md. We have drafted most of our second iteration features, but we still need to review these carefully in our team meeting later today.
diff --git a/MeetingMinutes/Team/2023-11-21.md b/MeetingMinutes/Team/2023-11-21.md
new file mode 100644
index 00000000..6ba53cef
--- /dev/null
+++ b/MeetingMinutes/Team/2023-11-21.md
@@ -0,0 +1,17 @@
+# Week of 11/20/2023
+## Meeting Start Time
+2023/11/21/17:30
+## Meeting End Time
+2023/11/21/19:00
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We recapped our client meeting with Dr.Mckoy. We collectively agreed that AWS cloud storage of video fies (mp4) is our most important objective for iteration 2. The webapp can be delayed until next semester. Dr. Mckoy's data scientists can assist us if need be. We have identified that there is no visualization in the webapp after the log-in screen. We may be able to split into 2 teams to work on AWS and the webapp seperately.
+## Things Clarified
+We will meet again on Thursday November 30th for our next team meeting. We are hoping to meet and further clarify and distribute tasks in class on Tuesday November 28th.
+## Tasks Distributed
+All team members have been instructed to update and select tasks from the story board on github to progress into iteration 2. Major work will resume after Thanksgiving Break.
diff --git a/MeetingMinutes/Team/2023-11-30 _DURING-CLASS-TIME.md b/MeetingMinutes/Team/2023-11-30 _DURING-CLASS-TIME.md
new file mode 100644
index 00000000..9a43f0fb
--- /dev/null
+++ b/MeetingMinutes/Team/2023-11-30 _DURING-CLASS-TIME.md
@@ -0,0 +1,14 @@
+## Meeting Start Time
+2023/11/30/9:30
+## Meeting End Time
+2023/11/30/10:50
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Things Clarified
+We will meet tonight at 4:00pm on discord. We will also meet throughout the following 3 days. Those being Friday, Saturday and Sunday. This will be drop-in, drop-out discord meetings to attempt to complete iteration 2 on time.
+## Progress Made
+The email to Dr.Mckoy was sent to clarify future tasks involved with iteration 2. CRC cards were created and the diagram of the webapp database was created. Signficant progress was made on creating the AWS S3 bucket.
diff --git a/MeetingMinutes/Team/2023-11-30.md b/MeetingMinutes/Team/2023-11-30.md
new file mode 100644
index 00000000..99bc81c1
--- /dev/null
+++ b/MeetingMinutes/Team/2023-11-30.md
@@ -0,0 +1,17 @@
+# Week of 11/27/2023
+## Meeting Start Time
+2023/11/27/16:30
+## Meeting End Time
+2023/11/71/19:00
+## Location/Medium
+Discord
+## Present
+Beethoven, Peter, Ryan, Tommy, Ethan
+## Minute Recorder
+Beethoven
+## Topics Discussed
+We decided that most if not all of us could meet with Dr.Mckoy on Monday at 11am to present our second iteration software to her. We sent her a follow-up email because she was originally unable to attend our original time slot. We all mob programmed together to advance our progress with the AWS S3 bucket to pave the way for deployment of the web app and backend.
+## Things Clarified
+We will meet again on Monday for both a client-partner meeting and team meeting to put together our presentation for our iteration 2 functional software.
+## Tasks Distributed
+Tommy will continue to flesh out the CRC cards and work with Ethan on diagramming. Ryan will manage the communication with Dr.Mckoy regarding the integration of PeakMind interns for data analysis. Peter will send the zoom link to Dr. Mckoy regarding our Monday meeting and will continue his work on setting up the AWS S3 bucket. Beethoven will deploy the web app to AWS. Ethan will deploy the backend to AWS. All team members will work on improvements to the webapp.
diff --git a/Presentations/DesignDay.pdf b/Presentations/DesignDay.pdf
new file mode 100644
index 00000000..08a96453
Binary files /dev/null and b/Presentations/DesignDay.pdf differ
diff --git a/Presentations/Project Iteration 1 .pdf b/Presentations/Project Iteration 1 .pdf
new file mode 100644
index 00000000..73489738
Binary files /dev/null and b/Presentations/Project Iteration 1 .pdf differ
diff --git a/README.md b/README.md
index 7afb0fb7..4346d7ce 100644
--- a/README.md
+++ b/README.md
@@ -1,14 +1,16 @@
-# CapstoneProjectTemplate /* Replace this line with the title of your project */
+# Next Gen Emotion Computing
## **Summary**
-Put a very high-level summary of the project.
+"SaaS software, becoming a Software as a Medical Device (SaMD) for high stress users. We provide stress relief via our software and VR integration and simulations."
## **Team Members**
-- Joe Black
-- Joe Pesci
-- Joe Dalton
+- Beethoven Meginnis
+- Ethan Forrest
+- Peter Owolabi
+- Ryan Martinez
+- Tommy Nyugen
## **Client Partner Information**
@@ -16,8 +18,7 @@ Put a very high-level summary of the project.
WHATEVER COMPANY or CORRESPONDENCE
### *People:*
-- Jane Fonda
-- Jane Lynch
+- Dr. Alicia Mckoy
## **Links**
@@ -25,6 +26,7 @@ WHATEVER COMPANY or CORRESPONDENCE
- [Team meeting minutes](MeetingMinutes/Team)
- [Mentor meeting minutes](MeetingMinutes/Mentor)
- [Client partner meeting minutes](MeetingMinutes/ClientPartner)
+- [First Iteration Features (Project Management Tool)](https://github.com/users/eforrest8/projects/1)
- ... any other documents/links you see need
## **Code Repositories**
@@ -33,3 +35,14 @@ WHATEVER COMPANY or CORRESPONDENCE
- [Php Backend](https://www.github.com/WHEREEVER_THE_PHP_CODE_IS)
- Others if more.
+## User Documentation
+
+- [User.md](./Documentation/User.md)
+
+## Development Documentation
+
+- [Development.md](./Documentation/Development.md)
+
+## Deployment Documentation
+
+- [Deployment.md](./Documentation/Deployment.md)