From eec241d3c0c60d73624cf2c6e539082995ee9960 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Mon, 22 Jun 2026 20:39:54 -0400 Subject: [PATCH] feat(plugin): sharpen the recall-before-acting reflex in static context MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Turn the SessionStart static guidance into a concrete recall trigger — search Scribe before answering about the operator projects/people/places/decisions or starting a task, and pass the active project id to scope results — instead of a vague "search for related work". Step 4 (pull-path sharpening); the cross-encoder rerank half is deferred until auto_inject telemetry shows precision is the bottleneck. Scribe: project 2, milestone 93, task 1034. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01Xz4j1H7pjYSjKsEpgcNH5E --- plugin/hooks/scribe_static_context.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/plugin/hooks/scribe_static_context.md b/plugin/hooks/scribe_static_context.md index cb2ed02..98ac8a9 100644 --- a/plugin/hooks/scribe_static_context.md +++ b/plugin/hooks/scribe_static_context.md @@ -12,10 +12,15 @@ for the operator's work, and as your own working memory across sessions. recent notes in one shot. **While you work:** -- **Recall before acting** — `search` Scribe for related prior work before - answering a question about the operator's work, starting a task, or - re-deriving a decision. Assume a related note, task, or decision already - exists. +- **Recall before acting** — before you answer anything about the operator's + work or start a task, `search` Scribe first; assume a related note, task, or + decision already exists. Concretely, reach for recall whenever a request + touches the operator's projects, people, places, prior decisions, or existing + work: check for an existing task before opening a new one, and for a prior + note/decision before re-deriving one. When a project is in scope (you entered + one), pass its id to `search` so results stay scoped to it. Treating Scribe as + the first place you look — not just somewhere you write — is what makes it a + trustworthy record. - **Record as you go** — track work as Scribe tasks and log progress with `add_task_log`. Always log when you **complete a task** and when you **hit or discover a problem** — so changes of direction are captured, not just