Knolo 5.1.0 published · V4 compatibility preserved · Apache-2.0Knolo 5.1.0 published · V4 compatible
Product · KNOLO
The differentiation is not better vector search. The moat is one portable artifact that binds knowledge + policy + retrieval + memory + execution into a reproducible, authority-scoped state machine.
Evidence query
What does the 2024 MSA say about indemnification for subcontractors?
Answer · strict
lexical first · rerank off
Indemnification for subcontractors is in §8.3 of the 2024 MSA. The contractor remains liable for subcontractor acts as if they were its own, with a written flow-down required before any subcontract is effective.
North star
01
What did the agent know?
02
What evidence did it use?
03
What was it authorized to do?
04
What did it change?
05
Can another machine reproduce and verify the result?
V5 · 5.1.0 published
A unified ledger for knowledge, memory, policy, authority, and run events. Durable, resumable agent runs. EQL. Read, write, and run receipts. Rust as the reference kernel. Current published version on npm and crates.io.
Read the V5 architecture →V4 · compatibility
Portable .knolo files. Deterministic lexical-first retrieval. Evidence spans, plan hashes, and read receipts. TrustBench Phase 5 remains the V4 compatibility contract in knolo-core. TypeScript @knolo/core still speaks that path.
V4 compatibility →Positioning
Not a replacement for SQL. Not a generic vector database. Not a hosted control plane. Local-first. Offline verification is first-class.
01
Durable agent runs: tools, budgets, approvals, resume, audit.
V5.1.0 published; contracts continue to harden
02
Embedded transactional knowledge database inside the runtime.
Transactional mutation remains follow-on work
03
One mountable file: knowledge + state + policy + proofs.
V4 compatibility preserved; V5 container is the published image
04
Evidence Query Language. Canonical evidence packages.
V5 query-planning foundation active
05
Agent memory on the same ledger.
V4: overlay log. V5: ledger-backed views
06
Read / write / run evidence.
V4: read receipts. V5: read + write + run
07
Open one artifact. Inspect roots, timelines, plans, runs.
Read-only V5 snapshot contract; full UI remains follow-on work
The artifact
A .knolo Knowledge Image is something counsel, SIU, or an operator can inspect. V4 still ships that file as the compatibility path: knowledge you can retrieve, permissions that travel with it, hashes you can recompute, read receipts you can verify. V5.1.0 is the published runtime that extends the same artifact into state, policy, authority, and runs.
Public source: github.com/HiveForensics-AI/knolo-core. HIVE owns the commercial product story on this domain.
Knolo Hub — Knowledge you can pin. Public beta: a registry of portable, verifiable Knowledge Images you can inspect, pin by digest, and mount with Knolo Core / @knolo/core.
V4 capabilities →What Knolo is not
Determinism contract · V5
Same state root + same EQL plan + same authority + same runtime contract = the same canonical evidence package.
If another machine cannot reproduce and verify the result, it is not Knolo. It is theater with citations.
V5 architecture →Bootcamp is how a corpus becomes an image and a workflow. Hive Forensics AI Inc. deploys and operates the system.