M31: align RAG verification with provider contract
MobilityOps acceptance / backend (push) Canceled after 0s
MobilityOps acceptance / frontend (push) Canceled after 0s

This commit is contained in:
NuklearRabbit
2026-08-10 21:02:47 +02:00
parent efab8d816f
commit cb7edb0b84
8 changed files with 18 additions and 13 deletions
+3 -1
View File
@@ -31,7 +31,9 @@ provide an exact identity lookup through `GET /v1/documents?source_id=...&extern
Fleet Ops uses that documented read contract concurrently and with bounded per-request
timeouts for every managed source in the requested language. A document counts only when
RAGcore returns exactly one active document in the configured space with a published active
version whose `content_sha256` matches Fleet Ops's authoritative file. Results are cached
version. RAGcore's `content_sha256` represents its canonical parsed artifact rather than
the uploaded source bytes, so Fleet Ops deliberately does not compare that provider-owned
hash with its raw Markdown hash. Results are cached
for five minutes. This produces an independently verified `document_count` without changing
RAGcore or relabelling an upload/sync report as index evidence. If exact verification is
temporarily unavailable, `document_count` remains `null` and the sync report stays visibly