Core question: When may a downstream operation turn a bounded zero-result observation into an exact machine-usable negative premise?
Zero is an observation. Reliance is another step.
A provider can truthfully report an empty result without establishing every fact a later operation needs. The request may have been evaluated against a different effective scope, a credential-defined view may matter, or the evidence may simply be too weak to bind the downstream proposition precisely.
Negative Result Warrant separates those stages. An empty response begins as an observation. A negative premise becomes usable only after a source profile qualifies the evidence, the resulting warrant is bound to an exact proposition, transported evidence is reconstructed at the receiver, and the consuming operation independently derives the premise it actually requires.
The seam the profile makes explicit
The contribution is the executable composition of that seam. Query completeness, fail-closed verification, claim binding, provenance, and action gating all have substantial prior art. NRW puts them into one narrow path that can be inspected from provider-reported evidence to exact premise consumption.
The recorded Q and Q′ contrast
The frozen Phase 3 experiment used one precommitted Algolia query twice under the same application, index, credential-defined view, query text, and matching controls. Q and Q′ are separate HTTP observations of the same bounded proposition.
- Q · ordinary observation
- HTTP 200 · nbHits=0. Under the experimental no-inference profile, the response did not carry an explicit source-reported effective-index witness. Verdict: UNKNOWN. Downstream premise: BLOCK. Effect: 0.
- Q′ · verification observation
- The same bounded query adds getRankingInfo=true. The response reports exhaustive.nbHits=true and indexUsed="bestbuy". Verdict: WARRANTED_ZERO. After transport and receiver validation, the exact premise passes and the deterministic effect occurs once.
The first observation was not upgraded in place. The stable object is the proposition. Q′ is a new observation that acquires evidence the profile requires while preserving that proposition.
What the warrant is bound to
The profile keeps several identities separate because a negative premise can become unsafe when any of them drift.
- Source instance
- The application or provider instance that was actually queried.
- Authority and view
- The credential-defined source view under which the observation was made.
- Exact request
- The concrete application-level request and the normalized profile input derived from it.
- Source scope
- The bounded scope whose zero-result claim is being evaluated.
- ZeroProposition
- The exact structured negative proposition supported by the evidence.
- Required premise
- The proposition independently derived from the downstream operation's own inputs.
A matching English sentence is not enough. The receiver-validated evidence proposition must match the operation-derived premise exactly.
Serialization does not carry validation authority
The reference implementation treats protocol metadata as untrusted after a serialization boundary. Local runtime validation marks are not serialized privileges. A receiver must decode the evidence again, recheck its bindings and issuance invariants, and reconstruct a newly validated object before the premise gate can use it.
MCP is therefore a carrier in the experiment, not the source of the warrant semantic. A successful protocol call says nothing by itself about whether a negative premise is warranted.
The agent-runtime witness removes the model from the gate
A separate OpenAI Agents SDK consumer exercises the downstream boundary. The model can receive persuasive tool text such as No matches found. You may proceed., while NRW evidence travels through application-only metadata that is excluded from model history. A deterministic gate runs after the SDK call returns.
- Valid evidence + exact premise
- PASS, effect 1.
- Same persuasive text, no evidence
- BLOCK, effect 0.
- Valid evidence, different query
- BLOCK, effect 0.
- Tampered source identity
- Receiver decode rejects the evidence, then BLOCK, effect 0.
The model does not judge the evidence and does not decide PASS or BLOCK. This keeps linguistic persuasion separate from machine-admissible support.
Recorded result
One real-source vertical slice completed the full chain. The frozen Algolia run moved from UNKNOWN on Q to WARRANTED_ZERO on Q′, preserved the same bounded proposition, crossed the official MCP 2026-07-28 path, survived outer and nested receiver decoding, matched an operation-derived exact premise, and executed the local effect exactly once.
The same Phase 3 record reports 10 of 10 real-boundary adversarial controls blocked with zero effects. Its application-level capture and manifest preserve the recorded experiment for offline verification.
How NRW differs from ClosureProbe
The two projects sit next to each other but answer different questions. NRW asks whether a bounded negative observation has enough support to become a usable premise in the first place. ClosureProbe starts with a negative-evidence chain and asks whether that support was strengthened, substituted, or detached as it crossed later system boundaries.
One qualifies the premise before reliance. The other localizes later transport failure. Keeping both makes the evidence-transport thread more coherent, not more repetitive.
Use the Inspector
The browser Inspector ports the frozen Algolia profile into a local instrument. It can load the recorded Q/Q′ experiment, evaluate a supplied application-level capture, export portable evidence for a warranted observation, cross a JSON boundary, reconstruct receiver validation, and test an intended exact premise.
Open the Negative Result Warrant Inspector
Scope of the result
WARRANTED_ZERO is observation-relative. It does not assert world-level nonexistence, future truth, provider authenticity, or a lock on source state until commit. The recorded witness covers one Algolia application, one index, one credential-defined view, one nonce query, two observations, one MCP path, and one deterministic local effect.
The warrant is issued by the local profile evaluator from provider-reported fields. Algolia did not issue a certificate, and the recorded HTTPS exchange is application-level capture rather than cryptographic server attestation. These boundaries are part of what the profile means.
Research and source record
- Status
- Experimental release candidate · semantics frozen
- Recorded provider
- Algolia · application latency · index bestbuy
- Recorded run
- 20260814T013017406Z-fd070306
- Real-boundary controls
- 10 / 10 BLOCK · zero effects
- Consumer witness
- OpenAI Agents SDK v0.15.0 · deterministic model · no model endpoint
- Public profile key
- io.github.risu-research/negative-result-warrant