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
{{ message }}
Repository navigation
Commit 8a65a76
Browse filesBrowse the repository at this point in the historyBrowse files
Vikhyath Mondreti
committed
fix(provenance): preserve mixed files and repeated durable bindings
Copy file name to clipboardExpand all lines: apps/sim/content/blog/secret-provenance/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ faq:
21
21
- q: "Does Sim use regular expressions to detect secrets in logs?"
22
22
a: "No. Sim resolved the secret itself, so it can compare content against the exact values activated in that run. Pattern matching is useful when a scanner does not know which secrets exist; the execution runtime has stronger context."
23
23
- q: "What happens if Sim cannot determine whether content contains a secret?"
24
-
a: "The boundary fails closed. The payload is withheld, while non-sensitive structure such as timing, block identity, and status remains available for debugging."
24
+
a: "Incomplete provenance at a run's own egress boundaries withholds the payload while preserving safe diagnostic structure. Durable reads follow the surface's enforcement policy: legacy content remains readable, and unknown stored provenance can be observed before enforcement is enabled."
25
25
- q: "Are secrets tracked across files and tables, or only within one execution?"
26
26
a: "Across both. Durable content such as workspace files, table cells, knowledge documents, and agent memory carries encrypted provenance so a later run does not mistake secret-bearing data for clean data."
27
27
- q: "Is the model treated as an internal component or an egress boundary?"
0 commit comments