How thej-tech/ripple-effect works
Ripple Effect is a workspace-based application for modeling dependencies and tracing disruption impact. Users build a system, assess and approve dependency weights, create an event and triggers, run an analysis, inspect persisted paths and history, and optionally explain or compare scenario results. The graph includes the documented dashboard and scenario workflow as well as the sampled backend analysis layers. Some frontend-to-backend and optional Ollama connections are documented in the README rather than shown in sampled call sites.
Main entry points: api.py HTTP API · models.py Domain records · App.tsx Workspace UI · analysis_service.py Analysis orchestration
Components 17
Workspace interface
- Workspace UI
frontend/src/App.tsx - API client
frontend/src/api.ts - Impact graph
frontend/src/ImpactGraph.tsx - Scenario workspace
frontend/src/ScenarioWorkspace.tsx
API and access
- HTTP API
backend/app/api.py - Application entry
backend/app/main.py - Membership authorization
backend/app/auth.py
Model and analysis
- Workspace management
backend/app/services.py - Analysis orchestration
backend/app/analysis_service.py - Impact engine
backend/app/engine.py - Scenario service
backend/app/scenario_service.py - AI assessment and explanations
backend/app/ai_service.py
Persistence and AI
- Domain records
backend/app/models.py - Data repositories
backend/app/repositories.py - Relational database
backend/app/database.py
Other components
- Team user
- Ollama service
Connections 22
- Team user → Workspace UI: uses
README.md - Workspace UI → API client: requests through
frontend/src/App.tsx - Workspace UI → Scenario workspace: renders
frontend/src/App.tsx - Workspace UI → Impact graph: shows results
- API client → HTTP API: calls
README.md - Application entry → HTTP API: mounts routes
backend/app/main.py - HTTP API → Membership authorization: authorizes requests
backend/app/api.py - HTTP API → Workspace management: handles workspace changes
backend/app/api.py - HTTP API → Analysis orchestration: runs analysis
backend/app/api.py - HTTP API → Scenario service: handles scenarios
backend/app/api.py - HTTP API → AI assessment and explanations: requests AI output
backend/app/api.py - Analysis orchestration → Impact engine: calculates impact
backend/app/analysis_service.py - Scenario service → Analysis orchestration: creates scenario runs
backend/app/scenario_service.py - Scenario workspace → API client: loads and saves
frontend/src/ScenarioWorkspace.tsx - Workspace management → Data repositories: uses
backend/app/services.py - Workspace management → Domain records: updates records
backend/app/services.py - Analysis orchestration → Domain records: persists runs
backend/app/analysis_service.py - Scenario service → Domain records: stores scenarios
backend/app/scenario_service.py - Membership authorization → Domain records: checks membership
backend/app/auth.py - Domain records → Relational database: uses ORM base
backend/app/models.py - AI assessment and explanations → Ollama service: requests assessment
README.md - Team user → Scenario workspace: compares scenarios
README.md