louis/gigafibre-fsm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
gigafibre-fsm/docs/architecture
History
louispaulb f33f7a6309 Optimisation (consolidation helpers address) + doc Vision/modularisation 
Optimisation sûre (vérifiée, 0 régression) :
- helpers.js : `cors()` partagé (en-têtes CORS génériques) au lieu de 2 copies locales.
- address-conformity.js : réutilise `pool` (address-db) + `cors` (helpers) au lieu de redéfinir un Pool +
  cors → 1 seul client pg local partagé pour rqa_addresses/fiber.
- address-validate.js : utilise helpers.cors.

docs/architecture/VISION.md (NOUVEAU) — vision + plan de modularisation + roadmap d'optimisation, fondé sur
un audit chiffré (hub 58 modules/23k lignes, Ops 45k lignes, god-files identifiés). Découpe en 9 domaines
(bounded contexts), principe « source de vérité + validation à la saisie + lien stable » (modèle Adresses
généralisé à Client/Device/Service), optimisations P0/P1/P2, métriques de succès. Complète les docs
architecture existants + ENGINEERING_PRACTICES.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-07 01:28:54 -04:00
..
app-design.md docs: reorganize into architecture/features/reference/archive folders 2026-04-22 11:51:33 -04:00
data-model.md docs: bring all docs in sync with the May 2026 reality 2026-05-05 20:10:40 -04:00
module-interactions.md docs: bring all docs in sync with the May 2026 reality 2026-05-05 20:10:40 -04:00
overview.md docs: recommend frappe_pg community app for ERPNext PostgreSQL compat 2026-05-21 14:40:36 -04:00
README.md fix(tech): restore Gemini-native scanner + port equipment UX into ops 2026-04-22 15:56:38 -04:00
VISION.md Optimisation (consolidation helpers address) + doc Vision/modularisation 2026-06-07 01:28:54 -04:00

README.md

Architecture

How the pieces fit together. Read overview.md first unless you have a specific reason not to.

Doc Read when…
overview.md You need the full service map — ERPNext, Ops PWA, targo-hub, DocuSeal, Authentik, Traefik, Docker networks, the legacy retirement plan
module-interactions.md You're chasing a call across modules — one-page matrix + sequence diagrams for the hot paths (dispatch → SMS → tech scan → equipment install, Stripe webhook → ERPNext, customer portal → hub proxy)
data-model.md You're about to touch ERPNext: Customer, Service Location, Service Subscription, Service Equipment, Sales Invoice, Payment Entry. Also covers the "Lead to Live" customer flow
app-design.md You're building frontend. Feature-sliced layout, Vue/Quasar patterns, Pinia, router, theming, Storybook conventions

Back to docs/README.md · roadmap.md