Platform
The Knowledge Image is the mountable artifact. Evidence is lexical, spanned, and receipted. V5.1.0 extends the same file into a transactional runtime.
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
Builder-facing layers
01
The mountable artifact. A portable file you can hash, ship, revoke, and run locally. V4 ships this today. It is not a pile of embeddings and not a chat memory.
02
Lexical grounding, spans, plan hash, read receipt. The same question against the same image under the same policy is replayable. Approximate search, if used, sits behind that contract — it is not the trust root.
03
State roots, write receipts, run receipts, default-deny authority, resumable runs. V5.1.0 ships on npm as @knolo/core. Same file, transactional runtime.
The artifact
Vector search is a useful index. It is not a knowledge runtime. Cosine distance is not an audit trail. When counsel asks why a passage appeared, the answer is a span, a plan hash, and a read receipt — not a nearest-neighbor vibe.
Hive Forensics AI implements that runtime inside the systems we ship — on-prem or in a VPC — rather than bolting a chat UI onto someone else’s index.
What we refuse
Similarity is an index. It is not permission, not a receipt, and not an answer to “why did it retrieve this.”
An agent does not act without an approval or capability record. Default-deny is the control, not a courtesy.
If a passage cannot be pointed at, hashed, and replayed, it does not enter production.
Where the runtime sits
Image and model serving in your cage or your rack. Air-gap patterns when the data class requires it.
Isolated network, customer-owned keys, no shared tenancy with another buyer.
A named, logged, contractually bounded API — never a silent public default.
Workspace
This is the density we install. Images, retrieval, receipts, approval. If a screen cannot show why an answer happened, it is not ready.
HIVE WORKSPACE · EVIDENCE
EVAL GATE: PASS
EVIDENCE QUERY
query · exhibit 12 chain of custody · image=EVID-07
Exhibit 12 — chain of custody addendum
EVID-07 / box-4 / p.14 · Lexical span · permission ok
Intake SOP — evidence handling
POLICY-SET / sop-03 · Section lock · same matter
Export runbook — human approval gate
RUNBOOK-OPS / export.md · Capability record, not content
read receipts
1.00
citation coverage
1.00
ungrounded answers
0
tool-policy pass
1.00
Engage
Chat with the on-site desk, book a call with an engineer, or send a scoped engineering brief. There is no public phone line. Work is scoped privately.
On-site only · no public phone · no public rate card