LinkedIn·Thursday, 16 July 2026·16 Jul 2026
I've started thinking about a potential role for #Drupal in an Open Source Context Engineering Stack (#MOCES ? anyone? e.g. MOCES: Open…
Kristof Van Tomme
Open Source Developer Portals & API Docs
I've started thinking about a potential role for #Drupal in an Open Source Context Engineering Stack (#MOCES ? anyone? e.g. MOCES: Open Context Engineering Stack 😆) after my interview with Daniel Kocot yesterday for the API Resilience podcast. Drupal would allow non technical users to review generated entities before they are added to a Graph database (like Neo4j). Michael Hunger already suggested me that this would only make sense for key entities where the review costs/efforts make business sense.
Has anybody done work building an entity extraction pipeline in Drupal for a similar purpose? we've done a POC for content augmentation that adds AI generated fields to an entity with a markdown body, but haven't yet done a one-to-many generated entities POC. I think it should work with ECA though...
View on LinkedIn Cross-referenced
Related on the wire
What is the best boundary choice when publishing capabilities? Daniel Kocot just published a great article about the difference between…
Got any interesting stories about Drupal's applications that leverage AI or AI's applications that leverage Drupal? The call for speakers…
I'm super psyched about the "share of voice report" my colleagues created to help customers decide if they want to work with us for their…
repost for additional reach
Who owns the business meaning of your APIs? "The answer is uncomfortable because it is not a single role. The work will remain…
sharing for extended reach