Claude
250a5cb2a6
- UNAS layout decoded from the user's tree: services/<svc>/ is the homelab-wide docker config store (every container follows the same pattern — immich, karakeep, nextcloud, ntfy, paperless-ai, pocketid, shelfmark, stremio, traccar, vaultwarden, gluetun). Nexa MUST follow the same pattern at services/nexa/. backup/<svc>/ for snapshots. Pinned in CLAUDE.md and docs/12 #31. - Stale services flagged for retirement: services/siyuan/ (migrated to Obsidian) and services/open-webui/ (unused, only LobeHub is alive). Drops the "two LLM UIs" item (#15) — it's now "retire open-webui". - Hard-blocklist for any Nexa indexer pinned in CLAUDE.md: _sortMe/wallet/**, *.gpg/asc/key/pem/kdbx/credentials/secret, plus the Nextcloud appdata dir. - Three new "future user-facing wins" surfaced from the tree: Paperless-AI as a Phase-2.x triage helper for _sortMe/Downloads/, media/Recipes/ (~300 entries) as the showcase RAG corpus, and Paperless-AI's existing ChromaDB as a potential read-from source rather than re-embedding scanned docs. - Housekeeping campaign in docs/12 §35-37: consolidate postgres, audit UNAS-everywhere, S3 archive tier on s3.nuclide.systems. - Phase 6 added to the roadmap: "Nexa as homelab steward". Polls Dockge/docker/Proxmox, diffs vs documented state, emits a daily drift report. Most of the housekeeping campaign becomes semi-automatic once 6.1-6.3 ship. - New docs/13-information-wishlist.md packages the still-needed inventory as 5-6 paste-and-run tasks, each with explicit "📍 Where" markers (which shell or which UI) and what it unblocks. Highest leverage = Task 1 (read an existing compose stack to lock Q19). - docs/index.md TOC extended to 13 rows. Also fixed numbering drift in docs/12 (duplicate #28, missing #17/#18) and added Q19 to docs/11 covering the SMB-share verification step.
61 lines
4.3 KiB
Markdown
61 lines
4.3 KiB
Markdown
# 02 — Roadmap & Phases
|
||
|
||
Iterative build-out, value-first. Each phase is shippable on its own.
|
||
|
||
## Phase 1 — The Spine (connectivity)
|
||
|
||
**Focus:** datapath between Memos, n8n and SAIA.
|
||
**Milestone:** Nexa replies on Memos and answers simple questions.
|
||
|
||
- [ ] **1.1 Memos ↔ n8n bridge** — webhook ingress, content filter, comment-back.
|
||
- [ ] **1.2 SAIA integration** — call LiteLLM proxy from n8n; chat via Memos comments.
|
||
- [ ] **1.3 Git-sync** — periodic export of n8n workflows into this repo.
|
||
|
||
## Phase 2 — Senses (input channels)
|
||
|
||
**Focus:** e-mail filter and the Work-vs-Personal router.
|
||
**Milestone:** Nexa distinguishes work tasks from personal tasks without manual tags.
|
||
|
||
- [ ] **2.1 Email butler** — filter & summarize the ~20 daily personal mails.
|
||
- [ ] **2.2 RSS morning digest** — curated daily summary in Memos.
|
||
- [ ] **2.3 Bluesky antenna** — store liked posts as knowledge snippets.
|
||
|
||
## Phase 3 — Memory (Qdrant & RAG)
|
||
|
||
**Focus:** Qdrant + graph layer for retrieval-augmented answers.
|
||
**Milestone:** RAG works — Nexa answers from archived notes; images captured today are queued for visual indexing later.
|
||
|
||
- [ ] **3.1 Text RAG (Path A)** — TEI + `bge-m3`, single Qdrant collection `nexa_knowledge_text`. `#nexa:ask` reads it before answering. Image attachments are *recorded* as `nexa:Note` with `pendingVisualIndex` but not embedded yet.
|
||
- [ ] **3.2 Visual collection (Path C)** — swap TEI → infinity, add `jina-clip-v2`, create `nexa_knowledge_visual`, backfill all queued image notes. RAG workflow gets a parallel branch for visual hits. See [09 § "Phase add-on: visual collection"](./09-deployment.md#phase-add-on-visual-collection-phase-32).
|
||
- [ ] **3.3 S3 long-term archive** — Qdrant snapshots (both collections) to the S3 server.
|
||
- [ ] **3.4 Ontotext GraphDB** — SPARQL pillar; structural queries combined with vector hits in `#nexa:ask`. See [08](./08-graphrag-architecture.md).
|
||
|
||
## Phase 4 — Motor (organization & action)
|
||
|
||
**Focus:** calendar integration and time-boxing.
|
||
**Milestone:** Nexa proactively proposes morning focus slots in the work calendar.
|
||
|
||
- [ ] **4.1 Nextcloud Tasks sync** — bidirectional status sync (Memos ↔ NC Tasks).
|
||
- [ ] **4.2 Time-boxing agent** — calendar-aware slot suggestions.
|
||
- [ ] **4.3 Karakeep curation** — automated review cycle for saved links.
|
||
|
||
## Phase 5 — Daily integration (polish)
|
||
|
||
**Focus:** Home Assistant Voice and monitoring.
|
||
**Milestone:** Nexa speaks via HA-Voice and surfaces critical system states proactively.
|
||
|
||
- [ ] **5.1 HA Voice** — Wake-word integration, Wyoming protocol.
|
||
- [ ] **5.2 System monitoring** — Proxmox / Backrest alerts into the Memos system feed via ntfy.
|
||
|
||
## Phase 6 — Nexa as homelab steward
|
||
|
||
**Focus:** Nexa actively maintains the homelab inventory instead of being told manually.
|
||
**Milestone:** Nexa runs a daily *drift report* — what changed, what's stale, what's missing — and turns it into actionable comments under a pinned `[STEWARD]` memo.
|
||
|
||
- [ ] **6.1 Inventory sync** — Nexa polls Dockge / `docker ps` / Proxmox API on a schedule and stores the running-state snapshot in GraphDB (`nexa:Service`, `nexa:LastSeen`, `nexa:DataPath`, …).
|
||
- [ ] **6.2 Drift detection** — diff against the documented desired state in this repo (`docs/12`, `CLAUDE.md`, the housekeeping campaign at #35–37). Emit findings as structured Memos comments: *"`open-webui` last used 38 d ago — retire?"*, *"Container `foo` has no `services/foo/` bind — schedule UNAS migration?"*.
|
||
- [ ] **6.3 Steward commands** — `#nexa:retire <svc>` (tar to `backup/`, stop, archive the stack), `#nexa:document <svc>` (template a CLAUDE.md entry), `#nexa:wishlist-status` (which entries in [docs/13](./13-information-wishlist.md) are still needed).
|
||
- [ ] **6.4 Self-update of docs** — when the user resolves an open question via Memos, Nexa proposes the corresponding edit to `docs/11-open-questions.md` as a PR-ready diff (the doc itself becomes a Nexa-managed surface).
|
||
|
||
This phase is what turns Nexa from "an assistant that answers questions" into "an assistant that takes care of its own runtime", and it's the natural home for the cross-cutting [housekeeping campaign](./12-optimization-opportunities.md#housekeeping-campaign-cross-cutting-do-together) — most of those items become semi-automatic once 6.1–6.3 ship.
|