Opaque request-time context
Environment-dependent retrieval
Evidence discarded after generation
Vendor-coupled storage
Audit added later
Hard-to-reproduce runtime state
The open-source @knolo/core runtime for portable, verifiable Knowledge Images. Pack knowledge once, pin it by digest, and retrieve evidence locally. No vector database required.

Knowledge should be an asset you can inspect, verify, migrate, and run.
Opaque request-time context
Environment-dependent retrieval
Evidence discarded after generation
Vendor-coupled storage
Audit added later
Hard-to-reproduce runtime state
Mounted Knowledge Image
Deterministic plans and receipts
Persistent provenance
Portable artifacts
Verification built into the contract
Committed runtime state
Copy it, mount it, inspect it, verify it, and compare it. V5 stateRoot identifies the image. KAR's knowledgeRoot is a different digest.
commit → state rootA/B superblocksImmutable segmentsDeterministic CBORDomain-separated SHA-256 rootsCommit rootsBounded sectionsFail-closed verificationVerification is structural. A passing check means the bytes match the declared roots. It does not mean a claim is true, a KAR status is a proof, or a Cortex answer is correct.
verifiedsha256: example…generation 42requirements metroots matchtraceablenot claimedImport KAR from @knolo/core/kar. The root package does not load it. SATISFIED means the declared evidence requirements were met.
Portable evidence. V5 stateRoot is its identity.
Editable graph compiled into a Kar sidecar.
Support, opposition, qualification, time, and authority stay typed.
The packaged result. A coverage report names gaps.
A composition record cites images, packs, KAR sidecars, Domain Packs, excerpts, and nested records. It does not change stateRoot or KARRoot.
Statements are mount, cited, and used. used means a query or evaluation ran. It is not SATISFIED, and Hub attested: true is only a listing flag.
Knolo Cortex runs a bounded evidence loop over a V4 pack or a V5 image and returns a trace. Import it from @knolo/core/cortex. The host supplies any model. Core does not call a network. verifyCortexAnswer checks that the trace matches the declared evidence. It does not mean the answer is true.
createCortexSession@knolo/core/cortexcreateCortex@knolo/coreremember / recallhost-ownedV4 remains the path for ordinary search: portable .knolo packs, lexical-first retrieval, namespace and source boundaries, and local mounting in Node, browser, and mobile. KAR does not replace query().
import { buildPack, mountPack, query } from '@knolo/core';
const bytes = await buildPack(docs, {
semantic: { enabled: false }
});
const pack = await mountPack({ src: bytes });
const hits = query(pack, 'refund policy', { topK: 5 });Existing V1–V4 artifacts remain readable and can migrate into a V5 genesis image with evidence identity mappings and a deterministic receipt.
The image contract is still the V5 Knowledge Image. These surfaces stay bounded. They are not a hosted database.
Bounded deterministic EQL with plan and result receipts.
Policy evaluation bound to committed knowledge state.
Signed envelopes, key rotation, and bounded delegation.
Immutable commits and deterministic state evolution.
Compare, fast-forward, and explicitly resolve divergence.
Durable, host-controlled run state and replay protection.
Deterministic runtime health snapshots.
Read-only KIP-0026 management snapshots. No Studio UI.
Networking · credentials · model inference · deployment · external effects
Artifact · roots · identity · validation · deterministic planning · bounded runtime state
Minimum typed evidence set over a committed graph.
Offline citations and attestations. Roots stay put.
Bounded evidence retrieval and a verifiable trace.
Claim decisions and an offline certificate. Version 0.1.0.
Behavior packs and selection receipts. Version 0.2.0.
Packs, images, KAR, composition, Cortex, and Hub.
Read-only local tools, including KAR and Cortex evidence checks.
Local V4 code Knowledge Image tools for structure-first retrieval.
Discover, pin by digest, and mount a public image.
Knolo Core provides knowledge state. Knolo Agents is a separate control plane for inspectable workflows. Host applications still provide model providers, credentials, tools, network access, and external effects.
Explore Knolo AgentsOrdinary search stays on V4. V5 mounts the image. KAR and Cortex are separate entrypoints. The host keeps inference.
npm install @knolo/core
buildPack()
mountPack()
query()import {
migrateV4ToV5,
mountKnowledgeImageV5,
verifyKnowledgeImageV5,
} from '@knolo/core';
const { image, receipt } = await migrateV4ToV5(v4Bytes);
const verification = verifyKnowledgeImageV5(image);
const mounted = mountKnowledgeImageV5(image);import { createKarSession, evaluateKar, verifyKar } from '@knolo/core/kar';
const session = createKarSession({ image, graph });
const result = evaluateKar(session, { proposition, plan });
const verification = verifyKar({ image, graph, proposition, plan, result });import { askCortex, createCortexSession, verifyCortexAnswer } from '@knolo/core/cortex';
const session = await createCortexSession({
image,
policy: { maxRounds: 2, allowAbstain: true },
});
const trace = await askCortex(session, {
question: 'Where is the valve inspection?',
mode: 'find_relevant',
});npm install -g @knolo/cli
knolo v5 info ./dist/knowledge.v5
knolo v5 health ./dist/knowledge.v5
knolo kar dossier verify ./dossier
knolo cortex verify --image ./dist/knowledge.v5 --answer ./answer.cortex.jsonIn 6.2.0 is the published product line. Bounded or draft is real and narrower than the headline. Still ahead is not shipped.
knolo.dev is the product site. The other public hosts have different jobs.
Discover a pack, inspect it, pin its digest, and mount it locally. Queries do not go through Hub.
Hub guideLessons and the Knolo Certified Developer credential. Participation is not the credential.
learn.knolo.devSpecifications, custodianship, and the public record. It is not this product site and it is not knolo.io.
www.knolo.orgPortable. Inspectable. Reproducible. Verifiable.
Portable images you pin by digest and query locally.
Knolo is an open-source, local-first runtime and file format for Knowledge Images. You pack documents into a single portable image, pin it by digest, and retrieve evidence from it locally. The core runtime is @knolo/core on npm, released under the Apache-2.0 license.
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.