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
feat(runtime): add strict secrets mode to secrets provider
test(runtime): add strict-mode tests for file provider
docs: clarify async LLM in README and architecture; add TDS parser support matrix; document SECRET_PROVIDER_MODE; TDS scope/risk in ENFORCEMENT
chore(lint): fix E402/E702 and run fmt; translate Swedish comments in workflow
Copy file name to clipboardExpand all lines: README.md
+17-8Lines changed: 17 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,13 +18,13 @@
18
18
<br/>
19
19
</p>
20
20
21
-
SQLumAI is an invisible, AI‑powered proxy for Microsoft SQL Server.
21
+
SQLumAI is an invisibleproxy for Microsoft SQL Server with out‑of‑band AI insights.
22
22
23
23
For non‑technical readers
24
24
- What it does: Watches data flowing to SQL Server and helps improve data quality – without slowing anything down.
25
25
- How it helps: Finds missing values, inconsistent formats (dates, phone numbers), and process gaps; proposes fixes and simpler input rules; summarizes issues daily.
26
26
- Why it’s safe: It forwards traffic transparently by default (dry‑run). You control when to enforce rules.
27
-
- Where AI fits: A local LLM turns raw events into a short list of high‑value actions and insights.
27
+
- Where AI fits: A local LLM turns raw events into a short list of high‑value actions and insights (generated asynchronously, not inline).
{"id":"bss-email-required","target":"column","selector":"dbo.Customers.Email","action":"block","reason":"Email required at onboarding","confidence":1.0},
213
-
{"id":"bss-no-test-subs","target":"pattern","selector":"INSERT INTO dbo.Subscriptions","action":"block","reason":"Stoppa testabonnemang i prod","confidence":0.9}
222
+
{"id":"bss-no-test-subs","target":"pattern","selector":"INSERT INTO dbo.Subscriptions","action":"block","reason":"Block test subscriptions in production","confidence":0.9}
214
223
]
215
224
```
216
225
- LLM insights (examples):
@@ -225,7 +234,7 @@ Principles:
225
234
```json
226
235
[
227
236
{"id":"booking-no-overlap","target":"pattern","selector":"INSERT INTO dbo.Bookings","action":"block","reason":"Overlapping times must be prevented in app logic","confidence":0.8},
228
-
{"id":"booking-email-format","target":"column","selector":"dbo.Bookings.Email","action":"autocorrect","reason":"Korrigera vanliga typos","confidence":0.7}
237
+
{"id":"booking-email-format","target":"column","selector":"dbo.Bookings.Email","action":"autocorrect","reason":"Correct common typos","confidence":0.7}
This document outlines what the built‑in TDS handling currently supports, what is explicitly out of scope, and the safety posture. The goal is transparency so operators can decide when to enable parsing and enforcement.
4
+
5
+
## Philosophy
6
+
- Keep the hot path safe and fast: minimal, best‑effort parsing only where it adds value.
7
+
- Fail open: if parsing or mapping fails, the proxy forwards traffic unchanged and logs context.
8
+
- Prefer explicit rules over heavy rewrites; keep autocorrects reversible and auditable.
9
+
10
+
## Summary Matrix
11
+
12
+
| Area | Support | Notes |
13
+
|------|---------|-------|
14
+
| TDS packet headers | Basic | Used for flow control and identifying packet types. |
0 commit comments