Fail-Closed Gates
If a gate can't prove compliance, release is blocked. Safety is the default, not the override — every lane is fail-closed by construction.
v0.2.0 · Non-bypassable release gate
Forge audits every release against a 15-domain framework, scrubs secrets, and gates delivery through signed admin approval — so nothing reaches prod that hasn't been verified.
Why Forge
Three principles differentiate Forge from off-the-shelf SAST/DAST stacks. All three are load-bearing in regulated environments.
If a gate can't prove compliance, release is blocked. Safety is the default, not the override — every lane is fail-closed by construction.
The agent audits. Humans approve. The push-service pushes. No single actor can ship unreviewed code — enforced at the protocol level, not by convention.
One 15-domain framework (security, quality, docs, audit) — the same bar for every client, every release. Client configs layer in policy floors, never exceptions.
How it works
Discover the project, scaffold .iata/, detect stack.
Run 18 gates across security, quality, docs, audit trail.
Build a clean delivery branch; scrub secrets, archive evidence.
Signed admin approval required before any remote push.
Push-service ships the tag with its own scoped deploy key.
Modules
One-shot discovery + manifest scaffolding. No config required to start.
Deterministic gates + LLM assist. Evidence archived to the registry.
Staged delivery branch, SBOM, signed tag, archive with checksums.
Admin-only sign-off, tenant-scoped, fully audit-logged.
Industries
Meet the documentation and evidence bar regulators expect.
Prove non-bypass to auditors; separate duties by design.
HIPAA-minded release trails with tamper-evident approvals.
Supply-chain-safe releases for safety-critical software.
We'll stand up a demo tenant against a repo you pick. Under 30 minutes from SSO handshake to first audit.