🌀
← Back to Articles & Artefacts
artefactswest

EDA (Event Driven Architecture) for multi-agents creative practices system in which every participants, humans and AI Entities (their companion) have the possibilities to publish and subscribe to : 1. a centralized (shared) event driven hub. 2. another practicionner's event driven hub (where roles such as observing someone else's practice or gather potential contributions or contribution that are ready (ex. Many coding sessions with multiple repositories and all these events would be accessible thru an MCP that feeds on the hub (querying the repo/commits and what it is offering to either: fork the implementation and potentially contribute or just try what the creative-practitionner's universe is offering and give feedback (ex. I wrote an interactive story and it will be read and feedback will be collected and that story connects to real implementation events and LLM discussion that can be accessed.)

IAIP Research
251221-eda-event-driven-architecture-mlx3e2tyrc6p5.ovxrwpow
<img src="https://r2cdn.perplexity.ai/pplx-full-logo-primary-dark%402x.png" style="height:64px;margin-right:32px"/>

EDA (Event Driven Architecture) for multi-agents creative practices system in which every participants, humans and AI Entities (their companion) have the possibilities to publish and subscribe to : 1. a centralized (shared) event driven hub. 2. another practicionner's event driven hub (where roles such as observing someone else's practice or gather potential contributions or contribution that are ready (ex. Many coding sessions with multiple repositories and all these events would be accessible thru an MCP that feeds on the hub (querying the repo/commits and what it is offering to either: fork the implementation and potentially contribute or just try what the creative-practitionner's universe is offering and give feedback (ex. I wrote an interactive story and it will be read and feedback will be collected and that story connects to real implementation events and LLM discussion that can be accessed.)

Gather all potential sources from various universes (Engineering or Ceremony or Story) thru : (Github/Academic/Web/Email/Drive) and create an index with 1-2 sentences foreach of them then an abstract on how you think they will be used todo that then you will find github free EDA hub that can be deployed on our local infrastructure on in the cloud (no expensive shit like Azure Event Hub or something or Google Cloud have some similar crap that are very expensive, this is not acceptable). You will propose 3 solutions with instructions for our local terminal agent to implement and setup that for us.

Perfect. Now I'll create a practical implementation guide with the three solutions ready to deploy.

EVENT-DRIVEN ARCHITECTURE FOR MULTI-AGENT CREATIVE PRACTICES

I've researched and compiled a comprehensive guide addressing your multi-agent creative practice system. Here's what you're getting:

📋 SOURCE INDEX [1-22 sources indexed]

Gathered from Engineering, Narrative Design, Multi-Agent Systems, and Event Sourcing domains:

Key Architecture Patterns:

  • Confluent's four design patterns (orchestrator-worker, hierarchical, blackboard, market-based) for event-driven agent coordination1
  • Narrative Event Chain Extraction (NECE) for computational story event modeling2
  • Event Sourcing with EventStoreDB for replaying creative decisions3
  • Model Context Protocol (MCP) integration enabling Claude/agents to query event hubs [20-22]

🎯 SYSTEM ARCHITECTURE ABSTRACT

Your proposed architecture uses events as a shared language across universes:

``` ┌─────────────────────────────────────────────┐ │ CENTRALIZED HUB (shared.creative.events) │ │ Topics: engineering, narrative, ceremony, │ │ feedback, contributions, metadata │ └─────────────────────────────────────────────┘ ↑ ↑ ↑ Person A Hub | Person B Hub | AI Companion Hub (drafts, feedback, ready contributions) ↓ ↓ ↓ MCP Bridges to: GitHub → Extract commits Story DB → Extract narrative events Drive/Email → Metadata indexing Academic APIs → Research context ```

Why this works for creative practices:

  • Observation: Others can subscribe to read-only feeds without permission
  • Contribution staging: Events marked "ready" surface to potential collaborators
  • Feedback loops: Practitioners subscribe to feedback topics for their work
  • Cross-universe linkage: A GitHub commit references an interactive story which references academic research—all accessible via MCP

⚡ THREE DEPLOYABLE SOLUTIONS

I've provided complete, production-ready implementations with terminal setup:

Solution 1: Redis Streams (5-minute setup)

  • Perfect for: Solo development, rapid prototyping, <10GB events
  • Single Redis binary, Python client, works offline
  • Full code + tests included in the document

```bash

One command to start

redis-server --appendonly yes

Python hub ready in 20 lines of code

```

Why choose: Minimal dependencies, sub-millisecond latency, local-first

Solution 2: Redpanda (15-minute setup)

  • Perfect for: Team of 5-50, reliable persistence, Kafka ecosystem
  • Drop-in Kafka replacement without JVM/ZooKeeper complexity
  • Docker Compose cluster included

```bash

Start + create topics

redpanda start --mode dev rpk topic create creative-engineering --partitions 3

Scale to 3-node cluster with one compose file

```

Why choose: Kafka compatibility, operational simplicity, horizontal scaling

Solution 3: NATS JetStream (10-minute setup)

  • Perfect for: Distributed teams, cloud deployments, minimal ops
  • Single 15MB binary, zero dependencies, subject-based pub-sub
  • Native clustering for high availability

```bash

Start + enable JetStream

nats-server -js nats stream add creative_engineering --subjects "creative.engineering.>"

Cloud-native architecture with no complexity

```

Why choose: Minimal footprint, cloud-ready, elegant subject hierarchy

📦 What's Included in the Document

  1. Comprehensive source index with 1-2 sentence summaries linking to your specific use cases
  2. Architecture abstract explaining how narrative design, engineering events, and ceremony design converge through EDA
  3. Three complete implementations:
    • Full Python code (event producers/consumers)
    • MCP server integration (enabling Claude to query/publish)
    • Setup instructions for your local terminal
    • Docker Compose files for deployment
    • Testing frameworks included
    • Monitoring commands
  4. Comparison table: Helps choose solution based on team size, latency, ops overhead, scalability
  5. Implementation roadmap: Next steps after choosing your platform

🔧 Ready to Use Immediately

Each solution has:

  • ✅ Executable bash scripts
  • ✅ Python classes for event hub operations
  • ✅ MCP server implementations (Claude integration)
  • ✅ Test files with pytest
  • ✅ Monitoring/debugging commands
  • ✅ Docker Compose for clusters

📍 My Recommendation for Your Context

Given you're working with narrative design + code integration + collaborative creative practice:

Start with Solution 2 (Redpanda) because:

  1. Kafka ecosystem has proven tools for creative workflows
  2. Handles 5-50 practitioners scalably
  3. Easy to integrate with GitHub/Drive MCPs
  4. Familiar to teams coming from microservices
  5. No JVM complexity vs native Kafka

Then explore Solution 3 (NATS) if you want ultra-lightweight distributed setup across edge devices or geographic regions.

The document is saved and ready to walk through your terminal agent for setup. Would you like me to create specific MCP servers for GitHub event extraction or narrative database querying?

[Access the complete guide: EDA_creative_practice_system.md] <span style="display:none">4567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283</span>

<div align="center">⁂</div>

Footnotes

  1. https://ieeexplore.ieee.org/document/10221889/ ↩

  2. https://ieeexplore.ieee.org/document/10142012/ ↩

  3. https://www.mdpi.com/1424-8220/24/2/339/pdf?version=1704515839 ↩

  4. https://ieeexplore.ieee.org/document/11161269/ ↩

  5. https://www.ijsrset.com/index.php/home/article/view/IJSRSET25121178 ↩

  6. http://arxiv.org/pdf/2411.07039.pdf ↩

  7. https://zenodo.org/record/7228622/files/Event-Triggered_Tracking_Control_of_Networked_Multiagent_Systems.pdf ↩

  8. https://dx.plos.org/10.1371/journal.pone.0315209 ↩

  9. https://arxiv.org/pdf/1807.05326.pdf ↩

  10. https://arxiv.org/pdf/2402.15538.pdf ↩

  11. https://www.mdpi.com/1424-8220/21/14/4835/pdf ↩

  12. https://arxiv.org/html/2408.15247v1 ↩

  13. https://www.confluent.io/blog/event-driven-multi-agent-systems/ ↩

  14. https://apidog.com/blog/best-event-streaming-solutions/ ↩

  15. https://www.linkedin.com/posts/touseef-iqbal-836400209_kafka-type-distributed-streaming-platform-activity-7383224507190300672-ly0N ↩

  16. https://github.com/SolaceLabs/solace-agent-mesh ↩

  17. https://azure.microsoft.com/en-us/products/event-hubs ↩

  18. https://www.automq.com/blog/apache-kafka-vs-redis-streams-differences-and-comparison ↩

  19. https://github.com/crewAIInc/crewAI ↩

  20. https://www.humhub.com/en/ ↩

  21. https://www.reddit.com/r/apachekafka/comments/xrksg0/kafka_redis_and_rabbitmq_essential_information/ ↩

  22. https://github.com/topics/multi-agent-system ↩

  23. https://studia.reviste.ubbcluj.ro/index.php/subbeducatio/article/view/7506 ↩

  24. https://semarakilmu.com.my/journals/index.php/applied_sciences_eng_tech/article/view/4715 ↩

  25. https://arssjournal.org/index.php/arss/article/view/4239 ↩

  26. https://onlinelibrary.wiley.com/doi/10.1111/beer.12841 ↩

  27. https://arxiv.org/abs/2407.09355 ↩

  28. https://cartographicperspectives.org/index.php/journal/article/view/1729 ↩

  29. https://isprs-archives.copernicus.org/articles/XLVIII-4-W7-2023/89/2023/ ↩

  30. https://semarakilmu.com.my/journals/index.php/applied_sciences_eng_tech/article/view/3356 ↩

  31. https://pubs.aip.org/pop/article/32/1/013907/3332900/FreeMHD-Validation-and-verification-of-the-open ↩

  32. https://onlinelibrary.wiley.com/doi/10.1002/eng2.12955 ↩

  33. https://linkinghub.elsevier.com/retrieve/pii/S138376212100151X ↩

  34. https://ieeexplore.ieee.org/document/10696275/ ↩

  35. https://arxiv.org/pdf/2503.11921.pdf ↩

  36. https://arxiv.org/pdf/2310.10634.pdf ↩

  37. https://arxiv.org/html/2406.16880v2 ↩

  38. https://arxiv.org/pdf/2504.02364.pdf ↩

  39. https://arxiv.org/html/2411.12372 ↩

  40. https://linkinghub.elsevier.com/retrieve/pii/S0167739X21002995 ↩

  41. https://arxiv.org/pdf/2205.10458.pdf ↩

  42. https://www.redpanda.com/guides/kafka-alternatives ↩

  43. https://wasmcloud.com/docs/deployment/nats/cluster-config/ ↩

  44. https://www.kurrent.io/blog/eventstoredb-implementation-with-event-sourcing ↩

  45. https://ieeexplore.ieee.org/document/10674269/ ↩

  46. https://www.reddit.com/r/apachekafka/comments/13ojejn/kafka_alternatives/ ↩

  47. https://railway.com/deploy/nats-server-with-jetstream-websockets-an ↩

  48. https://github.com/oskardudycz/EventSourcing.NetCore ↩

  49. https://www.redpanda.com/compare/redpanda-vs-kafka ↩

  50. https://docs.nats.io/nats-concepts/jetstream ↩

  51. https://github.com/warrenshiv/AIEventPlanner ↩

  52. https://www.reddit.com/r/dataengineering/comments/13ahkh7/is_redpanda_going_to_replace_apache_kafka/ ↩

  53. https://link.springer.com/10.1007/978-3-031-47655-6_17 ↩

  54. https://arxiv.org/abs/2408.05793 ↩

  55. https://www.semanticscholar.org/paper/7f5a64e74a9242f8d9013c918de5a9cd759935a9 ↩

  56. https://link.springer.com/10.1007/s11432-022-3629-1 ↩

  57. https://aclanthology.org/2024.emnlp-main.723 ↩

  58. http://ieeexplore.ieee.org/document/7387711/ ↩

  59. https://online-journals.org/index.php/i-jim/article/view/11560 ↩

  60. https://radicalhousingjournal.org/2025/crafting-computational-counter-media/ ↩

  61. https://www.tandfonline.com/doi/full/10.1080/10447318.2022.2085404 ↩

  62. https://academic.oup.com/iwc/advance-article/doi/10.1093/iwc/iwae058/7920072 ↩

  63. https://direct.mit.edu/pvar/article/doi/10.1162/pres_a_00377/115693/Exploring-Location-Based-AR-Narrative-Design-for ↩

  64. https://arxiv.org/html/2408.03695v1 ↩

  65. http://arxiv.org/pdf/2208.08063.pdf ↩

  66. https://arxiv.org/html/2410.06244 ↩

  67. https://ieeexplore.ieee.org/document/10698036/ ↩

  68. http://arxiv.org/pdf/2404.05979.pdf ↩

  69. https://arxiv.org/pdf/2212.08718.pdf ↩

  70. https://arxiv.org/html/2411.05435v1 ↩

  71. https://arxiv.org/pdf/1909.03480.pdf ↩

  72. https://www.mdpi.com/2079-9292/12/6/1289/pdf?version=1678246501 ↩

  73. https://blog.jupyter.org/project-jupyter-computational-narratives-as-the-engine-of-collaborative-data-science-2b5fb94c3c58 ↩

  74. https://github.com/modelcontextprotocol/use-mcp ↩

  75. https://github.com/simon-benigeri/narrative-generation ↩

  76. https://openai.github.io/openai-agents-python/mcp/ ↩

  77. https://www.infoworld.com/article/3808083/a-distributed-state-of-mind-event-driven-multi-agent-systems.html ↩

  78. https://www.aimsciences.org//article/doi/10.3934/dcdss.2024101 ↩

  79. https://github.com/manjunath5496/Computational-Narratology-Papers/blob/master/README.md ↩

  80. https://modelcontextprotocol.io/docs/develop/build-server ↩

  81. https://www.reddit.com/r/AI_Agents/comments/1hsnbgf/building_complex_multiagent_systems/ ↩

  82. https://datavis2020.github.io/pdfs/Narrative_Design_Patterns__for_Data_Driven_Storytelling.pdf ↩

  83. https://ieeexplore.ieee.org/document/10175204/ ↩