← Blog

· Hive AI

Knolo for Agents: Pack, Pin, Mount and Prove Shared Knowledge

How Knolo lets two AI agents share knowledge in four open, checkable steps: pack a Knowledge Image, pin it by digest, mount it locally, and prove what was used.

Knolo is the open-source, local-first Knowledge Image runtime and format, released under Apache-2.0 and published on npm as @knolo/core. On 11 Nov 2026 the Knolo Core repository changed how it introduces itself (pull request #166): Knolo is the open framework AI agents use to share knowledge with one another. A new guide, "Two agents sharing knowledge", spells out the loop in four steps: pack, pin, mount, prove. This note looks at why each step is an open, checkable artifact rather than a service.

Knolo step one: pack

One agent packs knowledge into a portable Knowledge Image, or installs a skill pack that already carries one. Packing writes knowledge.v5 plus the image SHA-256 and state root into the manifest. The bytes are the unit of exchange, and the format is public: the Knolo specifications on knolo.org describe it.

Knolo step two: pin by digest

The pin is the digest. A V5 image is also identified by its stateRoot. Publishing the same pin to the hub again leaves the catalog row unchanged, and a different pin for the same name is refused. The hub stores the pack and the pin. It does not run a model and it does not answer questions. Trust comes from the digest, not from where the file was downloaded.

Knolo step three: mount locally

The second agent mounts the image on its own machine, usually through the Knolo MCP server. The server speaks stdio, opens no port and downloads nothing. The caller is the agentId in the config file, and tool arguments cannot change it. That id must be listed in the mount's agents array, so access is a local policy decision, not a remote one.

Knolo step four: prove what was used

A search returns hits and a receipt record: a receipt id, the state root, the plan root and the result root. The receipt file is written to the local audit directory before hits come back. knolo_verify checks the mounted bytes and V5 roots, and the next agent proves which image it mounted by that pin and state root.

The guide is careful about limits, and so are we. A receipt is an integrity check. It does not mean a claim is proven. Knolo does not call a model and does not run either agent. The host owns the model.

Why the Knolo loop stays open

Every step leaves something another runtime can check without asking anyone: a file, a digest, a root, a receipt. That is what lets independent implementations agree, and it is why Knolo compatibility is defined on bytes and roots. You can check an image yourself at Knolo Verify.

Knolo links

Knolo is built by Hive AI.

knolo · open-technology · agents · verification · knowledge-image