We want to creat sphinx documentation in /docs. This should cover client, server, and infrastructure and document file structure, patterns, and best practices.

Plans go in ./docs/plans

We are going to create a plan for this feature. This plan will include all context needed, any outstanding product or feature questions that need more investigation, and an explicit task list of things to do. ultrathink about implementing this plan and everything we'll want to account for to make sure this is a top notch implementation. Always focus on creating the cleanest, tightest, most focused implementation. Avoid abstractions unless clearly necesary, creating the minimal implementation to achieve our goals.

The template is as follows:

---

Created Date <Today's Date>

Feature Plan: <title>

Overview

<Context on why we're making this feature, and what it's looking to achieve>

Outcomes

<a bulleted list things that we want to achieve with this plan>

Open Questions

<A checkmarkable list of open questions we should resolve before starting the plan, after receiving the feedback from the user on the questions, we will checkmark the question as done, and include the answer below it. Example:

[ ] Do we have a perference on using stdlib versus a dependancy

[x] What Metrics do we need to collect

CPU, Memory, and average response time

Tasks

<A thorough list of checkmarkable tasks that need to be completed in order to achieve the plan: EG

[ ] Define API Interface for the new endpoint using swagger

[ ] Create tests for the new endpoint

[ ] Implement database migrations

[ ] Create DAOs

[ ] Create Seeders

[ ] Implement business logic between endpoint router and DAO

[ ] Implement endpoint and swagger

Security

<Parts of the implementation we need to consider especially for security ramifications>

<Other sections as make sense for the implementation, including schemas, diagrams, or other concerns>