@triedotdev/mcp 1.0.167 → 1.0.168
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 +2 -10
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Trie: Governance ledger for agent-human teams
|
|
2
2
|
|
|
3
|
-
**
|
|
3
|
+
**Context that travels from Agents → CLI → CI/CD, keeping agents and humans aligned.**
|
|
4
4
|
|
|
5
5
|
[](https://www.trie.dev) [](https://x.com/louiskishfy)
|
|
6
6
|
|
|
@@ -23,7 +23,7 @@ Trie keeps a **governance ledger**—a tamper-evident record of decisions, incid
|
|
|
23
23
|
- **Governance ledger** - Decision memory with Git-backed audit trail and digital signatures
|
|
24
24
|
- **Cross-tool context** - Same ledger in Cursor, CLI, CI/CD—no coordination needed
|
|
25
25
|
|
|
26
|
-
Think of it as **double-entry bookkeeping for code decisions**—
|
|
26
|
+
Think of it as **double-entry bookkeeping for code decisions**—tamper-evident accountability that works with Git and your existing workflow.
|
|
27
27
|
|
|
28
28
|
## Quick Start
|
|
29
29
|
|
|
@@ -526,14 +526,6 @@ Create `.trie/config.json`:
|
|
|
526
526
|
}
|
|
527
527
|
```
|
|
528
528
|
|
|
529
|
-
## Why Trie Exists
|
|
530
|
-
|
|
531
|
-
When agents and humans ship code together, coordination becomes the bottleneck. Context fragments across tools, decisions get forgotten, and nothing prevents repeating the same mistakes.
|
|
532
|
-
|
|
533
|
-
Trie solves this with a governance ledger—a tamper-evident record that travels with your code. Every tool reads from the same ledger, so agents and humans stay aligned. Teams that can coordinate contributors (human and AI) without losing coherence will ship faster and more reliably.
|
|
534
|
-
|
|
535
|
-
As codebases move toward agent autonomy—agents that merge PRs, manage rollouts, and monitor production—governance becomes critical. Trie keeps your work compliant, scales your contributors, and turns your decision history into durable institutional knowledge.
|
|
536
|
-
|
|
537
529
|
## Troubleshooting
|
|
538
530
|
|
|
539
531
|
**Trie not finding issues**: You haven't taught Trie about your patterns yet. Use `trie tell` to report incidents.
|
package/package.json
CHANGED