## Research Question Can the [Rules](https://www.drupal.org/project/rules) module realistically host the GitLab workflow automation for the AI Initiative — receiving GitLab webhooks, evaluating conditions, and calling the GitLab API to update issues, MRs, labels, and comments? ## Background The umbrella issue #3586474 captures the full goal. We need to choose a Drupal-side platform to host the automation logic. Rules is the most mature Drupal workflow engine and is worth evaluating first because many maintainers already understand its UI and conditions/actions model. ## Scope **In scope:** - Standing up a minimal Drupal site with Rules (D11/D10 compatible state). - Wiring an inbound webhook endpoint that Rules can react to. - A proof-of-concept rule: e.g. "when MR pipeline fails on a `state::needsReview` issue, transition to `state::needsWork`". - Cataloging Rules' fit (or gaps) for the 7 automation behaviors listed in the umbrella. **Out of scope:** - Production deployment. - Implementing all 7 automations — those are separate tickets blocked by this exploration. - Comparing to ECA (covered in its own exploration issue). ## Approach - Set up a fresh Drupal install and enable Rules (and `gitlab_api` if useful here too). - Configure a GitLab project webhook against the local environment (use ngrok or DDEV share). - Build one end-to-end PoC rule end-to-end. - Identify gaps: missing condition/action types, custom code likely required, maintainability of complex multi-step rules. ## Deliverables - [ ] PoC site or DDEV recipe demonstrating one webhook → Rules → GitLab API round-trip. - [ ] Written findings document covering: feasibility, gaps, estimated custom-code surface, and a recommendation (yes / no / maybe). - [ ] If "yes": a follow-up rollout plan referenced from the umbrella issue. ## Findings <!-- To be filled during and after the investigation. --> ## Related issues ## AI Usage - [x] AI Assisted Issue — This issue was generated with AI assistance, but was reviewed and refined by the creator.