Local-first
Mount the image on the machine that asks the question. Queries do not go through a hosted service.
Knowledge layerNew · Knolo Spawn · @knolo/core 6.2.3
Pack knowledge into a Knowledge Image, pin it by digest, and let any agent mount it locally and verify what was used.
import { migrateV4ToV5, mountKnowledgeImageV5, verifyKnowledgeImageV5 } from '@knolo/core';
const { image, receipt } = await migrateV4ToV5(v4Bytes);
const verification = verifyKnowledgeImageV5(image);
const mounted = mountKnowledgeImageV5(image);TypeScript is the V5 quickstart. Rust and Python stay on 5.5.1. MCP is read-only and local. A receipt confirms the bytes and the plan match. It is not a truth verdict.
The knowledge layer
Knowledge should be an asset you can inspect, verify, migrate, and run. The longer guides live in the docs.
Mount the image on the machine that asks the question. Queries do not go through a hosted service.
Knowledge layerKnolo retrieves evidence locally from the image itself, so there is no vector database or hosted service to run.
V4 quickstartTransfers a verified V5 Knowledge Image between agents through signed offers. Adopt stays denied until the host allows it.
Exchange installCopy it, mount it, inspect it, verify it, and compare it. V5 stateRoot identifies the image.
V5 conceptsThe minimum typed evidence set over a committed graph. SATISFIED means the declared evidence requirements were met.
Read KARA bounded evidence loop and a trace you can replay. The host supplies any model. Core does not call a network.
Knolo CortexA receipt confirms the bytes and the plan match. It is not a truth verdict, and a passing check does not mean a claim is true.
Roots and receiptsOpen source under the Apache-2.0 license. Built under Hive Forensics AI Inc. Corp R&D.
Apache-2.0 licenseA composition record cites images, packs, and graphs. It does not change stateRoot or KARRoot.
CompositionKnolo owns the artifact, roots, and bounded runtime state. It is not an agent runtime and it is not a control plane.
Durable runsExisting V1–V4 artifacts remain readable and can migrate into a V5 genesis image with a deterministic receipt.
MigrationA parent agent issues an inert envelope and closes the worker's output into a receipt. Spawn is not an agent runtime and it is not a control plane.
Core and AgentsWhat exists today
In 6.2.3 is the published product line. Bounded or draft is narrower than the headline. Still ahead is not shipped.
Ecosystem
knolo.dev is the product site. The other public hosts have different jobs.
Registry
Discover a pack, inspect it, pin its digest, and mount it locally. Queries do not go through Hub.
Hub guideEducation
Lessons and the Knolo Certified Developer credential. Participation is not the credential.
learn.knolo.devPublic record
Specifications, custodianship, and the public record. It is not this product site and it is not knolo.io.
www.knolo.orgFAQ
Knolo is the open framework AI agents use to share knowledge with one another: pack it into a portable Knowledge Image, pin it by digest, mount it locally, and verify what was used. It is local-first and open source. The package is @knolo/core on npm, released under the Apache-2.0 license. A receipt confirms the bytes and plan match. It does not mean a claim is true.
A Knowledge Image is a packed, content-addressed bundle of knowledge. Because it is pinned by digest, the same image gives the same evidence wherever it runs, and changes are easy to spot.
No. Knolo retrieves evidence locally from the image itself, so there is no vector database or hosted service to run.
Install @knolo/core from npm and follow the installation guide at /docs/installation.
No. Knolo (knolo.dev and knolo.org) is the open-source Knowledge Image project. knolo.io is a different product.