From b4d5c4d9b2487a86a05f9017ca222f9d6fab3e49 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Sun, 9 Aug 2026 04:17:29 +0200 Subject: [PATCH] docs: correct the vault policy, and qualify workspace decision ids This repo's Work tracking section still described the reversed policy -- that tickets and decisions live in the workspace vault and this repo's trees stay empty. That was overturned the same day: repo vaults are standalone and a repo's work travels with a clone, because the changelog is committed. Every other repo was corrected at the time; this one was missed because the search for the offending phrase used a fixed string and the phrase happened to wrap across a line break here. Worth noting as a search failure rather than a writing one -- five files were checked, four matched, and the fifth was reported clean. Decision ids are also qualified now. They are per-vault sequences, so a bare D-15 here will mean this repo's D-15 the moment this repo records one; pql already holds D-1 through D-31 against the workspace's D-1 through D-21, all of them unrelated. Co-Authored-By: Claude --- CLAUDE.md | 29 ++++++++++++++++++----------- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 1f3bf3b..e93c3b8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -125,24 +125,31 @@ pytest and ruff only run locally or on request. Verify tests pass before tagging ## Work tracking -Work lives in **pql**, not a markdown TODO or `docs/COVERAGE.md`. Tickets *and* decisions for -this repo live in the **workspace** vault; this repo's `.pql/` and `governance/` trees stay -empty (D-15). +Work lives in **pql**, not a markdown TODO or `docs/COVERAGE.md`. **This repo's vault is +standalone** — its tickets and its internal decisions live here in `.pql/` and `governance/`, +and travel with a clone, because `.pql/changelog/` is committed and replayed by the git hooks +(workspace D-15). The databases are gitignored and rebuildable with `pql plan rebuild`. -Two things must be spelled out on every invocation from in here, and each fails differently: +`pql` is **not** on the non-interactive `PATH` — invoke it as +`/home/jpmschweitzer/.local/bin/pql`. From inside this repo no `--vault` is needed: pql anchors +at the nearest `.git/` ancestor, which is this repo. -- **`pql` is not on the non-interactive `PATH`** — use `/home/jpmschweitzer/.local/bin/pql`. -- **`--vault /mnt/media/Projects` is mandatory.** pql anchors a vault at the nearest `.git/` - ancestor, and this repo is one, so a bare call resolves to *this repo's* empty vault. Reads - return nothing; a **write** creates a stray vault and starts ticket ids at T-1, colliding - with the real ones. +```bash +/home/jpmschweitzer/.local/bin/pql ticket list # this repo's open work +/home/jpmschweitzer/.local/bin/pql plan whatsnext # next unblocked item, with context +/home/jpmschweitzer/.local/bin/pql decisions list # this repo's own decisions +``` + +Stack-level decisions that constrain this service live in the **workspace** vault and need the +flag: ```bash -/home/jpmschweitzer/.local/bin/pql --vault /mnt/media/Projects ticket list -/home/jpmschweitzer/.local/bin/pql --vault /mnt/media/Projects plan whatsnext /home/jpmschweitzer/.local/bin/pql --vault /mnt/media/Projects decisions list --domain webber ``` +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. + Do not add a TODO section to a markdown file. ## Git