windyboyandClaude Sonnet 4.5
9f6e62676e
Resolved 48 identified issues across 5 remediation batches: Critical Fixes (2/2 = 100%): - Removed duplicate "System Architec" directory with 4 archived files - Fixed broken PARA Notes wikilinks in 2 Outline.md files High Priority (14/15 = 93%): - Consolidated 10+ duplicate file pairs to canonical locations - Added frontmatter to 30 files in 200-area (now 100% coverage) - Relocated orphaned image with updated reference - Removed security-sensitive file duplicates Medium Priority (32/41 = 78%): - Deleted 4 empty files (0-15 bytes each) - Relocated misplaced files to proper PARA categories - Improved archive organization structure File Changes: - Modified: 33 files (frontmatter + wikilink fixes) - Moved: 16 files (to archive or new locations) - Deleted: 6 files (duplicates after archival) - Created: 25 files (archived copies + documentation) Vault Health Improvement: - Frontmatter coverage: 43% → 75% - Broken wikilinks: 2 → 0 - Duplicate files: 10+ → 0 - Empty files: 4 → 0 - Overall health score: 6.5/10 → 8.5/10 Documentation: - Created comprehensive remediation plan and batch reports in copilot/ - All changes tracked with detailed change reports - No data loss - duplicates archived, not deleted 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1.1 KiB
Executable File
1.1 KiB
Executable File
caastm dashboard:
# 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.