wip(394): steps 6+7 — backend path and instruction surfaces

docs/features.md

@@ -60,8 +60,10 @@ Scribe stores the operator's engineering and workflow **rules** so Claude follow
 across sessions.
 
 - **Rulebooks → topics → rules** — Rules are grouped by topic inside a rulebook.
-- **Always-on rules** — A rulebook can be flagged always-on; its rules load at the
-  start of every session through the plugin's push channel.
+- **Rules arrive by retrieval** — Nothing is preloaded. A rule reaches a
+  session when what the agent is about to do matches its trigger: a command,
+  a file being written, or the operator's own message. `when_to_apply` is
+  therefore the field that decides whether a rule is ever seen.
 - **Per-project scope** — A project subscribes to rulebooks, and can add
   project-scoped rules or suppress individual inherited rules/topics.
 
@@ -94,7 +96,7 @@ The whole store is reachable by Claude through a built-in **MCP endpoint at `/mc
 (Bearer-auth with an API key). The **Scribe Claude Code plugin** (shipped in this
 repo) wires it up:
 
-- a `SessionStart` hook that injects the operator's always-on rules + active-project
+- a `SessionStart` hook that injects active-project
   context so Scribe surfaces without being asked (fail-open if Scribe is unreachable);
 - universal process-skills — writing-plans, systematic-debugging, verification,
   brainstorming — that route their output into Scribe;