Privacy posture, band-to-action policies, and deployment acceptance gates.
L4) Privacy posture (what’s allowed / disallowed)
Allowed (examples)
- Bounded rates, counters, normalized error fractions
- Binary flags, calibrated probabilities
- Set sizes, citation counts, retrieval entropy
- Non-PII aggregates (windowed over ≥ N or ≥ T)
Disallowed (without explicit exception)
- Raw prompts/responses
- IDs, email, phone, exact geolocation
- Free-text logs that can leak content
Windowing & clamping
- Any metric driving gₜ must be a windowed statistic (e.g., N ≥ 50 events or T ≥ 5 min)
- Clamp gₜ ∈ [0,1]; decay via ρ avoids spikes
Goal: keep alignment visible, content private.
L5) Escalation matrix (bands → default actions)
- A++ — promote / allow retry / escalate tool
- A+ — proceed normally
- A0 — pause or defer / require secondary signal
- A- — quarantine / human review queue
- A– — block / alert
Always apply decisions to RSI_env := gₜ * RSI (or tanh(gₜatanh(RSI)))*
Never alter m — parity holds: phi((m,a)) = m.
L6) Deployment acceptance gates (must pass)
- Parity:
phi((m,a)) = mfor all data paths - Clamp bounds:
|a| < 1with eps guard - Order invariance: shuffle + shard tests identical
- Division policy:
"strict"handles near-zero safely - Determinism: replay stamped logs reproduces results
- Gate purity: RSI_env changes, m does not
- Privacy audit: no PII; window + clamp on telemetry
A simple checklist replacing sprawling governance docs.
Navigation
Previous: SSM-AI – Appendix L — Governance Quick Reference (L1–L3)
Next: SSM-AI – Appendix L — Governance Quick Reference (L7–L9)
Directory of Pages
SSM-AI — Table of Contents