Sign In

jamgate

Package Overview
Dependencies
Maintainers
1
Versions
37
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

jamgate - npm Package Compare versions

Comparing version
0.15.0
to
0.15.1
+1
-1
dist/version.js

@@ -9,2 +9,2 @@ /**

*/
export const VERSION = "0.15.0";
export const VERSION = "0.15.1";
{
"name": "jamgate",
"version": "0.15.0",
"version": "0.15.1",
"mcpName": "io.github.amirj4m/jamgate",

@@ -5,0 +5,0 @@ "description": "A neutral, cross-agent memory quality gate for AI agents, delivered as an MCP server — a gate, not a store.",

@@ -115,2 +115,11 @@ # Jamgate

**A name written in one script cannot be found by its spelling in the other.** Matching is
token-based and script-literal, with no transliteration bridge. Measured on my own store, on
two names recorded in Latin inside a Persian-speaking user's memory: `Rahman` and `Iraj` each
return the right record at **rank 1 for every natural English phrasing** (11 of 12 at rank 1,
one at rank 2) — and `رحمان`, `ایرج`, `بدهی رحمان`, `بدهی ایرج` return **nothing at all**, 0 of 4.
Cross-script queries only work when the record happens to share tokens in the query's script.
For a bilingual user this is data-loss-equivalent: the memory is there, correct, and
unreachable in half the languages they actually type. Not fixed — see D-075 for the scope.
**Nobody outside me has installed it.** Getting on for thirty releases, ten supported clients, one user.

@@ -117,0 +126,0 @@ I've simulated a cold install (fresh `HOME`, empty npm cache, published package rather than