V5
Unified transaction ledger
Knowledge, memory, policy, authority, and run events commit as one history. Cortex stops being a side log.
Knolo · V5 · not the public contract yet
Architecture of the verifiable runtime.
V5 is the active upgrade: a proposed verifiable knowledge runtime. V4 is what you can mount today. This page is public architecture, not a spec dump and not a ship date.
Determinism contract
Same root. Same plan. Same authority. Same runtime contract.
= the same canonical evidence package.
If a second machine cannot reproduce it, the first machine did not produce Knolo. It produced a completion.
Labeled V5
Capabilities of the upgrade. Not claimed as shipping.
V5
Crash-safe incremental store
Writes do not force a full-corpus rebuild. The image stays live while the store advances.
V5
State roots and time-travel snapshots
Pin a moment. Replay from it. Ask what the agent knew then, not what the index happens to hold now.
V5
EQL with hashed plans
Evidence Query Language. Strict versus exploratory profiles. Abstain, clarify, or answer — with a plan another machine can hash.
V5
Read, write, and run receipts
V4 proves a read. V5 proves a write and a run: what changed, under which authority, with which tools.
V5
Default-deny capabilities
Authority is committed state, not a config file on the side. If it is not in the image, the tool does not run.
V5
Durable, resumable agent runtime
Tools, budgets, approvals, resume, audit. Kill the process. Continue on another machine from the same root.
V5
Rust reference kernel
V5 inverts the V4 language story. Other languages bind to the kernel. They do not reimplement it.
V5
Branch and delta sync
Replicas can diverge and merge. Sync cannot silently broaden authority.
V5
Offline verification
No Knolo-hosted control plane is required to check a receipt, a plan, or a run. Local-first is the product.
Air-gapped demo · plain language
Mount. Query. Wait. Commit. Kill. Resume. Verify.
That sequence is the product test. Not a chatbot demo. Not a hosted dashboard. An independent verifier, offline, reproducing the chain.
01
Mount
A signed Knowledge Image is mounted offline. No phone-home.
02
Query
The agent asks through evidence rules. Strict profile: answer, abstain, or clarify.
03
Wait
A sensitive tool does not fire. It waits for approval. Authority is default-deny.
04
Commit
Knowledge and memory commit together. One ledger, one state root.
05
Kill
The process dies. The run is not lost. The image still holds the pinned snapshot.
06
Resume
Another machine mounts the same artifact and continues the run.
07
Verify
An independent verifier reproduces the chain. Same root, same plan, same authority, same evidence package.
Allowed public concepts
State root. Pinned snapshot. Receipt. Evidence span. Capability. Default-deny. Knowledge Image. EQL. Cortex. Run resume. Fail closed.
Internals stay internals. This page is for a CISO, a senior engineer, and an agent-platform buyer — not a recipe for forging receipts.
Not product goals
- ZK proofs as a product headline
- On-chain storage as the kernel
- SQL compatibility as a sales promise
- Embedding-first retrieval
Current public contract: Knolo V4.
HIVE builds systems on this trajectory.
V4 images go into production now. V5 is the runtime those images are becoming. Bootcamp is how a corpus enters the contract.