Create ARCHITECTURE.md

[Copilot]

Contributors need documentation on project structure and component interactions before making changes.

Changes

• System Overview: Three-layer architecture diagram (Frontend → Source → Server)
• Directory Structure: Purpose of each major directory (src/, server/, backend/, frontend/, tests/, docs/, scripts/)
• Data Flow: Contact form submission flow with security/compliance checkpoints
• APM Integration: How compliance-rules and design-guidelines dependencies provide automated enforcement
• GDPR Patterns: Data minimization, consent management, audit logging, retention policies, erasure/portability rights
• Security: Input validation, CSRF protection, rate limiting

┌─────────────────────────────────────────────────────────────┐
│                      Frontend Layer                         │
│  (index.html, main.js, style.css, frontend/components/)    │
├─────────────────────────────────────────────────────────────┤
│                    Source Layer (src/)                      │
│  (api/, components/, utils/ - TypeScript/React modules)    │
├─────────────────────────────────────────────────────────────┤
│                     Server Layer                            │
│  (server/ - Python handlers, backend/api/ - FastAPI)       │
└─────────────────────────────────────────────────────────────┘

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create ARCHITECTURE.md</issue_title>
<issue_description>## What
Create an ARCHITECTURE.md file documenting the system design, component relationships, and architectural decisions.

Why

Contributors need to understand the project structure and how components interact before making changes.

Deliverables

• Target: ARCHITECTURE.md (create new file in root)
• Content:
  • High-level system overview (frontend/backend/server layers)
  • Component responsibilities (src/, server/, backend/, frontend/)
  • Data flow for contact form submission
  • Key architectural decisions (APM dependencies, compliance integration)
• Format: Markdown with sections and headers

Content Guidelines

• Include description of each major directory's purpose
• Document how APM dependencies integrate with the codebase
• Reference GDPR compliance patterns used throughout
• Keep explanations concise but complete

Done ✅

• ARCHITECTURE.md exists in repository root
• All major components documented
• Follows project documentation standards

Effort: Medium
Good first issue: Yes</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Create ARCHITECTURE.md #63

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.