Buildability / Receipt

Does RAG Know When Retrieval Is Wrong? Diagnosing Context Compliance under Knowledge Conflict

This public receipt window renders only fields present in the canonical receipt object, deterministic fixture receipt, or canonical evidence receipt. Missing compute, demo, hash, signature, approval, telemetry, and adoption fields stay explicit.

API receipt Buildability hub

Public buildability page receipt window

Watch and verify: Does RAG Know When Retrieval Is Wrong? Diagnosing Context Compliance under Knowledge Conflict

/buildability/does-rag-know-when-retrieval-is-wrong-diagnosing-context-compliance-under-knowledge-conflict

Watchwatch

Subject: Does RAG Know When Retrieval Is Wrong? Diagnosing Context Compliance under Knowledge Conflict

Verdict

Watch

Verdict is Watch because viability or proof quality is intermediate and should be re-evaluated before execution.

Time to first demo

Insufficient data

No first-demo timestamp, owner estimate, or elapsed demo receipt is attached to this surface.

Compute envelope

Structured compute envelope

Insufficient data

No data, compute, hardware, memory, latency, dependency, or serving requirement receipt is attached.

Evidence ids

Truth Boundary

External gate remains unresolved for live deployment claims.

Buildability surfaces only report computed viability and proof receipts. They do not claim live production usage, pilot outcomes, founder sign-off, public Brier calibration, judge divergence, or external adoption unless explicitly sourced.

Proof divergence Developer guide

Does RAG Know When Retrieval Is Wrong? Diagnosing Context Compliance under Knowledge Conflict

Watch and verify: Does RAG Know When Retrieval Is Wrong? Diagnosing Context Compliance under Knowledge Conflict

Compute envelope

Evidence ids

External gate remains unresolved for live deployment claims.

Freshness

Hash state

Signature state

Blockers