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
+58Lines changed: 58 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,6 +77,8 @@ The current recommendation for enterprise teams is a controlled pilot first: sta
77
77
78
78
Use `summarize_operational_telemetry()` with emitted telemetry events when you want route-level, tenant-level, and model-level summaries, blocked-event counts, and rollout visibility for operators.
79
79
80
+
Enterprise deployments can also enrich emitted events with SSO/user context and forward flattened records to Power BI or other downstream reporting systems.
81
+
80
82
### Output grounding and tone review
81
83
82
84
`OutputFirewall` can compare a response to retrieval documents and flag unsupported claims or unprofessional tone before the answer leaves your service.
@@ -105,6 +107,8 @@ Protects the response path by checking outputs for secret leaks, unsafe code pat
105
107
106
108
Protects tool execution with allowlists, blocklists, validators, and approval-required workflows.
107
109
110
+
It can also integrate with `ValueAtRiskCircuitBreaker` for high-value actions and `ShadowConsensusAuditor` for secondary logic review before sensitive tools execute.
111
+
108
112
### `RetrievalSanitizer`
109
113
110
114
Helps keep hostile or manipulative text in retrieved documents from becoming model instructions.
@@ -339,6 +395,8 @@ For Gemini-heavy apps, the bundled adapter now preserves system instructions plu
339
395
- A controlled pilot is a good fit today when you want shadow-mode prompt and output protection without forcing hard blocking on every route immediately.
340
396
- If you prefer not to depend on Blackwall directly everywhere, wrap it behind your own internal model-security abstraction and expose only the contract your app teams need.
341
397
- For broader approval, focus rollout reviews on false-positive rates, noisiest routes, and latency budgets alongside jailbreak coverage.
398
+
- For executive or staff-facing workflows, always attach authenticated identity metadata so telemetry can answer which user triggered which risky request or output event.
399
+
- For high-impact agentic workflows, combine tool approval, VaR limits, digital-twin tests, and signed agent passports instead of relying on a single detector.
0 commit comments