# Module Boundary Analysis

## Context

Module: {{MODULE_NAME}}
Domain: {{DOMAIN}}
Other module READMEs: {{OTHER_MODULES}}

## Instructions

Analyze how the proposed {{MODULE_NAME}} module fits within the existing module landscape.

1. Read ALL other module READMEs at the paths above
2. For each existing module, extract:
   - Module purpose and scope
   - Key entities it owns
   - Features it provides
3. Analyze boundaries:
   - What entities might be shared with existing modules?
   - What dependencies will this module have on others?
   - What dependencies might others have on this module?
   - Are there potential scope overlaps?

## Boundary Checks

| Check                | Question                                                |
| -------------------- | ------------------------------------------------------- |
| entity_ownership     | Which entities are new vs shared with existing modules? |
| scope_overlap        | Does this domain overlap with existing module scopes?   |
| dependency_direction | What are the expected dependency directions?            |
| integration_points   | Where will this module need to integrate with others?   |

## Output Format

Return your analysis as a structured markdown report:

### Existing Module Landscape

Table of existing modules with columns: Module, Relationship (none/depends_on/depended_by/overlaps), Detail

### Shared Entities

Table with columns: Entity, Owned By, Referenced By

### Boundary Concerns

Table with columns: Concern, Severity (high/medium/low), Recommendation

### Integration Points

Table with columns: With Module, Type (data_reference/command_call/event), Description
