Knowledge Packs

A pack (.ydbpack) is a sealed, signed, measured YantrikDB file. Mounting one gives your local model the knowledge, rules and skills inside; unmounting gives them back and leaves your database byte-for-byte as it was. Nothing is merged, nothing leaks into your own memories, and nothing survives the unmount.

That makes packs the answer to a specific problem: things your model was never trained on. Post-cutoff releases, breaking API changes, private domain knowledge, product documentation — facts a model cannot derive and would otherwise guess at.

Install and mount

pip install yantrikdb          # >= 0.11
yantrikdb pack install ./mcp-spec.ydbpack

Or from Python:

from yantrikdb import YantrikDB

db = YantrikDB("memory.db")
db.mount_pack("./mcp-spec.ydbpack")

hits = db.recall_text("how does elicitation work in MCP?")

recall() now sees the pack’s records alongside your own memories — tagged with their origin, so provenance survives. unmount_pack() removes every trace.

The marketplace

First-party packs are published at packs.yantrikdb.com. Every official pack is:

• Signed — the file carries its signature and digest; tampering is detectable before anything mounts. Verify any file on the marketplace’s verify page.
• Measured — packs are published with efficacy measured against control questions, so “this pack helps” is a number, not a hope.
• Self-describing — since engine v0.11.3 the sealed manifest carries the retrieval settings its author measured (recommended_top_k, recommended_min_similarity), signed with everything else. A consumer never guesses a similarity floor for a corpus they didn’t write.

Clustered packs (server v0.14.0)

RFC 031 brings packs to the network server: a pack mounts once, server-side, on a replicated cluster — so a fleet of agents shares one mounted corpus instead of each carrying its own copy, with the same seal-and-signature guarantees.

Building your own

A pack has three tiers — a small constitution of rules, a corpus of retrievable records, and coverage examples — and the authoring rules that make records actually retrieve are their own craft (write the heading in the asker’s words; every sibling needs its own trigger; scope each claim). The tooling to build, measure, sign and publish ships with the engine.

Have a pack worth publishing? Publish it on the marketplace →