Skip to content

docs: say which targets to trust #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
khushi-git-7 merged 1 commit into from
Nov 11, 2026
Merged

docs: say which targets to trust #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -277,6 +277,10 @@ ragprobe baseline --target http://localhost:8000/ask
ragprobe diff --target http://localhost:8000/ask
```

**Which targets to trust.** An HTTP target only receives test requests. A Python target is imported
and called inside RAGProbe's own process, so its module-level code runs with your permissions: point
`--target module:attr` only at code you trust, or run RAGProbe in a container or VM when you don't.

**HTTP contract.** RAGProbe POSTs `{"question": "..."}` and reads a JSON object back.
Only `answer` is required; return `contexts` (the chunks your retriever used, with the
stable ids your golden set names in `expected_chunks`) to get retrieval metrics:
Expand Down
Loading