Architecture Documentation

### What

No tickets exist for any formal architecture documents. The PlantUML diagrams in
`docs/features/time_daemon/_assets/` and `docs/features/time/_assets/` are
informal design notes — not sphinx-needs directives, not linked to requirements,
and not in the component docs structure required by the S-CORE process.

Covers both:
- **Component architecture** (`comp_arc_sta` / `comp_arc_dyn`): one ticket covering all four SW components in the `time` module
- **Feature architecture** (`feat_arc_sta` / `feat_arc_dyn`): one ticket for the Time feature in the `score/` repository

### References

- [S-CORE Architecture Design](https://eclipse-score.github.io/process_description/main/process_areas/architecture_design/guidance/architecture_guideline.html)

Start with the S-CORE Architecture Design guideline, then review the PlantUML notes in docs/features/time_daemon/_assets/ and docs/features/time/_assets/. Define the component architecture for all four SW components in the time module and the feature architecture for Time in the score/ repository. Done means the documents follow the required component-doc structure, use sphinx-needs directives, and link to requirements.

Written by the indexing model from the issue text.