FactuGES_ERP/docs/architecture/README.md
david e5e73a5a13 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 13:18:03 +02:00

26 lines
1.1 KiB
Markdown

# ERP Architecture Docs
Índice de arquitectura vigente y documentos transicionales relacionados con autenticación, tenant context y migración a `identity`.
## Documentación canónica vigente
- [Identity and companies](./identity-and-companies.md)
- [Tenant context](./tenant-context.md)
- [Identity auth API](./identity-auth-api.md)
- [Identity migration status](./identity-migration-status.md)
- [Identity roadmap](./identity-roadmap.md)
## Documentación complementaria
- [Identity backend architecture](./identity-backend-architecture.md)
`identity-backend-architecture.md` se mantiene como nota complementaria de diseño backend. Para contratos operativos concretos, prevalecen `tenant-context.md`, `identity-auth-api.md` y los README de módulo.
## Resumen actual
- `identity` gestiona autenticación, sesión, refresh y memberships.
- `companies` gestiona la ficha operativa de empresa.
- `GET /companies/available` es la vía vigente para companies accesibles.
- El contexto tenant se resuelve con `X-Company-Id` y `requireIdentityTenant(params)`.
- El frontend ERP ya usa el runtime nuevo de `identity`.