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
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,9 +40,9 @@ The wrapper process is still named `datafog-shim` for compatibility, but we desc
40
40
41
41
## Positioning
42
42
43
-
-**Developers and agent builders:** DataFog is a **privacy firewall for CLI tools and AI agents**. It sits in your PATH or runtime, inspects what is flowing through your commands, and enforces policy before data-sensitive actions execute.
44
-
-**Security/compliance buyers:** DataFog is runtime policy-as-code enforcement at the process level with receipts for every decision.
45
-
-**Broader view:** DataFog is the **data plane for agent governance** — detect, decide, enforce, and audit—not just “PII redaction.”
43
+
-**Developers and agent builders:** DataFog is a **data-aware policy enforcement layer**for CLI tools and AI agents. It sits in your PATH or runtime, inspects data flowing through commands, and enforces policy before sensitive actions execute.
44
+
-**Security/compliance buyers:** DataFog maps closely to runtime DLP for developer workstations, but without the legacy footprint: policy is programmable (OPA-style), decision-aware, and process-bound.
45
+
-**Broader view:** DataFog is the **data plane for agent governance** — detect, decide, enforce, and audit.
46
46
47
47
## Repository layout
48
48
@@ -373,8 +373,9 @@ spec:
373
373
## If something fails, check these first
374
374
375
375
1. `go test ./...` (build/runtime validation before changing policy)
376
-
2. `/health` response for policy id/version mismatch
377
-
3. Environment variables are set and files are writable
378
-
4. API token/header if `DATAFOG_API_TOKEN` is configured
379
-
5. Policy JSON is valid and rules match expected action fields
0 commit comments