Session 3 β Architecture Standards β
Goal: Confirm the technical architecture decisions are still current and internally consistent. Estimated time: 90 min
Reading Order β
Read in this order β dependencies flow top-down:
| # | File | What It Covers |
|---|---|---|
| 1 | domain-driven-design.md | Bounded contexts, CQRS, cross-context patterns, context map. The architectural backbone. |
| 2 | database.md | PostgreSQL strategy, schema separation, pgvector. |
| 3 | frontend.md | Vue 3/Nuxt/Quasar split, FSD layers, shared packages. |
| 4 | app-structure.md | Workspace app feature layout, folder conventions, route structure. |
| 5 | design-system.md | Component library, token system, Tailwind conventions. |
| 6 | roles.md | RBAC roles, capability model, roleβfrontend matrix. |
| 7 | validation-strategy.md | Input validation layers, Zod schemas, Hasura validation. |
| 8 | monorepo.md | Turborepo pipeline, caching, Docker build strategy, pnpm conventions. |
| 9 | realtime-strategy.md | WebSocket, Hasura subscriptions, live updates. |
| 10 | ai.md | RAG pipeline, agent workflows, Paperclip, MCP bridge. |
| 11 | communications.md | Omnichannel inbox, notification pipeline, channel provisioning. |
| 12 | workflow-orchestration.md | BullMQ, event triggers, scheduled jobs, worker patterns. |
| 13 | gdpr-strategy.md | Data retention, encryption, TTL policies, right to erasure. |
| 14 | tests.md | Testing strategy, Vitest, Playwright, offline testing. |
π What to Validate β
- [ ]
domain-driven-design.mdΒ§8 Context Map: does each upstream/downstream relationship still hold? Cross-reference withevent-catalog.md(Session 5). - [ ]
roles.md: the Manager/Dispatcher/Driver trio β is the Driver auth flow documented anywhere? (Flagged as missing.) - [ ]
ai.mdreferences Paperclip for agentic company governance β is this still the chosen platform? - [ ]
monorepo.mdreferences Vercel Remote Cache as "planned" β still planned or dropped? - [ ]
gdpr-strategy.md: does it cover the right-to-erasure implementation, or only the strategy? - [ ]
tests.md: does the testing strategy match what tests actually exist in the repo today? - [ ]
frontend.mdlistsapps/backoffice/β does this app still exist, or was it merged into workspace? - [ ]
design-system.md: does it reference Quasar's default UI bypass accurately? Is ShadCN-vue still the chosen library? - [ ]
validation-strategy.mdat 3 KB β is this complete, or does it need expanding? - [ ]
workflow-orchestration.mdat 18 KB β does it still reflect the actual NestJS worker patterns in the codebase?