@triedotdev/mcp 1.0.57 → 1.0.58
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/README.md +1 -1
- package/dist/{chunk-3XZO27U7.js → chunk-JAVEBJF4.js} +230 -131
- package/dist/chunk-JAVEBJF4.js.map +1 -0
- package/dist/cli/yolo-daemon.js +1 -1
- package/dist/index.js +8 -1
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/dist/chunk-3XZO27U7.js.map +0 -1
package/README.md
CHANGED
|
@@ -17,7 +17,7 @@ So I built Trie with a few principles:
|
|
|
17
17
|
|
|
18
18
|
**Memory that travels with git.** The `.trie/` directory commits to your repo. Same incident history, same patterns, same risk scores—whether you're in Cursor, VS Code, CLI, or CI/CD. No external service. No re-explaining. Your context is *yours*.
|
|
19
19
|
|
|
20
|
-
**One guardian, not a committee.** Skills, on their own, have no unified view. Trie has 26 specialized skills, but they all feed into one guardian agent that knows the full picture. One brain that watches, learns, and warns. You can also add skills from any repo you find online.
|
|
20
|
+
**One guardian, not a committee.** Skills, on their own, have no unified view. Trie has 26 specialized "scouts" (same as skills, but I call them scouts as they scan and report up), but they all feed into one guardian agent that knows the full picture. One brain that watches, learns, and warns. You can also add skills from any repo you find online.
|
|
21
21
|
|
|
22
22
|
**Fast enough for git hooks.** I chose a trie data structure because I needed O(m) lookups that don't slow down my workflow. File paths as tree branches. Hot zones light up where problems cluster. Under 10ms for pattern matching, under 500ms for pre-push checks.
|
|
23
23
|
|