---
title: Obsidian Data Accuracy Audit
area: atlas-reports
tags: [obsidian, data-quality, infrastructure, audit]
created: 2026-05-27
status: completed
---

# Obsidian Data Accuracy Audit

## Scope

Pass over the shared Obsidian vault for stale infrastructure/model claims, prompted by the wrong local LLM model in [[Infrastructure/Architecture]].

Vault path checked:

`/home/will/lab/swarm/swarm-common/obsidian-vault/will/will-shared-zap`

## Live evidence checked on 2026-05-27

- Local llama.cpp service: `llama-server.service` active on `18806`.
- `/v1/models` on `http://127.0.0.1:18806` returned current model id:
  - `gemma-4-26B-A4B-it-UD-IQ2_M.gguf`
- Ollama on `18807` includes `nomic-embed-text:latest` for embeddings and older chat models; it is not the direct local LLM endpoint used by llama.cpp.
- Hermes default model config: `openai-codex` / `gpt-5.5`.
- Current host IPs include `192.168.153.130`, `192.168.153.141`, and Tailscale `100.123.88.127`.
- Vault path is on host btrfs (`/home`), not currently a VM `virtiofs` mount.
- n8n on `18808` returned HTTP 200.
- MinIO health at `192.168.153.253:9000` returned HTTP 200.
- Hermes cron job `atlas-minio-self-backup` is enabled, scheduled daily at 02:50, and last status was `ok`.

## Updated during this pass

- [[Infrastructure/Architecture]]
  - Corrected local LLM from Gemma 3 to `gemma-4-26B-A4B-it-UD-IQ2_M.gguf`.
  - Corrected Hermes model from `gpt-5.4` to `gpt-5.5` via `openai-codex`.
  - Marked OpenClaw VM / `virtiofs` details as historical.
  - Corrected current host IPs, MinIO bucket purpose, Gitea repo references, and local model verification command.
- [[Infrastructure/Automation/Cron Jobs]]
  - Marked the old OpenClaw cron inventory as stale/historical.
  - Added current Hermes cron/MinIO backup details from live `cronjob list`.
- [[Resources/Service Catalog]]
  - Refreshed high-risk local service rows: SearXNG, LiteLLM, Brave MCP, whisper containers, direct local LLM model id.

## Previously blocked edits completed

Will repaired the permissions on the previously blocked files. On the follow-up pass, ownership was verified as `will:will` and the stale active-note claims were corrected in:

- [[Infrastructure/Services/Docker Services]]
  - Updated old LAN host references from `192.168.153.113` / `.117` to current local/LAN endpoints.
  - Updated llama.cpp model from `gemma-3-12b-it-q4_0.gguf` to `gemma-4-26B-A4B-it-UD-IQ2_M.gguf`.
  - Updated MinIO backup wording from current OpenClaw `zap` backups to current Atlas/Hermes `atlas` backups with legacy `zap` noted.
- [[Infrastructure/Automation/n8n IMAP Triage Pipeline]]
  - Updated model and endpoint to the current Gemma 4 / `18806` endpoint.
  - Marked old `claw`/`openclaw` VM ownership checks as historical.
- [[Infrastructure/Automation/n8n Nightly Vault Sync]]
  - Updated local LLM and health URLs to current local endpoints.

## Historical snapshot notes

Many `Notes/YYYY-MM-DD Nightly Vault Sync.md` files contain the old Gemma 3 model id and old VM/virtiofs/IP state. I did **not** rewrite those because they are dated snapshots. They should be read as historical breadcrumbs, not canonical current-state docs.

## Search patterns used

Searched current vault markdown for local-model and infrastructure drift terms including:

- `gemma-3-12b`, `gemma 3`, `gpt-5.4`
- `192.168.153.113`, `192.168.153.117`
- `~/.openclaw`, `openclaw.json`, `bucket zap`
- local service ports `18801`–`18814`, `27123`
