< Prev | Up: Session Overview | Next >

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	Lines	What It Covers
1	domain-driven-design.md	159	Bounded contexts, CQRS, cross-context patterns, context map.
2	database.md (merged into domain-driven-design.md §3)	—	PostgreSQL strategy, schema separation, pgvector.
3	frontend.md	~65	Vue 3/Nuxt/Quasar split, FSD layers, shared packages.
4	app-structure.md	292	Workspace app feature layout, folder conventions, route structure.
5	design-system.md	122	Component library, token system, Tailwind conventions.
6	roles.md	~110	RBAC roles, capability model, role→frontend matrix.
7	validation-strategy.md (merged into domain-driven-design.md §4)	—	Input validation layers, Valibot schemas, Hasura validation.
8	monorepo.md	151	Turborepo pipeline, caching, Docker build strategy, pnpm.
9	realtime-strategy.md	153	WebSocket, Hasura subscriptions, live updates.
10	ai.md	~100	RAG pipeline, agent workflows, Paperclip, MCP bridge.
11	communications.md	~60	Omnichannel inbox, notification pipeline, channel provisioning.
12	workflow-orchestration.md	282	BullMQ, event triggers, scheduled jobs, worker patterns.
13	gdpr-strategy.md	~110	Data retention, encryption, TTL policies, right to erasure.
14	tests.md	156	Testing strategy, Vitest, Playwright, offline testing.

🔍 What to Validate

• [ ] domain-driven-design.md §8 Context Map: does each upstream/downstream relationship still hold?
• [ ] roles.md: the Manager/Dispatcher/Driver trio — is the Driver auth flow documented anywhere?
• [ ] ai.md references Paperclip for agentic company governance — is this still the chosen platform?
• [ ] monorepo.md references 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.md lists apps/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 chosen?
• [x] validation-strategy.md at 3 KB — is this complete, or does it need expanding? Resolved: merged into domain-driven-design.md §4.
• [ ] workflow-orchestration.md at 18 KB — does it still reflect the actual NestJS worker patterns?

🗺️ Mindmap & Path Optimization

Grab your pen and paper:

• [ ] Map the Data Flow: Draw how an incoming GraphQL request passes through validation, hits the database, triggers a Hasura event, and processes via BullMQ.
  • Observation: To understand this single flow, a developer must read domain-driven-design.md (§3–§5) + workflow-orchestration.md.
  • Optimization: Should we consolidate? Partially resolved: database.md and validation-strategy.md merged into domain-driven-design.md.
• [ ] Check Frontend Fragmentation: How does a developer know where to put a Vue component?
  • Observation: They must cross-reference frontend.md (high-level), app-structure.md (292 lines of details), and design-system.md.
  • Optimization: Could we consolidate these into a single UI_ARCHITECTURE.md?

📝 Findings & Actions

Severity	File / Topic	Issue & Optimization Potential	Action Required

---

< Prev | Up: Session Overview | Next >