AI Governance

Publishing an AI-generated answer raises two questions: who oversees its production, and what can its reader verify? ...more

AI becomes a different infrastructure problem once organisations need to know where data goes, which models are approved, and how spending is controlled. amazee.ai and Tag1 will bring those questions to DrupalCon Rotterdam through a private gateway and Scolta implementation. ...more

For several DrupalCon Rotterdam sessions, the useful question is not simply whether Drupal teams can automate more. It is where automation should stop, where review should begin, and what people still have to judge for themselves. ...more

The more consequential part of Dropsolid's Rotterdam presence is not the sponsorship tier. It is the argument that Drupal's content, permissions and workflows can form part of the control layer around AI systems using organisational knowledge. ...more

Putting AI into production raises harder questions than connecting a model to Drupal. Rotterdam speakers focus on context, evidence, controls and human review. ...more

What should an agency return to the open-source ecosystem it relies on? Zoocha’s answer connects community investment with harder questions about AI accountability and Drupal’s ability to explain its value beyond familiar audiences. ...more

Community safety and the risks surrounding public AI tools are on the agenda for online sessions taking place this week. ...more

A Drupal AI operation can incur provider charges without showing its estimated cost to the person who triggered it. AI Metering brings that visibility into Drupal while giving administrators ways to set and enforce monthly limits. ...more

Employees can use public AI tools before security, privacy, or compliance teams have clear visibility into how company information is handled. The session examines that governance gap and approaches to more controlled AI access. ...more

Drupal publishers testing AI-generated content now have a configurable way to record origin and display disclosures, but the beta leaves legal interpretation and final configuration to site operators. ...more

A capable model becomes a fragile dependency when access, pricing, or policy changes. Drupal teams need routing and fallback plans that keep governance inside the site rather than inside one provider. ...more