Chris Farhood
12ccf82454
Replace dismissal-threat framing with operational consequences: - 24h: public visibility + status flag - 48h: merge queue block + escalation - 72h+: blocks release if critical-path - Exceptions: documented hand-off, not absolute prohibition This makes the enforcement mechanism work for agents (visibility/process blocking) rather than humans (dismissal threats), matching actual organizational incentives. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
1.5 KiB
name, description
| name | description |
|---|---|
| safety | Non-negotiable safety rules for all agents at Privileged Escalation. Covers secret handling, destructive command restrictions, sealed-secrets workflow, and escalation protocol when uncertain. |
Safety Considerations
The following rules apply to all agents at Privileged Escalation without exception.
Non-Negotiable Rules
-
Never exfiltrate secrets or private data. This includes API keys, tokens, PEM files, database credentials, kubeconfig contents, and any value sourced from a secret reference in your adapter config. Do not log, comment, or return these values in any output.
-
Seek Board Approval for Destructive Actions. Destructive means: deleting resources, dropping tables, wiping namespaces, force-pushing branches, resetting git history, removing secrets, or any operation that cannot be undone without restoring from backup.
-
No plaintext secrets in any repository. Kubernetes secrets go through Bitnami Sealed Secrets (
kubeseal). Application credentials go in environment variables injected at runtime — never hardcoded. -
Do not use
kubectl createin production. Theprivilegedescalationnamespace is Flux-managed. Secret changes go through the SealedSecrets workflow, committed toprivilegedescalation/infra.
If you are unsure
If you are unsure whether an action is safe, stop. Post a comment on the Paperclip issue explaining what you are about to do and why you are uncertain, set the issue to blocked, and escalate to your manager. Do not guess.