01
They find Knolo
Operators arrive because retrieval they already bought is not evidence. The answers cannot be replayed. The authority cannot be shown.
V4 ships today. V5 is the runtime. Local-first. Offline verification is first-class.V4 ships today · V5 is the runtime

HIVE · Knolo
HIVE builds production AI systems on Knolo. V4 packs ship today. V5 makes the pack a runtime.
Evidence over demos. American urgency, European caution.
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?
Software

Knowledge Image
One mountable file: knowledge + state + policy + proofs.

Receipts
What was read, written, and run — with a trail another machine can verify.

Runtime
Durable agent runs: tools, budgets, approvals, resume, audit. V5 destination.

Bootcamp
How work starts. One corpus, one workflow, scoped after intake.
Failure mode
Not because the model is dull. Because the system cannot prove what it used, who allowed the action, or whether yesterday’s answer still holds.
01
The model answers. The source is the draft, the email, or last year’s policy.
02
An agent can write, send, or file. Nobody can stop it with a record.
03
Quality is a demo reaction. Production has no pass/fail.
04
A prototype with three champions and zero operator of record.
05
Privileged files sit in a vendor’s default region because the slide said “secure.”

A number an operator understands
A mid-market SIU team was losing a week-plus per complex claim just locating the controlling documents. Bootcamp week produced a Knolo Knowledge Image over the live file corpus and a grounded path with citations. Deploy closed in week eight. Hive Forensics has operated the system since.
Anonymized pattern. No Fortune logos. Legal, insurance, property, and payments are the lanes.
Case patterns →How clients start
01
Operators arrive because retrieval they already bought is not evidence. The answers cannot be replayed. The authority cannot be shown.
02
One corpus. One workflow. One owner. A working path on Knolo, in the environment they name.
03
Investigations, private ops, or an operator agent — sitting on the Knowledge Image, not on a prompt.
04
The legal entity runs the system. Scope is set after intake. There is no public price list.
The product
HIVE systems are built on Knolo. Models are replaceable. The knowledge runtime is not. V4 is what you can mount today. V5 is what the product is becoming.
01
Durable agent runs: tools, budgets, approvals, resume, audit.
V5 destination
02
Embedded transactional knowledge database inside the runtime.
V5 destination
03
One mountable file: knowledge + state + policy + proofs.
V4 ships the file today; V5 extends the contract
04
Evidence Query Language. Canonical evidence packages.
V5 destination
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.
V5 destination
Who it is for
Who it is not for
HIVE BOOTCAMP
A five-day engagement on the customer’s real data. Friday: working workflow, eval notes, a production proposal. Scope is set after intake. Bootcamp is the motion — not a priced SKU on this site.
Not ready to put data in a bootcamp? Advisory review remains available— secondary, not the hero path.
Read the V5 architecture