From 31d09a6ed190739e33c951d19889c51e47c91c69 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Sun, 9 Aug 2026 04:17:07 +0200 Subject: [PATCH] docs: qualify workspace decision ids cited from this repo Decision ids are per-vault sequences, so they collide by construction once there is more than one vault -- and every repo now has one. A bare D-15 here will mean this repo's D-15 the moment this repo records one. Cross-vault references are therefore qualified: workspace D-15. Not hypothetical: pql holds D-1 through D-31 while the workspace holds D-1 through D-21, so every workspace id currently collides with an unrelated pql one. A bare id is not wrong the day it is written -- it decays into wrong as the other vault grows, and nothing flags it. Co-Authored-By: Claude --- CLAUDE.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 4d044ff..8be11f3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -30,7 +30,7 @@ exist". backend.** A cold `import src.main` inside the container shows `agents, anthropic, chat, core, main, models, responses` — no `ollama`. The only import of it is a *function-body* one at `src/anthropic/model_selector.py:230`. Meanwhile `PREFER_CLOUD_BACKEND=false`, so every request -actually goes to Ollama and the Claude path is off (see **D-11**). Reading the module list +actually goes to Ollama and the Claude path is off (see **workspace D-11**). Reading the module list naively gives you exactly the wrong answer: the package that looks live is the disabled fallback, and the one that looks dead is the hot path. Do not conclude anything about backends from `sys.modules`; read the config. @@ -46,10 +46,10 @@ populated. Recorded in the workspace vault, not here. Read before assuming anything about the LLM backend: ```bash -/home/jpmschweitzer/.local/bin/pql --vault /mnt/media/Projects decisions read D-11 +/home/jpmschweitzer/.local/bin/pql --vault /mnt/media/Projects decisions read workspace D-11 ``` -**D-11 — the Claude migration is abandoned. Tatlock stays on Ollama.** Do not resume it and do +**workspace D-11 — the Claude migration is abandoned. Tatlock stays on Ollama.** Do not resume it and do not treat its remnants as unfinished work. What you will find, and why none of it is a TODO: `ANTHROPIC_MODEL` is set on the container (`claude-sonnet-4-20250514`) and never used because `PREFER_CLOUD_BACKEND=false`; `ANTHROPIC_API_KEY` is a variable reference whose literal was @@ -149,7 +149,7 @@ The old AGENTS.md pointed at **`portainer-core`** for full-stack documentation. Work lives in **pql**, not a markdown TODO. **This repo's vault is standalone** — its tickets and internal decisions live here in `.pql/` and `governance/`, and travel with a clone, because -`.pql/changelog/` is committed and replayed by the git hooks (D-15). The databases are gitignored +`.pql/changelog/` is committed and replayed by the git hooks (workspace D-15). The databases are gitignored and rebuildable with `pql plan rebuild`. `pql` is **not** on the non-interactive `PATH` — invoke it as `/home/jpmschweitzer/.local/bin/pql`. @@ -169,7 +169,7 @@ Stack decisions that constrain this service need the flag: The workspace domain is `tatlock-api`, not `tatlock` — pql rejects a domain stem that prefixes another, and `tatlock` prefixes `tatlock-ui`. A `tatlock-api -> tatlock` symlink at the workspace -root makes the directory answer to both (D-15). +root makes the directory answer to both (workspace D-15). Note `ticket new --decision D-N` resolves ids within **one** vault, so a ticket here cannot link to a workspace decision. Cite the id in the ticket body instead.