@vib795/agent-memory 0.1.12 → 0.1.13

package/README.md

@@ -465,11 +465,27 @@ that drifts as the work progresses does not create a duplicate.
 
 ## Status
 
-Capture is **explicit**. You invoke it, or `/handoff` does; nothing fires on its own.
+Capture is **judged, not scheduled.** You invoke it, `/handoff` does, or the agent
+does on its own when a juncture has just passed — a decision settled, a constraint
+found, a root cause identified, a convention agreed. It says so in one line and
+carries on with what you actually asked:
+
+```
+captured 2 notes [decision, constraint]
+```
+
+Nothing fires on a timer, on a tool count, or on every reply. That distinction is the
+whole design: a store full of task chatter is worse than an empty one, because it
+buries the four notes that mattered. The judgment of what is durable belongs to the
+model, in the turn where the context still exists; there is no keyword list deciding
+it. And because a request is charged per prompt rather than per tool call, capture
+that rides inside a turn you already paid for is free — which is why it can afford to
+happen at the moment the knowledge is fresh instead of whenever someone remembers.
 
 Not built yet, by choice:
 
-- Automatic or ambient capture
+- A capture-gap signal — the store knows when a note has gone stale, but not yet when
+  a repo has moved a hundred commits with nothing captured at all
 - Team sharing, multi-machine sync
 - An MCP server. It would read this same store, so it is an addition, not a rewrite.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vib795/agent-memory",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "Durable cross-repo knowledge graph for GitHub Copilot and Claude Code. Markdown source of truth, disposable SQLite index, zero runtime dependencies.",
   "keywords": [
     "github-copilot",

package/skills/remember/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: remember
 version: 0.1.0
-description: Capture durable project knowledge from the current conversation into the shared memory graph, so a later conversation in any window or repository already knows it. Use when the user says remember this, save this, note this for later, or /remember.
+description: Capture durable project knowledge from this conversation into a cross-repo memory graph, so a later conversation anywhere already knows it. Use when the user says remember this, save this, note this for later, or /remember. Also invoke it unasked when a juncture passes - a decision settled, a constraint found, a root cause identified, a convention agreed - then say so in one line and carry on.
 license: MIT
 allowed-tools: Bash Read Write
 triggers:
@@ -25,11 +25,51 @@ call. Do not ask the user to confirm each node.
 
 ---
 
-## Two forms
+## Three forms
 
 - **`/remember`** — you select the durable knowledge from the conversation so far.
 - **`/remember <what>`** — the user named the thing. Write that, with full context
   from the conversation, and write nothing unrelated to it.
+- **Unasked** — you noticed a juncture pass and captured it without being told.
+
+### Capturing unasked
+
+A memory that only grows when someone remembers to grow it stays thin, and thin is
+how it dies: the one fact worth having is the one nobody stopped to write down.
+
+Invoke this yourself the moment one of these has just happened, in the same turn:
+
+- a **decision** was settled, and the reasons and rejected options are still in view
+- a **constraint** surfaced — a blocked tool, a policy, an environment restriction
+- a **root cause** was found, as opposed to a symptom worked around
+- a **convention** was agreed, or discovered by reading the code
+
+Do not capture on a timer, on a tool count, or at every reply. Those produce volume,
+and volume is what makes a graph useless — a store full of task chatter is worse than
+an empty one, because it buries the four notes that mattered.
+
+Never capture: task status, what you are about to do next, anything already in the
+graph, or anything that will be false next month. If you captured a juncture earlier
+in this conversation, do not capture it again because it came up a second time.
+
+**It is free, and that is the point.** A request is charged per prompt, not per tool
+call, so capturing inside a turn you were already answering costs nothing. Only a
+user typing `/remember` spends a request. That is the whole reason to do this
+yourself rather than wait to be asked.
+
+**Report it in one line, then carry on:**
+
+```
+captured 2 notes [decision, constraint]
+```
+
+At the end of the answer you were already giving. Do not print the JSON, do not
+summarize what you wrote, and do not make it the subject of the reply — the user
+asked you about something else and is still waiting for it. One line is enough for
+them to know it happened and to run `/recall` if they want the detail.
+
+If nothing durable happened, say nothing at all. Silence is the correct output for
+most turns.
 
 ---