windyboy
daf4aa3dfa
- Created Methodology.md to outline the P.A.R.A. system and its components. - Added Outline.md for a structured overview of P.A.R.A. content. - Documented PKM content organization decisions in PKM-Consolidation-Decision.md. - Introduced Workflows.md to explain practical applications of P.A.R.A. in work scenarios. - Moved sensitive information to security-sensitive folder and restructured the Personal folder to align with P.A.R.A. principles. - Archived backup files including Matrix Me.md and TTG Cookies.md. - Implemented a comprehensive refactor of the Personal folder to improve organization and security.
45 lines
1.1 KiB
Markdown
Executable File
45 lines
1.1 KiB
Markdown
Executable File
|
|
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.
|
|
|
|
|
|
|
|
```
|
|
|
|
|