# Epic 3: Module Framework (Feature Services)

## Overview
Design and implement the module framework for feature services. Modules are implemented as independent services with their own entry points (`cmd/{service}/`), gRPC servers, and database schemas. The framework provides module interfaces, service registration, permission code generation, and CLI tooling for service management.

**Key Principle:** Modules are services - each module is an independently deployable service that registers with Consul and communicates via service clients.

## Stories

### 3.1 Module System Interface and Service Registry
- [Story: 3.1 - Module System Interface](./3.1-module-system-interface.md)
- **Goal:** Design module interface for feature services with service registration and dependency resolution.
- **Deliverables:** Module interface, module manifest, service registration integration

### 3.2 Permission Code Generation System
- [Story: 3.2 - Permission Code Generation](./3.2-permission-code-generation.md)
- **Goal:** Create automated permission code generation from module manifests to ensure type-safe permission constants.
- **Deliverables:** Permission generation script, Go generate integration, Makefile integration

### 3.3 Service Loader and Initialization
- [Story: 3.3 - Service Loader](./3.3-module-loader.md)
- **Goal:** Implement service loading and initialization for feature services with dependency resolution.
- **Deliverables:** Service loader, service initialization, FX lifecycle integration, Consul registration

### 3.4 Service Management CLI Tool
- [Story: 3.4 - Service CLI](./3.4-module-cli.md)
- **Goal:** Provide CLI tooling for managing feature services, validating dependencies, and testing service loading.
- **Deliverables:** CLI tool, Makefile integration

### 3.5 Service Registry and Discovery
- [Story: 3.5 - Service Registry](./3.5-service-registry.md)
- **Goal:** Implement Consul-based service registry for service discovery (already implemented in Epic 1, verify integration).
- **Deliverables:** Service registry interface verification, Consul integration verification

## Deliverables Checklist
- [ ] Module interface for feature services
- [ ] Service registration with Consul
- [ ] Permission code generation tool
- [ ] Service loader with dependency resolution
- [ ] Service initialization in service entry points
- [ ] CLI tool for service management
- [ ] Service registry integration verified

## Acceptance Criteria
- Feature services can register via module interface
- Permission constants are generated from `module.yaml`
- Services load in correct dependency order
- Service migrations run on startup
- Services register with Consul automatically
- `platformctl services list` shows all services
- Integration test: load multiple services and verify Consul registration