You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+55-12Lines changed: 55 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,19 +24,19 @@ Existing tools don't solve this at runtime:
24
24
-**LLM guardrails** handle safety and policy enforcement well - toxicity, jailbreaks, off-topic content. Their provenance validators strip unsupported sentences but don't return a structured claim→URL map, a compliance rate, or a source allowlist.
25
25
-**Prompt engineering** reduces the problem. It doesn't eliminate it.
26
26
27
-
Dokis sits inline - between your retriever and your LLM response going out - and enforces provenance in real time.
27
+
Dokis sits inline between retrieval and response delivery and returns a runtime trust report for the exact answer your system is about to ship. It acts as a provenance and enforcement boundary in real time.
28
28
29
29
---
30
30
31
31
## How it works
32
32
33
-
Dokis does exactly two things:
33
+
Dokis does two things in one deterministic runtime pass:
34
34
35
35
**1. Pre-retrieval enforcement.** Strip chunks whose source URL is not on your allowlist before they enter the prompt.
36
36
37
-
**2. Post-generation auditing.** Split the response into atomic claim sentences. Match each claim to the chunk it came from using BM25 lexical scoring. Build a `claim → chunk → URL` provenance map. Compute a compliance rate. Flag anything below your threshold.
37
+
**2. Post-generation auditing.** Split the response into atomic claim sentences. Match each claim to the best supporting chunk using BM25 lexical scoring by default. Build a `claim → chunk → URL` provenance map. Compute a compliance rate. Return blocked-source details, claim-level verdicts, policy issues, and a final enforcement verdict.
38
38
39
-
No LLM call. No API key. No network request after startup. Deterministic output.
39
+
No LLM call or API key is required for the default BM25 path. Output is deterministic for identical inputs and config.
40
40
41
41
<divalign="center">
42
42
@@ -51,7 +51,7 @@ No LLM call. No API key. No network request after startup. Deterministic output.
0 commit comments