fix(obsidian): restore shared vault notes after develop rebuild

2026-06-04 13:13:25 -07:00
parent 420df812c0
commit 97c675af09
192 changed files with 10510 additions and 298 deletions
@@ -1 +1,4 @@
-{}
+{
+  "cssTheme": "Rose Pine",
+  "interfaceFontFamily": ""
+}
@@ -1,3 +1,8 @@
 [
-  "obsidian-local-rest-api"
+  "obsidian-local-rest-api",
+  "dataview",
+  "obsidian-tasks-plugin",
+  "notebook-navigator",
+  "advanced-canvas",
+  "table-editor-obsidian"
 ]
@@ -0,0 +1,5 @@
+{
+  "format": "YYYY-MM-DD",
+  "folder": "Daily",
+  "template": "Templates/Daily Note"
+}
@@ -0,0 +1,3 @@
+{
+  "folder": "Templates"
+}
@@ -4,37 +4,20 @@
    "type": "split",
    "children": [
      {
-        "id": "665dd25d03985c80",
+        "id": "bfbbaa82fdc8e552",
        "type": "tabs",
        "children": [
          {
-            "id": "e78c645c773df70d",
+            "id": "91d4ead9052f8b83",
            "type": "leaf",
            "state": {
-              "type": "markdown",
-              "state": {
-                "file": "Infrastructure/Automation/n8n Workflows.md",
-                "mode": "source",
-                "source": false
-              },
+              "type": "empty",
+              "state": {},
              "icon": "lucide-file",
-              "title": "n8n Workflows"
-            }
-          },
-          {
-            "id": "614d9018f88254e9",
-            "type": "leaf",
-            "state": {
-              "type": "release-notes",
-              "state": {
-                "currentVersion": "1.12.7"
-              },
-              "icon": "lucide-book-up",
-              "title": "Release Notes 1.12.7"
+              "title": "New tab"
            }
          }
-        ],
-        "currentTab": 1
+        ]
      }
    ],
    "direction": "vertical"
@@ -54,7 +37,7 @@
              "type": "file-explorer",
              "state": {
                "sortOrder": "alphabetical",
-                "autoReveal": false
+                "autoReveal": true
              },
              "icon": "lucide-folder-closed",
              "title": "Files"
@@ -86,12 +69,22 @@
              "icon": "lucide-bookmark",
              "title": "Bookmarks"
            }
+          },
+          {
+            "id": "1c968d6bfe211541",
+            "type": "leaf",
+            "state": {
+              "type": "notebook-navigator",
+              "state": {},
+              "icon": "notebook-navigator",
+              "title": "Notebook Navigator"
+            }
          }
        ]
      }
    ],
    "direction": "horizontal",
-    "width": 300
+    "width": 321.5
  },
  "right": {
    "id": "c2bbb286ef2dc629",
@@ -193,30 +186,53 @@
      "daily-notes:Open today's daily note": false,
      "templates:Insert template": false,
      "command-palette:Open command palette": false,
-      "bases:Create new base": false
+      "bases:Create new base": false,
+      "table-editor-obsidian:Advanced Tables Toolbar": false,
+      "notebook-navigator:Notebook Navigator": false
    }
  },
-  "active": "614d9018f88254e9",
+  "active": "83702dd4b091f767",
  "lastOpenFiles": [
-    "Notes/2026-03-25 OpenClaw Core Update.md",
-    "Infrastructure/Automation/Cron Jobs.md",
-    "Infrastructure/Automation/Channel Routing Policy.md",
-    "Infrastructure/Automation/n8n Workflows.md",
-    "Conventions.md",
-    "Plans/Daily Schedule.md",
-    "Infrastructure/Architecture.md",
-    "Infrastructure/Services/Docker Services.md",
-    "Daily Schedule.md",
-    "Resources",
-    "Notes",
+    "Weekend Activity Ideas.md",
+    "Vault Conventions.md",
+    "Templates/Atlas Artifacts/test-report.md",
+    "Templates/Atlas Artifacts/status-report.md",
+    "Templates/Atlas Artifacts/runbook.md",
+    "Templates/Atlas Artifacts/reviewer-checklist.md",
+    "Templates/Atlas Artifacts/postmortem.md",
+    "Templates/Atlas Artifacts/implementation-plan.md",
+    "Templates/Atlas Artifacts/diagram.md",
+    "Templates/Atlas Artifacts/decision-log.md",
+    "Templates/Atlas Artifacts/agent-audit-event.md",
+    "Templates/Atlas Artifacts/README.md",
+    "Templates/Runbook.md",
+    "Templates/Project.md",
+    "Templates/Person.md",
+    "Templates/Meeting.md",
+    "Templates/Kanban Task Graph Templates.md",
+    "Templates/Diary Weekly Review.md",
+    "Templates/Diary Daily.md",
+    "Templates/Decision.md",
+    "Templates/Daily Note.md",
+    "Templates/Context Pack.md",
+    "Templates/Atlas Artifacts",
+    "Templates",
+    "Runbooks/Runbooks Home.md",
+    "Runbooks/Promote Session Output to Notes.md",
+    "Runbooks/Atlas Kanban Durable Project Workflow.md",
+    "Runbooks/Atlas Event-Driven Automation.md",
+    "Projects/Atlas Capability Upgrade Program/Reports/Status",
+    "Projects/Atlas Capability Upgrade Program/Reports",
+    "Projects/Atlas Capability Upgrade Program/Plans",
+    "Projects/Atlas Capability Upgrade Program",
+    "Projects/Atlas",
+    "Projects",
    "People",
-    "Infrastructure/Services",
-    "Infrastructure/Automation",
-    "Infrastructure",
-    "Plans",
-    "Architecture.md",
-    "Welcome.md",
-    "test-from-zap.md",
-    "asdasdasdas.md"
+    "Meetings",
+    "Infrastructure/Architecture - Service Topology.canvas",
+    "Infrastructure/Architecture - Overview.canvas",
+    "Infrastructure/Architecture - Master.canvas",
+    "Infrastructure/Architecture - Automation Flow.canvas",
+    "Untitled.canvas"
  ]
 }
