V4 is the file. V5 is the runtime.
Knolo is not a retrieval pack and not a RAG library. That is the V4 surface. The category is an embedded, verifiable knowledge runtime for autonomous agents. V4 ships today. V5 is the upgrade, not a ship date.
Docs · Knolo
What operators need before a Bootcamp.
Canonical product pages live under /knolo. The V4 public contract is knolo-core. This page is the short operator note.
A Knowledge Image
A .knolo file is a portable unit: sources, permission metadata, a lexical index, optional rerank artifacts, and a hash. Counsel can ask what is in it. An operator can diff two versions. V5 extends the same artifact into state, policy, authority, and runs.
Retrieval on V4
Deterministic lexical retrieval first. Exact terms, identifiers, clause numbers, and exhibit labels are the spine. Optional rerank is a layer you turn on when the eval says it earns its keep. It never replaces lexical grounding. Answers that cannot bind to a source do not ship as evidence. Read receipts are the V4 proof. Write and run receipts are V5.
Deployment shapes
- On-prem — images and serving beside the file store. No outbound corpus.
- VPC — your account, your keys, your logs.
- Air-gap — no phone-home. Updates are artifacts. Offline verification is first-class.
Around the image
HIVE systems sit on Knolo: investigations, private ops, operator agents. Bootcamp is how a real corpus becomes an image and a workflow in five days. Systems.