Contribution Guardrails

The cross-cutting discipline for AI-assisted Drupal contribution development. The recurring failure this prevents: AI claiming correctness it never verified. Drupal treats this as an existential review-cost problem — AI makes contributing cheap but makes reviewing expensive.

When to Use

• During any development between /drupal-ai-contrib:issue and /drupal-ai-contrib:verify
• Before stating that anything "passes", "works", "is done", or "is secure"
• When about to use an SDK symbol, API parameter, or version-specific behavior
• NOT for: running the gates themselves (that is contribution-verify)

Rule 1 — Evidence over assertion

A gate passes only on a produced artifact. Never on the model stating a verdict.

For each gate, produce → capture → check the artifact: