fkrebs/nexa
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Resolve Q6/Q7/Q8/Q9/Q11; pin actual list names; add host tuning suggestions

Browse Source 
Verified from screenshots:

- Q6/Q7 → Lists & calendars discovered by NAME, not by ID. Names confirmed:
  "Persönlich" (personal), "DLR" (work), "Einkaufsliste" (shopping),
  "Wunschliste" (wishes). Self-healing: #nexa:config runs daily and on
  cache-miss, so user-added lists become routable without code changes.
  Routing logic in docs/07 expanded from 2-way to 4-way switch with a
  Resolver step that consults the Qdrant _config cache before fanning out;
  default route is "Persönlich" when SAIA confidence < 0.7.
- Q8 → Single Nextcloud Mail account fkrebs@nucli.de. No separate IMAP.
  The "Waiting" folder is honored as a manual user signal — items there are
  excluded from digest.
- Q9 → Pocket-ID SSO is global at the Zoraxy layer; Nexa surfaces inherit
  it. No app-level basic-auth. Q10 folded in.
- Q11 → Capacity confirmed: 22 threads (Core Ultra 7 155H), 62 GiB RAM
  (~32 GiB used, ~24 GiB of which is ZFS ARC), 1.64 TiB disk (0.35%).
  Phase-3 budget (~7 GB) is comfortable; two levers documented (raise
  LXC cap, or cap zfs_arc_max). Earlier "16 CPU" references corrected.

Propagation:
- system_prime.txt rewritten with the four context labels and the new
  list names; legacy NC_LIST_ID_* placeholders removed.
- docs/04 integration matrix uses the German names directly.
- docs/05 documents that #nexa:config also runs scheduled and on
  cache-miss, with the example output reflecting real list IDs.
- docs/09 step 6 mirrors the same flow + lists the Waiting-folder
  semantics.
- CLAUDE.md gets an authoritative block of homelab decisions so future
  agents don't re-litigate any of these.

New section in docs/12 (#17–25): Proxmox host tuning suggestions
based on the live node summary — cap ZFS ARC (frees ~16 GiB),
enable KSM (~1-3 GiB savings across 40 containers), suppress the
no-subscription banner, drop swappiness, verify scrub/SMART/fstrim
timers, NTP via AdGuard.
This commit is contained in:
Claude
2026-05-04 22:08:10 +00:00
parent e1c2ba96e2
commit 0b470b3e12
8 changed files with 100 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
nexa-core/ai-prompts/system_prime.txt
+10 -5
View File
@@ -3,11 +3,16 @@ Rolle: Zentrales Nervensystem
Aufgabe: Überwacht E-Mails, kuratiert Wissen und plant Tasks.
WICHTIGE LOGIK:
- Tasks müssen strikt zwischen "Work" und "Personal" unterschieden werden.
- Analysiere den Inhalt eines Memos: Bezieht es sich auf professionelle Projekte (Obsidian Context) -> Work List. Bezieht es sich auf Haushalt, Einkäufe oder Freizeit -> Personal List.
- Im Zweifel: Nachfragen via Memos-Kommentar.
- Tasks werden auf vier Nextcloud-Listen geroutet: "DLR" (Arbeit), "Persönlich", "Einkaufsliste", "Wunschliste".
- Analysiere den Inhalt eines Memos und entscheide über das Feld "context": "work" | "personal" | "shopping" | "wishes".
- work -> Liste "DLR" (Beruf, Projekte, Meetings, Deadlines, Forschung).
- personal -> Liste "Persönlich" (Alltag, Familie, Termine, Behördenkram).
- shopping -> Liste "Einkaufsliste" (Lebensmittel, Drogerie, Verbrauchsgüter).
- wishes -> Liste "Wunschliste" (Hobby, Technik, Bücher, Geschenkideen).
- Listennamen sind dynamisch — bei Bedarf werden weitere Listen vom Runtime-Config eingespeist, dann darfst du auch deren Namen als context vorschlagen.
- Im Zweifel (Konfidenz < 0.7): Default auf "personal" und Nachfrage via Memos-Kommentar.
KONSUM-LOGIK:
- Wenn ein Link von Karakeep kommt, analysiere das Produkt.
- Haushaltswaren/Verbrauchsgüter -> NC_LIST_ID_SHOPPING.
- Besondere Wünsche/Hobby/Technik -> NC_LIST_ID_WISHES.
- Haushaltswaren/Verbrauchsgüter -> context "shopping".
- Besondere Wünsche/Hobby/Technik -> context "wishes".