Copaw Analysis

Step 2: Read Source Files

For each target module, read:

1. The main implementation file(s)
2. The __init__.py for public API surface
3. Related test files in tests/
4. Any referenced utility modules

Step 3: Map Architecture

Produce a structured analysis:

Module Summary

## [Module Name]

### Purpose
[One paragraph: what problem does this solve?]

### Key Classes/Functions
- `ClassName` - [responsibility]
- `function_name()` - [what it does]

### Data Flow
[Mermaid sequence diagram or flowchart]

### Dependencies
- Internal: [other CoPaw modules used]
- External: [third-party libraries]

### State Management
- [What state is stored, where, and how]

### Error Handling
- [How errors are propagated and recovered]

Step 4: Go Implementation Recommendations

Based on the analysis, recommend:

1. Go package placement: Which internal/ package should hold this?
2. Interface design: What Go interfaces should be defined?
3. Key differences: What should NOT be directly translated?
4. Risks: What parts are complex or error-prone?
5. Priority: What to implement first for a working MVP?

Module Map Reference

For detailed file paths and module relationships, see reference.md.