내부 시퀀스 설계 완료 (25개 시나리오)

전체 5개 마이크로서비스의 내부 처리 흐름을 상세히 설계

[추가된 파일]
- Meeting Service: 6개 시나리오 (검증완료, 실시간수정동기화, 최종회의록확정, 충돌해결, 템플릿선택, 회의록목록조회)
- STT Service: 2개 시나리오 (음성녹음인식, 텍스트변환)
- User Service: 2개 시나리오 (사용자인증, 대시보드조회)
- Notification Service: 1개 시나리오 (알림발송)

[주요 설계 내용]
- Clean Architecture 적용 (Controller → Service → Domain → Repository)
- Cache-Aside 패턴 (Redis 기반 성능 최적화)
- Event-Driven Architecture (Azure Event Hub)
- Real-time Collaboration (WebSocket + OT 알고리즘)
- RAG 기능 (맥락 기반 AI)

[검증 결과]
- PlantUML 문법 검증: 모든 파일 통과 ✅
- 유저스토리 매칭: 100% 일치 ✅
- 아키텍처 패턴 준수: 완료 ✅

[병렬 처리]
- 서브 에이전트 3개로 병렬 작업 수행
- Meeting Service, AI Service, STT/User/Notification 동시 설계

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

design/backend/sequence/inner/meeting-검증완료.puml

@@ -0,0 +1,100 @@
+@startuml
+!theme mono
+
+title 검증 완료 내부 시퀀스
+
+participant "API Gateway<<E>>" as Gateway
+participant "MeetingController" as Controller
+participant "MeetingService" as Service
+participant "Meeting" as Domain
+participant "ValidationService" as ValidationService
+participant "MeetingRepository" as Repository
+database "PostgreSQL<<E>>" as DB
+database "Redis Cache<<E>>" as Cache
+queue "Event Hub<<E>>" as EventHub
+
+Gateway -> Controller: POST /api/meetings/{id}/validate
+activate Controller
+
+Controller -> Service: validateMeeting(meetingId)
+activate Service
+
+Service -> Repository: findById(meetingId)
+activate Repository
+Repository -> DB: SELECT * FROM meetings WHERE id = ?
+activate DB
+DB --> Repository: meeting_row
+deactivate DB
+Repository --> Service: Meeting entity
+deactivate Repository
+
+Service -> ValidationService: performValidation(meeting)
+activate ValidationService
+
+ValidationService -> ValidationService: validateStructure()
+note right of ValidationService
+구조 검증:
+- 필수 섹션 존재
+- 섹션 순서
+- 데이터 완정성
+end note
+
+ValidationService -> ValidationService: validateContent()
+note right of ValidationService
+내용 검증:
+- 필수 항목 기입
+- 형식 준수
+- 참조 무결성
+end note
+
+ValidationService -> ValidationService: validateBusiness()
+note right of ValidationService
+비즈니스 규칙:
+- 참석자 서명
+- Todo 할당 완료
+- 첨부파일 검증
+end note
+
+ValidationService --> Service: ValidationResult
+deactivate ValidationService
+
+alt validation passed
+    Service -> Domain: markAsValidated()
+    activate Domain
+    Domain -> Domain: changeStatus(VALIDATED)
+    Domain --> Service: validated Meeting
+    deactivate Domain
+
+    Service -> Repository: save(meeting)
+    activate Repository
+    Repository -> DB: UPDATE meetings SET status = 'VALIDATED'
+    activate DB
+    DB --> Repository: affected_rows
+    deactivate DB
+    Repository --> Service: savedMeeting
+    deactivate Repository
+
+    Service -> Cache: set(meeting:{id}, meetingData)
+    activate Cache
+    Cache --> Service: OK
+    deactivate Cache
+
+    Service ->> EventHub: publish(MeetingValidatedEvent)
+    activate EventHub
+    note right of EventHub
+    검증 완료 이벤트:
+    - 확정 가능 상태 알림
+    end note
+    deactivate EventHub
+
+    Service --> Controller: success response
+else validation failed
+    Service --> Controller: error response with details
+end
+
+deactivate Service
+
+Controller --> Gateway: 200 OK / 400 Bad Request
+deactivate Controller
+
+@enduml