Product-scoped folders
Each top-level folder under this repository is one product or program. Handover markdown lives inside that folder.
Start here, then open the guide for each product in the sidebar.
aimet-product-library/
├── index.md # This landing page (VitePress home)
├── README.md # Same reading guide for GitHub
├── docs/.vitepress/ # VitePress config (not product content)
├── c2fit/ # c2fit handover pack
│ ├── project-overview.md
│ ├── business-logic-dataflow.md
│ ├── deployment-and-infrastructure.md
│ ├── repository-map.md
│ ├── ux-ui-and-design-links.md
│ └── other/ # Production and study assessment details
├── digital-thai-moca/ # Digital Thai MoCA handover pack
│ ├── project-overview.md
│ ├── business-logic-dataflow.md
│ ├── deployment-and-infrastructure.md
│ ├── repository-map.md
│ ├── ux-ui-and-design-links.md
│ └── others/ # Drafts and working files (not in the site nav)
├── dmind/ # DMIND maintainer handover pack
│ ├── project-overview.md
│ ├── system-architecture.md
│ ├── repository-map.md
│ ├── prescreening/
│ ├── ivr/
│ └── ai-platform/
├── emmind-mtl/ # EMmind MTL maintainer handover pack
│ ├── project-overview.md
│ ├── system-architecture.md
│ ├── business-logic.md
│ ├── data-and-integrations.md
│ ├── deployment-and-operations.md
│ ├── repository-map.md
│ └── ux-ui-and-design-directory.md
└── package.json # `yarn docs:dev` / `yarn docs:build`Add a new product by creating a sibling folder (for example another-product/) with its own overview and topic documents, then register it in docs/.vitepress/config.ts navigation and sidebar.
yarn install then yarn docs:dev, and open the URL printed in the terminal (usually http://localhost:5173).| Read this for… | Document |
|---|---|
| Product scope, environments, services, and handover links | project-overview |
| Assessment journey, scoring, auth, and data flow | business-logic-dataflow |
| Production assessment behavior | Production assessment detail |
| Study assessment behavior | Study assessment detail |
| Frontend and backend deployment, AWS topology, and dependencies | deployment-and-infrastructure |
| Application repositories and cross-repo integration | repository-map |
| Figma sources and implemented product surfaces | ux-ui-and-design-links |
| Read this for… | Document |
|---|---|
| Scope, surfaces, environments, deprecated paths, topic index | project-overview |
| System boundaries and current dashboard path | system-architecture |
| Related repositories and current/historical classification | repository-map |
| Participant and staff business/data/infrastructure | Prescreening business logic |
| IVR route/state/data/infrastructure | IVR business logic |
| AI orchestration, workers, queues, data, infrastructure | AI pipeline |
| Implemented UI surfaces, code owners, and Figma link status | UX/UI and design directory |
| Read this for… | Document |
|---|---|
| Purpose, products, environment URLs, topic index | project-overview |
| Flows, auth, MoCA domains, scoring, data model | business-logic-dataflow |
| AWS topology, DNS, CI/CD, secrets, external services | deployment-and-infrastructure |
| GitHub repos, Bruno API spec, cross-repo flows | repository-map |
| Figma and product surfaces | ux-ui-and-design-links |
| Read this for… | Document |
|---|---|
| Product purpose, users, capability map, repository boundary, infrastructure summary, and topic index | project-overview |
| LINE, LIFF, CMS, core, data-store, and identity flows | system-architecture |
| Onboarding, 9Q, CBT paths, journals, activities, safety, feedback, and CMS behavior | business-logic |
| PostgreSQL, Redis, S3, LINE, Google, authentication, and deletion | data-and-integrations |
| Runtime dependencies, image builds, deploy events, configuration, migrations, schedules, and health routes | deployment-and-operations |
| GitHub repositories, snapshots, API collections, and source ownership | repository-map |
| Employee and CMS surfaces, checked-in artwork, fonts, copy, LINE assets, and question export | ux-ui-and-design-directory |
Draft unit requirements and spreadsheets under digital-thai-moca/others/ are intentionally excluded from the published site navigation; open those files directly in the repository when needed.