@dug-21/unimatrix 0.5.8 → 0.5.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dug-21/unimatrix",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.9",
|
|
4
4
|
"description": "Unimatrix knowledge engine for multi-agent development",
|
|
5
5
|
"bin": {
|
|
6
6
|
"unimatrix": "bin/unimatrix.js"
|
|
@@ -9,8 +9,8 @@
|
|
|
9
9
|
"postinstall": "node postinstall.js"
|
|
10
10
|
},
|
|
11
11
|
"optionalDependencies": {
|
|
12
|
-
"@dug-21/unimatrix-linux-x64": "0.5.
|
|
13
|
-
"@dug-21/unimatrix-linux-arm64": "0.5.
|
|
12
|
+
"@dug-21/unimatrix-linux-x64": "0.5.9",
|
|
13
|
+
"@dug-21/unimatrix-linux-arm64": "0.5.9"
|
|
14
14
|
},
|
|
15
15
|
"files": [
|
|
16
16
|
"bin/",
|
|
@@ -34,7 +34,7 @@ Call the `mcp__unimatrix__context_lookup` MCP tool:
|
|
|
34
34
|
|
|
35
35
|
**Get all ADRs for a specific feature:**
|
|
36
36
|
```
|
|
37
|
-
mcp__unimatrix__context_lookup(topic: "nxs-002", category: "decision")
|
|
37
|
+
mcp__unimatrix__context_lookup(topic: "nxs-002", category: "decision", helpful: true)
|
|
38
38
|
```
|
|
39
39
|
|
|
40
40
|
**Get a specific entry by ID (full content):**
|
|
@@ -57,6 +57,14 @@ mcp__unimatrix__context_lookup(category: "decision", tags: ["adr", "serializatio
|
|
|
57
57
|
mcp__unimatrix__context_lookup(topic: "vnc-001")
|
|
58
58
|
```
|
|
59
59
|
|
|
60
|
+
### Helpful Vote Guidance
|
|
61
|
+
|
|
62
|
+
Pass `helpful: true` when the retrieved entries applied to the task — this is the standard case for deliberate lookups.
|
|
63
|
+
Pass `helpful: false` when entries were retrieved but did not apply to the task (e.g., the result was for the wrong feature or an unrelated concern). Negative signal is valuable for confidence calibration.
|
|
64
|
+
Omit `helpful` when you cannot determine applicability, such as during exploratory browsing or pre-flight checks where you don't yet know which entries will be used.
|
|
65
|
+
|
|
66
|
+
Note: `context_lookup` already records a doubled access signal automatically (×2 weight vs. search). The `helpful` vote is an additional optional signal for quality calibration.
|
|
67
|
+
|
|
60
68
|
---
|
|
61
69
|
|
|
62
70
|
## Single Entry Retrieval
|
|
@@ -31,7 +31,7 @@ Call the `mcp__unimatrix__context_search` MCP tool:
|
|
|
31
31
|
|
|
32
32
|
**Find ADRs about error handling across all features:**
|
|
33
33
|
```
|
|
34
|
-
mcp__unimatrix__context_search(query: "error handling strategy", category: "decision")
|
|
34
|
+
mcp__unimatrix__context_search(query: "error handling strategy", category: "decision", helpful: true)
|
|
35
35
|
```
|
|
36
36
|
|
|
37
37
|
**Find anything related to MCP transport:**
|
|
@@ -49,6 +49,12 @@ mcp__unimatrix__context_search(query: "test patterns integration", topic: "nxs-0
|
|
|
49
49
|
mcp__unimatrix__context_search(query: "serialization approach", format: "markdown")
|
|
50
50
|
```
|
|
51
51
|
|
|
52
|
+
### Helpful Vote Guidance
|
|
53
|
+
|
|
54
|
+
Pass `helpful: true` when the retrieved entries were useful for completing the current task — this is the standard case.
|
|
55
|
+
Pass `helpful: false` when entries were retrieved but did not apply to the task (e.g., the results were about a different concern). Negative signal is valuable for confidence calibration.
|
|
56
|
+
Omit `helpful` when you cannot determine applicability — for example, when the search is exploratory or you are not yet sure which results will be used.
|
|
57
|
+
|
|
52
58
|
---
|
|
53
59
|
|
|
54
60
|
## Available Categories
|