> ## Documentation Index
> Fetch the complete documentation index at: https://help.stralos.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Module requirements

> Module-level documentation index

This page maps source requirements into the help-centre structure.

## Source documents

| Source | Promote To | Treatment |
| - | - | - |
| `frontend/product-scope.md` | Product overview, product scope | Summarise current modules; do not promote stale frontend-only/mock-only language. |
| `frontend/module-requirements.md` | User guides and internal product requirements | Split by workflow; keep acceptance criteria internal. |
| `frontend/ux-workflow-requirements.md` | User workflows and UX requirements | Use workflow principles in Guides; keep UX direction internal. |
| `frontend/domain-model.md` | Key concepts and domain model | Explain concepts publicly; keep TypeScript/entity detail internal. |
| `frontend/estimate-workbook-field-analysis.md` | Rates, work items, SOP/TAGs, workbook mapping | Summarise; keep workbook-derived field mapping internal. |
| `prd/estimate-document-ai-pipeline.md` | Documents guide, Documents API, Document AI pipeline | Split user workflow, API reference, and internal operations. |
| `prd/micro-frontend-federation.md` | Micro-frontends and frontend architecture | Mark runtime federation as target/future, not current shipped state. |

## Current implementation priority

* Make current UI workflows understandable for estimators and managers.
* Make service boundaries and local development clear for engineers.
* Keep historical prototype content in internal/archive context.
* Avoid presenting roadmap modules as shipped product.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.