// security & guardrails

Guardrails
before autonomy.

Forgewarden is built around scoped credentials, small automations, visible logs and human approval for dangerous actions.

Credential posture

  • Scoped API tokens — never global account keys
  • Wrangler / Cloudflare secrets — never committed env files
  • GitHub secret scanning and gitleaks workflows
  • Redaction before logs, reports and model context

Operational posture

  • Read-only first when exploring unknown systems
  • Approval gates in front of production changes
  • Rollback notes written before deploys
  • Local, staging and production kept strictly separate
// risk defaults

What asks. What acts.

RiskDefaultWhy
DNS / nameserversAsk firstCan break domains, email and production services
Billing resourcesAsk firstCan create unexpected cost
SecretsNever print · never commitLeaked credentials stay dangerous in history forever
Local tunnelsAsk firstCan expose private machines or services
Routine reportsAutoSafe, useful and reversible

Safety is the product

Every protocol from the Build Lab ships with these guardrails baked in — not bolted on afterwards.

Design a gated agent ⚒