PROFILE
Strict
The plan is pinned. The evidence must hold. If it does not, the runtime abstains or asks to clarify. No fluent guess dressed as a citation.
Knolo · EQL · V5 destination
Evidence Query Language.
EQL is how an agent asks the Knowledge Image for evidence, not for a vibe. Plans hash. Packages are canonical. Another machine can check that the same plan, against the same state root, under the same authority, produced the same package.
PROFILE
Exploratory
The operator is searching. The plan is still hashed, the spans are still bound, but the profile is allowed to survey. It is labeled. It is not strict.
Outcomes
Abstain, clarify, or answer.
Answer
The evidence is sufficient under the profile. The package names the spans, the plan, and the image.
Abstain
The evidence is not sufficient. Silence with a reason is a product feature. Hallucination is not.
Clarify
The query is underspecified or the authority is incomplete. The runtime asks before it acts.
Canonical evidence packages
An EQL result is not a chat transcript. It is a package: the plan, the spans, the image, the authority, the profile. V5 receipts bind to that package. V4 already hashes retrieval plans on the current contract; EQL is the language that makes those plans first-class.
What EQL is not
- Not SQL. Knolo is not a replacement for a relational store.
- Not a prompt template with extra adjectives.
- Not embedding-first search with a query DSL painted on.
V4 retrieval contract: what ships today. Runtime that executes EQL: V5 architecture.