Platform / Knolo
Knolo is a verifiable knowledge runtime for agents. Hive Forensics AI is the builder that images it, permissions it, evaluates it, and runs it inside HIVE systems. Product storytelling lives on HIVE.
We build AI systems on Knolo, a verifiable knowledge runtime for agents. V5.1.0 ships on npm as @knolo/core: a verifiable Knowledge Image and transactional runtime — one ledger for knowledge, policy, memory, authority, and agent runs. V4 Knowledge Images remain the compatible prior line: portable .knolo files with deterministic lexical evidence, receipts, and local execution.
This page is the implementation view: what we actually do when a corpus has to survive counsel, a CISO, and a Monday morning operator. We do not treat Knolo as an SDK sticker. The Knowledge Image is the unit of work. Knolo Hub is a public-beta registry of portable, verifiable Knowledge Images you can inspect, pin by digest, and mount with Knolo Core.
Product pages, open-source knolo-core, docs, and the Hub are one runtime — not four products. This domain explains how the company implements and operates it.
Knolo contract
We build AI systems on Knolo, a verifiable knowledge runtime for agents. V5.1.0 ships on npm as @knolo/core: a verifiable Knowledge Image and transactional runtime — one ledger for knowledge, policy, memory, authority, and agent runs. V4 Knowledge Images remain the compatible prior line: portable .knolo files with deterministic lexical evidence, receipts, and local execution.
Compatible prior line
Portable .knolo files with deterministic lexical evidence, receipts, and local execution. V4 pack and retrieval APIs remain unchanged. Open-source contract lives in knolo-core.
OPEN SOURCE · knolo-core
github.com/HiveForensics-AI/knolo-core →Current shipping runtime · V5.1.0
Published on npm as @knolo/core 5.1.0. The same .knolo file becomes a transactional runtime: one ledger for knowledge, policy, memory, authority, and agent runs.
V5.1.0 · @KNOLO/CORE · SAME .KNOLO FILE
V4 evidence path
01 / LEXICAL GROUNDING
The default retrieval path is deterministic and lexical. Embeddings, if used, rerank behind that contract. They are not the trust root.
02 / SPANS
A hit points at a location in the image — source, region, passage. An answer that cannot point is a failure, not a style.
03 / PLAN HASH
The retrieval plan is hashable. Same question, same image, same policy: the same evidence set, replayable later.
04 / READ RECEIPT
A query leaves a receipt. Counsel can ask what was read. The receipt is part of the system, not a chat log export.
V5 runtime path
V5.1.0 is published on npm as @knolo/core. V4 pack and retrieval APIs remain the compatible prior line.
01 / STATE ROOTS
V5 pins runtime state so a run can be named, compared, and resumed. V5.1.0 ships that contract on npm.
02 / WRITE RECEIPTS
Mutations to knowledge, policy, or memory are receipted. An unreceipted write is not a write we will operate.
03 / RUN RECEIPTS
An agent run is a record: what it read, what it attempted, what was allowed. Fluency is not the log.
04 / DEFAULT-DENY AUTHORITY
Tools and side effects require an approval or capability record. Available actions remain deliberately narrow.
05 / RESUMABLE RUNS
A run that suspends for a human can continue from the same root. Abandoning the trace is not an architecture.
What we will not do with it
Approximate nearest neighbors are not a permission model and not an audit trail.
If there is no approval or capability record, the tool does not run.
If it cannot be mounted, pointed at, and replayed, it does not ship.
Broader stack: architecture. Data handling: security. Product language: hiveai.tech/knolo.
Engage
Unscoped work starts at hiveai.tech/bootcamp. This domain is for engineering already constrained. Work is scoped privately.
Scoped privately · no public rate card on this domain