FactuGES_ERP/docs/architecture
David 5ad446be00 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 18:52:45 +02:00
..
DOCUMENTO-DE-DISEÑO-—-ERP-MODULAR-BACKEND-(ESTADO-CONSOLIDADO).md feat: add proforma duplicator service and related tests 2026-08-26 13:03:39 +02:00
DTOS - GUÍA DE DISEÑO.md feat: add proforma duplicator service and related tests 2026-08-26 13:03:39 +02:00
http-error-handling-frontend.md feat: add error handling and feedback state management for customer and proforma updates 2026-08-06 13:03:48 +02:00
identity-and-companies.md feat(companies): implement update current company use case and associated controllers 2026-08-17 15:49:11 +02:00
identity-auth-api.md feat: implement account management features 2026-08-17 23:30:41 +02:00
identity-backend-architecture.md Refactor documentation for ERP architecture and customer invoices 2026-08-05 13:18:03 +02:00
identity-migration-status.md feat: restructure frontend documentation and introduce new architectural guidelines 2026-09-04 18:52:45 +02:00
identity-roadmap.md Doc 2026-07-06 14:04:47 +02:00
README.md feat: add error handling and feedback state management for customer and proforma updates 2026-08-06 13:03:48 +02:00
tenant-context.md feat(companies): implement update current company use case and associated controllers 2026-08-17 15:49:11 +02:00

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

Documentación complementaria

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.