FactuGES_ERP/docs/REQUISITOS GENERALES.md

# Requisitos Generales (Histórico / Descubrimiento)

Este documento resume requisitos funcionales tempranos del ERP. No define el runtime actual ni sustituye la documentación operativa vigente.

## Estado

- Documento histórico de descubrimiento.
- Útil para entender intención de producto y necesidades de negocio amplias.
- No usar como contrato técnico actual de autenticación, tenant context, JWT, base de datos o endpoints.

## Temas que sí conserva como contexto

- multiempresa y multisucursal
- auditoría y trazabilidad
- seguridad y permisos
- soporte multiidioma
- extensibilidad modular

## Documentación vigente relacionada

- Arquitectura y tenant context: [architecture/README.md](./architecture/README.md)
- Auth actual: [architecture/identity-auth-api.md](./architecture/identity-auth-api.md)
- Flujo frontend: [frontend/auth-and-company-selection.md](./frontend/auth-and-company-selection.md)
- Módulos documentales: [customer-invoices/README.md](./customer-invoices/README.md) y [document-series/README.md](./document-series/README.md)

## Nota

Las decisiones antiguas sobre JWT con `active_company_id`, `tab_id`, tablas SQL de ejemplo y flujos de selección tempranos quedaron superadas por la arquitectura actual y se conservan solo a nivel histórico.
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`# Requisitos Generales (Histórico / Descubrimiento)`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`Este documento resume requisitos funcionales tempranos del ERP. No define el runtime actual ni sustituye la documentación operativa vigente.`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`## Estado`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`- Documento histórico de descubrimiento.`
			`- Útil para entender intención de producto y necesidades de negocio amplias.`
			`- No usar como contrato técnico actual de autenticación, tenant context, JWT, base de datos o endpoints.`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`## Temas que sí conserva como contexto`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`- multiempresa y multisucursal`
			`- auditoría y trazabilidad`
			`- seguridad y permisos`
			`- soporte multiidioma`
			`- extensibilidad modular`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`## Documentación vigente relacionada`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`- Arquitectura y tenant context: [architecture/README.md](./architecture/README.md)`
			`- Auth actual: [architecture/identity-auth-api.md](./architecture/identity-auth-api.md)`
			`- Flujo frontend: [frontend/auth-and-company-selection.md](./frontend/auth-and-company-selection.md)`
			`- Módulos documentales: [customer-invoices/README.md](./customer-invoices/README.md) y [document-series/README.md](./document-series/README.md)`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			`## Nota`
Importación inicial 2025-01-28 14:01:02 +00:00
Refactor documentation for ERP architecture and customer invoices - Updated general requirements document to clarify its historical context and remove outdated technical details. - Revised template documentation to serve as a base for writing prompts, emphasizing its auxiliary nature. - Enhanced architecture documentation with clear distinctions between canonical and complementary documents. - Added a new document for backend prompt base to centralize common context for backend prompts. - Created a dedicated README for customer invoices, organizing current contracts, operational support, and historical context. - Improved clarity and structure in various customer invoice documents, consolidating operational semantics and referencing canonical sources. 2026-08-05 11:18:03 +00:00			Las decisiones antiguas sobre JWT con `active_company_id`, `tab_id`, tablas SQL de ejemplo y flujos de selección tempranos quedaron superadas por la arquitectura actual y se conservan solo a nivel histórico.