app-ai-guardrails

# app-ai-guardrails Scaffold a greenfield app so the **full guardrail canon** is live in **commit #1** and every one of the 7 **gates** is **verified green** before that commit exists. The canon is stack-agnostic; each stack's mechanics live in one adapter file. The differentiator is **teeth**: gates that *fail* on violations, not report-only tooling. You wire the canon, run every gate green, prove the tree is clean, then commit. ## 1. Scope Greenfield only in v1. Six native adapters — Next.js (deep), NestJS, Django, Go, Rust, Spring Boot — plus a discovery method that maps the canon to any other stack. All six native adapters have benchmark medians (Spring Boot: sonnet n3, median 89, all gates green); **discovery is unbenchmarked and says so**. Retrofitting the canon onto an existing codebase — or scaffolding a new package **inside** an existing monorepo (every mechanism here assumes repo-root ownership: hooks, CI, commit #1, `.claude/` all at root) — is **out of scope**. If asked, decline politely and say why (an agent under a "make gates green" mandate inside real code can weaken tests/code to pass; greenfield bounds that blast radius), and leave value behind: point the user at `references/canon/gate-interface.md` for the 7-gate contract they can wire by hand today. ## 2. The gate contract Every guardrailed repo exposes the same 7 gate **names** on its native runner. The names are identical across stacks; only the runner prefix differs. | Gate | Semantic | |---|---| ...