Rodax_Software/FactuGES_ERP
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
021c19fc40
FactuGES_ERP/docs/REQUISITOS GENERALES.md

29 lines
1.3 KiB
Markdown
Raw Normal View History

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)
feat: restructure frontend documentation and introduce new architectural guidelines - Removed outdated documents on screen design and editor layout audit. - Added comprehensive documentation on frontend architecture, UI patterns, and UI system. - Established clear guidelines for component usage, routing, and layout structures. - Enhanced accessibility and responsiveness standards across UI components. - Defined testing protocols and anti-patterns to maintain code quality and consistency.
2026-09-04 16:52:45 +00:00
- Arquitectura y flujo frontend: [frontend/frontend-architecture.md](./frontend/frontend-architecture.md)
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
- 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.
Reference in New Issue Copy Permalink