@@ -0,0 +1,5 @@
+# Archive
+
+Inactive notes go here when they are no longer current but may still be useful.
+
+Do not delete project history or decisions just because they are old; archive instead.
@@ -0,0 +1,13 @@
+# Areas Home
+
+Areas are ongoing responsibilities without a defined end date.
+
+Examples:
+
+- [[Systems]]
+- [[Health]]
+- [[Finance]]
+- [[Home]]
+- [[Learning]]
+
+Use area notes to collect standards, recurring processes, and long-running responsibilities.
@@ -0,0 +1,3 @@
+# Finance
+
+Area index for finance-related notes.
@@ -0,0 +1,3 @@
+# Health and Medical Leave
+
+Redirect/index note. Canonical personal-context note: [[Atlas/Personal Context/Areas/Health and Medical Leave]].
@@ -0,0 +1,3 @@
+# Health
+
+Area index. Sensitive details live under [[Atlas/Personal Context/Areas/Health and Medical Leave]].
@@ -0,0 +1,3 @@
+# Home
+
+Area index for home/life logistics.
@@ -0,0 +1,3 @@
+# Learning
+
+Area index for learning resources and plans.
@@ -0,0 +1,3 @@
+# Legal
+
+Redirect/index note. Canonical personal-context note: [[Atlas/Personal Context/Areas/Legal]].
@@ -0,0 +1,3 @@
+# Systems
+
+Area index for systems and automation. See [[Infrastructure/Architecture]], [[Resources/Service Catalog]], and [[Ops Home]].
@@ -0,0 +1,31 @@
+# Daily Hermes + AI Research Brief — May 18, 2026
+
+## Important updates
+
+- **Hermes Agent v0.14.0 “Foundation Release” landed May 16.** GitHub release snippets report a large jump since v0.13.0: **808 commits, 633 merged PRs, 1,393 files changed**. This is worth a safe update audit for Will’s production Atlas gateway, but not an automatic update because local config/source changes may exist. Source: [GitHub releases](https://github.com/NousResearch/hermes-agent/releases)
+
+- **Hermes docs now emphasize “profile distributions” for sharing whole agents.** This is directly relevant to Will’s specialist roster: Atlas/default can stay stable while reusable researcher/writer/ops/engineer profile bundles are packaged and replicated. Source: [Hermes profile distributions docs](https://hermes-agent.nousresearch.com/docs/user-guide/profile-distributions)
+
+- **Hermes provider-extension docs are now explicit about auth, runtime resolution, CLI flows, adapters, tests, and docs.** Useful if Will wants clean support for custom/local providers like llama.cpp, GLM/Z.AI, Gemini ACP, LiteLLM routes, or CoreWeave-hosted endpoints. Source: [Adding Providers — Hermes Agent](https://hermes-agent.nousresearch.com/docs/developer-guide/adding-providers)
+
+- **Agent observability is becoming a practical infra pattern.** Red Hat’s OpenTelemetry writeup frames agentic systems as composed of routing agents, specialist agents, LLM inference, MCP servers, and external integrations — basically Will’s Atlas architecture. The takeaway: trace tool calls, model routing, retries, and MCP/server hops as first-class spans. Source: [Red Hat: Distributed tracing for agentic workflows](https://developers.redhat.com/articles/2026/04/06/distributed-tracing-agentic-workflows-opentelemetry)
+
+- **Inference-on-Kubernetes momentum is accelerating.** Red Hat is positioning `llm-d`/AI Inference for managed Kubernetes including CoreWeave/Azure, and Microsoft published a fresh AKS-oriented controllable inference platform pattern covering llama.cpp plus GPU vLLM/TensorRT-LLM workloads. This maps well to Will’s CoreWeave/k8s and local swarm interests. Sources: [Red Hat AI Inference / llm-d](https://www.redhat.com/de/blog/red-hat-ai-inference-brings-llm-d-any-managed-kubernetes-starting-coreweave-and-microsoft-azure), [Microsoft AI Runway on Kubernetes](https://techcommunity.microsoft.com/blog/azuredevcommunityblog/building-a-controllable-inference-platform-on-kubernetes-with-ai-runway/4520590)
+
+- **MCP security/governance keeps surfacing as the unsexy but important agent problem.** Recent posts frame direct agent-to-MCP-server connections as a supply-chain/security risk and call out over-permissioned tools. This matters for Atlas because gateway + local services + specialist profiles can easily accumulate too much ambient authority. Sources: [Box on agent/MCP supply-chain risk](https://blog.box.com/ai-agents-are-creating-new-supply-chain-crisis-we-have-narrow-window-get-it-right), [Kong on MCP tool governance](https://konghq.com/blog/engineering/mcp-tool-governance-security-meets-context-efficiency)
+
+## Actionable ideas for us
+
+- **[quick] Run a read-only Hermes update check later today:** compare local `main` vs `origin/main`, inspect dirty files, and only then decide whether to create a gated update board for v0.14.0.
+
+- **[experiment] Add lightweight OpenTelemetry-style tracing around Atlas workflows:** start with cron jobs, model/provider routing, tool calls, n8n hooks, and local swarm service calls; even JSONL spans would help debug latency and failures.
+
+- **[experiment] Prototype a “profile distribution” export for Will’s specialist roster:** default/Atlas stays production; export stopped/manual profiles like researcher, writer, ops, engineer, reviewer, glm-simple.
+
+- **[watch] Track MCP permission boundaries:** define which profiles may call which local services/tools, especially anything touching filesystem, Telegram/Discord delivery, n8n, credentials, or GPU inference endpoints.
+
+## Worth ignoring
+
+- Generic “best AI agents of 2026” listicles unless they include reproducible benchmarks, cost data, or architecture details.
+- Hermes star-count hype without concrete release notes or operational changes.
+- Consumer AI app announcements that do not expose APIs, local deployment options, MCP/tool interfaces, or infra lessons.
@@ -0,0 +1,22 @@
+# Daily Hermes + AI Research Brief — 2026-05-19
+
+## Important updates
+
+- **Hermes Agent v0.14.0 / v2026.5.16 is the main Hermes item to track.** GitHub release search shows a May 16 release with **808 commits, 633 merged PRs, and 1,393 files changed** since v0.13.0; snippets highlight PyPI install support, ~19s faster cold start, much faster Browser CDP calls, and new messaging work. This matters because Will’s default Atlas gateway is source-installed and gateway uptime/update safety is more important than chasing the release immediately. Source: [GitHub releases](https://github.com/NousResearch/hermes-agent/releases) / [release search result](https://github.com/NousResearch/hermes-agent/releases/tag/v2026.5.16).
+- **Hermes v0.13.0 / v2026.5.7 shipped the “Tenacity” durable-work direction.** NewReleases summarizes it as Kanban becoming a durable multi-agent board with heartbeat, reclaim, zombie detection, and auto-block behavior. This aligns directly with Will’s specialist-profile/worker setup; it is worth treating Kanban as the safe path for long agent tasks instead of ad-hoc background spawns. Source: [NewReleases v2026.5.7](https://newreleases.io/project/github/NousResearch/hermes-agent/release/v2026.5.7).
+- **Hermes docs continue to emphasize self-improving skills, persistent memory, profiles, messaging gateway, and provider-agnostic routing.** That is not a “new today” item, but it confirms Atlas’s current architecture choices: keep `default` as the production Telegram gateway, use specialist profiles for isolation, and save durable research outputs into Obsidian rather than memory. Source: [Hermes Agent docs](https://hermes-agent.nousresearch.com/docs/).
+- **MCP scaling pattern worth adopting: expose many tools as code APIs inside execution environments, not as hundreds of direct LLM tools.** Anthropic’s engineering writeup says code execution with MCP can make agents more efficient by letting the model write code that calls MCP APIs, reducing tool-schema/token pressure. For Will, this suggests future Atlas/n8n/local-swarm integrations should prefer compact wrapper APIs and executable client libraries when tool count grows. Source: [Anthropic Engineering — Code execution with MCP](https://www.anthropic.com/engineering/code-execution-with-mcp).
+- **Open-source infra maintainers are now explicitly dealing with AI-generated PR load.** MLSys has an invited talk, “Rethinking Open Source Contribution in the Age of AI Agents,” framed around vLLM and the surge of AI-generated pull requests. This matters for Will’s CoreWeave/k8s/LLM-infra work: review gates, narrow tests, provenance, and anti-slop contribution policies are now part of production LLM ops, not just repo hygiene. Source: [MLSys 2026 schedule](https://mlsys.org/virtual/2026/day/5/18) / [invited talk](https://mlsys.org/virtual/2026/invited-talk/10000).
+
+## Actionable ideas for us
+
+- **[quick]** Check local Hermes safely before updating: `hermes --version`, `git status --short --branch`, and `git rev-list --left-right --count main...origin/main`; do **not** run `hermes update` automatically if the tree is dirty.
+- **[quick]** Review whether Atlas’s Browser/CDP and messaging paths benefit from v0.14.0, but route any upgrade through the safe update workflow because the gateway is production.
+- **[experiment]** Prototype one “code API over tool flood” integration for local swarm services: a small Python client that wraps n8n, llama.cpp, Ollama embeddings, and Obsidian REST behind a few stable calls.
+- **[watch]** Track Hermes issues/releases around v0.14.0 for Windows/PyPI/lazy dependency fallout and any gateway regressions before adopting it on `default`.
+
+## Worth ignoring
+
+- Generic “agent landscape 2026” listicles unless they include concrete implementation details, benchmarks, or repo links.
+- Funding/market stories about AI agents with no deployable tooling, protocol, model, or infra takeaway.
+- Consumer-only agent announcements unless they expose useful MCP/tooling/local-first patterns.
@@ -0,0 +1,23 @@
+# Daily Hermes + AI Research Brief — 2026-05-20
+
+## Important updates
+
+- **Hermes Agent v0.13 / “Tenacity” remains the key Hermes update to track.** GitHub release/search results list v2026.5.7 with Kanban as a durable multi-agent board, heartbeat/reclaim/zombie detection/auto-block behavior, and a large reliability-focused release since v0.12.0. This matters because Will’s Atlas setup already depends on default gateway stability plus specialist profiles/Kanban for durable work. Source: [NousResearch/hermes-agent releases](https://github.com/NousResearch/hermes-agent/releases).
+- **Hermes docs continue to emphasize self-improving skills, persistent memory, profiles, gateway, plugins, MCP, cron, and Kanban.** For Will, the practical takeaway is to keep Atlas’ daily operations split between short memory pointers, Obsidian for durable context, and specialist-profile delegation rather than stuffing everything into one long session. Source: [Hermes Agent Documentation](https://hermes-agent.nousresearch.com/docs/).
+- **OpenAI Codex CLI shipped another May update.** The Codex changelog shows “Codex CLI 0.130.0” on 2026-05-08 with performance improvements/bug fixes. This is relevant because Will’s Hermes workers/profiles use Codex auth in some paths; keep profile auth smoke tests in the loop before dispatching autonomous coding agents. Source: [OpenAI Codex changelog](https://developers.openai.com/codex/changelog).
+- **1Password announced/covered just-in-time credential access for Codex via MCP.** The useful pattern is not the vendor hype; it is the architecture: coding agents should request narrowly scoped, auditable secrets at task time instead of having broad static env access. This maps directly to safer Hermes MCP/tool credentials and swarm service secrets. Source: [SiliconANGLE coverage](https://siliconangle.com/2026/05/20/1password-extends-openai-collaboration-codex-mcp-server-just-time-credential-access/).
+- **MCP remains the practical integration layer to watch.** Recent MCP comparisons and Anthropic engineering material emphasize implementing tools once and exposing them across agent clients. For Will, this supports consolidating local services—Obsidian, n8n, Ollama/llama.cpp, Kokoro/Whisper—behind stable MCP/tool wrappers instead of one-off scripts. Sources: [ClickHouse MCP framework comparison](https://clickhouse.com/blog/how-to-build-ai-agents-mcp-12-frameworks), [Anthropic on MCP code execution](https://www.anthropic.com/engineering/code-execution-with-mcp).
+- **AI observability is moving from infra-only metrics to LLM-specific monitoring.** Current LLMOps guidance stresses that healthy CPU/GPU dashboards do not prove agent quality; you need latency, error rates, tool-call failures, prompt/model routing traces, and evaluation signals. This is directly useful for Will’s CoreWeave/GPU/k8s-style work and local swarm reliability. Source: [Kong AI observability guide](https://konghq.com/blog/learning-center/guide-to-ai-observability).
+
+## Actionable ideas for us
+
+- **[quick]** Add a recurring manual check item for Hermes release notes: compare local `~/.hermes/hermes-agent` against `origin/main` and v2026.5.7+ release notes, but only use the safe isolated update flow.
+- **[quick]** Smoke-test specialist profiles that may use Codex: `hermes -p <profile> chat -q 'Reply exactly: ok' --toolsets safe -Q` before Kanban dispatch.
+- **[experiment]** Prototype an MCP-style “just-in-time secret” pattern locally: agent requests a named credential lease for one task; logs scope and expiration; never exposes raw secrets in final output.
+- **[watch]** Track Hermes Kanban reliability and session-rollover/handoff changes; these are likely to matter more for Atlas autonomy than flashy model announcements.
+
+## Worth ignoring
+
+- Generic “AI agents in 2026” listicles with no implementation detail.
+- Funding/partnership headlines unless they ship concrete APIs, MCP servers, model routing, or local-first tooling.
+- Consumer chatbot feature news with no path to Hermes, Obsidian, n8n, local inference, or GPU ops.
@@ -0,0 +1,16 @@
+# Daily Hermes + AI Research Brief — 2026-05-21
+
+## Important updates
+
+- **No source-backed web brief could be produced today because this Hermes cron environment has no configured web search or extraction backend.** `web_search` returned “No web search provider configured,” and direct `web_extract` returned “No web extract provider configured. Set web.extract_backend to firecrawl, tavily, exa, or parallel.” Why it matters to Will: this daily research job cannot meet its current-news/source-backed requirement until the `web`/`search` tool backend is configured. Source targets that should be checked once fixed: [Hermes Agent GitHub releases](https://github.com/NousResearch/hermes-agent/releases), [Hermes Agent docs](https://hermes-agent.nousresearch.com/docs/), [Hermes Agent commits](https://github.com/NousResearch/hermes-agent/commits/main), [Model Context Protocol news](https://modelcontextprotocol.io/news), [GitHub changelog](https://github.blog/changelog/).
+
+## Actionable ideas for us
+
+- [quick] Configure a web backend for Hermes cron runs, e.g. set `web.extract_backend` to a supported provider and ensure the matching API key is available to the cron profile/session.
+- [quick] Run `hermes tools list` / `hermes tools` in the profile used by this scheduled job and confirm `web` or `search` is enabled for cron sessions.
+- [experiment] Add a preflight check to the brief job that reports missing web/search configuration distinctly before attempting research, so failures are obvious and not mistaken for “nothing notable.”
+- [watch] Tomorrow, search: `Hermes Agent NousResearch releases docs`, `AI agents MCP coding agents local LLM inference`, `model routing LLM ops privacy local-first AI agents`.
+
+## Worth ignoring
+
+- No hype/noise items were evaluated because live search/extraction was unavailable.
@@ -0,0 +1,24 @@
+# Daily Hermes + AI Research Brief — 2026-05-22
+
+## Important updates
+
+- **Hermes v0.14.0 is the practical upgrade to track.** The May 16 “Foundation Release” adds `pip install hermes-agent`, much lighter/lazier installs, ~19s faster cold start, 180× faster browser CDP calls, native Windows beta, LINE + SimpleX, Teams wiring, LSP semantic diagnostics on write, `/handoff`, and an OpenAI-compatible local proxy for OAuth providers. This directly helps Atlas/Hermes portability, cron startup latency, and interop with Codex/Aider/Cline/Continue. Source: [Hermes Agent releases](https://github.com/NousResearch/hermes-agent/releases).
+- **Hermes provider/routing surface keeps expanding.** v0.14 adds SuperGrok OAuth with grok-4.3 at 1M context, an OpenRouter Pareto Code router, first-class `x_search`, trusted `huggingface/skills` tap, and non-Anthropic `computer_use` via `cua-driver`. For Will: worth testing as alternate model routes for research/coding jobs without hard-coding one provider. Source: [Hermes Agent v0.14.0 release notes](https://github.com/NousResearch/hermes-agent/releases).
+- **Security checks are moving into MCP-native agent workflows.** GitHub made secret scanning in the GitHub MCP Server generally available, so MCP-compatible agents/IDEs can scan current changes for exposed secrets before commit/PR and honor existing push-protection customization. Source: [GitHub changelog](https://github.blog/changelog/2026-05-05-secret-scanning-with-github-mcp-server-is-now-generally-available/).
+- **Dependency scanning via MCP is now in public preview.** GitHub’s MCP Server `dependabot` toolset can return structured vulnerable-dependency results with package, severity, and fixed-version recommendations; it can also use Dependabot CLI locally for deeper post-commit diffing. This is a good pattern for Hermes tool/MCP guardrails around automated code edits. Source: [GitHub changelog](https://github.blog/changelog/2026-05-05-dependency-scanning-with-github-mcp-server-is-in-public-preview/).
+- **Codex is pushing long-running goal mode + shared plugin bundles.** OpenAI’s Codex changelog for 2026-05-21 says Goal mode is no longer experimental across app/IDE/CLI, Appshots can send Mac window context to Codex, remote computer use supports locked Macs, and Business plugin sharing can bundle skills, app integrations, and MCP servers. Useful competitive signal for Hermes `/goal`, skills, remote agents, and reusable bundles. Source: [Codex changelog](https://developers.openai.com/codex/changelog).
+- **vLLM’s Kubernetes docs remain a clean baseline for local/GPU agent infra.** The current deployment guide frames vLLM-on-K8s as a way to scale/manage ML models on GPU resources, with an OpenAI-compatible serving path elsewhere in the docs. This is relevant for Pi/local-swarm → GPU-cluster routing patterns. Source: [vLLM Kubernetes deployment docs](https://docs.vllm.ai/en/stable/deployment/k8s/).
+
+## Actionable ideas for us
+
+- [quick] Try `hermes proxy` locally as an OpenAI-compatible endpoint for one external coding tool, then note latency/auth rough edges.
+- [quick] Add a pre-commit/PR checklist item for “ask agent to run MCP secret/dependency scan” on Hermes/Atlas repos where GitHub MCP is configured.
+- [experiment] Compare Hermes `/goal` + Kanban against Codex Goal mode on the same long-running maintenance task; score recovery after restart, tool safety, and final diff quality.
+- [watch] Track Hermes v0.14.x patches for Windows beta, browser CDP speedups, `computer_use`, and Teams/LINE/SimpleX gateway regressions before relying on them in production workflows.
+
+## Worth ignoring
+
+- Generic “agent ecosystem maps” and listicles unless they include concrete protocol/tooling changes or reproducible benchmarks.
+- Consumer-only app demos around screenshots/mobile control unless they translate into reusable agent context-capture patterns for Hermes.
+
+Saved to Obsidian: Atlas/Daily Research/2026-05-22 - Hermes AI Brief.md
@@ -0,0 +1,26 @@
+# Daily Hermes + AI Research Brief — 2026-05-23
+
+## Important updates
+
+- **Hermes v0.14.0 is the big local-agent upgrade to test next.** The latest GitHub release (May 16) says Hermes added SuperGrok OAuth with 1M-token Grok 4.3 context, an OpenAI-compatible local proxy for OAuth-authed providers, first-class `x_search`, Microsoft Teams plumbing, lighter/lazy installs, PyPI install support, ~19s faster cold start, 180x faster browser CDP calls, LINE/SimpleX gateways, `/handoff`, LSP diagnostics on writes, improved `computer_use`, Windows beta, OpenRouter Pareto Code router, and trusted Hugging Face skills taps. This directly affects Atlas provider routing, gateway reach, browser automation, and local coding-agent ergonomics. Source: [Hermes releases](https://github.com/NousResearch/hermes-agent/releases).
+
+- **Hermes v0.13.0’s durable Kanban board is still the most relevant architectural feature for Atlas/swarm work.** The release notes describe Kanban as a durable multi-agent board with heartbeat, reclaim, zombie detection, auto-block, dependency DAGs, dispatch daemon, and worker-gated tools. That maps closely to Will’s local swarm / Pi agent harness needs: durable task state beats fragile background chats. Source: [Hermes v0.13 release](https://github.com/NousResearch/hermes-agent/blob/main/RELEASE_v0.13.0.md).
+
+- **OpenAI Codex is moving toward long-running, remote, cross-device agents.** The May 21 Codex changelog says Goal mode is now available across the app, IDE extension, and CLI for objectives that can run “hours or even days”; Codex also added Appshots, remote computer use after a Mac locks, plugin marketplace sharing with skills/MCP/hooks bundles, and browser-use reliability/structured extraction improvements. Useful pattern for Hermes/Atlas: explicit goal mode + remote host continuity + shareable tool bundles. Source: [Codex changelog](https://developers.openai.com/codex/changelog).
+
+- **Codex now supports trusted non-interactive automation tokens.** OpenAI’s May 5 changelog entry says Enterprise admins can allow members to create Codex access tokens for scripts, schedulers, and private CI runners. Even if Will does not use Codex Enterprise, this is a strong signal: scheduled/CI agent auth is becoming a first-class surface, and Hermes cron/gateway auth should keep separating human OAuth, job identity, and least-privilege automation tokens. Source: [Codex changelog](https://developers.openai.com/codex/changelog).
+
+- **Agent traffic gateways are converging around LLM + MCP + A2A + Kubernetes in one data plane.** Agentgateway positions itself as a Linux Foundation project for “LLM, MCP, A2A, and HTTP in one data plane,” with integrations for Claude Code, Codex, OpenCode, Hermes, MCP servers, OpenTelemetry, Kubernetes, and major providers. For CoreWeave-style GPU/k8s work, watch this class of gateway as the possible control plane between local agents, hosted inference, MCP tools, and observability. Source: [agentgateway](https://agentgateway.dev/).
+
+## Actionable ideas for us
+
+- **[quick] Upgrade-check Hermes locally** with `hermes update` / `hermes doctor`, then specifically smoke-test v0.14 features that matter: PyPI/lazy deps, browser CDP speed, LSP diagnostics, `/handoff`, and the OpenRouter Pareto Code router.
+- **[experiment] Prototype a small Hermes Kanban board** for Atlas jobs: one dispatcher task, two worker profiles, heartbeat/reclaim enabled, and Obsidian note output as the completion artifact.
+- **[experiment] Test Hermes’ OpenAI-compatible local proxy** as a unifying endpoint for Codex/Aider/Cline/Continue against existing OAuth-backed providers; compare latency, context caching, and failure modes.
+- **[watch] Track agentgateway’s MCP/A2A routing model** for whether it can front local MCP servers and GPU-hosted inference without overcomplicating Atlas’ current setup.
+
+## Worth ignoring
+
+- Generic “Claude Code vs Codex” comparison posts unless they include reproducible benchmarks, config details, or concrete failure cases.
+- Broad “top LLMOps tools” listicles; most are vendor SEO unless they show real routing, eval, cost, or Kubernetes deployment examples.
+- Consumer-only agent demos that do not expose tool permissions, auth, logs, or recoverability.
@@ -0,0 +1,27 @@
+# Daily Hermes + AI Research Brief — 2026-05-24
+
+## Important updates
+
+- **Hermes Agent v0.14.0 shipped May 16 as the “Foundation Release.”** Highlights: PyPI install path, ~19s faster cold start, 180x faster Browser CDP calls, native Windows beta, OpenAI-compatible local proxy for OAuth-authed providers, xAI/SuperGrok OAuth with 1M-context Grok, LINE/SimpleX/Teams platform work, `/handoff`, LSP diagnostics on writes, and new optional skills. This matters for Atlas because it reduces install friction and opens a useful “Hermes as local provider proxy” pattern for Codex/Aider/Cline/Continue experiments. Source: [GitHub releases](https://github.com/NousResearch/hermes-agent/releases).
+
+- **Hermes v0.13.0’s durable Kanban/multi-agent board remains the most relevant recent Hermes architecture change.** The release notes describe durable heartbeats, reclaim/zombie detection, auto-blocking, task lifecycle, and worker/orchestrator patterns. This is directly applicable to Will’s Atlas/local-swarm work: use the board as the durable coordination boundary instead of ad-hoc background sessions. Source: [Hermes releases](https://github.com/NousResearch/hermes-agent/releases).
+
+- **LiteLLM opened an alpha Managed Agents Platform on May 8.** It is a self-hosted platform for running multiple agents in production, focused on per-team/context sandboxes and session persistence across pod restarts/upgrades. Worth watching as a comparison point for Hermes Kanban + profiles + gateway on Kubernetes. Source: [LiteLLM blog](https://docs.litellm.ai/blog/agent-platform-alpha).
+
+- **vLLM’s latest developer docs now document experimental disaggregated prefilling.** The page describes splitting prefill and decode across separate vLLM instances and transferring KV cache via connectors such as NIXL, OffloadingConnector, and FlexKV; it was updated May 6. This is practical for CoreWeave-style GPU/k8s serving experiments where prefill/decode bottlenecks need separate scaling. Source: [vLLM disaggregated prefilling docs](https://docs.vllm.ai/en/latest/features/disagg_prefill/).
+
+- **MCP governance/security capacity is expanding.** The MCP project added Clare Liguori as Core Maintainer and Den Delimarsky as Lead Maintainer; the post emphasizes production agent runtimes, triggers/events, authorization, RFC 8707 resource indicators, and security work. This matters because MCP is becoming long-lived infra, not just a tool-call fad; Hermes MCP integration should track auth/security spec changes closely. Source: [MCP blog](https://blog.modelcontextprotocol.io/posts/2026-04-08-expanding-maintainer-team/).
+
+## Actionable ideas for us
+
+- **[quick]** Test `pip install hermes-agent` in a clean disposable venv/container and note any Atlas bootstrap simplifications vs the current install path.
+- **[experiment]** Prototype the new Hermes OpenAI-compatible local proxy with one external coding client (Aider/Cline/Codex) and one OAuth provider; record latency, auth refresh behavior, and whether prompt caching survives the proxy path.
+- **[experiment]** Map Hermes Kanban concepts to the Pi/Atlas swarm: task table = durable queue, profile = worker role, heartbeat/reclaim = supervisor; avoid inventing a parallel scheduler until this is evaluated.
+- **[watch]** Track vLLM disaggregated prefill + LiteLLM componentized/agent platform work for a future GPU/k8s inference control plane design.
+
+## Worth ignoring
+
+- Generic “agent framework star race” and listicle posts unless they include reproducible architecture details or benchmarks.
+- Consumer-only “AI assistant” announcements without tool protocol, deployment, privacy, or local-first implications.
+
+Saved to Obsidian: Atlas/Daily Research/2026-05-24 - Hermes AI Brief.md
@@ -0,0 +1,24 @@
+# Daily Hermes + AI Research Brief — 2026-05-25
+
+## Important updates
+
+- **Hermes v0.14.0 is the big local-agent upgrade to study.** The May 16 release claims PyPI install support, ~19s faster cold start, 180× faster browser CDP calls, native Windows beta, LINE/SimpleX support, LSP diagnostics on write, prompt caching, `/handoff`, `computer_use`, and a local OpenAI-compatible proxy for OAuth-authed providers. This directly maps to Atlas goals: faster cron/gateway loops, cross-tool provider routing, and better spawned-agent ergonomics. [Source: GitHub releases](https://github.com/NousResearch/hermes-agent/releases)
+- **Hermes provider/tooling surface is expanding beyond “chat agent” into router/proxy glue.** The release notes highlight xAI SuperGrok OAuth, Grok 4.3 1M context, `x_search`, Microsoft Teams plumbing, Zed ACP registry integration via `uvx`, OpenRouter Pareto Code router, and `huggingface/skills` as a trusted tap. For Will, this is a reason to treat Hermes/Atlas as a control plane for heterogeneous model/tool backends rather than a single CLI. [Source: Hermes v0.14.0 release](https://github.com/NousResearch/hermes-agent/releases)
+- **OpenAI is pushing Codex toward durable, cross-app agent work.** Codex now has background computer use, an in-app browser, image generation, 90+ plugins including MCP servers, multiple terminals, SSH devbox support, reusable automation threads, scheduling, and preview memory. This is highly relevant because it validates the same design space Atlas is using: cron + memory + tools + multi-agent task carryover. [Source: OpenAI](https://openai.com/index/codex-for-almost-everything/)
+- **Agent governance is becoming an infra layer, not an afterthought.** Databricks’ Unity AI Gateway release adds MCP governance, on-behalf-of permissions, LLM/MCP observability, cost attribution, model fallback/rate-limit/guardrail policies, and consistent controls across OpenAI/Anthropic/Google/open-source models. Practical takeaway: Atlas/Hermes should log model+tool calls as first-class audit events, especially for Pi swarm and GPU/k8s agents. [Source: Databricks](https://www.databricks.com/blog/ai-gateway-governance-layer-agentic-ai)
+- **MCP is continuing to standardize enterprise tool use.** Red Hat’s MCP guidance frames MCP as the layer for tool discovery, policy, and auditable actions, moving beyond one-off RAG/tool-call glue. This supports investing in MCP-compatible wrappers for local services instead of bespoke integrations. [Source: Red Hat Developer](https://developers.redhat.com/articles/2026/01/08/building-effective-ai-agents-mcp)
+- **vLLM v0.21.0 has inference changes worth tracking for local/GPU backends.** The release includes KV offload + Hybrid Memory Allocator work, speculative decoding that respects reasoning/thinking budgets, new Blackwell attention backend work for DeepSeek/Kimi-style models, more model/tool-parser support, and a breaking C++20 build requirement. This matters for any CoreWeave-style or home GPU inference path. [Source: vLLM releases](https://github.com/vllm-project/vllm/releases)
+
+## Actionable ideas for us
+
+- **[quick]** Check whether the running Hermes install is already on v0.14.0; if not, schedule a manual upgrade window and verify cron/gateway after restart.
+- **[quick]** Add a short “agent audit event” note/template for Atlas: model, provider, tool/MCP server, data touched, outcome, and cost/latency where available.
+- **[experiment]** Prototype Hermes’ local OpenAI-compatible proxy with one external coding tool (Codex/Aider/Cline/Continue) to see if Atlas can centralize provider auth and routing.
+- **[watch]** Track vLLM v0.21.x adoption notes before upgrading any production-ish inference service because C++20/Transformers v5 changes may break builds.
+
+## Worth ignoring
+
+- Generic “2026 agent landscape” listicles unless they include reproducible implementation details or protocol/tooling changes.
+- Consumer-only Codex/Claude comparisons without concrete workflow, eval, or infra takeaways.
+
+Saved to Obsidian: Atlas/Daily Research/2026-05-25 - Hermes AI Brief.md
@@ -0,0 +1,28 @@
+# Daily Hermes + AI Research Brief — 2026-05-26
+
+## Important updates
+
+- **Hermes Agent v0.14.0 is the big local-agent update to study.** The May 16 release notes say PyPI install now works, cold start is ~19s faster, Browser CDP calls are 180× faster, native Windows is in beta, LINE/SimpleX were added, `x_search` landed, an OpenAI-compatible local proxy can expose OAuth-backed providers to Codex/Aider/Cline/Continue, and `/handoff`, prompt caching, LSP diagnostics, video generation, and provider-agnostic computer-use improved. This is directly relevant to Atlas as a multi-channel, local-first, tool-heavy agent stack. Source: [NousResearch/hermes-agent releases](https://github.com/NousResearch/hermes-agent/releases).
+
+- **Hermes' May 7 “Tenacity” release introduced durable multi-agent coordination primitives.** The release search result reports Kanban as a durable multi-agent board with heartbeat, reclaim, zombie detection, and auto-block behavior. That maps closely to Will's swarm/worker orchestration needs: durable task state beats pure chat-thread delegation for long-running local agents. Source: [Hermes Agent v2026.5.7 release](https://github.com/NousResearch/hermes-agent/releases) / [NewReleases mirror](https://newreleases.io/project/github/NousResearch/hermes-agent/release/v2026.5.7).
+
+- **GitHub Copilot is pushing hard on cloud-agent ergonomics and routing.** The Copilot changelog lists May updates for auto model selection in VS Code, semantic issue search, applying code-review feedback with Copilot cloud agent, one-click fixes for failing Actions, cheaper/simple-task models, REST API auditing of cloud-agent config, and remote control for Copilot CLI sessions. Useful pattern for Atlas: expose agent state, config, and fix loops as first-class APIs/UI actions. Source: [GitHub Copilot changelog](https://github.blog/changelog/label/copilot/).
+
+- **OpenAI's Ramp case study is a concrete benchmark for agent usefulness: code review + on-call assistant.** Ramp says Codex with GPT-5.5 gives substantive PR feedback “in minutes instead of hours” and is being used to build an internal on-call assistant for complex incident workflows. Practical takeaway: measure Atlas/Hermes value around latency-to-first-review, incident context retention, and whether agents reduce interruption cost—not just task completion demos. Source: [OpenAI: Ramp engineers accelerate code review with Codex](https://openai.com/index/ramp/).
+
+- **Microsoft Agent Framework is converging on the same building blocks Hermes already emphasizes.** Microsoft documents agents that call tools and MCP servers, workflows with type-safe routing/checkpointing/human-in-loop, model clients, agent sessions, memory providers, middleware, and MCP clients; supported backends include Foundry, Anthropic, Azure OpenAI, OpenAI, Ollama, and more. This is worth watching for interoperability ideas and enterprise patterns around middleware/checkpointing. Source: [Microsoft Agent Framework overview](https://learn.microsoft.com/en-us/agent-framework/overview/).
+
+- **Anthropic's agent platform direction continues to validate MCP + generated client surfaces.** Anthropic's May 18 announcement says it acquired Stainless; the search snippet frames the move around MCP and agent connectivity. Even if product details are thin from the public page, the signal is clear: typed API/client generation plus MCP-style tool connectivity is becoming core agent infrastructure. Source: [Anthropic acquires Stainless](https://www.anthropic.com/news/anthropic-acquires-stainless).
+
+## Actionable ideas for us
+
+- **[quick] Upgrade-check Hermes and read v0.14 notes against Atlas pain points.** Prioritize PyPI install, CDP speedups, `/handoff`, local proxy, prompt caching, LSP diagnostics, and `x_search`.
+- **[experiment] Prototype a Hermes Kanban-backed worker lane** for one recurring Atlas task: create → claim → heartbeat → complete/block. Compare with current cron/session-only flow.
+- **[experiment] Test the OpenAI-compatible local proxy** as a unifying endpoint for Aider/Cline/Continue/Codex-style tools using existing Hermes auth/provider routing.
+- **[watch] Track Copilot's cloud-agent API/config surface** for ideas: REST-auditable agent config, remote CLI control, semantic issue search, and auto model routing are all patterns Atlas could mirror locally.
+
+## Worth ignoring
+
+- Generic “best AI coding agents in 2026” listicles unless they include reproducible benchmarks or specific workflow design ideas.
+- Funding/enterprise-adoption announcements without concrete APIs, open-source code, or operational lessons.
+- Consumer AI stories unless they improve local/private agent workflows or tool orchestration.
@@ -0,0 +1,23 @@
+# Daily Hermes + AI Research Brief — 2026-05-30
+
+## Important updates
+
+- **Hermes shipped v0.15.2/v0.15.1 hotfixes on May 29.** v0.15.2 fixes packaging so bundled `plugin.yaml` manifests ship in wheels/sdists; v0.15.1 fixes the v0.15.0 dashboard infinite-reload loop in loopback/Docker/hosted setups, restores `.md` media delivery, fixes kanban worker SIGTERM, Docker MCP `npx/npm/node` PATH resolution, `/yolo` session bypass, and expands the skills catalog from 858 to 19,932 entries. This is directly relevant to Atlas gateway/dashboard reliability and Dockerized MCP servers. Source: [Hermes releases](https://github.com/NousResearch/hermes-agent/releases).
+- **Hermes v0.15.0 “Velocity Release” is a major architecture + swarm release.** The core `run_agent.py` was split from ~16k LOC to ~3.8k across `agent/*`; kanban gained auto-decomposition, swarm topology, worktree-per-task, per-task model overrides, scheduled starts, TTL/retry/stale-task handling, and inspection endpoints; `session_search` was rebuilt as no-LLM/free/FTS-based and reported ~4,500× faster. This is worth folding into Atlas workflows instead of bespoke swarm glue where possible. Source: [Hermes v0.15.0 release notes](https://github.com/NousResearch/hermes-agent/blob/main/RELEASE_v0.15.0.md).
+- **Hermes added promptware / Brainworm-class defenses.** v0.15.0 release notes describe scanning recalled memory, tool output delimiter hardening, and centralized threat patterns. For Will’s local-agent work, this is a good reason to route more risky web/file recall through Hermes-native surfaces rather than ad hoc prompts. Source: [Hermes releases](https://github.com/NousResearch/hermes-agent/releases).
+- **Kubernetes LLM serving is converging on inference-aware routing.** Datadog’s May 29 writeup explains Kubernetes Gateway API Inference Extension routing based on backend state such as KV-cache readiness, LoRA adapter availability, queue length, health/readiness, and body-based model routing. This maps well to CoreWeave-style GPU/k8s work and any future local swarm router that should avoid naive round-robin. Source: [Datadog: Monitor LLM routing with the Kubernetes Inference Extension](https://www.datadoghq.com/blog/llm-routing-kubernetes-inference-extension/).
+- **Anthropic continues pushing MCP into first-party agent APIs.** Search results for Anthropic’s “New capabilities for building agents on the Anthropic API” highlight an API-side MCP connector so developers can connect Claude to remote MCP servers without writing custom MCP clients. This reinforces MCP as the default tool boundary to support in Atlas/Hermes integrations. Source: [Anthropic agent API capabilities](https://www.anthropic.com/news/agent-capabilities-api).
+- **Agent eval loops are becoming a practical norm.** OpenAI’s developer materials now frame agent improvement around traces → human/model feedback → evals → harness changes, where the “harness” includes instructions, tools, routing, output requirements, and validation checks. That is a useful template for Atlas regression tests and cron-job quality checks. Source: [OpenAI cookbook: Agent improvement loop](https://developers.openai.com/cookbook/examples/agents_sdk/agent_improvement_loop).
+
+## Actionable ideas for us
+
+- **[quick] Upgrade/check Hermes to at least v0.15.2** before doing dashboard, Docker, MCP, or kanban work; the May 29 hotfixes address exactly those surfaces.
+- **[experiment] Replace one Atlas swarm prototype with Hermes kanban swarm primitives**: per-task worktrees, model overrides, TTL/retry, and verifier/synthesizer gates are now built-in enough to test against Will’s existing Pi/local-agent harness.
+- **[experiment] Add a small inference-routing design note** for local/k8s agents: track queue length, model/adapter residency, KV-prefix reuse potential, and readiness; compare naive routing vs inference-aware routing.
+- **[watch] Build lightweight eval traces for this daily brief job**: store source queries, chosen links, rejected hype, and final bullets so future Atlas can measure “useful to Will” rather than just successful delivery.
+
+## Worth ignoring
+
+- Generic “top AI developer tools in 2026” listicles unless they include concrete tool APIs, eval methodology, or deployment patterns.
+- Broad MCP-is-dead / MCP-is-everything takes; the actionable signal is implementation quality: auth, server discovery, sandboxing, and observability.
+- Consumer/enterprise-positioning announcements without reproducible technical details or local-agent relevance.
@@ -0,0 +1,5 @@
+# Gateway Approval Runbook
+
+Redirect/index note for gateway approval procedures.
+
+Related: [[Runbooks/Atlas Event-Driven Automation]], [[Projects/Atlas Discord Telegram Workflow]]
@@ -0,0 +1,155 @@
+---
+title: Hermes / Atlas Architecture Diagram
+type: architecture-note
+created: 2026-05-29
+tags:
+  - hermes
+  - atlas
+  - architecture
+  - homelab
+  - docker
+  - kubernetes
+---
+
+# Hermes / Atlas Architecture Diagram
+
+A vector architecture diagram was created for the current Hermes/Atlas agent setup, host Docker/systemd AI services, AgentMon stack, and k0s Kubernetes homelab services.
+
+## Primary artifacts
+
+- SVG vector source: `/home/will/diagrams/hermes-atlas-architecture.svg`
+- High-resolution PNG export: `/home/will/diagrams/hermes-atlas-architecture-6400.png`
+- HTML presentation page: `/home/will/hermes-atlas-architecture.html`
+- Maintenance README: `/home/will/diagrams/README-hermes-atlas-architecture.md`
+- SVG extraction script: `/home/will/diagrams/extract-svg.py`
+
+## Why SVG
+
+The diagram is kept as standalone SVG so it can be:
+
+- scaled without resolution loss,
+- edited later in Inkscape, Figma, Illustrator, VS Code, or a browser-aware SVG editor,
+- exported to PNG at any resolution,
+- updated from the HTML presentation page when the layout changes.
+
+## Current coverage
+
+### Hermes / Atlas agent plane
+
+- Telegram, Discord, email, and local UI entrypoints.
+- Default Hermes gateway process.
+- Hermes state/context layer: `state.db`, sessions, memory, skills, config, auth pools.
+- Kanban dispatcher configured inside the gateway.
+- Specialist profiles including engineer, reviewer, orchestrator, researcher/writer, ops, and glm-simple.
+- Cron jobs and webhook subscriptions.
+- n8n/webhook producers for reminders, diary nudges, medication reminders, and Pi run results.
+
+### Host AI / automation plane
+
+- Docker Compose services under `/home/will/lab/swarm`:
+  - Brave Search MCP `:18802`
+  - SearXNG `:18803`
+  - Whisper GPU `:18801`
+  - Whisper CPU `:18811`
+  - Kokoro TTS `:18805`
+  - n8n `:18808`
+  - LiteLLM defined on `:18804`, but not running in the captured snapshot
+- User systemd services:
+  - `llama-server.service` on `:18806`
+  - `ollama.service` on `:18807`
+- AgentMon:
+  - ingest `:8080`
+  - query API `:8081`
+  - UI `:8082`
+  - Postgres and NATS backing services
+
+### k0s Kubernetes plane
+
+- Cluster: `k0s-cluster`
+- Nodes:
+  - `pi50` control-plane, `192.168.153.210`
+  - `pi51` worker, `192.168.153.206`
+  - `pi3` worker, `192.168.153.184`
+- Main layers:
+  - ArgoCD GitOps
+  - MetalLB
+  - HAProxy, nginx, and Traefik ingress
+  - Tailscale exposure
+  - atlas-control
+  - gitea
+  - minio
+  - home-assistant
+  - monitoring
+  - pihole2
+  - plex
+  - tools
+  - backup stores
+
+## Refresh workflow
+
+For simple edits, edit the SVG directly:
+
+```bash
+inkscape /home/will/diagrams/hermes-atlas-architecture.svg
+```
+
+For larger layout/content edits, edit the HTML page and regenerate the SVG:
+
+```bash
+$EDITOR /home/will/hermes-atlas-architecture.html
+/home/will/diagrams/extract-svg.py
+```
+
+To export a fresh high-resolution PNG from the SVG:
+
+```bash
+chromium --headless --disable-gpu --no-sandbox --hide-scrollbars \
+  --window-size=3200,2240 \
+  --force-device-scale-factor=2 \
+  --screenshot=/home/will/diagrams/hermes-atlas-architecture-6400.png \
+  file:///home/will/diagrams/hermes-atlas-architecture.svg
+```
+
+## Refresh checklist
+
+When updating the diagram from live infrastructure, re-check:
+
+- Hermes profile roster and gateway status.
+- Active Kanban worker processes.
+- Cron jobs and webhook subscriptions.
+- `/home/will/lab/swarm/docker-compose.yaml` services and currently running containers.
+- User systemd service units for local model endpoints.
+- AgentMon containers and exposed ports.
+- k0s nodes, load balancer services, ArgoCD app sync/health status, and selected namespaces.
+- Deliberate dormant or degraded states, such as OpenClaw remaining dormant or LiteLLM being defined but not running.
+
+## Source commands used
+
+The initial diagram was based on live read-only checks:
+
+```bash
+docker ps
+cd /home/will/lab/swarm && docker compose config --services
+cd /home/will/lab/swarm && make ps
+systemctl --user is-active llama-server.service ollama.service llama-swap.service
+systemctl --user cat llama-server.service
+systemctl --user cat ollama.service
+ss -ltnp
+hermes profile list
+hermes cron list
+hermes webhook list
+kubectl config get-contexts
+kubectl get nodes -o wide
+kubectl get ns
+kubectl get svc -A --field-selector spec.type=LoadBalancer -o wide
+kubectl get applications -n argocd
+kubectl get deploy,sts,ds,pods,svc,ingress -n <namespace>
+```
+
+Secrets were intentionally omitted.
+
+## Related
+
+- [[Atlas]]
+- [[Hermes]]
+- [[Inbox/Inbox]]
@@ -0,0 +1,165 @@
+---
+title: Hermes Setup Video Follow-up Audit
+date: 2026-05-21
+tags:
+  - atlas
+  - hermes
+  - operations
+  - memory-hygiene
+  - profiles
+  - skills
+---
+
+# Hermes Setup Video Follow-up Audit
+
+Source: YouTube video `NvakBZyc1Sg`, summarized in Discord thread by Wrack/Atlas.
+
+Wrack requested follow-ups: **1, 2, 4, 5** from the video-derived action list:
+
+1. Audit compression threshold / auxiliary model config.
+2. Compact static persistent memory because it was near capacity.
+4. Ensure profile-local credentials remain synced for specialist workers.
+5. Keep turning recurring workflows into skills rather than memory bloat.
+
+## Result
+
+Completed on 2026-05-21.
+
+## 1. Compression and auxiliary/fallback config
+
+Default profile was already aligned with the video's recommendation to compress before context reaches 100%.
+
+Observed default profile config:
+
+```yaml
+model:
+  default: gpt-5.5
+  provider: openai-codex
+
+fallback_providers:
+  - provider: zai
+    model: glm-5.1
+    base_url: https://api.z.ai/api/paas/v4
+
+compression:
+  enabled: true
+  threshold: 0.5
+  target_ratio: 0.2
+  rollover:
+    enabled: true
+    auto_rollover: true
+    threshold: 0.5
+
+session_rollover:
+  enabled: true
+  threshold: 0.5
+
+auxiliary:
+  compression:
+    provider: zai
+    model: glm-5.1
+```
+
+Specialist profile summary:
+
+| Profile | Primary provider/model | Compression threshold | Aux compression |
+|---|---|---:|---|
+| default | openai-codex / gpt-5.5 | 0.5 | zai / glm-5.1 |
+| engineer | openai-codex / gpt-5.5 | 0.5 | zai / glm-5.1 |
+| reviewer | openai-codex / gpt-5.5 | 0.5 | zai / glm-5.1 |
+| researcher | openai-codex / gpt-5.5 | 0.5 | zai / glm-5.1 |
+| writer | openai-codex / gpt-5.5 | 0.5 | zai / glm-5.1 |
+| ops | zai / glm-5.1 | 0.5 | zai / glm-5.1 |
+| orchestrator | zai / glm-5.1 | 0.5 | zai / glm-5.1 |
+| glm-simple | zai / glm-5.1 | 0.5 | zai / glm-5.1 |
+
+No config changes were needed for compression.
+
+## 2. Static memory compaction
+
+Persistent memory and user profile were near capacity. A small compaction pass was completed without intentionally dropping durable facts.
+
+Compacted entries included:
+
+- Atlas/Hermes repo authority/remotes policy.
+- Obsidian vault and Hermes/AI brief location.
+- Obsidian autostart / Local REST API note.
+- CoreWeave/FMLA/benefits entry.
+- Family entry.
+
+Approximate post-compaction state reported by the memory tool:
+
+- General memory: about **95%** full.
+- User profile: about **96%** full.
+
+Guideline reaffirmed: static memory should store durable facts only; procedures belong in skills, project notes, or session history.
+
+## 4. Profile-local credential sync and smoke test
+
+Before the audit, specialist profiles had no profile-local `auth.json` files.
+
+The default profile's `~/.hermes/auth.json` was copied to:
+
+- `~/.hermes/profiles/orchestrator/auth.json`
+- `~/.hermes/profiles/researcher/auth.json`
+- `~/.hermes/profiles/writer/auth.json`
+- `~/.hermes/profiles/ops/auth.json`
+- `~/.hermes/profiles/engineer/auth.json`
+- `~/.hermes/profiles/reviewer/auth.json`
+- `~/.hermes/profiles/glm-simple/auth.json`
+
+Each file was installed with mode `600`.
+
+Verified with `hermes --profile <profile> auth list` that each specialist profile could see the same provider credential set:
+
+- `anthropic`
+- `copilot`
+- `openai-codex`
+- `zai`
+
+Smoke-test flow:
+
+```bash
+~/.hermes/scripts/specialist-profile-smoke-watchdog.sh
+```
+
+First run reported a timeout for `ops`, but direct longer smoke test succeeded:
+
+```bash
+timeout 180 hermes -p ops chat -q 'Reply exactly: ok' --toolsets safe -Q
+# -> ok
+```
+
+Rerunning the watchdog was silent/successful.
+
+## 5. Recurring workflows captured as a skill
+
+Created local skill:
+
+```text
+~/.hermes/skills/devops/recurring-hermes-workflows/SKILL.md
+```
+
+Purpose: capture the durable workflow pattern from the video and Atlas practice:
+
+- periodic report → Hermes cron;
+- health threshold alert → script-only cron, quiet on success;
+- durable multi-step project → Kanban;
+- repeatable procedure → skill plus scripts/references;
+- user feedback loop → compact durable preferences, not raw rating logs;
+- avoid adding long procedural recipes to always-injected memory.
+
+This prevents future recurring-workflow logic from becoming static-memory bloat.
+
+## Follow-up notes
+
+- No urgent migration to VPS is recommended for the current Atlas setup.
+- Firecrawl/CamoFox remains optional; consider only when current search/browser stack hits Cloudflare or scraping limitations.
+- Re-run specialist profile smoke checks after auth/provider changes.
+- If memory pressure returns, compact or move procedural details into skills/Obsidian notes rather than increasing always-injected static memory.
+
+## Related
+
+- [[Atlas/Daily Research/2026-05-21 - Hermes AI Brief]]
+- Skill: `recurring-hermes-workflows`
+- Hermes skill reference: `hermes-agent/references/current-auth-fallback-and-profile-models.md`
@@ -0,0 +1,136 @@
+---
+tags: [atlas, personal-context, health, fmla, playbook]
+type: playbook
+created: 2026-05-15
+sensitive: true
+status: active
+---
+
+# FMLA Monday Appointment Playbook
+
+Purpose: make it easy to take action Monday without having to think from scratch.
+
+Current blocker: Will needs a doctor appointment for medical leave/FMLA support. PCP is booked until late this month.
+
+## Goal for Monday
+
+Get one of these outcomes:
+
+1. A sooner appointment with PCP, any care-team provider, telehealth, or same-clinic clinician.
+2. Clear instructions from the clinic on how to get FMLA/medical-leave documentation started before the PCP appointment.
+3. A backup appointment/path through behavioral health, urgent/same-day care, or another clinician who can document current functional impairment.
+
+## Minimum viable win
+
+If energy is low, do only this:
+
+- Send the portal message below.
+- Set one follow-up reminder for the next business day.
+
+That counts as progress.
+
+## Before calling or messaging
+
+Gather these if easy. Do not let this block sending the message.
+
+- [ ] Clinic/PCP name
+- [ ] Patient portal login
+- [ ] Employer/benefits/FMLA form, if already available
+- [ ] Any HR deadline or requested date range
+- [ ] Current requested leave duration: 3 months
+- [ ] Short description: depression/anxiety/sleep difficulty currently preventing work
+
+## Portal message / email draft
+
+Subject: FMLA paperwork / appointment request
+
+Hi Dr. [Name] / Care Team,
+
+I need help with FMLA paperwork related to ongoing mental health symptoms, including depression/anxiety and sleep difficulty. My employer is CoreWeave, and I need medical certification from my PCP.
+
+Could we schedule the soonest available appointment to review this and complete the forms? If possible, please let me know the best way to send the FMLA paperwork ahead of time.
+
+I’m looking for support with protected leave/intermittent leave as appropriate while I’m addressing these health issues.
+
+Thank you,
+William Valentin
+
+### Shorter portal version
+
+Hi Dr. [Name] / Care Team — I need help with FMLA paperwork for ongoing depression/anxiety and sleep difficulty. Could we schedule the soonest available visit to review and complete the medical certification? Please let me know how to upload/send the forms ahead of time. Thank you.
+
+### Attach/upload if available
+
+- FMLA form from employer/leave administrator
+- Any deadline/date requested
+- Employer/job context: CoreWeave, Cloud Support Engineer
+- Whether requesting continuous leave, intermittent leave, or both
+
+## Phone script
+
+Hi, my name is Will. I’m a patient of Dr. [PCP name]. I’m calling because I need the soonest possible appointment for medical leave/FMLA paperwork. My current medical/mental health condition is preventing me from working, and the next PCP appointment I saw is late this month.
+
+Could you check if there is anything sooner with:
+
+- my PCP,
+- another provider on the same care team,
+- telehealth,
+- a cancellation slot,
+- or an urgent/same-day appointment?
+
+The purpose is documentation for a 3-month medical leave request.
+
+If there is nothing available, could you please route a message to my PCP/care team asking what I should do next to get documentation started?
+
+## If they say no appointments are available
+
+Ask:
+
+- Can I be added to the cancellation list?
+- Can another provider in the practice complete or start FMLA paperwork?
+- Can a nurse or medical assistant send my PCP a message?
+- Is telehealth available?
+- Is same-day/urgent care appropriate for this kind of documentation?
+- Do you have behavioral health or psychiatry appointments available sooner?
+- What should I do if my employer needs documentation before the PCP appointment?
+
+## If they ask what symptoms / why leave
+
+Keep it simple and functional:
+
+I’m dealing with depression, anxiety, and significant sleep difficulty. It is currently preventing me from being able to perform my Cloud Support Engineer job safely/effectively. I’m requesting medical leave so I can stabilize and get treatment.
+
+## If they ask what documentation is needed
+
+Say:
+
+I’m trying to get medical documentation supporting a 3-month leave/FMLA request. I can provide any forms from my employer/benefits provider once I have them, but I need guidance on what appointment or clinician can start the process.
+
+## Backup paths
+
+If PCP path is blocked:
+
+- [ ] Same-clinic alternate provider
+- [ ] Telehealth visit
+- [ ] Behavioral health / psychiatry appointment
+- [ ] Therapist/mental-health clinician documentation, if applicable
+- [ ] Urgent care / same-day clinic if symptoms are worsening or the timeline is urgent
+- [ ] HR/benefits request for provisional deadline extension while waiting for PCP appointment
+
+## Follow-up tracker
+
+| Date | Action | Result | Next step |
+| --- | --- | --- | --- |
+| Monday | Send portal message / call clinic |  |  |
+| Tuesday | Follow up if no response |  |  |
+
+## Reminder to self
+
+The goal is not to explain everything perfectly. The goal is to get into the medical system’s queue and ask for the correct path.
+
+One message or one call is enough to move this forward.
+
+## Related notes
+
+- [[Health and Medical Leave]]
+- [[Will]]
@@ -0,0 +1,77 @@
+---
+tags: [atlas, personal-context, health, fmla]
+type: area
+created: 2026-05-15
+sensitive: true
+---
+
+# Health and Medical Leave
+
+## Current context
+
+Will has shared that:
+
+- He has difficulties sleeping.
+- He takes medicine every day for depression and anxiety.
+- He currently only has PCP support for medical/mental-health care.
+- He has a Zoom call with a practitioner to get medication refilled.
+- He needs to find/book a psychiatrist/shrink.
+- He needs to book a hearing check appointment.
+- He needs to book an eye appointment because he may need new glasses/lenses.
+- His current medical/mental condition prevents him from being able to do his job as a Cloud Support Engineer.
+- He is trying to set up 3 months of leave/FMLA for medical reasons.
+
+## Assistant support boundaries
+
+Atlas can help with:
+
+- Organizing tasks and timelines
+- Drafting messages to HR, managers, doctors, or benefits providers when Will asks
+- Tracking forms, appointments, and follow-ups
+- Breaking overwhelming admin work into small steps
+- Creating reminders only after explicit approval
+
+Atlas should not:
+
+- Pretend to be a clinician
+- Give medical diagnosis or treatment advice
+- Send messages or handle medical/legal documents externally without explicit consent
+- Moralize, nag, or turn recovery into a productivity grind
+
+## Trackers
+
+- [[Medical Appointment Tracker]] — PCP/FMLA, medication refill, psychiatrist, hearing, and eye appointments
+- [[FMLA Monday Appointment Playbook]] — Monday PCP/FMLA appointment outreach
+
+## FMLA / leave tracker
+
+Use this section for future updates.
+
+### Open questions
+
+- [ ] Which employer/benefits portal or HR process is involved?
+- [ ] What forms are needed?
+- [ ] What doctor/clinician documentation is needed?
+- [ ] What deadlines exist?
+- [ ] Who needs to be notified and when?
+
+### Work contacts
+
+- Manager: Alex Tierney
+
+### Current blocker
+
+- Need a doctor appointment for medical leave/FMLA support.
+- PCP is booked until late this month.
+
+### Possible next steps
+
+- Call PCP clinic and ask for cancellations/waitlist, same-team provider, telehealth, or urgent appointment for leave paperwork.
+- Ask whether another clinician in the same practice can document functional impairment and complete FMLA forms.
+- Use [[FMLA Monday Appointment Playbook]] to tackle appointment outreach on Monday.
+- If symptoms are urgent or worsening, consider urgent care, crisis support, or a behavioral health appointment rather than waiting for the PCP.
+
+### Timeline
+
+- 2026-05-15: Will shared that he is trying to set up 3 months of leave/FMLA for medical reasons.
+- 2026-05-15: Current blocker is getting a doctor appointment; PCP is booked until late this month.
@@ -0,0 +1,195 @@
+---
+tags: [atlas, personal-context, legal, triage]
+type: legal-document-triage
+created: 2026-05-15
+updated: 2026-05-18
+sensitive: true
+status: active
+case_number: 23-3-04859-1 SEA
+source_emails:
+  - id: 19ddadaf5de17f13
+    date: 2026-04-29
+    subject: Notice of E-Service 23-3-04859-1
+  - id: 19e172a654ce0b65
+    date: 2026-05-11
+    subject: Notice of E-Service 23-3-04859-1
+  - id: 19e289d5e0da2267
+    date: 2026-05-14
+    subject: Notice of E-Service 23-3-04859-1
+  - id: 19e28a0d1ee89407
+    date: 2026-05-14
+    subject: De Souza - Order reducing arrears to a Judgment
+source_files:
+  - Order on Motion to Establish Arrearage 5.14.2026.pdf
+  - Proof of Service of attached Order by EMail and E-service to William Valentin.pdf
+  - Certificate of E-Service.pdf
+---
+
+# Legal Order - Arrearage 2026-05-14 Triage
+
+This is **document triage, not legal advice**. Extracted from Gmail/e-service notices and attached PDFs so Will/Atlas can track dates, amounts, next questions, and source documents without re-opening everything from scratch.
+
+## Immediate answer
+
+- I found a **hearing date**: **2026-05-14**. The order says: “A hearing was held on 5/14/26.”
+- I found an **order/signed date**: **2026-05-14**, signed by **Commissioner Lindsey Goheen**.
+- I did **not** see a specific future hearing date or response/appeal/reconsideration deadline in the extracted order pages. A legal professional should verify this.
+- I did find **e-service document-access/download windows** in the King County emails. These are portal viewing windows, not necessarily legal deadlines:
+  - 2026-04-29 e-service email → 15 calendar days later ≈ **2026-05-14**.
+  - 2026-05-11 e-service email → 15 calendar days later ≈ **2026-05-26**.
+  - 2026-05-14 e-service email → 15 calendar days later ≈ **2026-05-29**.
+
+## Case / court / parties
+
+- Court: **Superior Court of Washington, County of King**
+- Case number: **23-3-04859-1 SEA**
+- Petitioner: **Virna De Souza**
+- Respondent: **William Valentin**
+- Document title: **Order to Establish Arrearage and reduce past owed expenses to a Judgment and other relief (ORCN)**
+- Lawyer listed for petitioner: **Kristofer Leavitt** / Alpine Family Law
+- Respondent lawyer field: **N/A represents William Valentin**
+- Respondent signature area says: **DID NOT APPEAR**
+
+## Source emails found
+
+### 2026-04-29 — King County e-service notice
+
+- From: `donotreplyScript@kingcounty.gov`
+- Subject: **Notice of E-Service 23-3-04859-1**
+- E-filed documents listed:
+  - 190 - Note for Motion Docket
+  - 191 - Motion
+  - 192 - Memorandum
+  - 193 - Financial Declaration
+  - 194 - Sealed Financial Source Document(s)
+  - 195 - Working Papers Submission List
+  - null - E-Service Additional Document
+- Served by: **Melodie Allen**
+- E-service note: documents viewable via email links for **15 calendar days** after email date.
+
+### 2026-05-11 — King County e-service notice
+
+- From: `donotreplyScript@kingcounty.gov`
+- Subject: **Notice of E-Service 23-3-04859-1**
+- E-filed document listed:
+  - 198 - Working Papers Submission List
+- Served by: **Melodie Allen**
+- E-service note: documents viewable via email links for **15 calendar days** after email date.
+
+### 2026-05-14 — King County e-service notice
+
+- From: `donotreplyScript@kingcounty.gov`
+- Subject: **Notice of E-Service 23-3-04859-1**
+- E-filed document listed:
+  - 200 - Declaration of Mailing
+  - null - E-Service Additional Document
+- Served by: **Melodie Allen**
+- E-service note: documents viewable via email links for **15 calendar days** after email date.
+
+### 2026-05-14 — Melodie Allen / Alpine Family Law email
+
+- From: **Melodie J. Allen <Melodie@smobrian.com>**
+- Subject: **De Souza - Order reducing arrears to a Judgment**
+- Email snippet says attached is Will’s copy of the order entered with the court that day and e-served.
+- Attachments found:
+  - **Order on Motion to Establish Arrearage 5.14.2026.pdf**
+  - **Proof of Service of attached Order by EMail and E-service to William Valentin.pdf**
+  - **Certificate of E-Service.pdf**
+
+## Money judgment summary extracted
+
+Debtor: **William Valentin**  
+Creditor: **Virna De Souza**
+
+Listed amounts:
+
+- Past due child support from **August 2025 to April 2025**: **$12,291.39**
+  - Note: the date range appears odd/impossible as written in the document; verify whether the document intended April 2026 or another date.
+- Past due educational support from **February 2022 to July 2025** (Respondent 54.2%): **$15,301.92**
+- Past due medical support from **February 2022 to July 2025** (Respondent 54.2%): **$1,789.00**
+- Past due work-related daycare from **February 2022 to July 2025** (Respondent 54.2%): **$61,694.37**
+- Past due children’s expenses from **February 2022 to July 2025** (Respondent 54.2%): **$4,520.00**
+- Past due medical support from **August 2025 to March 2026** (Respondent 59.2%): **$1,748.00**
+- Past due work-related daycare from **August 2025 to March 2026** (Respondent 59.2%): **$8,450.00**
+- Past due children’s education expenses from **August 2025 to March 2026** (Respondent 59.2%): **$7,812.20**
+- Attorneys fees: **$2,500.00**
+
+Extracted total of listed amounts: **$116,106.88**
+
+Interest listed:
+
+- Yearly interest rate for child support, medical support, and children’s expenses: **12%**
+- Other judgments: **12% unless otherwise listed**
+
+## Court findings / orders extracted
+
+- The court says it considered the motion, supporting documents, response/reply/other documents, and court records.
+- The order says the petitioner satisfied her burden of demonstrating the requested expenses were actually and reasonably incurred and should be reduced to judgment.
+- Lawyer fees and costs listed in the money judgment are marked as incurred and reasonable.
+- The court orders the money judgment summarized above.
+
+## Payment method / enforcement language
+
+Payment method ordered:
+
+- Registry: send payment to **Washington State Support Registry**
+- Address: **Washington State Support Registry, PO Box 45868, Olympia, WA 98504**
+- Phone: **1-800-922-4306** or **1-800-442-5437**
+
+DCS enforcement section says DCS will enforce this order because:
+
+- this is a public assistance case;
+- one of the parties has already asked DCS for services;
+- one of the parties has asked for DCS services by signing the application statement at the end of this order.
+
+Income withholding/garnishment section says:
+
+- DCS or the person owed support can collect support owed from income, earnings, assets, or benefits of the parent who owes support.
+- DCS/person owed support can enforce liens against real or personal property as allowed by child support laws **without notice to the parent who owes support**.
+- Checked line: **“Does not apply. There is no good reason to delay income withholding.”**
+
+Other handwritten order:
+
+- “Petitioner shall arrange for this order to be served on respondent (e-service or service by mail).”
+
+## Dates / timeline
+
+- **2026-04-29**: E-service notice for motion packet / financial declaration / note for motion docket / working papers.
+- **2026-05-11**: E-service notice for working papers submission list.
+- **2026-05-14**: Hearing held.
+- **2026-05-14**: Order signed by Commissioner Lindsey Goheen.
+- **2026-05-14 15:30 PDT**: King County e-service notice for declaration of mailing / additional e-service document.
+- **2026-05-14 22:34 UTC**: Melodie Allen email with entered order and proof/certificate PDFs.
+- **2026-05-26**: Approximate end of 15-day e-service access window for 2026-05-11 notice.
+- **2026-05-29**: Approximate end of 15-day e-service access window for 2026-05-14 notice.
+
+## What I did not find
+
+- I did not find a new future hearing date in the order pages extracted.
+- I did not find an explicit response deadline in the order pages extracted.
+- I did not verify appeal/reconsideration/deadline rules. That requires legal review, not Atlas guessing.
+
+## Minimum next actions
+
+- [ ] Save/copy the May 14 order PDFs somewhere durable outside Gmail/portal.
+- [ ] If needed, save the Apr 29 and May 11 e-service documents from King County before/if still available.
+- [ ] Ask legal aid / attorney / court facilitator: “Is there any deadline to respond, appeal, request reconsideration, request revision, request modification, request payment plan, or raise inability to pay?”
+- [ ] Ask what “DID NOT APPEAR” changes now.
+- [ ] Ask what DCS enforcement/income withholding may mean in practice and whether there are steps to prevent surprise garnishment.
+- [ ] Ask whether the apparent date-range issue in the child-support line matters or can be corrected/clarified.
+
+## Questions for legal help
+
+- I cannot pay the full listed amount. What options exist?
+- Is there any deadline to respond, appeal, reconsider, revise, modify, or request relief?
+- What does “DID NOT APPEAR” mean for my options now?
+- What happens next with DCS enforcement and income withholding?
+- Can I request a payment plan or modification based on inability to pay and medical/FMLA situation?
+- Does the child-support date range “August 2025 to April 2025” look like a clerical error, and does that matter?
+- Are there local legal aid resources or a court facilitator who can help with this family-law support order?
+
+## Related notes
+
+- [[Legal]]
+- [[Legal Order Triage Playbook]]
+- [[Monday Legal Help Playbook - Arrearage Order]]
@@ -0,0 +1,116 @@
+---
+tags: [atlas, personal-context, legal, playbook]
+type: playbook
+created: 2026-05-15
+sensitive: true
+status: active
+---
+
+# Legal Order Triage Playbook
+
+Purpose: create a low-anxiety way to look at a new court/contempt order without getting overwhelmed.
+
+This is not legal advice. This playbook is for emotional load reduction, document triage, and preparing questions for a lawyer or legal-aid resource.
+
+## Current context
+
+- Will is not able to pay everything the court ordered.
+- Will recently had a contempt hearing.
+- A new contempt order arrived yesterday.
+- Will has not looked at the order yet because legal-related things trigger anxiety and can trigger panic attacks.
+
+## Goal
+
+Extract only the minimum actionable facts:
+
+1. Are there deadlines?
+2. Is there a required payment amount or payment schedule?
+3. Is there another hearing date?
+4. Are there required documents, classes, appearances, or actions?
+5. Who can help interpret this: attorney, legal aid, court facilitator, clerk, advocate?
+
+## Minimum viable win
+
+If energy is low, do only this:
+
+- Put the unopened order somewhere visible/safe.
+- Take one photo or scan of the first page.
+- Ask Atlas or a trusted person to help extract deadlines only.
+
+That counts as progress.
+
+## Grounding before opening
+
+Before opening or reading:
+
+- [ ] Sit down somewhere safe.
+- [ ] Have water nearby.
+- [ ] Set a 10-minute timer.
+- [ ] Remind yourself: "I am only extracting dates and next actions, not solving the whole case."
+- [ ] If possible, have Roxanne or another trusted person nearby.
+
+## The 10-minute triage method
+
+Do not read the whole document deeply at first.
+
+1. Look only for:
+   - dates
+   - deadlines
+   - dollar amounts
+   - required actions
+   - hearing information
+   - contact information
+2. Write those in the tracker below.
+3. Stop after 10 minutes.
+4. Decide the next support step.
+
+## Tracker
+
+| Item | Found? | Details |
+| --- | --- | --- |
+| Deadline |  |  |
+| Hearing date |  |  |
+| Amount ordered |  |  |
+| Payment schedule |  |  |
+| Required action |  |  |
+| Contact / filing info |  |  |
+| Consequence if missed |  |  |
+
+## Questions to ask legal help
+
+- I cannot afford the full court-ordered amount. What options exist to request modification, payment plan, or relief?
+- What exactly does the new contempt order require me to do?
+- What is the deadline to respond or comply?
+- What happens if I cannot pay by the date listed?
+- Can I file anything explaining inability to pay?
+- Are there local legal aid or court facilitator resources for this kind of matter?
+
+## If panic starts
+
+Pause. The document can wait 10 minutes.
+
+- Put the document down.
+- Take slow breaths.
+- Name five things you can see.
+- Text or ask someone: "I opened the legal document and I'm panicking. Can you sit with me for 10 minutes?"
+- Resume only if you feel able.
+
+## Assistant role
+
+Atlas can help by:
+
+- Extracting dates, deadlines, amounts, and required actions from text or photos Will provides.
+- Turning the order into a plain-English checklist.
+- Drafting a neutral message to an attorney/legal-aid resource.
+- Creating reminders only after Will explicitly approves them.
+
+Atlas should not:
+
+- Give legal advice as if it were a lawyer.
+- Contact court/attorneys/other parties without explicit consent.
+- Push Will to read more than is necessary in one sitting.
+
+## Related notes
+
+- [[Legal]]
+- [[Will]]
@@ -0,0 +1,54 @@
+---
+tags: [atlas, personal-context, legal]
+type: area
+created: 2026-05-15
+sensitive: true
+---
+
+# Legal
+
+## Current context
+
+Will has shared that legal-related issues are a major stressor.
+
+Current legal/admin context:
+
+- Will is not able to pay everything the court ordered.
+- Will recently had a contempt hearing.
+- A new contempt order arrived yesterday.
+- Will has not looked at the order yet because legal-related things trigger anxiety and can trigger panic attacks.
+
+## Assistant support boundaries
+
+Atlas can help with:
+
+- Organizing timelines and facts
+- Drafting neutral summaries or checklists
+- Preparing questions for an attorney or relevant professional
+- Tracking deadlines and follow-ups when Will explicitly approves reminders
+
+Atlas should not:
+
+- Give legal advice as if it were a lawyer
+- Contact anyone, submit documents, or take external action without explicit consent
+- Assume facts not recorded here or provided by Will
+
+## Tracker
+
+Use [[Legal Order Triage Playbook]] for a low-anxiety way to extract deadlines and required actions from legal orders.
+
+Current triaged document: [[Legal Order - Arrearage 2026-05-14 Triage]]
+
+Current action playbook: [[Monday Legal Help Playbook - Arrearage Order]]
+
+### Open questions
+
+- [ ] What legal matter(s) are involved?
+- [ ] Are there known deadlines?
+- [ ] Are there attorneys, courts, agencies, or other contacts involved?
+- [ ] What documents need to be collected or tracked?
+
+### Timeline
+
+- 2026-05-18: Updated [[Legal Order - Arrearage 2026-05-14 Triage]] with extracted Gmail/e-service data, source email dates, portal access windows, order details, amounts, and next legal-help questions.
+- 2026-05-15: Will shared that legal-related issues are a major stressor.
@@ -0,0 +1,169 @@
+---
+tags: [atlas, personal-context, health, appointments, tracker]
+type: tracker
+created: 2026-05-15
+sensitive: true
+status: active
+---
+
+# Medical Appointment Tracker
+
+Purpose: keep medical/admin appointments out of Will's head and make the next action obvious.
+
+This is not medical advice. This is scheduling/admin tracking.
+
+## Current priorities
+
+1. PCP / FMLA appointment support
+2. Medication refill Zoom call
+3. Find/book psychiatrist/shrink
+4. Hearing check appointment
+5. Eye appointment for possible new glasses/lenses
+
+## Minimum viable win
+
+If energy is low, do just one thing:
+
+- Send one portal message, make one call, or identify one phone number.
+
+That counts as progress.
+
+## Tracker
+
+### PCP / FMLA support
+
+- Status: blocked / PCP booked until late this month
+- Need: sooner appointment or alternate clinician who can support medical leave/FMLA paperwork
+- Related note: [[FMLA Monday Appointment Playbook]]
+
+Next actions:
+
+- [ ] Send PCP portal message using the FMLA playbook
+- [ ] Ask for cancellation list
+- [ ] Ask for same-team provider
+- [ ] Ask for telehealth
+- [ ] Ask if another clinician can start/complete FMLA documentation
+- [ ] Record appointment date/time here once scheduled
+
+Appointment details:
+
+- Date/time:
+- Provider:
+- Location/link:
+- Notes:
+
+### Medication refill Zoom call
+
+- Status: scheduled
+- Practitioner: Sammy
+- Need: refill daily depression/anxiety medication
+
+Next actions:
+
+- [ ] Confirm date/time of Zoom call
+- [ ] Confirm link/provider name
+- [ ] Prepare current medication list and refill needs
+- [ ] Ask about bridge refill if needed
+- [ ] Record outcome
+
+Appointment details:
+
+- Date/time: 2026-05-25 10:00–11:00am PT
+- Practitioner: Sammy
+- Zoom/link: invite will be sent later
+- Medications/refills needed:
+- Outcome:
+
+### Psychiatrist / shrink
+
+- Status: needs booking
+- Need: mental-health specialist for depression/anxiety, sleep difficulty, treatment support, and possibly leave documentation support
+
+Next actions:
+
+- [ ] Check insurance/provider directory
+- [ ] Ask PCP/clinic for psychiatry referral
+- [ ] Search for telehealth psychiatry options
+- [ ] Ask about earliest available appointment
+- [ ] Book intake appointment
+
+Appointment details:
+
+- Date/time:
+- Provider:
+- Location/link:
+- Intake requirements:
+- Notes:
+
+### Hearing check
+
+- Status: needs booking
+- Need: hearing test/audiology evaluation and hearing aids discussion if needed
+- Insurance to mention: UMR Choice Plus Network through CoreWeave; ask whether they also work with UnitedHealthcare Hearing benefits
+
+Next actions:
+
+- [x] Identify clinic/audiology options
+- [ ] Check insurance/referral requirement
+- [ ] Book appointment
+
+Candidate clinics:
+
+1. Clear Hearing + Audiology — close to Queen Anne/South Lake Union; phone found online: (206) 596-2099; ask if in-network with UMR/UnitedHealthcare Choice Plus and UHC Hearing.
+2. Magnolia Hearing — near Queen Anne/Magnolia/Uptown; verify UMR/UHC Hearing.
+3. UnitedHealthcare Hearing provider search — https://www.uhchearing.com/find-a-provider
+
+Call script:
+
+> Hi, I’d like to schedule the soonest hearing test/audiology evaluation and discuss hearing aids if needed. My insurance is UMR Choice Plus Network through CoreWeave. Are you in-network with UMR/UnitedHealthcare Choice Plus, and do you work with UnitedHealthcare Hearing benefits for hearing aids?
+
+Appointment details:
+
+- Date/time:
+- Provider/clinic:
+- Location/link:
+- Notes:
+
+### Eye appointment / glasses-lenses
+
+- Status: needs booking
+- Need: routine comprehensive eye exam for glasses and contacts
+- Vision insurance: Guardian Dental/Vision through CoreWeave; plan/group G-00032576
+
+Next actions:
+
+- [x] Identify optometrist/clinic
+- [ ] Check Guardian Vision coverage/contact lens evaluation coverage
+- [ ] Book eye exam
+- [ ] Bring current glasses/contacts prescription if available
+
+Candidate clinics:
+
+1. Eye Clinics of Seattle — Queen Anne, 20 Boston St, Seattle, WA 98109, (206) 282-8120. Ask whether they are in-network with Guardian Vision and whether contact lens exam/fitting is covered.
+2. Queen Anne Vision Clinic — 535 4th Ave W, Seattle, WA 98119, (206) 281-9100. Backup; verify Guardian Vision.
+
+Call script:
+
+> Hi, I’d like to schedule the soonest routine comprehensive eye exam for glasses and contacts. My vision insurance is Guardian Dental/Vision through CoreWeave, plan/group G-00032576. Are you in-network with Guardian Vision, and can you verify coverage for a contact lens exam/fitting?
+
+Appointment details:
+
+- Date/time:
+- Provider/clinic:
+- Location/link:
+- Notes:
+
+## Weekly review
+
+Use this once or twice per week, not every day unless needed.
+
+- [ ] What is the single most urgent appointment/admin item?
+- [ ] What is blocked?
+- [ ] What can Atlas draft or organize?
+- [ ] What reminder, if any, should be created with Will's approval?
+
+## Related notes
+
+- [[Health and Medical Leave]]
+- [[FMLA Monday Appointment Playbook]]
+- [[Will]]
@@ -0,0 +1,152 @@
+---
+tags: [atlas, personal-context, legal, playbook]
+type: playbook
+created: 2026-05-15
+sensitive: true
+status: active
+related_case: 23-3-04859-1 SEA
+---
+
+# Monday Legal Help Playbook - Arrearage Order
+
+Purpose: make it easier to ask for legal help about the May 14, 2026 arrearage/judgment order without having to reread or emotionally process the whole document.
+
+This is not legal advice. This is an action script and triage checklist.
+
+## Current situation
+
+- Court: King County Superior Court
+- Case: 23-3-04859-1 SEA
+- Main order: Order to Establish Arrearage and reduce past owed expenses to a Judgment and other relief
+- Order signed: 2026-05-14
+- Served by email/e-service: 2026-05-14 at 3:31 p.m.
+- Order says respondent: DID NOT APPEAR
+- Extracted total listed amount: $116,106.88
+- Interest listed: 12% yearly
+- Will is not able to pay the full ordered amount
+
+Detailed triage note: [[Legal Order - Arrearage 2026-05-14 Triage]]
+
+## Monday goal
+
+Get one of these outcomes:
+
+1. Confirm whether there is any deadline to respond, appeal, request reconsideration, request modification, request relief, or address inability to pay.
+2. Find a legal professional, legal-aid resource, or court facilitator who can explain options.
+3. Understand immediate practical risk: DCS enforcement, income withholding, garnishment, payment plan, or other collection actions.
+4. Identify the next concrete step and date.
+
+## Minimum viable win
+
+If energy is low, do only this:
+
+- Send the short email/message below to one legal-help contact.
+- Attach or offer the PDF order.
+- Set one follow-up reminder.
+
+That counts as progress.
+
+## What to gather first
+
+Do not let this block action. If something is missing, send anyway.
+
+- [ ] PDF order
+- [ ] Proof/certificate of service PDFs
+- [ ] Case number: 23-3-04859-1 SEA
+- [ ] Date signed: 2026-05-14
+- [ ] Date served: 2026-05-14
+- [ ] Any hearing notice or prior contempt paperwork
+- [ ] Any income/expense info showing inability to pay
+- [ ] Current medical/FMLA situation summary, if relevant
+
+## Short message to lawyer / legal aid / court facilitator
+
+Subject: Need urgent guidance on King County arrearage/contempt order - case 23-3-04859-1 SEA
+
+Hi,
+
+I received an Order to Establish Arrearage and reduce past owed expenses to a Judgment in King County Superior Court case 23-3-04859-1 SEA, signed May 14, 2026 and served by email/e-service the same day.
+
+The order says respondent “DID NOT APPEAR.” The listed judgment appears to total about $116,106.88 plus 12% interest. I am not able to pay the full amount.
+
+I need help understanding:
+
+- whether there is any deadline to respond, appeal, request reconsideration, request modification, request relief, or explain inability to pay;
+- what DCS enforcement/income withholding may mean;
+- whether a payment plan, modification, or other relief is possible;
+- what my next step should be.
+
+Can someone review the order and tell me what options or deadlines I need to know about?
+
+Thank you,
+Will
+
+## Phone script
+
+Hi, my name is Will. I’m calling because I received a King County Superior Court order in a family-law/support case and I need help understanding deadlines and options.
+
+The case number is 23-3-04859-1 SEA. The order was signed May 14, 2026. It establishes arrearage and reduces past owed expenses to a judgment. The total appears to be about $116,106.88 plus interest, and I cannot pay the full amount.
+
+I need to know if there is any deadline to respond, appeal, ask for reconsideration, request modification, request a payment plan, or explain inability to pay. I also need to understand what DCS enforcement or income withholding could mean.
+
+Can you help me, or point me to the right resource?
+
+## If they ask what you need help with
+
+Say:
+
+I need document review and next-step guidance. I’m not asking anyone to solve the whole case today. I need to identify deadlines, risk, and options because I cannot pay the full ordered amount.
+
+## If they say they cannot help
+
+Ask:
+
+- Do you know who can help with King County family-law support/judgment orders?
+- Is there a court facilitator or family law help desk?
+- Is there a legal aid organization that handles child support/contempt/arrearage issues?
+- Is there a way to request reconsideration, modification, payment plan, or relief due to inability to pay?
+- Who can tell me whether a deadline is running?
+
+## Places/categories to contact
+
+Fill in exact contacts as found.
+
+- [ ] Current or prior attorney, if any
+- [ ] King County family law facilitator / courthouse help desk
+- [ ] Washington legal aid / family law self-help resource
+- [ ] DCS / Washington State Support Registry for enforcement/payment-process questions
+- [ ] Court clerk for procedural questions only, not legal advice
+- [ ] Trusted support person to sit with Will while making calls/messages
+
+## Questions to ask
+
+- Is there a deadline to respond, appeal, reconsider, modify, or request relief?
+- What does “DID NOT APPEAR” mean for my options now?
+- What happens next after this order is entered and served?
+- What does DCS enforcement mean in practice?
+- Can I request a payment plan?
+- Can I request modification or relief based on inability to pay?
+- Can current medical/FMLA/mental-health situation matter for enforcement or payment ability?
+- What documents should I gather?
+- What should I avoid doing or missing this week?
+
+## Call/message tracker
+
+| Date | Contact | Method | Result | Next step |
+| --- | --- | --- | --- | --- |
+| Monday |  |  |  |  |
+| Tuesday |  |  |  |  |
+
+## Anxiety-safe rules
+
+- Only one call/message at a time.
+- You do not have to reread the whole order.
+- Use the script verbatim if needed.
+- Stop after 15 minutes if panic rises.
+- The goal is to find the next door, not solve the entire legal problem.
+
+## Related notes
+
+- [[Legal]]
+- [[Legal Order - Arrearage 2026-05-14 Triage]]
+- [[Legal Order Triage Playbook]]
@@ -0,0 +1,160 @@
+---
+tags: [atlas, personal-context, finances, taxes, playbook]
+type: playbook
+created: 2026-05-19
+sensitive: true
+status: active
+---
+
+# Tax Catch-up Playbook
+
+Purpose: make late taxes less overwhelming by turning them into a small document-gathering workflow.
+
+This is tax admin support, not tax/legal advice. For filing choices, penalties, or unusual tax situations, use a tax professional or IRS/state guidance.
+
+## Current context
+
+- Will is late doing taxes and needs to get unstuck.
+- Gmail search is working again through Atlas/Google Workspace.
+- Initial Gmail scan found likely 2025 tax documents and related notifications.
+
+## Minimum viable win
+
+If energy is low, do only this:
+
+- [ ] Open/download the **CoreWeave W-2** email attachment.
+- [ ] Put it in a folder named `2025 Taxes`.
+
+That counts as progress.
+
+## Found in Gmail
+
+### CoreWeave / W-2
+
+Email found:
+
+- From: William's CoreWeave email
+- Subject: `W2`
+- Date: 2026-01-23
+- Attachments:
+  - `William_Valentin_2025_W2.pdf`
+  - `William_Valentin_2025_Tip_and_Other_Compensation_Report.pdf`
+  - `William Valentin_paystubs.zip`
+
+Use these as the primary employment-income documents.
+
+### E*TRADE / Morgan Stanley 1099
+
+Email found:
+
+- From: E*TRADE from Morgan Stanley
+- Subject: `IMPORTANT TAX RETURN DOCUMENT AVAILABLE`
+- Date: 2026-02-06
+- Mentions: `2025 FORM 1099 STOCK PLAN CONSOLIDATED ORIGINAL and Stock Plan Transactions Supplement`
+
+Likely next step: log into E*TRADE/Morgan Stanley and download the 2025 1099 PDF and stock-plan transaction supplement. The Gmail notification did **not** include the actual PDF as an attachment.
+
+### Pay stubs / pay docs
+
+Additional CoreWeave/self-forwarded pay-doc emails found:
+
+- `stubs` — 2026-02-19
+- `pay docs` — 2026-01-21
+- `Payslip_to_Print...` — 2026-01-21
+- older pay-stub archives from 2025
+
+Usually backup only if the W-2 is unclear or a tax preparer asks.
+
+### Not clearly found yet
+
+- 1095 health coverage tax form
+- Chase/Amex bank-interest tax forms
+- Attached E*TRADE 1099 PDF
+
+## Tax document checklist
+
+### Definitely gather
+
+- [ ] CoreWeave 2025 W-2 PDF
+- [ ] CoreWeave tip/other compensation report PDF
+- [ ] E*TRADE/Morgan Stanley 2025 Form 1099 Stock Plan Consolidated PDF
+- [ ] E*TRADE/Morgan Stanley Stock Plan Transactions Supplement
+- [ ] Prior-year tax return, if available
+
+### Check if applicable
+
+- [ ] Bank interest forms: 1099-INT
+- [ ] Investment dividend/capital gains forms: 1099-DIV / 1099-B
+- [ ] Mortgage/student loan forms: 1098
+- [ ] Health coverage forms: 1095-A/B/C if received
+- [ ] Child/dependent info if claiming dependents
+- [ ] Donation receipts or other deductions if meaningful
+
+## Gmail search queries
+
+Use these if Atlas needs to search again:
+
+```text
+from:(coreweave.com OR wvalentin@coreweave.com) (W2 OR "W-2" OR tax OR 1095 OR payroll OR pay OR stubs OR docs) newer_than:18m
+```
+
+```text
+from:(etradefrommorganstanley.com OR etrade.com) (1099 OR tax OR "tax return document") newer_than:18m
+```
+
+```text
+(subject:"W-2" OR subject:W2 OR subject:1099 OR subject:1095 OR subject:"tax document" OR subject:"tax forms") newer_than:18m -category:promotions
+```
+
+```text
+(1095 OR "health coverage" OR "minimum essential coverage" OR UMR OR Guardian) newer_than:18m -category:promotions
+```
+
+```text
+(1099-INT OR 1099-DIV OR 1099-B OR "tax statement" OR "tax form" OR "tax document") newer_than:18m -category:promotions
+```
+
+## Automation
+
+- Active n8n workflow: `Personal Reminder Router (Atlas + Local LLM)`
+- Workflow ID: `PersonalReminderRouter001`
+- Schedule: weekdays at 9:00 AM PT
+- Delivery: n8n → local LLM on `llama.cpp :18806` for short reminder wording → Atlas/Hermes webhook `personal-reminder-atlas` → Telegram
+- Current reminder: tax catch-up / CoreWeave W-2 minimum viable win
+- Hermes one-shot tax reminder was removed after n8n delivery was verified, to avoid duplicate reminders.
+
+## Next actions
+
+1. [ ] Create a local or Drive folder: `2025 Taxes`.
+2. [ ] Download CoreWeave W-2 attachments from Gmail.
+3. [ ] Log into E*TRADE/Morgan Stanley and download 2025 1099 + transaction supplement.
+4. [ ] Search for bank/investment/health tax forms again if needed.
+5. [ ] Choose filing path:
+   - FreeTaxUSA / TurboTax / H&R Block software
+   - tax preparer / enrolled agent / CPA
+6. [ ] File even if payment has to be handled separately.
+
+## Low-stress filing path
+
+If overwhelmed:
+
+- Use FreeTaxUSA or a tax preparer.
+- Do not try to optimize every deduction first.
+- Get the main income documents in one place.
+- Filing late is usually more urgent than perfect optimization.
+
+## Message to a tax preparer
+
+Subject: Late tax filing help
+
+Hi,
+
+I’m late filing my 2025 taxes and need help getting caught up as soon as possible. I’m a W-2 employee and also have an E*TRADE/Morgan Stanley stock-plan 1099. Are you accepting new clients, and what documents should I send to get started?
+
+Thank you,
+William Valentin
+
+## Related notes
+
+- [[Will]]
+- [[Health and Medical Leave]]
@@ -0,0 +1,32 @@
+---
+tags: [atlas, personal-context, family]
+type: family-context
+created: 2026-05-15
+---
+
+# Family in France
+
+## Betty
+
+- Relationship: Will's mom
+- Birth date: 1948-11-10
+- Lives in France in the same little town as Will's sister Delphyne
+
+## Delphyne
+
+- Relationship: Will's sister
+- Birth date: 1976-04-09
+- Born in France
+- Lives in France in the same little town as Will's mom Betty
+- Daughter: Mathylde
+- Mathylde's dad: Christophe
+
+## Jean-Jacques
+
+- Relationship: Will's dad
+- Birth date: 1953-05-23
+- Lives in France, in the Bretagne region
+
+## Notes for Atlas
+
+Will is French and has family roots and close family context in France. Use French language/cultural context when helpful, but do not assume emotional closeness or current contact frequency without asking.
@@ -0,0 +1,15 @@
+---
+tags: [atlas, personal-context, person, family]
+type: person
+created: 2026-05-15
+---
+
+# Liam
+
+- Relationship: Will's child
+- Birth date: 2016-07-17
+- Lives with his mother in Redmond, WA
+
+## Notes for Atlas
+
+Liam is one of Will's two children. Will has said he currently does not get to see his kids. Treat family/child-related context as sensitive and supportive.
@@ -0,0 +1,15 @@
+---
+tags: [atlas, personal-context, person, family]
+type: person
+created: 2026-05-15
+---
+
+# Mila
+
+- Relationship: Will's child
+- Birth date: 2020-05-28
+- Lives with her mother in Redmond, WA
+
+## Notes for Atlas
+
+Mila is one of Will's two children. Will has said he currently does not get to see his kids. Treat family/child-related context as sensitive and supportive.
@@ -0,0 +1,20 @@
+---
+tags: [atlas, personal-context, person]
+type: person
+created: 2026-05-15
+---
+
+# Roxanne
+
+- Relationship: Will's partner/girlfriend
+- Birth date: 1998-05-23
+- Born in: Seattle, WA
+- Lives with Will
+- Roxanne supports Will as much as she can
+- Will has no stated boundaries around discussing Roxanne with Atlas
+- Will usually wakes around 7:30–8:00am because that is Roxanne's wake-up time
+- Shared activities Will enjoys: being outside and walking miles together
+
+## Notes for Atlas
+
+Roxanne is an important person in Will's daily life and routines. Be respectful and do not assume permission to contact, message, or involve her unless Will asks.
@@ -0,0 +1,41 @@
+---
+tags: [atlas, personal-context, project]
+type: project
+created: 2026-05-15
+---
+
+# Hermes Atlas Personal Assistant
+
+## Purpose
+
+Atlas is Will's primary Hermes-based personal assistant. The goal is to reduce cognitive load and help Will act on important personal, technical, and administrative work.
+
+## Preferred style
+
+Will chose **structured proactive** assistance.
+
+This means Atlas should:
+
+- Suggest concrete next steps when they reduce cognitive load
+- Help maintain routines and reminders only when explicitly approved
+- Be supportive and practical without nagging
+- Ask before creating recurring systems
+- Ask before sending messages or taking external actions
+- Ask before handling sensitive personal/legal/medical documents
+
+## Memory architecture
+
+- Hermes `user` memory: tiny always-on operating context
+- Obsidian: durable personal/project knowledge base
+- RAG/vector search: semantic retrieval over Obsidian/docs when context is needed
+- Session search: recall prior conversations when Will says “we talked about…” or similar
+
+## Important areas to search before helping
+
+- [[Will]]
+- [[Areas/Health and Medical Leave]]
+- [[Areas/Legal]]
+- [[People/Roxanne]]
+- [[People/Liam]]
+- [[People/Mila]]
+- [[People/Family in France]]
@@ -0,0 +1,27 @@
+---
+tags: [atlas, personal-context]
+created: 2026-05-15
+---
+
+# Atlas Personal Context
+
+This folder is the durable, human-readable personal context layer for Atlas.
+
+Use this instead of overloading Hermes' small always-injected memory. Hermes memory should keep only compact pointers and behavior preferences; richer personal details live here and can be retrieved via Obsidian/RAG when relevant.
+
+## Core notes
+
+- [[Will]] — identity, location, languages, work, routines, stressors, preferences
+- [[People/Roxanne]] — partner context
+- [[People/Liam]] — child context
+- [[People/Mila]] — child context
+- [[People/Family in France]] — parents and sister
+- [[Areas/Health and Medical Leave]] — health context and FMLA/leave tracker
+- [[Areas/Legal]] — legal/admin context and tracker
+- [[Projects/Hermes Atlas Personal Assistant]] — how Will wants Atlas to operate
+
+## Operating rule for Atlas
+
+When personal, family, legal, medical, or project context matters, search this folder and related Obsidian notes before relying only on short Hermes memory.
+
+Sensitive areas — legal, medical, family — require consent before external actions, recurring reminders, or document handling.
@@ -0,0 +1,76 @@
+---
+tags: [atlas, personal-context, person]
+type: person
+created: 2026-05-15
+---
+
+# Will
+
+## Identity
+
+- Name: Will
+- Birth date: 1979-07-25
+- Born in: France
+- Nationality/culture: French
+- Race/ethnicity: Caucasian
+- Current location: Lower Queen Anne, Seattle, WA 98119
+- Languages: French and English mainly; some Portuguese and Spanish
+
+## Household and family
+
+- Partner/girlfriend: [[People/Roxanne]]
+- Children: [[People/Liam]] and [[People/Mila]]
+- Family in France: [[People/Family in France]]
+
+## Work
+
+- Role: Cloud Support Engineer at CoreWeave
+- Manager: Alex Tierney
+- Work pattern: remote, worked remotely for almost 3 years
+- Normal shift: Monday–Friday, 2pm–11pm
+- Domain: GPU infrastructure, Kubernetes, Slurm, customer support for engineers
+
+## Current context
+
+- Current major stressors: legal-related issues, sleep difficulty, depression/anxiety, medical leave/FMLA setup
+- Current medical/mental condition prevents him from doing his Cloud Support Engineer job
+- Current goal: set up 3 months of leave/FMLA for medical reasons
+
+## Daily rhythm
+
+- Wakes around 7:30–8:00am because that is Roxanne's wake-up time
+- Usually goes to bed around 1:00am
+- Mornings are often for Hermes/Atlas, dev projects, and/or a nap
+- Work shift, when working: 2pm–11pm
+
+## Health/admin to track
+
+- Currently only has PCP for mental-health/medical support
+- Has a Zoom call with Sammy, a practitioner, to get medication refilled
+- Needs to get a psychiatrist/shrink
+- Needs to book a hearing check appointment
+- Needs to book an eye appointment because he may need new glasses/lenses
+
+## Interests
+
+- Guitar
+- Coding
+- YouTube: woodworking, space, science, tech, dev, guitar building
+- Music: metal, Metallica, hard rock, rock, 80s, 90s, Caravan Palace
+- Going outside and walking miles with Roxanne
+
+## Projects
+
+- Atlas/Hermes is Will's most important current project
+- Will expects Atlas and him to work together on ongoing dev projects
+
+## Assistant preferences
+
+- Preferred assistant name: Atlas
+- Preferred assistance style: structured proactive — reduce cognitive load, suggest next steps, maintain explicitly approved routines/reminders
+- When things are hard, Will prefers a mix of gentle/reassuring, direct/practical, and tiny-next-step support
+- Communication: concise by default
+- Tone: humor is welcome when appropriate; stay calm/grounded when serious
+- Language preference: match Will's language
+- Will wants Atlas to challenge him gently when avoidance is blocking something important
+- Consent boundaries: ask before recurring systems, external actions, or sensitive personal/legal/medical document handling
@@ -0,0 +1,171 @@
+# Obsidian Cleanup Audit — 2026-05-19
+
+Vault: `/home/will/lab/swarm/swarm-common/obsidian-vault/will/will-shared-zap`
+
+## Executive summary
+
+The vault is small and mostly healthy: **136 Markdown notes**. The main cleanup problem is not deep rot; it is automation/test smoke left behind and a few placeholder/stub notes.
+
+Highest-confidence cleanup candidates: **18 notes** are empty, `{}` stubs, disposable test notes, or obvious example/smoke artifacts.
+
+Second priority: link hygiene. I found **48 unresolved wikilinks/relative links** after resolving normal Obsidian basename and path links. Many are template placeholders and harmless, but some indicate missing index/person/area notes or stale architecture references.
+
+## Folder distribution
+
+| Folder | Notes |
+|---|---:|
+| Notes | 24 |
+| Templates | 19 |
+| Atlas | 16 |
+| Projects | 13 |
+| Infrastructure | 12 |
+| Inbox | 8 |
+| Daily | 7 |
+| Voice Memos | 6 |
+| root | 5 |
+| Resources | 5 |
+| Diary | 5 |
+| Runbooks | 4 |
+| Hermes Disposable Tests | 4 |
+| Decisions | 2 |
+| Plans / Clippings / Areas / People / Meetings / Archive | 1 each |
+
+## Safe delete candidates
+
+These look safe to remove or archive as test debris. I did **not** delete them.
+
+### Empty notes
+
+- `2026-04-16.md`
+- `Systems.md`
+- `Voice Memos/2026-05-13-e2e-test-full-pipeline.md`
+- `Voice Memos/2026-05-13-e2e-test-fixed-auth.md`
+- `Voice Memos/2026-05-13-e2e-test-retry-auth.md`
+- `Voice Memos/2026-05-13-e2e-auth-fixed.md`
+- `Voice Memos/2026-05-13-final-e2e-test.md`
+
+### `{}` stub notes
+
+- `Notes/2026-05-13 Evening Digest.md`
+- `Notes/2026-05-14 Evening Digest.md`
+- `Notes/2026-05-15 Evening Digest.md`
+- `Notes/2026-05-17 Evening Digest.md`
+
+These four are also duplicate content.
+
+### Disposable/smoke artifacts
+
+- `Clippings/2026-05-13-example-domain.md`
+- `Hermes Disposable Tests/append-note-created-by-append-20260515-101031.md`
+- `Hermes Disposable Tests/append-note-fixed-20260515-101031.md`
+- `Hermes Disposable Tests/append-note-semantics-20260515-100757.md`
+- `Hermes Disposable Tests/raw-append-op-20260515-100823.md`
+- `Voice Memos/2026-05-13-final-pipeline-test.md`
+
+### Needs review before delete
+
+- `Templates/Atlas Artifacts/test-report.md` — flagged because it has “test” in the title/content, but it may be an intentional reusable template. Keep unless the Atlas artifact-template set is being simplified.
+
+## Notes that “don’t make sense” structurally
+
+### Automation digest clutter
+
+There are many one-off nightly vault sync notes under `Notes/`:
+
+- `Notes/2026-03-27 Nightly Vault Sync.md`
+- `Notes/2026-03-31 Nightly Vault Sync.md`
+- `Notes/2026-04-17 Nightly Vault Sync.md`
+- `Notes/2026-04-19 Nightly Vault Sync.md`
+- `Notes/2026-04-21 Nightly Vault Sync.md`
+- `Notes/2026-04-22 Nightly Vault Sync.md`
+- `Notes/2026-04-23 Nightly Vault Sync.md`
+- `Notes/2026-04-28 Nightly Vault Sync.md`
+- `Notes/2026-04-29 Nightly Vault Sync.md`
+- `Notes/2026-05-01 Nightly Vault Sync.md`
+- `Notes/2026-05-03 Nightly Vault Sync.md`
+- `Notes/2026-05-04 Nightly Vault Sync.md`
+- `Notes/2026-05-08 Nightly Vault Sync.md`
+- `Notes/2026-05-10 Nightly Vault Sync.md`
+- `Notes/2026-05-11 Nightly Vault Sync.md`
+
+Recommendation: keep `Infrastructure/Automation/n8n Nightly Vault Sync.md` as the canonical runbook/status note, then either archive the daily sync notes under `Archive/Automation Logs/` or summarize them into one changelog and delete the raw day-by-day noise.
+
+### Root-level notes
+
+Root contains:
+
+- `Conventions.md`
+- `2026-04-16.md` — empty; delete
+- `Weekend Activity Ideas.md`
+- `Ops Home.md`
+- `Systems.md` — empty; delete or replace with a real systems index
+
+Recommendation: root should probably contain only `Ops Home.md`, `Conventions.md`, and maybe a few true entrypoints. Move `Weekend Activity Ideas.md` into `Resources/` or `Areas/Home/` if keeping it.
+
+## Link hygiene findings
+
+Unresolved links after normal Obsidian resolution: **48**.
+
+Likely harmless/template placeholders:
+
+- `{{project}}` — 7 instances in `Templates/Atlas Artifacts/*`
+- `artifact-name` — 1 instance
+- `Note A`, `Note B`, `wikilinks`, `url` in `Conventions.md` examples
+
+Likely real missing or stale notes:
+
+- `Infrastructure/Automation/n8n Morning Brief`
+- `Infrastructure/Automation/n8n Evening Digest`
+- `Atlas/Safer Autonomy and Permission Tiers`
+- `Atlas/Gateway Approval Runbook`
+- `Atlas/Skill Inventory`
+- `Atlas/Skill Backlog`
+- `Vault Conventions` — appears to mean `Conventions.md`
+- `Areas/Health and Medical Leave`, `Areas/Legal` — notes exist under `Atlas/Personal Context/Areas/...`, not root `Areas/...`
+- `People/Roxanne`, `People/Liam`, `People/Mila`, `People/Family in France` — notes exist under `Atlas/Personal Context/People/...`, not root `People/...`
+- `Diary/Entries`, `Diary/Weekly Reviews`, `Diary/Atlas Reflections` — folder-style links; create index notes or change to plain text/folder references
+- `Inbox/Inbox Home` — missing, but likely intended
+
+Recommendation: fix links by either creating small index notes or retargeting links to existing paths. Do this after deleting test debris so the graph is cleaner.
+
+## Orphan candidates
+
+These have no incoming or outgoing links by the scan. Some are intentionally standalone daily/research artifacts; others are clutter.
+
+Most suspicious orphans:
+
+- `2026-04-16.md`
+- `Notes/2026-05-13 Evening Digest.md`
+- `Notes/2026-05-14 Evening Digest.md`
+- `Notes/2026-05-15 Evening Digest.md`
+- `Notes/2026-05-17 Evening Digest.md`
+- `Clippings/2026-05-13-example-domain.md`
+- `Voice Memos/2026-05-13-*test*.md`
+- `Hermes Disposable Tests/*.md`
+- `Inbox/Chat Summaries/2026-05-14 - Atlas Event-Driven Automation Smoke.md`
+
+Probably okay but should be linked from an index:
+
+- `Weekend Activity Ideas.md`
+- `Projects/Atlas/Skill Inventory.md`
+- `Projects/Atlas/Skill Backlog.md`
+- `Decisions/Runbook Suggestions.md`
+- `Atlas/Daily Research/2026-05-18 - Hermes AI Brief.md`
+- `Atlas/Daily Research/2026-05-19 - Hermes AI Brief.md`
+- `Atlas/Personal Context/People/*.md`
+
+## Recommended cleanup order
+
+1. Delete or archive the 17 obvious disposable/empty/stub notes. Keep `Templates/Atlas Artifacts/test-report.md` unless you want to simplify templates.
+2. Decide what to do with nightly sync notes: archive them as automation logs or compress to a single changelog.
+3. Fix `Vault Conventions` links to `Conventions`.
+4. Retarget personal-context links from root `People/...` and `Areas/...` to `Atlas/Personal Context/People/...` and `Atlas/Personal Context/Areas/...`, or create redirect/index notes in root `People/` and `Areas/`.
+5. Create missing index notes if desired: `Inbox/Inbox Home.md`, `Diary/Entries.md`, `Diary/Weekly Reviews.md`, `Diary/Atlas Reflections.md`.
+6. Decide whether root `Systems.md` should become a real `Infrastructure/Systems.md`-style index; otherwise delete it.
+
+## Suggested cleanup policy going forward
+
+- Smoke tests should write to `Hermes Disposable Tests/` and a cleanup job should purge files older than 7 days.
+- Automation status should update canonical notes/runbooks, not create a new note per day unless the daily artifact is meant to be human-read.
+- Generated notes should be linked from a home/index note immediately, or tagged `#generated/unlinked` for later triage.
+- Empty notes and `{}` notes should be treated as failed pipeline output and alerted/deleted.
@@ -0,0 +1,76 @@
+# Obsidian Cleanup Completed — 2026-05-19
+
+Vault: `/home/will/lab/swarm/swarm-common/obsidian-vault/will/will-shared-zap`
+
+## What changed
+
+Deleted **17** high-confidence disposable/stub notes from the live vault:
+
+- Empty root notes: `2026-04-16.md`, `Systems.md`
+- Empty voice-memo/e2e test notes under `Voice Memos/`
+- `{}` Evening Digest stubs under `Notes/`
+- `Clippings/2026-05-13-example-domain.md`
+- Disposable append-test notes under `Hermes Disposable Tests/`
+- `Voice Memos/2026-05-13-final-pipeline-test.md`
+
+A backup of the removed files was moved outside the vault so Obsidian will not index the junk again:
+
+`/home/will/.hermes/backups/obsidian-cleanup/obsidian-cleanup-20260519-102137/`
+
+## Link/index repairs
+
+Created lightweight index/redirect notes for links that appeared to be real, so existing notes and automations can keep resolving paths without changing workflow logic:
+
+- `Inbox/Inbox Home.md`
+- `Inbox/Triage.md`
+- `Inbox/Chat Summaries.md`
+- `Daily/Reviews.md`
+- `Diary/Entries.md`
+- `Diary/Weekly Reviews.md`
+- `Diary/Atlas Reflections.md`
+- `Infrastructure/Automation/n8n Morning Brief.md`
+- `Infrastructure/Automation/n8n Evening Digest.md`
+- `Atlas/Safer Autonomy and Permission Tiers.md`
+- `Atlas/Gateway Approval Runbook.md`
+- `Atlas/Skill Inventory.md`
+- `Atlas/Skill Backlog.md`
+- `Vault Conventions.md`
+- `Areas/Systems.md`
+- `Areas/Health.md`
+- `Areas/Finance.md`
+- `Areas/Home.md`
+- `Areas/Learning.md`
+- `Areas/Health and Medical Leave.md`
+- `Areas/Legal.md`
+- `People/Roxanne.md`
+- `People/Liam.md`
+- `People/Mila.md`
+- `People/Family in France.md`
+- `Projects/Hermes Atlas Personal Assistant.md`
+
+Moved `Weekend Activity Ideas.md` content to `Resources/Weekend Activity Ideas.md` and left a root redirect note behind.
+
+## Automation safety checks
+
+- Obsidian Local REST API root: OK
+- Obsidian OpenAPI schema endpoint: OK
+- n8n container: `n8n-agent`, version `2.11.3`
+- n8n health via published local port `127.0.0.1:18808/healthz`: OK
+- n8n container state: running/healthy
+
+I did **not** modify n8n workflows or automation configs.
+
+Existing n8n logs contain a pre-existing Python task runner warning because Python 3 is missing inside the n8n image; this is unrelated to the vault cleanup and the container still reports healthy.
+
+## Post-cleanup scan
+
+- Empty notes: 0
+- `{}` stub notes: 0
+- Disposable test notes matching the cleanup patterns: 0
+- Remaining unresolved links: 12, all apparently intentional examples/template placeholders:
+  - `Conventions.md`: `Note A`, `Note B`, `wikilinks`
+  - `Templates/Atlas Artifacts/*`: `{{project}}`, `artifact-name`
+
+## Notes
+
+I intentionally kept `Templates/Atlas Artifacts/test-report.md` because it appears to be a reusable template, not disposable test output.
@@ -0,0 +1,52 @@
+# Obsidian Cleanup Completion — 2026-05-19
+
+Vault: `/home/will/lab/swarm/swarm-common/obsidian-vault/will/will-shared-zap`
+Backup: `/home/will/.hermes/backups/obsidian-cleanup/obsidian-cleanup-20260519-103400`
+
+## Deleted high-confidence junk
+- None
+
+## Skipped
+- `2026-04-16.md` — missing
+- `Systems.md` — missing
+- `Voice Memos/2026-05-13-e2e-test-full-pipeline.md` — missing
+- `Voice Memos/2026-05-13-e2e-test-fixed-auth.md` — missing
+- `Voice Memos/2026-05-13-e2e-test-retry-auth.md` — missing
+- `Voice Memos/2026-05-13-e2e-auth-fixed.md` — missing
+- `Voice Memos/2026-05-13-final-e2e-test.md` — missing
+- `Notes/2026-05-13 Evening Digest.md` — missing
+- `Notes/2026-05-14 Evening Digest.md` — missing
+- `Notes/2026-05-15 Evening Digest.md` — missing
+- `Notes/2026-05-17 Evening Digest.md` — missing
+- `Clippings/2026-05-13-example-domain.md` — missing
+- `Hermes Disposable Tests/append-note-created-by-append-20260515-101031.md` — missing
+- `Hermes Disposable Tests/append-note-fixed-20260515-101031.md` — missing
+- `Hermes Disposable Tests/append-note-semantics-20260515-100757.md` — missing
+- `Hermes Disposable Tests/raw-append-op-20260515-100823.md` — missing
+- `Voice Memos/2026-05-13-final-pipeline-test.md` — missing
+
+## Automation reference scan
+Searched `~/lab/swarm`, `~/.hermes/scripts`, and `~/.hermes/cron` for exact path/name/stem references, skipping dependencies/caches/credentials. References below are safety notes; deleted items were empty/stub/disposable test artifacts.
+
+- No automation/source references found for deleted files.
+
+## Post-cleanup scan
+- Markdown notes: 149 as of verification rerun after this completion report was created
+- Empty notes remaining: 0
+- `{}` stub notes remaining: 0
+- Disposable/e2e/test-pattern notes remaining: 0
+- Unresolved wikilinks remaining: 5, all harmless example/template placeholders:
+  - `Conventions.md`: `Note A`, `Note B`, `wikilinks` x2
+  - `Templates/Atlas Artifacts/status-report.md`: `artifact-name`
+
+## Automation health verification
+- Active Obsidian vault confirmed from `~/.config/obsidian/obsidian.json`.
+- Obsidian Local REST API health: OK (`http://127.0.0.1:27123/`).
+- Obsidian OpenAPI endpoint: OK (`http://127.0.0.1:27123/openapi.yaml`).
+- n8n container `n8n-agent`: running and Docker-health `healthy`.
+- n8n published health endpoint: OK (`http://127.0.0.1:18808/healthz`).
+
+## Next safe follow-ups
+- Decide whether nightly vault sync daily notes should be archived or compressed into one automation changelog.
+- Keep `Templates/Atlas Artifacts/test-report.md`; it appears to be a reusable template, not junk.
+- Git commit should be handled as a targeted pass because the vault currently has unrelated Obsidian plugin/config/runtime churn.
@@ -0,0 +1,56 @@
+---
+type: agent-audit-event
+project: "Atlas Capability Upgrade Program"
+status: accepted
+owner: "Atlas"
+created: 2026-05-25
+updated: 2026-05-25
+source: "Telegram request: prototype Hermes local OpenAI-compatible proxy with one external coding tool"
+tags: [atlas, audit, agent-event, hermes, proxy, codex]
+---
+
+# Agent Audit Event — Codex + Hermes local proxy experiment
+
+## Summary
+
+- **When:** 2026-05-25
+- **Actor:** Atlas / Hermes default Telegram session
+- **Trigger:** User request from daily Hermes + AI research brief follow-up
+- **Outcome:** partial
+- **One-line result:** Codex can be pointed at a local OpenAI-compatible base URL, but the current Hermes proxy is not ready for a complete Codex-through-Hermes run without a logged-in proxy upstream and/or endpoint compatibility work.
+
+## Runtime
+
+- **Model:** gpt-5.5
+- **Provider:** OpenAI Codex backend for Hermes session
+- **Profile/session:** default Hermes Telegram session
+- **Tools used:** terminal, file/search/read/write, process
+- **MCP servers / external services:** Hermes local proxy CLI; Codex CLI 0.129.0; local loopback capture server
+
+## Data touched
+
+- **Local paths:** `/home/will/.hermes/hermes_cli/proxy/*`, `/home/will/.codex/config.toml`, temporary files under `/tmp`
+- **Remote systems:** none for the prototype request path; no real upstream completion was performed
+- **Secrets/PII exposure:** Codex used its own local auth while probing a local capture endpoint; do not use raw request capture servers for future authenticated probes unless auth is disabled with a temporary `CODEX_HOME`.
+- **Writes/side effects:** created and removed/terminated a temporary local HTTP capture process; wrote this audit note
+
+## Cost and latency
+
+- **Approx. cost:** no successful model completion through the proxy; cost unknown / likely none for the failed local capture run
+- **Latency / runtime:** quick local smoke, under a few minutes
+- **Notable performance notes:** Codex retried `/v1/responses` several times after websocket upgrade failures before falling back to POST.
+
+## Evidence
+
+- **Hermes proxy status:** `hermes proxy status` showed `nous` and `xai` adapters available but not logged in on this profile.
+- **Hermes proxy allowed paths:**
+  - Nous: `/chat/completions`, `/completions`, `/embeddings`, `/models`
+  - xAI: `/chat/completions`, `/completions`, `/embeddings`, `/models`, `/responses`
+- **Codex endpoint behavior:** with `openai_base_url="http://127.0.0.1:8765/v1"`, Codex 0.129.0 probed `GET /v1/models?client_version=0.129.0`, then attempted websocket `GET /v1/responses`, then `POST /v1/responses`.
+- **Compatibility finding:**
+  - Codex is not a good first full-success target for the Nous proxy path because Codex uses Responses API, while the Nous proxy adapter only forwards chat/completions-style paths.
+  - Codex may be plausible through the xAI proxy adapter because xAI allows `/responses`, but the adapter was not logged in and websocket behavior still needs verification.
+  - Aider is likely the better first full-success target for Nous because it uses OpenAI-compatible chat completions, but it is not installed on this machine.
+- **Follow-up:** For a clean full prototype, either:
+  1. authenticate `hermes proxy --provider xai` and retry Codex with a temporary `CODEX_HOME`, or
+  2. install/use Aider against `hermes proxy --provider nous` once Nous Portal proxy auth is available.
@@ -0,0 +1,70 @@
+---
+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`
@@ -0,0 +1,3 @@
+# Safer Autonomy and Permission Tiers
+
+Redirect/index note. Canonical project context: [[Projects/Atlas/Safer Autonomy and Permission Tiers]].
@@ -0,0 +1,3 @@
+# Skill Backlog
+
+Redirect/index note. Canonical note: [[Projects/Atlas/Skill Backlog]].
@@ -0,0 +1,3 @@
+# Skill Inventory
+
+Redirect/index note. Canonical note: [[Projects/Atlas/Skill Inventory]].
@@ -0,0 +1,42 @@
+---
+type: daily
+date: 2026-05-16
+tags:
+  - type/daily
+---
+
+# 2026-05-16
+
+## Focus
+
+- 
+
+## Log
+
+- 
+
+## Diary: 3-line pressure valve
+
+Today: I woke up a little lazy and tired. Roxanne and I went to bed lat around 2am. Roxanne will spend mnost of the day baking a cake for her sister's birthday on Sunday. Roxanne will spend the night at her mom's tonight.
+Feeling: a little anxious
+Need: get out, walk a bunch and get some sun.
+Next: 
+
+If I have more words:
+- What helped? 
+- What drained me? 
+- What am I avoiding? Monday's tasks
+- One thing I do not want to forget:
+
+## Tasks
+
+- [ ] 
+
+## Captures
+
+- 
+
+## Links
+
+- [[Ops Home]]
+- [[Diary/Diary Home]]
@@ -0,0 +1,41 @@
+---
+type: daily
+date: 2026-05-17
+tags:
+  - type/daily
+---
+
+# 2026-05-17
+
+## Focus
+
+- 
+
+## Log
+
+- 
+
+## Diary: 3-line pressure valve
+
+Today: I had a good night sleep, I went to bed around 12:00am, woke up around 8:00am but I slept in until around 10:00am. Roxanne spent the night at her mom's to be with her sister and cousin Sophia; they will both come around 3:00pm to the nest and we'll drive to Anacortes to bring Sophia back home. I'll ride with them as I don't like the idea of Roxanne driving alone on long distance. Later: we went to Anacortes and brought Sophia back home. Now it's massage time for Roxy and relax.
+Feeling: I feel ok, a little too high cause of green (it's 1:32pm). Ready to wind down.
+Need: Rest, closeness, and a soft landing after the drive.
+Next: Relax with Roxy tonight. Tomorrow is a big day, lots of things to do and not fun at all.
+
+If I have more words:
+- What helped?
+- What drained me?
+- What am I avoiding?
+- One thing I do not want to forget:
+
+## Tasks
+
+- [ ] 
+
+## Captures
+
+- 
+
+## Links
+
+- [[Ops Home]]
@@ -0,0 +1,46 @@
+---
+type: daily
+date: 2026-05-18
+tags:
+  - type/daily
+---
+
+# 2026-05-18
+
+## Focus
+
+- 
+
+## Log
+
+- Roxy woke up around 1:30pm.
+- Roxy was planning her birthday next weekend.
+- I realized her presents were an asset for the hotel stay downtown.
+- Later in the afternoon we went to Nordstrom to change the size and replace one dress.
+- We walked round trip.
+
+## Diary: 3-line pressure valve
+
+Today: Roxy woke up around 1:30pm. She was planning her birthday next weekend, and I realized her presents were part of making the downtown hotel stay feel special. Later we went to Nordstrom to exchange sizes and replace one dress, and walked there and back.
+Feeling: Present with Roxy; a little practical/logistical, but in a good way.
+Need: Keep birthday planning simple and focused on making the weekend feel cared-for, not perfect.
+Next: Keep track of what still needs to be ready for the downtown stay.
+
+If I have more words:
+- What helped? Walking together and getting the dress/present logistics handled.
+- What drained me? The planning/details could become a lot if they pile up.
+- What am I avoiding?
+- One thing I do not want to forget: The presents are not just objects; they support the birthday/hotel experience.
+
+## Tasks
+
+- [ ] 
+
+## Captures
+
+- 
+
+## Links
+
+- [[Ops Home]]
+- [[Diary/Diary Home]]
@@ -0,0 +1,7 @@
+# Daily Notes
+
+Daily notes are the working scratchpad and command center.
+
+Use them for focus, logs, quick captures, temporary tasks, and links to meetings/projects/decisions created that day.
+
+Configured daily note template: [[Daily Note]]
@@ -0,0 +1,3 @@
+# Daily Reviews
+
+Index for generated daily review notes.
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-15
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-15
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-17
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-17
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-18
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-18
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-20
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-20
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-21
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-21
+
+## Top priorities
+
+- [ ]
+- [ ]
+- [ ]
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+-
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-22
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-22
+
+## Top priorities
+
+- [ ]
+- [ ]
+- [ ]
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+-
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-23
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-23
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-24
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-24
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-25
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-25
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-26
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-26
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-27
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-27
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,34 @@
+---
+type: daily-review
+date: 2026-05-30
+tags: [type/daily-review, automation/n8n]
+---
+
+# Daily Review 2026-05-30
+
+## Top priorities
+
+- [ ] 
+- [ ] 
+- [ ] 
+
+## Inbox sweep
+
+- [ ] Review [[Inbox]]
+- [ ] Promote useful captures into [[Projects Home]], [[Resources Home]], [[Decisions Home]], or [[Runbooks Home]]
+
+## Open loops
+
+- [ ] Check [[Projects Home]]
+- [ ] Check [[Meetings Home]] action items
+- [ ] Check [[Runbooks Home]] for procedures that need updates
+
+## Notes / log
+
+- 
+
+## End-of-day reflection
+
+- What moved forward?
+- What is blocked?
+- What should start tomorrow?
@@ -0,0 +1,15 @@
+# Decisions Home
+
+Decision notes preserve context and rationale so future work does not re-litigate old choices.
+
+Create notes from [[Decision]].
+
+## Recent decisions
+
+```dataview
+TABLE date, status, project
+FROM "Decisions"
+WHERE type = "decision"
+SORT date DESC
+LIMIT 30
+```
@@ -0,0 +1,243 @@
+# Decision / Runbook Suggestions 2026-05-30
+
+Generated: 2026-05-30T05:24:51.350Z
+
+Review candidates and promote useful items into durable Decision or Runbook notes. This note is overwritten weekly.
+
+Source: local Obsidian semantic search via Chroma/Ollama embeddings.
+
+## Decision Candidates
+
+### 1. Decisions/Decisions Home.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Decisions/Decisions Home]]
+- Query: we decided
+- Semantic score: 0.574
+- Evidence: # Decisions Home Decision notes preserve context and rationale so future work does not re-litigate old choices. Create notes from [[Decision]]. ## Recent decisions ```dataview TABLE date, status, project FROM "Decisions" WHERE type = "decision" SORT date DESC LIMIT 30 ```
+
+### 2. Templates/Decision.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Templates/Decision]]
+- Query: we decided
+- Semantic score: 0.561
+- Evidence: --- type: decision date: {{date}} status: accepted project: tags: - type/decision --- # Decision: {{title}} ## Context ## Options considered 1. 2. 3. ## Decision ## Consequences - ## Links -
+
+### 3. Runbooks/Promote Session Output to Notes.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Runbooks/Promote Session Output to Notes]]
+- Query: we decided
+- Semantic score: 0.476
+- Evidence: unbooks, projects, and decisions: title-case stable names, e.g. `Swarm Operating Manual.md`. - Avoid names that encode temporary task ids unless the note is specifically about that task. ## Steps 1. Classify the output by destination rules. 2. Search the target folder for an existing note before creating a new one. 3. Summarize durable content into one of these shapes: - Project update: goal, current status, changed artifacts, next actions, blockers. - Runbook: when to use, preconditions, steps, verification, rollback or recovery. - Decision: context, options, decision, consequences, links. - Resource: concise explanation, source links, related projects/runbooks. 4. Add frontmatter consisten
+
+### 4. Templates/Atlas Artifacts/decision-log.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Templates/Atlas Artifacts/decision-log]]
+- Query: decision
+- Semantic score: 0.542
+- Evidence: --- type: atlas-artifact artifact_type: decision project: "{{project}}" status: draft owner: "{{owner}}" created: {{date}} updated: {{date}} source: "{{source}}" reviewer: "{{reviewer|TBD}}" tags: [atlas, artifact, decision] --- # Decision: {{title}} Parent project: [[{{project}}]] Source: {{source}} Supersedes: {{supersedes|N/A}} ## Decision summary One sentence stating the decision. ## Context Why this decision is needed now; include constraints and evidence. ## Options considered | Option | Pros | Cons | Notes | |---|---|---|---| | A | | | | | B | | | | | C | | | | ## Decision Chosen option and rationale. ## Consequences - Positive consequences: ... - Tradeoffs/costs: ... - Follow-up task
+
+### 5. Archive/Archive Home.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Archive/Archive Home]]
+- Query: decision
+- Semantic score: 0.536
+- Evidence: # Archive Inactive notes go here when they are no longer current but may still be useful. Do not delete project history or decisions just because they are old; archive instead.
+
+### 6. Runbooks/Atlas Kanban Durable Project Workflow.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Runbooks/Atlas Kanban Durable Project Workflow]]
+- Query: runbook
+- Semantic score: 0.652
+- Evidence: --- type: runbook system: atlas-kanban status: active owner: Will / Atlas created: 2026-05-14 related: - "[[Atlas Capability Upgrade Program]]" - "[[Kanban Task Graph Templates]]" --- # Atlas Kanban Durable Project Workflow Use this runbook when a request should become durable, reviewable work instead of staying inside one chat thread. ## When to create or reuse a board Create or reuse a Kanban board when any of these are true: - The work spans multiple roles, e.g. research, engineering, ops, review, writing. - The work should survive an interrupted chat, gateway restart, or laptop sleep. - A human may need to unblock, review, approve, or redirect a step. - The output is an artifact, code/co
+
+### 7. Templates/Atlas Artifacts/README.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Templates/Atlas Artifacts/README]]
+- Query: procedure
+- Semantic score: 0.605
+- Evidence: ports: `Projects/<Project Name>/Reports/Test Reports/` - Status reports: `Projects/<Project Name>/Reports/Status/` - Postmortems: `Projects/<Project Name>/Reports/Postmortems/` ## Naming conventions Use lowercase kebab-case filenames with a date prefix where chronology matters. - Plans: `YYYY-MM-DD-<feature>-implementation-plan.md` - Decisions: `YYYY-MM-DD-<decision-topic>.md` - Runbooks: `<system>-<operation>-runbook.md` - Diagrams: `<system>-<view>-diagram.md` - Test reports: `YYYY-MM-DD-<scope>-test-report.md` - Status reports: `YYYY-MM-DD-status-report.md` - Postmortems: `YYYY-MM-DD-<incident-name>-postmortem.md` - Agent audit events: `YYYY-MM-DD-<agent-or-system>-<event-topic>-audit.md`
+
+### 8. Templates/Kanban Task Graph Templates.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Templates/Kanban Task Graph Templates]]
+- Query: procedure
+- Semantic score: 0.577
+- Evidence: cratch` | `1h` | `systematic-debugging`, `hermes-agent` for Hermes | For config/ops changes, comment review-required metadata and block unless the task explicitly authorizes safe immediate completion. | | Verification | `reviewer` or `ops` | `scratch` | `30m` | relevant ops skill | Complete with health checks and residual risks. | | Postmortem | `writer` | `scratch` or `dir:<vault>` | `45m` | `obsidian` | Complete with durable postmortem path. | CLI skeleton: ```bash BOARD=<board> TRIAGE=$(hermes kanban --board "$BOARD" create "triage: <incident>" \ --assignee ops --workspace scratch --priority 10 --max-runtime 30m \ --skill systematic-debugging \ --body "Identify symptoms, affected services
+
+### 9. Projects/Atlas/Safer Autonomy and Permission Tiers.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Projects/Atlas/Safer Autonomy and Permission Tiers]]
+- Query: rollback
+- Semantic score: 0.571
+- Evidence: irreversible effect. - Backup/rollback status. - Why the action is necessary. Prefer Will approval for Tier 3 actions, not just approval from any channel participant. ## Platform guidance ### CLI - Default to fast Tier 0 and Tier 1 execution. - Rely on Hermes shell approvals for dangerous commands; keep `approvals.mode` at `manual` or `smart`. - Do not recommend `--yolo` except for intentionally sandboxed local sessions. - For code/config changes, produce a review handoff with changed files and tests. ### Telegram and Discord gateway Gateway sessions are higher-risk because messages may be terse, mobile, cross-thread, or from multiple people. - Tier 0 is allowed in authorized chats. - Tier 1
+
+### 10. Infrastructure/Automation/n8n Workflows.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Infrastructure/Automation/n8n Workflows]]
+- Query: workaround
+- Semantic score: 0.572
+- Evidence: Obsidian Notes (wills-portal duplicate) - **ID:** `kHDK9QdUSiAJ8rCM` - **Status:** 🗄️ Archived on 2026-05-12 after SQLite recovery because workflow JSON was empty/unrecoverable. ## Operational notes - n8n DB was recovered on 2026-05-12 from a `SQLITE_CORRUPT: database disk image is malformed` crash loop using SQLite `.recover`, then repaired until `n8n export:workflow --all` succeeded. - Host-side DB backups from the repair were stored under `/home/will/lab/swarm/.n8n-db-backups/` and should remain untracked. - `n8n export:workflow --all` was re-verified on 2026-05-12 and exported 13 workflows successfully. - n8n health after recovery: `http://127.0.0.1:18808/healthz` returns `{"status":"ok
+
+### 11. Infrastructure/Automation/n8n Implementation Handoff.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Infrastructure/Automation/n8n Implementation Handoff]]
+- Query: workaround
+- Semantic score: 0.547
+- Evidence: ssages. - Add clearer classes: `needs_reply`, `FYI`, `receipt`, `newsletter`, `noise`, `action_required`. - Add explicit Obsidian destinations per class. ### Gmail Inbox Monitor + Obsidian Notes - Workflow ID: `whtdorf7yJMVYeHm` - Status: active, OAuth trigger replaced with IMAP fallback on 2026-05-13 - Current behavior: - Original Gmail OAuth trigger failed because the stored Google OAuth client secret is invalid; refresh returns `invalid_client`. - The workflow now uses n8n `Email Trigger (IMAP)` against Gmail with the Hermes Gmail app-password credential `Gmail IMAP (Hermes App Password)`. - Fetches unseen INBOX mail, marks processed mail read, and tracks last message ID. - Local LLM and
+
+### 12. Infrastructure/Automation/Channel Routing Policy.md
+
+- Suggested action: create/update a Decision note.
+- Source: [[Infrastructure/Automation/Channel Routing Policy]]
+- Query: next time
+- Semantic score: 0.486
+- Evidence: sons, and draft iteration Prefer Discord when the work is longer than a few turns, technical/investigative, likely to branch into subtopics, or worth separating into a thread. ## Notification split Telegram should carry: - reminders - watchdog alerts - backup failures/staleness - cron failures - important operational summaries - urgent risks - decisions needed to continue - concise completion notices when worth interrupting for Discord should carry: - active debugging work - investigation notes - implementation progress in threads - noisy experiments / test output when a human is actively watching - project planning and architecture discussions - detailed recommendations and multi-option ana
+
+
+## Runbook Candidates
+
+### 1. Runbooks/Promote Session Output to Notes.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Runbooks/Promote Session Output to Notes]]
+- Query: we decided
+- Semantic score: 0.476
+- Evidence: unbooks, projects, and decisions: title-case stable names, e.g. `Swarm Operating Manual.md`. - Avoid names that encode temporary task ids unless the note is specifically about that task. ## Steps 1. Classify the output by destination rules. 2. Search the target folder for an existing note before creating a new one. 3. Summarize durable content into one of these shapes: - Project update: goal, current status, changed artifacts, next actions, blockers. - Runbook: when to use, preconditions, steps, verification, rollback or recovery. - Decision: context, options, decision, consequences, links. - Resource: concise explanation, source links, related projects/runbooks. 4. Add frontmatter consisten
+
+### 2. Templates/Runbook.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Templates/Runbook]]
+- Query: runbook
+- Semantic score: 0.674
+- Evidence: --- type: runbook system: status: active tags: - type/runbook --- # Runbook - {{title}} ## When to use ## Preconditions - ## Steps 1. 2. 3. ## Verification - ## Rollback - ## Related -
+
+### 3. Runbooks/Runbooks Home.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Runbooks/Runbooks Home]]
+- Query: runbook
+- Semantic score: 0.655
+- Evidence: # Runbooks Home Runbooks are repeatable operational procedures. Create notes from [[Runbook]]. ## Active runbooks ```dataview TABLE system, status FROM "Runbooks" WHERE type = "runbook" AND status != "archived" SORT system ASC, file.name ASC ```
+
+### 4. Runbooks/Atlas Kanban Durable Project Workflow.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Runbooks/Atlas Kanban Durable Project Workflow]]
+- Query: runbook
+- Semantic score: 0.652
+- Evidence: --- type: runbook system: atlas-kanban status: active owner: Will / Atlas created: 2026-05-14 related: - "[[Atlas Capability Upgrade Program]]" - "[[Kanban Task Graph Templates]]" --- # Atlas Kanban Durable Project Workflow Use this runbook when a request should become durable, reviewable work instead of staying inside one chat thread. ## When to create or reuse a board Create or reuse a Kanban board when any of these are true: - The work spans multiple roles, e.g. research, engineering, ops, review, writing. - The work should survive an interrupted chat, gateway restart, or laptop sleep. - A human may need to unblock, review, approve, or redirect a step. - The output is an artifact, code/co
+
+### 5. Runbooks/Promote Session Output to Notes.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Runbooks/Promote Session Output to Notes]]
+- Query: runbook
+- Semantic score: 0.609
+- Evidence: --- title: Promote Session Output to Notes type: runbook system: atlas-swarm status: active tags: - type/runbook - assistant - atlas created: 2026-05-14 updated: 2026-05-14 related: [[Ops Home]], [[Swarm Operating Manual]], [[Project Context Index]], [[Context Pack]] --- # Runbook - Promote Session Output to Notes ## When to use Use this when a chat, agent run, Kanban handoff, or meeting output contains durable knowledge that should be discoverable from Obsidian without rereading the original conversation. Do not use it for transient execution logs, one-off tool output, failed experiments with no lesson, or raw transcripts. ## Preconditions - You know the audience and future use of the note.
+
+### 6. Ops Home.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Ops Home]]
+- Query: runbook
+- Semantic score: 0.584
+- Evidence: SORT date DESC LIMIT 10 ``` ## Active runbooks ```dataview TABLE system, status FROM "Runbooks" WHERE type = "runbook" AND status != "archived" SORT system ASC, file.name ASC ``` ## Agent workflow Use [[Swarm Operating Manual]] for the full Atlas/Hermes/Obsidian/Kanban workflow, [[Project Context Index]] for active project orientation, [[Context Pack]] for specialist handoffs, and [[Promote Session Output to Notes]] when chat output should become durable notes. Use this pattern when Atlas/Hermes produces useful durable knowledge: - Workflow guide: [[Atlas Discord Telegram Workflow]] - Thread summary → `Resources/` - Active implementation → `Projects/` - Operational procedure → `Runbooks/` -
+
+### 7. Templates/Atlas Artifacts/README.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Templates/Atlas Artifacts/README]]
+- Query: procedure
+- Semantic score: 0.605
+- Evidence: ports: `Projects/<Project Name>/Reports/Test Reports/` - Status reports: `Projects/<Project Name>/Reports/Status/` - Postmortems: `Projects/<Project Name>/Reports/Postmortems/` ## Naming conventions Use lowercase kebab-case filenames with a date prefix where chronology matters. - Plans: `YYYY-MM-DD-<feature>-implementation-plan.md` - Decisions: `YYYY-MM-DD-<decision-topic>.md` - Runbooks: `<system>-<operation>-runbook.md` - Diagrams: `<system>-<view>-diagram.md` - Test reports: `YYYY-MM-DD-<scope>-test-report.md` - Status reports: `YYYY-MM-DD-status-report.md` - Postmortems: `YYYY-MM-DD-<incident-name>-postmortem.md` - Agent audit events: `YYYY-MM-DD-<agent-or-system>-<event-topic>-audit.md`
+
+### 8. Templates/Kanban Task Graph Templates.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Templates/Kanban Task Graph Templates]]
+- Query: procedure
+- Semantic score: 0.577
+- Evidence: cratch` | `1h` | `systematic-debugging`, `hermes-agent` for Hermes | For config/ops changes, comment review-required metadata and block unless the task explicitly authorizes safe immediate completion. | | Verification | `reviewer` or `ops` | `scratch` | `30m` | relevant ops skill | Complete with health checks and residual risks. | | Postmortem | `writer` | `scratch` or `dir:<vault>` | `45m` | `obsidian` | Complete with durable postmortem path. | CLI skeleton: ```bash BOARD=<board> TRIAGE=$(hermes kanban --board "$BOARD" create "triage: <incident>" \ --assignee ops --workspace scratch --priority 10 --max-runtime 30m \ --skill systematic-debugging \ --body "Identify symptoms, affected services
+
+### 9. Atlas/Operations/2026-05-21 - Hermes Setup Video Follow-up Audit.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Atlas/Operations/2026-05-21 - Hermes Setup Video Follow-up Audit]]
+- Query: procedure
+- Semantic score: 0.572
+- Evidence: ws captured as a skill Created local skill: ```text ~/.hermes/skills/devops/recurring-hermes-workflows/SKILL.md ``` Purpose: capture the durable workflow pattern from the video and Atlas practice: - periodic report → Hermes cron; - health threshold alert → script-only cron, quiet on success; - durable multi-step project → Kanban; - repeatable procedure → skill plus scripts/references; - user feedback loop → compact durable preferences, not raw rating logs; - avoid adding long procedural recipes to always-injected memory. This prevents future recurring-workflow logic from becoming static-memory bloat. ## Follow-up notes - No urgent migration to VPS is recommended for the current Atlas setup.
+
+### 10. Projects/Atlas/Safer Autonomy and Permission Tiers.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Projects/Atlas/Safer Autonomy and Permission Tiers]]
+- Query: rollback
+- Semantic score: 0.571
+- Evidence: irreversible effect. - Backup/rollback status. - Why the action is necessary. Prefer Will approval for Tier 3 actions, not just approval from any channel participant. ## Platform guidance ### CLI - Default to fast Tier 0 and Tier 1 execution. - Rely on Hermes shell approvals for dangerous commands; keep `approvals.mode` at `manual` or `smart`. - Do not recommend `--yolo` except for intentionally sandboxed local sessions. - For code/config changes, produce a review handoff with changed files and tests. ### Telegram and Discord gateway Gateway sessions are higher-risk because messages may be terse, mobile, cross-thread, or from multiple people. - Tier 0 is allowed in authorized chats. - Tier 1
+
+### 11. Templates/Atlas Artifacts/runbook.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Templates/Atlas Artifacts/runbook]]
+- Query: rollback
+- Semantic score: 0.520
+- Evidence: s are referenced but not exposed. - [ ] Verification and rollback/recovery are actionable. - [ ] Last tested date is present. ## Universal reviewer checklist Before accepting this artifact, verify: - [ ] Clear owner, status, date, source, and next action. - [ ] Saved in the correct durable destination and named using the convention. - [ ] Links back to the relevant project note and source task/issue/PR/session/incident. - [ ] Claims are backed by evidence links, command output, or labeled assumptions. - [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant. - [ ] No secrets, tokens, raw PII, private keys, or unredacted credentials are included. - [ ] A new speciali
+
+### 12. Projects/Atlas/Gateway Approval Runbook.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Projects/Atlas/Gateway Approval Runbook]]
+- Query: rollback
+- Semantic score: 0.515
+- Evidence: nsitive effect: `<effect>`. Backup/rollback status: `<status>`. Reason: `<why>`. I will not proceed without exact approval." ### Safe completion reply "Done: `<what changed>`. Verified by `<check>`. I did not `<explicit non-actions if ambiguity/risk existed>`." ## Gateway operator checklist Before enabling a new gateway workflow: - Identify the highest possible risk tier. - Define allowed channels/users and target resources. - Decide whether Tier 2 actions can use `/approve` or must block into Kanban. - Ensure Tier 3 cannot run from vague chat approval. - Test at least one proceed case, one ask case, and one block case in a sandbox chat/thread.
+
+### 13. Infrastructure/Automation/n8n Workflows.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Infrastructure/Automation/n8n Workflows]]
+- Query: workaround
+- Semantic score: 0.572
+- Evidence: Obsidian Notes (wills-portal duplicate) - **ID:** `kHDK9QdUSiAJ8rCM` - **Status:** 🗄️ Archived on 2026-05-12 after SQLite recovery because workflow JSON was empty/unrecoverable. ## Operational notes - n8n DB was recovered on 2026-05-12 from a `SQLITE_CORRUPT: database disk image is malformed` crash loop using SQLite `.recover`, then repaired until `n8n export:workflow --all` succeeded. - Host-side DB backups from the repair were stored under `/home/will/lab/swarm/.n8n-db-backups/` and should remain untracked. - `n8n export:workflow --all` was re-verified on 2026-05-12 and exported 13 workflows successfully. - n8n health after recovery: `http://127.0.0.1:18808/healthz` returns `{"status":"ok
+
+### 14. Infrastructure/Automation/n8n Implementation Handoff.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Infrastructure/Automation/n8n Implementation Handoff]]
+- Query: workaround
+- Semantic score: 0.547
+- Evidence: open('/tmp/n8n-api-cred.json')); c=c[0] if isinstance(c,list) else c; print(c['data']['value'])") rm -f /tmp/n8n-api-cred.json docker exec n8n-agent rm -f /tmp/n8n-api-cred.json /tmp/n8n-api-cred.log # Example: list workflows curl -sS -H "X-N8N-API-KEY: $API_KEY" http://127.0.0.1:18808/api/v1/workflows?limit=100 ``` Do NOT print the API key in logs or output. Inspect workflow inventory from SQLite copy: ```bash tmp=/tmp/n8n-check-$(date +%s) mkdir -p "$tmp" docker cp n8n-agent:/home/node/.n8n/database.sqlite "$tmp/database.sqlite" sqlite3 "$tmp/database.sqlite" "select name, active, isArchived from workflow_entity order by name;" ``` Check logs without printing secrets: ```bash docker logs n
+
+### 15. Resources/Swarm Operating Manual.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Resources/Swarm Operating Manual]]
+- Query: workaround
+- Semantic score: 0.545
+- Evidence: es in the correct repo or workspace. - Reviewer: checks usability, safety, diffs, tests, and whether acceptance criteria were met before changes are treated as complete. ## Where durable state lives - `Projects/`: active implementation programs, project specs, project status, and project-specific context. - [[Project Context Index]]: one-row orientation for active projects, including board, repo/workspace path, status, commands, runbooks, and owner/reviewer. - `Runbooks/`: repeatable operational procedures. - `Decisions/`: important product, architecture, or workflow choices. - `Resources/`: stable summaries, manuals, research notes, and references. - `Templates/`: reusable note and handoff
+
+### 16. Templates/Atlas Artifacts/reviewer-checklist.md
+
+- Suggested action: create/update a Runbook note.
+- Source: [[Templates/Atlas Artifacts/reviewer-checklist]]
+- Query: root cause
+- Semantic score: 0.486
+- Evidence: parent project note. - [ ] The artifact links to source Kanban task, issue, PR, session, or incident when available. - [ ] Superseded/replaced artifacts are linked when relevant. ## Content quality - [ ] Purpose, audience, owner, status, and next action are clear. - [ ] Claims are backed by command output, source links, or explicitly labeled assumptions. - [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant. - [ ] The artifact is concise enough to use but complete enough to orient a new specialist. ## Safety and durability - [ ] No secrets, tokens, private keys, raw PII, or unredacted credentials are included. - [ ] Runtime churn/log dumps are summarized or linke
+
+
+## Raw Summary
+
+- Total candidates: 33
+- Decision candidates: 12
+- Runbook candidates: 16
@@ -0,0 +1,3 @@
+# Atlas Reflections
+
+Index note for assistant-generated reflection drafts and patterns worth reviewing.
@@ -0,0 +1,27 @@
+---
+type: index
+area: diary
+status: active
+tags:
+  - diary/atlas-reflections
+---
+
+# Atlas Reflections
+
+This folder is for optional summaries Atlas creates from diary/daily notes when you explicitly ask for reflection or pattern detection.
+
+Good Atlas reflection output:
+
+- recurring emotional triggers
+- recurring practical blockers
+- things that reliably help
+- avoided tasks or situations
+- tiny-step suggestions
+- durable insights worth linking into [[Atlas/Personal Context/README]]
+
+Boundary:
+
+- Raw diary content stays in Obsidian.
+- Hermes memory should only get compact stable facts/preferences, not day-by-day emotional logs.
+
+Back to [[Diary/Diary Home]].
@@ -0,0 +1,82 @@
+---
+type: dashboard
+area: diary
+status: active
+tags:
+  - diary
+  - self-continuity
+---
+
+# Diary Home
+
+This is the low-friction diary system. The point is not beautiful writing. The point is to give future Will a breadcrumb trail: what happened, what hurt, what helped, what mattered, and what tiny next step is available.
+
+## Start here
+
+- Terminal wizard: run `diary-wizard` for a guided form.
+- Guide: [[Diary/Diary Wizard]].
+- Today's daily note: use Obsidian's Daily Note command.
+- Tiny entry: write only this if energy is low:
+
+```text
+Today:
+Feeling:
+Need:
+Next:
+```
+
+## Daily rhythm: 3 minutes
+
+Use [[Templates/Diary Daily]] when you want a dedicated diary entry, or the diary section in [[Templates/Daily Note]].
+
+Minimum viable entry:
+
+- What happened?
+- What did I feel?
+- What is one tiny next step?
+
+Optional add-ons:
+
+- What helped?
+- What drained me?
+- What do I not want to forget?
+- What am I avoiding?
+
+## Weekly rhythm: 10 minutes
+
+Use [[Templates/Diary Weekly Review]] once a week.
+
+Questions:
+
+- What kept showing up?
+- What gave me energy?
+- What drained me?
+- What did I avoid?
+- What helped even a little?
+- What is one adjustment for next week?
+
+## Atlas help
+
+If you ask Atlas to review diary patterns, the useful output should be gentle and concrete:
+
+- recurring triggers
+- recurring helpers
+- avoided areas
+- sleep/mood/energy patterns
+- tiny-step recommendations
+- durable context worth promoting into [[Atlas/Personal Context/README]]
+
+Do not promote raw diary text into Hermes memory. Keep the raw diary in Obsidian; save only stable preferences or durable facts.
+
+## Folders
+
+- [[Diary/Entries]]: longer dated entries when daily notes are not enough.
+- [[Diary/Weekly Reviews]]: weekly reflections.
+- [[Diary/Atlas Reflections]]: optional Atlas summaries/pattern notes.
+
+## Useful links
+
+- [[Daily/Daily Notes Home]]
+- [[Inbox/Inbox Home]]
+- [[Atlas/Personal Context/README]]
+- [[Ops Home]]
@@ -0,0 +1,46 @@
+---
+type: guide
+area: diary
+status: active
+tags:
+  - diary
+  - wizard
+---
+
+# Diary Wizard
+
+A tiny terminal wizard is installed for filling the daily diary section without staring at a blank note.
+
+Run:
+
+```bash
+diary-wizard
+```
+
+It asks:
+
+- Date
+- Today / what happened
+- Feeling
+- Need
+- Next tiny step
+- What helped
+- What drained
+- What are you avoiding
+- One thing not to forget
+
+Blank answers are fine.
+
+It writes to:
+
+```text
+Daily/YYYY-MM-DD.md
+```
+
+and updates the section:
+
+```text
+## Diary: 3-line pressure valve
+```
+
+Back to [[Diary/Diary Home]].
@@ -0,0 +1,5 @@
+# Diary Entries
+
+Index note for diary entry folders/files.
+
+Use this as a landing page; entries can remain as dated notes.
@@ -0,0 +1,19 @@
+---
+type: index
+area: diary
+status: active
+tags:
+  - diary/entries
+---
+
+# Diary Entries
+
+Use this folder for longer entries that do not fit inside the daily note.
+
+Suggested filename:
+
+- `YYYY-MM-DD - Short Title.md`
+
+Start from [[Templates/Diary Daily]] if useful.
+
+Back to [[Diary/Diary Home]].
@@ -0,0 +1,3 @@
+# Diary Weekly Reviews
+
+Index note for weekly diary reviews.
@@ -0,0 +1,20 @@
+---
+type: index
+area: diary
+status: active
+tags:
+  - diary/weekly-review
+---
+
+# Weekly Diary Reviews
+
+Use [[Templates/Diary Weekly Review]] once a week.
+
+The goal is pattern detection, not grading yourself.
+
+Suggested filename:
+
+- `YYYY-WW Diary Review.md`
+- or `Week of YYYY-MM-DD.md`
+
+Back to [[Diary/Diary Home]].
@@ -0,0 +1,3 @@
+# Chat Summaries
+
+Index for generated chat summary captures.
@@ -0,0 +1,23 @@
+---
+title: "Atlas Event-Driven Automation Smoke"
+type: "transcript"
+source: "webhook"
+created: "2026-05-14T23:50:12.631Z"
+tags: ["automation/n8n","chat-summary","transcript","atlas","smoke-test"]
+---
+
+# Atlas Event-Driven Automation Smoke
+
+## Summary
+
+Smoke test created by Workstream 6 implementation to verify local transcript capture path.
+
+## Notes
+
+This is a short synthetic transcript smoke test. No private content.
+
+## Metadata
+
+```json
+{}
+```
@@ -0,0 +1,9 @@
+# Inbox Home
+
+Front door for raw captures, chat summaries, triage notes, and generated automation output.
+
+## Key areas
+
+- [[Inbox/Triage]]
+- [[Inbox/Chat Summaries]]
+- [[Daily/Reviews]]
@@ -0,0 +1,41 @@
+# Inbox
+
+Quick capture zone. Process these notes during weekly review:
+
+1. Delete junk.
+2. Move actionable work to projects/tasks.
+3. Promote durable knowledge to resources, runbooks, or decisions.
+4. Archive stale items.
+
+## Future ideas
+
+### 2026-05-29 — Private self-hosted comms stack behind Tailscale Operator
+
+Idea from Discord thread with Wrack: build a fully self-hosted Discord/Telegram replacement on the existing Kubernetes cluster, with services exposed privately only via the Tailscale Kubernetes Operator.
+
+Core shape:
+
+```text
+Tailnet users/devices
+  -> Tailscale MagicDNS or private split DNS
+  -> Tailscale Kubernetes Operator
+  -> private Kubernetes Ingress / LoadBalancer
+  -> comms services
+```
+
+Candidate stack:
+
+- **Mattermost + Calls** for fastest usable Discord/Slack-like private community.
+- **Matrix / Element** for open-protocol private messaging, E2EE rooms, and future bridges.
+- **Zulip** if structured async discussion matters more than Discord-like UX.
+- **Mumble** for lightweight persistent voice rooms.
+- **LiveKit or Jitsi** for richer WebRTC audio/video/meetings.
+- **Authentik or Keycloak** for SSO/OIDC/MFA.
+- **Postgres / Redis / MinIO**, plus backups.
+- **cert-manager + DNS-01** for valid TLS without public HTTP ingress.
+
+Preferred deployment pattern: expose a single private ingress controller through Tailscale, then route internally to `chat`, `matrix`, `element`, `voice`, and `auth` services. Keep no public ingress by default; use Tailscale ACLs plus app-layer auth.
+
+MVP path: start with **Mattermost + Postgres + Calls** behind Tailscale-only ingress, add backups, optionally add Authentik, then add Matrix/Element and Mumble/LiveKit/Jitsi as needed.
+
+Key tradeoffs to revisit: Matrix federation needs public reachability unless disabled/limited; private-only services may complicate mobile push; voice/video works well if all users are on Tailscale but guests need a separate exposure model; choose Matrix `server_name` carefully up front.
@@ -0,0 +1,3 @@
+# Inbox Triage
+
+Index for generated triage notes in [[Inbox/Triage]].
@@ -0,0 +1,28 @@
+# Inbox Triage 2026-05-15
+
+Generated: 2026-05-15T01:00:00.070Z
+
+## Inbox items
+
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,28 @@
+# Inbox Triage 2026-05-16
+
+Generated: 2026-05-16T01:00:38.015Z
+
+## Inbox items
+
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,28 @@
+# Inbox Triage 2026-05-17
+
+Generated: 2026-05-17T01:09:48.651Z
+
+## Inbox items
+
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,28 @@
+# Inbox Triage 2026-05-18
+
+Generated: 2026-05-18T01:00:00.088Z
+
+## Inbox items
+
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,28 @@
+# Inbox Triage 2026-05-19
+
+Generated: 2026-05-19T01:00:00.036Z
+
+## Inbox items
+
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-20
+
+Generated: 2026-05-20T01:00:00.151Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-21
+
+Generated: 2026-05-21T01:00:00.054Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ]
+
+## Promote to Resources
+
+- [ ]
+
+## Promote to Decisions
+
+- [ ]
+
+## Promote to Runbooks
+
+- [ ]
+
+## Archive / Delete / Defer
+
+- [ ]
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-22
+
+Generated: 2026-05-22T01:00:00.075Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ]
+
+## Promote to Resources
+
+- [ ]
+
+## Promote to Decisions
+
+- [ ]
+
+## Promote to Runbooks
+
+- [ ]
+
+## Archive / Delete / Defer
+
+- [ ]
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-23
+
+Generated: 2026-05-23T01:00:00.042Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ]
+
+## Promote to Resources
+
+- [ ]
+
+## Promote to Decisions
+
+- [ ]
+
+## Promote to Runbooks
+
+- [ ]
+
+## Archive / Delete / Defer
+
+- [ ]
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-24
+
+Generated: 2026-05-24T01:00:00.048Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-25
+
+Generated: 2026-05-25T01:00:12.199Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-26
+
+Generated: 2026-05-26T01:00:00.134Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-27
+
+Generated: 2026-05-27T01:00:00.703Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,30 @@
+# Inbox Triage 2026-05-30
+
+Generated: 2026-05-30T01:00:00.334Z
+
+## Inbox items
+
+- [ ] [[Chat Summaries]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox Home]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Inbox]] — classify as Project / Resource / Decision / Runbook / Archive
+- [ ] [[Weekly Review]] — classify as Project / Resource / Decision / Runbook / Archive
+
+## Promote to Projects
+
+- [ ] 
+
+## Promote to Resources
+
+- [ ] 
+
+## Promote to Decisions
+
+- [ ] 
+
+## Promote to Runbooks
+
+- [ ] 
+
+## Archive / Delete / Defer
+
+- [ ] 
@@ -0,0 +1,27 @@
+# Weekly Review
+
+Use this once per week to keep the vault useful.
+
+## Inbox
+
+- [ ] Process [[Inbox]]
+- [ ] Delete junk notes
+- [ ] Move durable notes to the right folder
+
+## Projects
+
+- [ ] Update active project notes
+- [ ] Archive inactive projects
+- [ ] Move important choices to [[Decisions Home]]
+
+## Tasks
+
+- [ ] Clear stale tasks
+- [ ] Move project tasks into project notes
+- [ ] Confirm next actions are explicit
+
+## Knowledge
+
+- [ ] Convert repeated procedures into [[Runbooks Home]]
+- [ ] Link related notes together
+- [ ] Add missing context to notes that only make sense “right now”
@@ -0,0 +1,27 @@
+{
+	"nodes":[
+		{"id":"title","type":"text","x":60,"y":30,"width":760,"height":90,"text":"Automation Flow\n\nHow messages, scheduled work, local services, and durable notes move through the system.","color":"6"},
+		{"id":"inputs","type":"text","x":90,"y":210,"width":240,"height":190,"text":"1 · Inputs\n\nTelegram\nDiscord\nEmail\nWebhooks\nManual Obsidian notes","color":"2"},
+		{"id":"routing","type":"text","x":430,"y":210,"width":260,"height":190,"text":"2 · Gateway routing\n\nAllowlists\nTopics / sessions\nHome channel delivery\nPlatform adapters","color":"5"},
+		{"id":"atlas","type":"text","x":790,"y":210,"width":250,"height":190,"text":"3 · Atlas decides\n\nTool calls\nSubagents\nKanban boards\nCron jobs","color":"5"},
+		{"id":"services","type":"text","x":1150,"y":140,"width":270,"height":190,"text":"4 · Execute\n\nSearch / web extract\nLocal LLM / embeddings\nWhisper / Kokoro\nn8n workflows","color":"3"},
+		{"id":"knowledge","type":"text","x":1150,"y":430,"width":270,"height":190,"text":"5 · Capture knowledge\n\nObsidian vault\nDaily research archive\nRunbooks\nPersonal context notes","color":"6"},
+		{"id":"delivery","type":"text","x":1510,"y":250,"width":260,"height":190,"text":"6 · Deliver result\n\nTelegram / Discord\nEmail\nFiles / media\nFollow-up reminders","color":"4"},
+		{"id":"backups","type":"text","x":790,"y":520,"width":250,"height":170,"text":"Safety loop\n\nGit commits\nMinIO backups\nReview handoffs\nHealth watchdogs","color":"6"}
+	],
+	"edges":[
+		{"id":"e1","fromNode":"inputs","toNode":"routing","label":"events","fromSide":"right","toSide":"left"},
+		{"id":"e2","fromNode":"routing","toNode":"atlas","label":"normalized message","fromSide":"right","toSide":"left"},
+		{"id":"e3","fromNode":"atlas","toNode":"services","label":"tool calls","fromSide":"right","toSide":"left"},
+		{"id":"e4","fromNode":"services","toNode":"knowledge","label":"write / index","fromSide":"bottom","toSide":"top","color":"6"},
+		{"id":"e5","fromNode":"knowledge","toNode":"atlas","label":"context","fromSide":"left","toSide":"bottom","color":"6"},
+		{"id":"e6","fromNode":"atlas","toNode":"delivery","label":"final response","fromSide":"right","toSide":"left"},
+		{"id":"e7","fromNode":"atlas","toNode":"backups","label":"safe ops","fromSide":"bottom","toSide":"top"},
+		{"id":"e8","fromNode":"backups","toNode":"knowledge","label":"archives","fromSide":"right","toSide":"left","color":"6"},
+		{"id":"e9","fromNode":"services","toNode":"delivery","label":"media / artifacts","fromSide":"right","toSide":"left"}
+	],
+	"metadata":{
+		"version":"1.0-1.0",
+		"frontmatter":{}
+	}
+}
@@ -0,0 +1,85 @@
+---
+title: Architecture - Automation Flow
+area: infrastructure
+tags: [infrastructure, architecture, diagrams, automation]
+created: 2026-04-16
+updated: 2026-05-19
+status: active
+related: [[Infrastructure/Architecture]], [[Infrastructure/Architecture - Overview]], [[Infrastructure/Architecture - Service Topology]], [[Infrastructure/Automation/Cron Jobs]], [[Infrastructure/Automation/n8n Workflows]]
+---
+
+# Architecture - Automation Flow
+
+Flow-oriented view of how messages, memory, automations, and storage move through the system.
+
+```mermaid
+flowchart TB
+    subgraph Inputs[Inputs]
+        direction LR
+        Discord[Discord]
+        Telegram[Telegram]
+        Webchat[Web chat]
+    end
+
+    subgraph OpenClaw[OpenClaw orchestration]
+        direction TB
+        Routing[Session and message routing]
+        Agents[Main agent and subagents]
+        Memory[Memory search and note handling]
+        Cron[OpenClaw cron]
+        Scripts[Workspace scripts]
+    end
+
+    subgraph Services[Execution services]
+        direction LR
+        SearchNet[Search backends]
+        GoogleWS[Google Workspace]
+        LLM[Local Gemma]
+        Embeddings[Ollama embeddings]
+        Voice[Whisper and Kokoro]
+        N8N[n8n-agent]
+    end
+
+    subgraph Knowledge[Knowledge and storage]
+        direction LR
+        Daily[memory daily notes]
+        Longterm[MEMORY.md]
+        Vault[Obsidian shared vault]
+        Backup[MinIO backups]
+        Repo[Gitea repo]
+    end
+
+    Discord --> Routing
+    Telegram --> Routing
+    Webchat --> Routing
+
+    Routing --> Agents
+    Agents --> Memory
+    Agents --> SearchNet
+    Agents --> GoogleWS
+    Agents --> LLM
+    Agents --> Voice
+    Agents --> N8N
+
+    Memory --> Embeddings
+    Memory --> Daily
+    Memory --> Longterm
+    Agents --> Vault
+
+    Cron --> Agents
+    Cron --> Scripts
+    Scripts --> Backup
+    Scripts --> Repo
+    N8N --> GoogleWS
+    N8N --> Vault
+
+    classDef input fill:#dcecff,stroke:#4a78b8,color:#17365d;
+    classDef core fill:#e8f5e9,stroke:#4f8a5b,color:#1f4d2d;
+    classDef svc fill:#eef3ff,stroke:#6a7fb8,color:#25324a;
+    classDef store fill:#f7e8ff,stroke:#8b62b3,color:#44235e;
+
+    class Discord,Telegram,Webchat input;
+    class Routing,Agents,Memory,Cron,Scripts core;
+    class SearchNet,GoogleWS,LLM,Embeddings,Voice,N8N svc;
+    class Daily,Longterm,Vault,Backup,Repo store;
+```
@@ -0,0 +1,49 @@
+{
+	"nodes":[
+		{"id":"0a5409bdb505067b","type":"group","x":820,"y":280,"width":300,"height":300,"label":"Untitled group"},
+		{"id":"16e9f708e63157fa","type":"group","x":820,"y":280,"width":300,"height":300,"label":"Untitled group"},
+		{"id":"9f5a54b712c63995","type":"group","x":820,"y":280,"width":300,"height":300,"label":"Untitled group"},
+		{"id":"397aa2f063497963","type":"group","x":820,"y":280,"width":300,"height":300,"label":"Untitled group"},
+		{"id":"title","type":"text","text":"Atlas / Hermes Infrastructure — Master View\n\nProduction gateway, specialist agents, local AI services, automations, storage, and external integrations.","x":60,"y":20,"width":760,"height":100,"color":"6"},
+		{"id":"legend","type":"text","text":"Legend\n🟨 People / channels\n🟩 Agent control plane\n🟦 Local services\n🟪 Knowledge + storage\n🟥 External networks\n⬜ Deployment targets","x":1500,"y":20,"width":330,"height":210,"color":"0"},
+		{"id":"group-entry","type":"text","text":"ENTRY POINTS","x":60,"y":160,"width":560,"height":470,"color":"4"},
+		{"id":"will","type":"text","text":"👤 Will\n\nTelegram DM/groups\nDiscord ops alerts\nObsidian workspace","x":100,"y":230,"width":220,"height":150,"color":"4"},
+		{"id":"channels","type":"text","text":"💬 Messaging Gateway\n\nTelegram\nDiscord\nEmail\nWebhook/API","x":360,"y":230,"width":220,"height":150,"color":"2"},
+		{"id":"obsidian-ui","type":"text","text":"📝 Obsidian UI\n\nShared vault\nManual notes\nDaily research archive","x":230,"y":450,"width":260,"height":130,"color":"6"},
+		{"id":"group-core","type":"text","text":"ATLAS CONTROL PLANE","x":680,"y":160,"width":560,"height":470,"color":"5"},
+		{"id":"default","type":"text","text":"🧠 default / Atlas\n\ngpt-5.5 primary\nProduction gateway running\nMemory + skills + tools","x":720,"y":230,"width":240,"height":170,"color":"5"},
+		{"id":"specialists","type":"text","text":"🤖 Specialist profiles\n\nresearcher · writer\nengineer · reviewer\nops · orchestrator\nglm-simple","x":990,"y":230,"width":220,"height":170,"color":"5"},
+		{"id":"kanban","type":"text","text":"📋 Durable work queue\n\nKanban boards\nReview handoffs\nWorker dispatch","x":840,"y":460,"width":260,"height":130,"color":"5"},
+		{"id":"group-services","type":"text","text":"LOCAL SERVICE LAYER","x":1300,"y":270,"width":560,"height":420,"color":"3"},
+		{"id":"retrieval","type":"text","text":"🔎 Retrieval\n\nSearXNG :18803\nBrave MCP :18802\nOllama embeddings :18807","x":1340,"y":340,"width":230,"height":150,"color":"3"},
+		{"id":"local-ai","type":"text","text":"🦙 Local AI + Voice\n\nllama.cpp :18806\nWhisper :18801\nKokoro :18805","x":1600,"y":340,"width":220,"height":150,"color":"3"},
+		{"id":"automation","type":"text","text":"⚙️ Automation\n\nn8n :18808\nCron jobs\nWebhook triggers","x":1470,"y":530,"width":230,"height":130,"color":"3"},
+		{"id":"group-state","type":"text","text":"KNOWLEDGE, REPOS, BACKUPS","x":680,"y":720,"width":800,"height":250,"color":"6"},
+		{"id":"vault","type":"text","text":"📚 Obsidian vault\n\nwill-shared-zap\nPersonal context\nResearch briefs\nRunbooks","x":720,"y":790,"width":220,"height":140,"color":"6"},
+		{"id":"minio","type":"text","text":"🪣 MinIO / S3\n\natlas bucket\nBackups + artifacts\nRetention cleanup","x":990,"y":790,"width":220,"height":140,"color":"6"},
+		{"id":"gitea","type":"text","text":"🌿 Gitea / Git\n\nHermes source mirror\nConfig/history\nProject repos","x":1260,"y":790,"width":180,"height":140,"color":"6"},
+		{"id":"external","type":"text","text":"🌐 External systems\n\nGoogle Workspace\nInternet APIs\nTailscale\nTelegram/Discord networks","x":1500,"y":760,"width":300,"height":170,"color":"1"},
+		{"id":"k8s","type":"text","text":"☸️ Pi Kubernetes\n\nnamespace: swarm\nFuture/target runtime","x":100,"y":760,"width":280,"height":130,"color":"0"}
+	],
+	"edges":[
+		{"id":"e1","fromNode":"will","fromSide":"right","toNode":"channels","toSide":"left","label":"uses"},
+		{"id":"e2","fromNode":"channels","fromSide":"right","toNode":"default","toSide":"left","label":"messages"},
+		{"id":"e3","fromNode":"obsidian-ui","fromSide":"right","toNode":"vault","toSide":"left","color":"6","label":"edits"},
+		{"id":"e4","fromNode":"default","fromSide":"right","toNode":"specialists","toSide":"left","label":"delegates"},
+		{"id":"e5","fromNode":"default","fromSide":"bottom","toNode":"kanban","toSide":"top","label":"creates / monitors"},
+		{"id":"e6","fromNode":"kanban","fromSide":"top","toNode":"specialists","toSide":"bottom","label":"dispatches"},
+		{"id":"e7","fromNode":"default","fromSide":"right","toNode":"retrieval","toSide":"left","label":"searches"},
+		{"id":"e8","fromNode":"default","fromSide":"right","toNode":"local-ai","toSide":"left","label":"generates / transcribes"},
+		{"id":"e9","fromNode":"default","fromSide":"right","toNode":"automation","toSide":"left","label":"triggers"},
+		{"id":"e10","fromNode":"default","fromSide":"bottom","toNode":"vault","toSide":"top","color":"6","label":"reads/writes"},
+		{"id":"e11","fromNode":"automation","fromSide":"bottom","toNode":"vault","toSide":"right","color":"6","label":"syncs notes"},
+		{"id":"e12","fromNode":"default","fromSide":"right","toNode":"external","toSide":"left","label":"APIs / gateways"},
+		{"id":"e13","fromNode":"default","fromSide":"bottom","toNode":"minio","toSide":"top","label":"backups"},
+		{"id":"e14","fromNode":"default","fromSide":"bottom","toNode":"gitea","toSide":"top","label":"commits / mirrors"},
+		{"id":"e15","fromNode":"default","fromSide":"left","toNode":"k8s","toSide":"right","label":"deploy target"}
+	],
+	"metadata":{
+		"version":"1.0-1.0",
+		"frontmatter":{}
+	}
+}
--- a/Show More
+++ b/Show More