Trust & compliance

Forgewarden is designed to make safe engineering behavior visible and reviewable.

What the system is designed to support

• Local-first processing and approved-repository boundaries
• Read-only inspection before any mutation is considered
• Content hashes, source revisions, and reproducible evidence
• Fail-closed handling for stale state, risky findings, and missing approvals
• Explicit separation between testing, approval, and deployment
• Audit records that avoid copying source contents or secrets unnecessarily

What this page does not claim

Forgewarden is not currently represented as SOC 2 certified, ISO certified, HIPAA compliant, or approved for a specific regulatory program. Compliance depends on implementation, configuration, operating procedures, and independent assessment. This page describes product design goals and evidence patterns—not a certification.

Designed for conversations with security teams

Use Forgewarden to make questions concrete: What was tested? Against which revision? What changed? Who approved it? What was blocked? What evidence remains? Formal compliance work can then evaluate those controls against the requirements that actually apply to your organization.