Knolo docs — verifiable Knowledge Images and @knolo/core
Knolo 6.2.3 is the open-source @knolo/core knowledge runtime. V5 Knowledge Images are the evidence container. V4 retrieval remains the compatibility path for ordinary search. V6 adds KAR. 6.1.0 adds composition. 6.2.0 adds Knolo Cortex.
Knolo owns artifact structure, roots, evidence identity, validation, deterministic planning, and bounded runtime state. The host owns models, credentials, networking, deployment, tools, and external effects.
This site documents @knolo/core. It is not knolo.io, which is a different product.
Where to start
| Path | Use it when |
|---|---|
| V4 quickstart | You want lexical search over a portable .knolo pack. |
| V5 quickstart | You want a verifiable Knowledge Image and a state root. |
| KAR | You want the minimum typed evidence set for a proposition. |
| Composition | You want to cite images and graphs without changing their roots. |
| Knolo Cortex | You want a bounded evidence loop and a replayable trace. |
| Versions | You need the published package matrix. |
Models change
Knowledge should be an asset you can inspect, verify, migrate, and run.
Conventional AI
- Opaque request-time context
- Environment-dependent retrieval
- Evidence discarded after generation
- Vendor-coupled storage
- Audit added later
- Hard-to-reproduce runtime state
Knolo
- Mounted Knowledge Image
- Deterministic plans and receipts
- Persistent provenance
- Portable artifacts
- Verification built into the contract
- Committed runtime state
Knolo is not an agent runtime and it is not a control plane. Knolo Spawn is delegation.
Claims these docs keep
SATISFIEDmeans the declared KAR evidence requirements were met. It does not mean a claim is proven.UNSATISFIED_EVIDENCE_REQUIREMENTSmeans those requirements were not met. It does not mean the claim is false.- A verified Cortex trace matches the declared evidence. It does not mean the answer is true.
createCortexon@knolo/coreis the V4 memory overlay. Knolo Cortex iscreateCortexSessionfrom@knolo/core/cortex.- Domain Packs shipped with the repository are
review-required. - Rust, Python, and the Internet Computer canister stay on 5.5.1. Rust evaluates and verifies the public KAR vectors. It does not author graphs, write coverage reports, or implement composition or Cortex.
The normative byte contracts are the KIPs in the specification. The 6.2.0 release notes are the product boundary. docs/ROADMAP.md in the repository still describes the earlier V5 gate. Use the release notes when the two disagree.