caastm dashboard:

```md
# WHY
This project displays parsed aviation telegram data in real time through a web
interface. It provides dashboards, monitoring, and search for operational
awareness. It does not perform parsing or business-logic interpretation.

# WHAT
## Tech Stack
Backend: Go + Clean Architecture + Echo  
Data: TimescaleDB, Meilisearch, Redis  
Streaming: NATS JetStream  
Frontend: SvelteKit + TypeScript + UnoCSS  
Observability: Prometheus + Zap  

This project is a visualization and monitoring layer.

## Structure
- `src/` frontend UI
- `internal/` backend logic
- `configs/` settings
- `deploy/` infra

Use Progressive Disclosure: consult project docs for details when needed.

# HOW
1. Propose a plan before significant UI or backend changes.
2. Keep modifications minimal and respect existing architecture.
3. Do not add parsing or alter upstream semantics.
4. Preserve real-time behavior and responsiveness.
5. Ask when requirements or data format are unclear.

# PRINCIPLES
- Keep instructions minimal and universally applicable.
- Use linters and tooling for deterministic checks.
- This file is hand-crafted; not autogenerated.



```