Portable .knolo files
A Knowledge Image you can move, inspect, and mount locally. Sources, permissions, hashes, and retrieval indexes travel together.
V4 ships today. V5 is the runtime. Local-first. Offline verification is first-class.V4 ships today · V5 is the runtime
Knolo · V4
Knolo V4 is a verifiable pack and retrieval contract you can run locally. It is not the category. The category is the runtime V5 is becoming. Do not confuse the current surface with the destination.
TrustBench Phase 5 · knolo-core

Shipped capabilities
A Knowledge Image you can move, inspect, and mount locally. Sources, permissions, hashes, and retrieval indexes travel together.
Exact terms, clause IDs, exhibit labels, and identifiers are the spine. No vector database is required.
Rerank can reorder a candidate set the lexical layer already constrained. It never replaces lexical grounding.
Answers bind to passages. Retrieval plans hash. If it cannot cite, it does not ship as evidence.
A read can leave a receipt another machine can check. Write and run receipts are V5.
The image stays mountable while a live overlay accepts change without pretending the corpus is frozen forever.
Agent memory as an append-only overlay on the image. V5 moves memory onto the same ledger as knowledge.
Claims as a graph over evidence, not a paragraph the model invented.
On-prem, VPC, air-gap, or a device next to the work. Not a multi-tenant default region.
Conformance for the v4 retrieval contract. The public repo is the record, not a slide.
Source of truth
Rust and Python exist as compatibility readers. They are not the v4 source of truth. V5 inverts that: Rust becomes the reference kernel, and other languages bind to it.
An optional ICP lexical canister exists. Blockchain is not the headline. Offline verification does not wait on a chain.
github.com/HiveForensics-AI/knolo-core →What V4 is not
HIVE systems sit on that image today. The runtime contract is the upgrade path, not a surprise rewrite.