>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3542728. --> Reported by: [therobyouknow](https://www.drupal.org/user/197207) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>As a website develops and its purpose evolves, this can inform suggestions of re-modelling content types - e.g. moving fields between types, new types, new entity relationships.</p> <p>We live in an Agile world. From experience, not everything is known about how a website - an information product - is going to be used - by the client/site builder and what they have in mind for content and how users use it.</p> <p>What I feel can happen now, is that a site can gradually diverge from effectiveness, as the restrictions on remodelling entities once they are populated with data limits it. The divergence continues until at some point everyone talks of rebuilding.</p> <p>Instead, with AI assistance, incrementally remodel the entities and relocate the data as an when required. This overlaps into Drupal migrate where data may be exported and re-imported back into a new site entity / content type model.</p> <p><a href="https://dri.es/why-drupal-is-built-for-the-ai-era">https://dri.es/why-drupal-is-built-for-the-ai-era</a> inspired me that AI agents can look inside Drupal config yaml files. </p> <p>Could they be used to automate remodelling?</p> <h4 id="summary-steps-reproduce">Steps to reproduce (required for bugs, but not feature requests)</h4> <p>Please provide information like AI modules enabled, which AI provider, browser, etc.</p> <p>Feature suggestion.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>As per summary.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Exploration, feasibility, protyping.</p> <h3>Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)</h3>