How the-srirup/cauveris works
Cauveris investigates cyber-physical incidents from uploaded evidence through causal diagnosis, counterfactual simulation, repair verification, and reporting. The graph emphasizes the backend pipeline and its operator-facing web console, while retaining documented holographic reconstruction and deployable repair packaging. Pipeline-stage links are supported by the orchestrator excerpt; other links use the README or SOURCE INDEX references. Unsampled subsystems are shown only where the repository tree and documentation establish their role.
Main entry points: main.py Backend API · runner.py Digital Twin · controller.py Bundle Intake · generator.py Hypothesis Generation
Components 20
Incident Intake
- Incident Record
cauveris/schemas/incident.py - Bundle Intake
cauveris/ingestion/controller.py - Intake Security
cauveris/security.py - Artifact Inventory
cauveris/inventory/artifact_inventory.py
Causal Investigation
- Evidence Timeline
cauveris/timeline/builder.py - System Model
cauveris/analysis/system_model.py - Hypothesis Generation
cauveris/hypothesis/generator.py - Model Gateway
cauveris/model_gateway/base.py - Temporal Analysis
cauveris/temporal/integration.py - Experiment Sandbox
cauveris/sandbox/controller.py - Digital Twin
cauveris/simulation/runner.py
Repair and Verification
- Patch Forge
cauveris/patch/generator.py - Patch Verification
cauveris/verifier/engine.py - Repair Packaging
cauveris/packaging/api_router.py - Investigation Report
cauveris/report/generator.py
Operator Platform
- Web Console
apps/web/app/page.tsx - Backend API
cauveris/api/main.py - Holographic Views
apps/web/app/holographic-reconstruction/page.tsx - Pipeline Persistence
cauveris/state_machine/persistence.py
Other components
- Operator
Connections 24
- Operator → Web Console: investigates incidents
README.md - Web Console → Backend API: requests investigation
- Backend API → Bundle Intake: accepts bundles
cauveris/api/main.py - Backend API → Incident Record: creates records
cauveris/api/main.py - Bundle Intake → Intake Security: validates input
cauveris/ingestion/controller.py - Bundle Intake → Artifact Inventory: inventories artifacts
cauveris/ingestion/controller.py - Backend API → Evidence Timeline: starts pipeline
cauveris/api/main.py - Backend API → Hypothesis Generation: starts pipeline
cauveris/api/main.py - Backend API → Digital Twin: starts pipeline
cauveris/api/main.py - Backend API → Patch Forge: starts pipeline
cauveris/api/main.py - Backend API → Experiment Sandbox: starts pipeline
cauveris/api/main.py - Backend API → Patch Verification: starts pipeline
cauveris/api/main.py - Backend API → Investigation Report: starts pipeline
cauveris/api/main.py - Evidence Timeline → System Model: provides evidence
- Hypothesis Generation → System Model: derives causes
cauveris/hypothesis/generator.py - Hypothesis Generation → Model Gateway: requests reasoning
cauveris/hypothesis/generator.py - Backend API → Temporal Analysis: runs analysis
cauveris/api/main.py - Experiment Sandbox → Digital Twin: tests interventions
cauveris/sandbox/controller.py - Patch Forge → Digital Twin: uses simulation mapping
cauveris/patch/generator.py - Patch Verification → Digital Twin: checks outcomes
cauveris/verifier/engine.py - Backend API → Repair Packaging: serves repair archives
cauveris/packaging/api_router.py - Backend API → Holographic Views: serves investigation views
- Backend API → Pipeline Persistence: persists pipeline state
cauveris/api/main.py - Backend API → Investigation Report: returns findings
cauveris/api/main.py