knolo — V5-compatible Python runtime
Compatibility status: V5 Knowledge Image verification, deterministic
lexical object queries, and read-only VQF-1 required object/event decoding,
with the existing V1–V3 .knolo reader/query APIs preserved for compatibility.
Python does not implement V5 mutation, coordination, Studio, network
transport, or model execution.
The staged cross-runtime plan is ../../docs/ROADMAP.md.
knolo is the pure-Python runtime for mounting existing .knolo packs and running deterministic lexical queries locally.
It is intentionally release-scoped for a portable, read-only V5 profile:
- local-first retrieval
- deterministic lexical retrieval
- no vector database
- no embeddings on the default query path
- no Python pack builder or V5 mutation API
- no LangChain or LlamaIndex integration
- no Node.js runtime dependency for mount/query
- no V4 receipt or analyzer-profile compatibility claim
- no V5 Studio management runtime
Packs are still built with @knolo/core in TypeScript, then mounted and queried from Python.
Install
From this package directory:
python -m pip install -e ".[dev]"
For a normal install, omit the extra:
python -m pip install .
Query
from knolo import mount_pack, query
pack = mount_pack("tests/fixtures/simple.knolo")
hits = query(pack, "alpha beta", top_k=5)
for hit in hits:
print(hit.block_id, hit.score, hit.text)
You can also mount bytes directly:
from pathlib import Path
from knolo import mount_pack_from_bytes
pack = mount_pack_from_bytes(Path("tests/fixtures/simple.knolo").read_bytes())
V5 Knowledge Images
The Python runtime mounts and verifies the shared V5 image contract without a Node.js dependency at query time:
import base64
from pathlib import Path
from knolo import mount_knowledge_image_v5, query_knowledge_image_v5
fixture = Path("conformance/v5/knowledge-image-v5.fixture.base64")
image = mount_knowledge_image_v5(base64.b64decode(fixture.read_text()))
hits = query_knowledge_image_v5(image, "hello", top_k=5)
print(image.state_root, hits[0].text)
verify_knowledge_image_v5() returns the verified state root, commit digest,
and active superblock. V5 verification is fail-closed for truncated images,
invalid superblocks, non-canonical CBOR, segment digest mismatches, object or
event identity mismatches, and root mismatches. query_knowledge_image_v5()
is a deterministic lexical query over UTF-8 object payloads; policy, authority,
receipts, synchronization, and writes remain host/runtime responsibilities.
The reader accepts the shared compressed object and event fixtures under
conformance/vqf1/ and verifies their logical segment digests and roots. Python
does not emit VQF bytes; TypeScript remains the canonical encoder.
Release Readiness
The package publishes from GitHub release events via Trusted Publishing. No secret-based PyPI credentials are required in CI.
Before a release, run:
python -m pytest
python -m build
python -m twine check dist/*
A manual upload fallback is still available when needed:
python -m twine upload dist/*
See RELEASE.md for the release checklist.
Fixture Regeneration
The committed fixture at tests/fixtures/simple.knolo is what tests use, so the test suite does not need Node.js at runtime.
To regenerate the fixture from the checked-in corpus, run the root helper script from the repo root:
node scripts/regenerate-python-fixture.mjs
The script reads tests/fixtures/corpus/intro.md, runtime.md, and other.md, then rewrites the committed binary fixture. Pass --check to verify that the committed bytes match the corpus without rewriting.
API
The public package exports:
mount_pack(source)mount_pack_from_bytes(data)query(pack, q, ...)KnoloErrorInvalidPackErrorPackStatsPackMetaPackQueryOptionsHitmount_knowledge_image_v5(source)query_knowledge_image_v5(image, query, ...)verify_knowledge_image_v5(source)KnowledgeImageV5KnowledgeImageVerificationV5KnowledgeObjectV5KnowledgeHitV5InvalidKnowledgeImageErrortokenize()normalize()__version__
Current Scope
- No Python pack builder or V5 writer
- No semantic reranking
- No embeddings or vector database integration on the default path
- No Node.js runtime dependency at query time
- No LangChain or LlamaIndex adapters in this package
- No V5 Studio, sync transport, authorization, or authority administration
Release files for knolo 5.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| knolo-5.5.0.tar.gz | 24.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| knolo-5.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:43.0 kB
Release files / knolo-5.5.0.tar.gz
| Download URL | knolo-5.5.0.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63b6b9fab812c260b1d69cd4a15785c4a22f3b38eabc168317be70a670691f1c
|
|
BLAKE2b-256 checksum How to use checksums |
2ffbea567d681e528dea2cf70d8a029743585735b3ab99df2597af5981616d03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.
Transparency logRelease files / knolo-5.5.0-py3-none-any.whl
| Download URL | knolo-5.5.0-py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcfe9b117ae2ff9018b646f7bef66b91b47a77729ced4dc0776e979c2ba96b3d
|
|
BLAKE2b-256 checksum How to use checksums |
a47e84eec874a8cab96fe4704cf5789c1f3a2dcd17f508a72d626589ecb4f55e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.
Transparency log