feat: [2026NewYearChallenge] Event-Driven Orchestration (Track B)#218
Open
aritra-os wants to merge 6 commits intoNevaMind-AI:mainfrom
Open
feat: [2026NewYearChallenge] Event-Driven Orchestration (Track B)#218aritra-os wants to merge 6 commits intoNevaMind-AI:mainfrom
aritra-os wants to merge 6 commits intoNevaMind-AI:mainfrom
Conversation
aritra-os
changed the title
Contributor
|
Hi, the build for this PR is not passing yet. Please make the necessary updates, and we’ll review again after that. Thanks! @Rain-09x16 |
Author
fixed can you run the build |
theomart
pushed a commit
to theomart/memU
that referenced
this pull request
Jan 15, 2026
Analyzed the MemU repository to document: - Memory types (Profile, Event, Knowledge, Behavior, Skill) - Three-layer hierarchical architecture (Resource → Item → Category) - Storage backends (InMemory, SQLite, PostgreSQL) - Memorize and Retrieve pipelines - Key architectural patterns GitHub activity analysis includes: - Hot PRs (NevaMind-AI#242 Engram integration, NevaMind-AI#218 Event-Driven Architecture) - Community trends and contribution opportunities - Recent merged features (workflow interceptors, clear memory)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[2026NewYearChallenge] Event-Driven Orchestration Implementation (Track B)
Summary
I have successfully implemented a decoupled, event-driven architecture for MemU as requested in Issue #190. This architecture offloads heavy memory processing to background Celery workers, preventing the main API from blocking.
Key Features Implemented:
EventManager(Pub/Sub pattern) to trigger signals likeon_memory_saved.CeleryDispatcherto route these events to Redis/Celery.worker.pyentry point.src/memu/task_utils) to ensure production readiness.Verification:
examples/example_4_event_driven_orchestration.pyconfirms end-to-end event delivery.tests/test_event_driven.py).tests/test_task_validation.py).