From 43c268d531c90808fac96ab0fc1289c85f9f762a Mon Sep 17 00:00:00 2001 From: Sam Keen Date: Wed, 23 Sep 2026 08:25:02 -0700 Subject: [PATCH 1/2] chore: backlog reset: an `observed` issue form, and the README's "Next" says so The backlog was reset (29 open issues to 4): work now starts from what real use shows. The issue form asks for what I was doing, what I expected, what happened and how often, and labels the issue `observed`. The README's status block still called the desktop chat pane "next" (it shipped in #155) and pointed at the resources roadmap, which the reset parked. Co-Authored-By: Claude Opus 5.5 --- .github/ISSUE_TEMPLATE/observed.yml | 39 +++++++++++++++++++++++++++++ README.md | 7 +++--- 2 files changed, 43 insertions(+), 3 deletions(-) create mode 100644 .github/ISSUE_TEMPLATE/observed.yml diff --git a/.github/ISSUE_TEMPLATE/observed.yml b/.github/ISSUE_TEMPLATE/observed.yml new file mode 100644 index 0000000..57a210c --- /dev/null +++ b/.github/ISSUE_TEMPLATE/observed.yml @@ -0,0 +1,39 @@ +name: Observed in use +description: Something you ran into while using B2 for real. Start here, not from a design guess. +labels: ["observed"] +body: + - type: textarea + id: doing + attributes: + label: What I was doing + description: The task, not the feature. "Looking for my notes on X", "linking two notes", "writing today's log". + validations: + required: true + - type: textarea + id: expected + attributes: + label: What I expected + validations: + required: true + - type: textarea + id: happened + attributes: + label: What happened + description: Screenshots, the exact text on screen, or a `B2_LOG_FILE` excerpt if you have one. + validations: + required: true + - type: dropdown + id: often + attributes: + label: How often + options: + - Once so far + - A few times + - Every time I do this + validations: + required: true + - type: textarea + id: vault + attributes: + label: Vault and build + description: Optional. Which vault (size is enough), `make app` or the installed build, commit if known. diff --git a/README.md b/README.md index f1b40ca..e367c17 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ explained connections between them yourself. > ([#151](https://github.com/AlteredCraft/B2/issues/151)). It talks to any **OpenAI-compatible** model > server (`crates/b2-llm`, a hand-rolled sync SSE client — nothing in B2 is async, and the `b2` binary > links no tokio); **Ollama** is the guided default, a cloud model is explicit opt-in, and nothing -> about a chat is written to your notes or the index. The chat pane in the desktop app is next. +> about a chat is written to your notes or the index. The desktop app has the same chat in its own pane. > **`b2 why NOTE CANDIDATE`** (the **Why?** on a *Similar & unlinked* card in the app) asks the same > model to explain one suggestion, as a **tool-using agent**: it calls B2's read-only tools (the > matched passages, the suggestion list, a note's links, reading a note), says what the two notes @@ -45,8 +45,9 @@ explained connections between them yourself. > (live progress, a Cancel button, the UI usable throughout). Projection and embedding are decoupled, so > a cold vault is browsable/keyword-searchable in seconds while embedding streams behind > ([#15](https://github.com/AlteredCraft/B2/issues/15)). Run it with `make app` — pick a vault from the -> in-app switcher, or skip straight to one via `B2_VAULT_PATH`. **Next:** file-type support (resources) — -> slice 1, inventory & graph, is built; the wider backlog lives in +> in-app switcher, or skip straight to one via `B2_VAULT_PATH`. **Next:** daily use. B2 is now built +> from what real use shows: an issue starts as an **`observed`** report (what I was doing, what I +> expected, what happened), not a design guess. The backlog lives in > [GitHub Issues](https://github.com/AlteredCraft/B2/issues). ## What B2 is (the north star) From 3ab18bd741b180e7c14dce954d89ca2fd75d0eef Mon Sep 17 00:00:00 2001 From: Sam Keen Date: Wed, 23 Sep 2026 08:45:25 -0700 Subject: [PATCH 2/2] chore: leave the README to PR #234, which rewrites it Co-Authored-By: Claude Opus 5.5 --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e367c17..f1b40ca 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ explained connections between them yourself. > ([#151](https://github.com/AlteredCraft/B2/issues/151)). It talks to any **OpenAI-compatible** model > server (`crates/b2-llm`, a hand-rolled sync SSE client — nothing in B2 is async, and the `b2` binary > links no tokio); **Ollama** is the guided default, a cloud model is explicit opt-in, and nothing -> about a chat is written to your notes or the index. The desktop app has the same chat in its own pane. +> about a chat is written to your notes or the index. The chat pane in the desktop app is next. > **`b2 why NOTE CANDIDATE`** (the **Why?** on a *Similar & unlinked* card in the app) asks the same > model to explain one suggestion, as a **tool-using agent**: it calls B2's read-only tools (the > matched passages, the suggestion list, a note's links, reading a note), says what the two notes @@ -45,9 +45,8 @@ explained connections between them yourself. > (live progress, a Cancel button, the UI usable throughout). Projection and embedding are decoupled, so > a cold vault is browsable/keyword-searchable in seconds while embedding streams behind > ([#15](https://github.com/AlteredCraft/B2/issues/15)). Run it with `make app` — pick a vault from the -> in-app switcher, or skip straight to one via `B2_VAULT_PATH`. **Next:** daily use. B2 is now built -> from what real use shows: an issue starts as an **`observed`** report (what I was doing, what I -> expected, what happened), not a design guess. The backlog lives in +> in-app switcher, or skip straight to one via `B2_VAULT_PATH`. **Next:** file-type support (resources) — +> slice 1, inventory & graph, is built; the wider backlog lives in > [GitHub Issues](https://github.com/AlteredCraft/B2/issues). ## What B2 is (the north star)