Component responsibilities
These functional areas organise the proposed architecture documentation. They do not prescribe service names or deployment units.
| Area | Responsibility to document |
|---|---|
| Regulatory configuration and resolution | Manage configured packages and connect them to relevant context |
| Entity context | Capture and reuse organisational information |
| Incident and impact intake | Collect facts and expose missing information |
| Qualification and decisions | Evaluate configured models and explain outcomes |
| Reporting lifecycle | Prepare packages, track stages and support follow-up |
Storage, reasoning engines, operational services and system integrations belong to the implementation track. Shared contracts should document information crossing these boundaries.