Claude
9b18e2710d
- /docs/ now contains 12 numbered guides + index.md (navigator).
- Old duplicates removed: nexa-core/doc/, DEPLOYMENT.md, PLAN.md,
config/{classification_logic,workflows_spec}.md.
- 09-deployment.md targets the running infra (LXC 104 docker host,
Zoraxy at 192.168.1.4, existing Memos/n8n/LiteLLM/Nextcloud/Qdrant)
rather than spinning a parallel stack; minimal-config approach.
- 11-open-questions.md tracks user-info-required blockers.
- 12-optimization-opportunities.md captures homelab tweaks.
- CLAUDE.md added so future agent runs know repo conventions and infra.
3.0 KiB
3.0 KiB
11 — Open Questions (user-info-required)
Items that block progress and need a human decision before a workflow can be implemented or a service deployed. Tick them off as you decide.
Architectural decisions
- Q1 — Graph DB choice. Phase 3.4 says Neo4j in 08 but the original deployment draft used Ontotext GraphDB. Recommendation: Neo4j (smaller footprint, Cypher is friendlier for n8n HTTP nodes, no SHACL/OWL needs identified). Confirm or override.
- Q2 — Reuse
qdrant_scientificor run a dedicatednexa-qdrant? Reuse keeps memory usage flat (~670 MB seen on Homepage); dedicated gives clean isolation and independent snapshot lifecycle. Recommendation: reuse with anexa_*collection prefix. - Q3 — Embeddings model. Default in
infra_manifest.yamlistext-embedding-3-small(OpenAI). Is the LiteLLM virtual key authorised to call it, or should we route to a self-hosted alternative (e.g.bge-m3via Ollama on the same host)? - Q4 — Obsidian sync mechanism.
system_prime.txtreferences Obsidian Context, but the current setup syncs via Nextcloud (nc.nuclide.systems→Notizenfolder, ~200 MB). Should Nexa watch the filesystem on LXC 105 (NC data dir) or the Nextcloud WebDAV API? FS is cheaper, WebDAV is portable. - Q5 — Karakeep vs. Hoarder naming. The Zoraxy host is
hoarder.nuclide.systemsbut the container iskarakeep-*and Homepage labels it Karakeep. They're the same product (rename in 2024). Pick one display name to use in docs and prompts.
Identifiers needed (auto-discoverable, but list now if known)
- Q6 — Nextcloud Tasks list IDs for:
Work_Tasks,Personal_Tasks,Shopping,Wishes. Discovery via#nexa:configwill fill these — confirm names match. - Q7 — Nextcloud Calendar IDs for:
Work_Calendar, primary personal calendar. - Q8 — IMAP credentials for the personal mail account. Can n8n reuse a Nextcloud Mail account (preferred — no extra password) or must we add a dedicated IMAP entry?
- Q9 — ntfy topic name for
nexa.system. Is the topic public onntfy.nuclide.systemsor should it be authenticated? - Q10 — Pocket-ID role.
id.nuclide.systemsis running. Do we want SSO in front of the n8n / Memos UIs, or skip for now?
Hardware / capacity
- Q11 — RAM headroom on docker host. Homepage shows 29.5 GiB free out of ~31 GiB total, ~8.5 GB used. Phase-3 Qdrant indexing of Obsidian + Memos history is fine here, but a Phase-3.4 GraphDB choice changes this (Neo4j ~2 GB heap, Ontotext ~4 GB). Confirm acceptable.
- Q12 — S3 archive bucket.
s3.nuclide.systemsis up. Bucket name + access key for Qdrant snapshots?
Process
- Q13 — Octoprint container is Exited (Homepage). Out of scope for Nexa, but flagging it because Phase 5 monitoring would alert on it. Suppress, or is it intentional?
- Q14 —
Missing Widget Type: zoraxyon Homepage — Homepage doesn't have a Zoraxy widget yet. Cosmetic, unrelated to Nexa.