How vorugantirahul/consequent works
Consequent is a customer-escalation decision-support application: a lead enters a case, receives an outcome-informed recommendation, records the real-world result, and uses accumulated consequences to guide later decisions. Its web client also exposes an experience library, learning analytics, Hindsight connection controls, and a guided walkthrough. The server routes these workflows to the decision engine and memory layer; memory combines seeded and locally persisted experiences with optional remote Hindsight retention. Some client and memory code was excerpted only partially, so uncertain wiring is omitted.
Main entry points: server.js HTTP API · hindsightMemory.js Memory Operations · app.js Decision Workspace · hindsightService.js Hindsight Client Service
Components 14
Decision Experience
- Decision Workspace
public/app.js - Outcome Capture
public/app.js - Experience Library
public/app.js - Learning Analytics
public/app.js - Hindsight Controls
public/app.js - Demo Walkthrough
public/app.js
Application API
- HTTP API
server.js - Recommendation Engine
src/engine/decisionEngine.js
Consequence Memory
- Memory Operations
src/engine/hindsightMemory.js - Seed Experiences
src/engine/seedData.js - Memory Store
src/data/memory_store.json
Hindsight Integration
- Hindsight Client Service
src/services/hindsightService.js - Hindsight Platform
Other components
- CS / Ops Lead
Connections 22
- CS / Ops Lead → Decision Workspace: enters case
README.md - Decision Workspace → HTTP API: requests recommendation
public/app.js - HTTP API → Recommendation Engine: evaluates case
server.js - Recommendation Engine → Memory Operations: retrieves similar cases
src/engine/decisionEngine.js - HTTP API → Decision Workspace: returns recommendation
public/app.js - CS / Ops Lead → Outcome Capture: reports outcome
README.md - Outcome Capture → HTTP API: saves consequence
README.md - HTTP API → Memory Operations: records outcome
server.js - Memory Operations → Memory Store: reads and writes
src/engine/hindsightMemory.js - Memory Operations → Seed Experiences: loads seed cases
src/engine/hindsightMemory.js - Memory Operations → Hindsight Client Service: retains consequence
src/engine/hindsightMemory.js - Hindsight Client Service → Hindsight Platform: retains and recalls
src/services/hindsightService.js - CS / Ops Lead → Experience Library: browses experiences
README.md - Experience Library → HTTP API: searches and filters
public/app.js - HTTP API → Memory Operations: lists case history
server.js - CS / Ops Lead → Learning Analytics: reviews trends
README.md - Learning Analytics → HTTP API: loads analytics
public/app.js - HTTP API → Memory Operations: computes analytics
server.js - CS / Ops Lead → Hindsight Controls: configures connection
README.md - Hindsight Controls → HTTP API: configures Hindsight
public/app.js - HTTP API → Hindsight Client Service: tests and syncs
server.js - CS / Ops Lead → Demo Walkthrough: runs walkthrough
README.md