Skip to content

V4 ships today · V5 is the runtime

Knolo · V4

What you can mount today.

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

Sealed Knolo Knowledge Image on a steel bench.

Shipped capabilities

You may state these as current. Nothing below is V5.

Portable .knolo files

A Knowledge Image you can move, inspect, and mount locally. Sources, permissions, hashes, and retrieval indexes travel together.

Deterministic lexical-first retrieval

Exact terms, clause IDs, exhibit labels, and identifiers are the spine. No vector database is required.

Optional hybrid semantic rerank

Rerank can reorder a candidate set the lexical layer already constrained. It never replaces lexical grounding.

Evidence spans and plan hashes

Answers bind to passages. Retrieval plans hash. If it cannot cite, it does not ship as evidence.

Verifiable read receipts

A read can leave a receipt another machine can check. Write and run receipts are V5.

LivePack mutable overlay

The image stays mountable while a live overlay accepts change without pretending the corpus is frozen forever.

Cortex overlay log

Agent memory as an append-only overlay on the image. V5 moves memory onto the same ledger as knowledge.

ClaimGraph

Claims as a graph over evidence, not a paragraph the model invented.

Local / edge / on-device

On-prem, VPC, air-gap, or a device next to the work. Not a multi-tenant default region.

TrustBench Phase 5

Conformance for the v4 retrieval contract. The public repo is the record, not a slide.

Source of truth

TypeScript @knolo/core is the v4 reference.

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

  • Not a RAG library, even though retrieval is the current surface.
  • Not embedding-first. Lexical grounding is required; semantic rerank is optional.
  • Not a hosted control plane. You can verify without phoning HIVE.
  • Not the durable agent runtime. Tools, budgets, resume, and run receipts are V5.
What V5 adds →

Put a V4 image on your corpus in a Bootcamp week.

HIVE systems sit on that image today. The runtime contract is the upgrade path, not a surprise rewrite.