Knolo KITE Verdicts: Why a Missing Record Is Not a Denial
How Knolo KITE keeps absence apart from refutation: six contract-scoped verdicts, signed completeness declarations, open schemas and conformance fixtures.
Knolo is the open-source, local-first Knowledge Image runtime and format, released under Apache-2.0 as @knolo/core on npm and developed in the open in the Knolo core repository. The newest public piece of Knolo is KITE, published in @knolo/core@6.2.3 on 14 Nov 2026. This note is about one design rule in it: a missing record is not a denial.
The Knolo KITE verdict vocabulary
KITE checks a finite contract against a Knowledge Image. Its result is one of six verdicts, and each verdict is about that contract only, not universal real-world truth:
| Verdict | Meaning |
|---|---|
WARRANTED_IN_SCOPE |
Support is closed, and every declared alternative agrees |
SUPPORTED_OPEN_WORLD |
Support exists, but a completeness or counterfactual obligation is still open |
REFUTED_IN_SCOPE |
Explicit evidence, or a signed completeness declaration, supports the negation, and every declared alternative agrees |
CONFLICTED |
Admitted evidence supports incompatible conclusions |
UNDERDETERMINED |
A required record or applicability fact is missing |
BOUND_EXCEEDED |
The search did not finish. This is not a certificate |
KITE verdicts sit beside Knolo Cortex statuses (ANSWERED, PARTIAL, INSUFFICIENT_EVIDENCE) and do not replace them.
Why Knolo separates absence from refutation
Many systems treat "I found nothing" as "no." Knolo KITE does not. A negative conclusion needs explicit opposing evidence, or a signed completeness declaration that covers the absence. Without one of those, a missing record yields UNDERDETERMINED.
The unit tests make the rule concrete: a signed absence can refute, an unsigned absence cannot. A single retracting change removes WARRANTED_IN_SCOPE. The enumerated worlds are the full subset lattice of declared changes, and a tampered certificate fails verification.
For anyone relying on a verdict, that separation matters. "We have no record of approval" and "approval was refused" are different facts, and the format keeps them apart.
Knolo KITE as an open contract
The KITE pieces are public files, not a hidden service:
- JSON schemas for the contract, completeness declaration and certificate under
schemas/kitein the Knolo GitHub repo - A conformance set,
conformance/kite/v1, that locks the expected verdict andInvarianceRootfor five synthetic fixtures. The runner fails if either changes. - A Rust replay that recomputes a certificate from a world snapshot without searching the image
The InvarianceRoot commits the KITE inputs beside the V5 stateRoot and does not replace it. Every Knolo runtime still verifies the same image bytes. This fits the way Knolo already handles specifications, compatibility and lifecycle: publish the contract and fixtures so that a second implementation can check itself.
Current limits of Knolo KITE
- KITE is optional and loads only from the
@knolo/core/kitesubpath. - The fixtures are synthetic. They are not a measurement against other retrieval approaches, and they are not a novelty claim. The repo says a patent search and a search of non-academic systems come before any such sentence.
- Python does not implement KITE, and the Rust, Python and ICP runtimes remain at 5.5.1.
- The default bounds (5000 graph nodes, 2048 variants, 2 counterfactual changes, 64 retrievals) can be lowered by a caller but never raised.
Developers can run it today with knolo kite evaluate in @knolo/cli@6.2.6. The how-to is on the Knolo developer blog at knolo.dev, and the open process behind Knolo is described on Knolo open technology at knolo.org and in the Knolo KIPs.
knolo · kite · open-technology · specifications · conformance
