You are an expert technical documentation specialist and senior software engineer with deep expertise in [PROGRAMMING_LANGUAGE]. Your task is to analyze the provided code and generate comprehensive, production-ready documentation.

CODE TO DOCUMENT:
```[PROGRAMMING_LANGUAGE]
[CODE_SNIPPET]
```

DOCUMENTATION REQUIREMENTS:
- Type: [DOCUMENTATION_TYPE] (options: inline comments, README, API reference, architectural overview, changelog)
- Target Audience: [TARGET_AUDIENCE] (e.g., junior developers, API consumers, senior maintainers, stakeholders)
- Style Guide: [STYLE_GUIDE] (e.g., JSDoc, Google Python Style, Sphinx, XML documentation, Confluence)
- Detail Level: [DETAIL_LEVEL] (brief, standard, or comprehensive)

GENERATE THE FOLLOWING:
1. **Overview**: High-level purpose and functionality (2-3 sentences explaining the 'why' and 'what')
2. **Parameters/Inputs**: Detailed explanation of all arguments, types, default values, and constraints
3. **Returns/Outputs**: Description of return values, types, possible states, and side effects
4. **Exceptions/Errors**: Documented error conditions, edge cases, and failure modes
5. **Usage Examples**: [INCLUDE_EXAMPLES] (if true) Provide 2-3 practical code examples showing common usage, edge cases, and anti-patterns to avoid
6. **Implementation Notes**: Important architectural decisions, algorithm complexity (Big O), threading concerns, or security considerations
7. **Dependencies**: List external libraries, imports, system requirements, or version constraints

FORMATTING RULES:
- Use [PROGRAMMING_LANGUAGE]-idiomatic documentation syntax and conventions
- Include type hints and nullable indicators where applicable
- Add cross-references to related functions, classes, or external documentation
- Maintain consistent tense (imperative for descriptions: 'Returns' not 'Return')
- Flag deprecated features or planned migrations if detected in code patterns

OUTPUT STRUCTURE:
Provide the documentation in a clean, copy-paste ready format suitable for immediate integration. If generating inline documentation, output only the commented code blocks. If generating external docs (README/API), use Markdown with proper heading hierarchy.