Knolo is an embedded, verifiable knowledge runtime for autonomous agents.
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.
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.
MSA-2024.pdfp.41 §8.3 · ev-8.3
rider-b-subs.pdfp.3 · ev-rB
memo-counsel-0312.pdfp.2 · ev-m12
North star
One .knolo artifact should answer:
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?
V4 · ships today
A verifiable pack and retrieval contract you can run locally.
Portable .knolo files. Deterministic lexical-first retrieval. Evidence spans, plan hashes, and read receipts. TrustBench Phase 5 is the public contract in knolo-core. TypeScript @knolo/core is the v4 reference.
The runtime that makes that pack the agent’s source of truth.
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. Not shipping as the public contract yet.
A .knolo Knowledge Image is something counsel, SIU, or an operator can inspect. V4 ships that file today: knowledge you can retrieve, permissions that travel with it, hashes you can recompute, read receipts you can verify. V5 extends the same artifact into state, policy, authority, and runs.