AAC: Improve UI diagrams -- pages, functional constructs, relationships, navigation #7
Description
Goal
Improve Architecture-as-Code (AaC) UI diagrams. Current output shows class-oriented shapes; we need user-facing views.
Scope
- Capture pages (routes/screens)
- Model functional constructs (FP pipelines, pure functions)
- Show relationships (data and event flow)
- Add navigation map (global and intra-feature)
Acceptance
- Diagram includes page inventory (C4-style where relevant)
- FP constructs represented (legend and notation)
- Relationships annotated (direction and data/event)
- Navigation map generated from source metadata
- Docs updated with usage and examples