How khairulhafis/mynav works
MynaV is an investigator-led CCTV direction-analysis system: users configure cameras, upload footage for processing, search candidate sightings by area and time, inspect evidence, and record review decisions. The backend coordinates job processing and investigation data; a separate video engine tracks people within uploaded footage and produces candidate sightings and media evidence. The README emphasizes that sightings are independent candidates—not automatic identification or cross-camera route reconstruction. Several frontend and persistence implementations were not sampled, so their internal links are omitted where evidence is unavailable.
Main entry points: compositionRoot.js HTTP application · App.jsx Workspace app · pipeline.py Video analysis · application.js Job orchestration
Components 21
Investigator interface
- Workspace app
Frontend/src/app/App.jsx - Camera setup
Frontend/src/features/cameras - Job workspace
Frontend/src/features/processing - Sighting search
Frontend/src/features/investigations/useSightingSearch.js - Evidence review
Frontend/src/features/evidence - Review decisions
Frontend/src/features/reviews
Backend services
- HTTP application
Backend/src/app/compositionRoot.js - Camera service
Backend/src/modules/cameras - Investigation search
Backend/src/modules/investigations - Review service
Backend/src/modules/reviews - Job orchestration
Backend/src/modules/processing/application.js - Application data
Backend/src/infrastructure/persistence/json - Engine client
Backend/src/infrastructure/engine/httpModelProcessingClient.js
Analysis engine
- Processing API
VideoAnalysisEngine/app.py - Attempt handling
VideoAnalysisEngine/src/application/attempts.py - Video analysis
VideoAnalysisEngine/src/application/pipeline.py - Person tracking
VideoAnalysisEngine/src/domain/tracking.py - Candidate sightings
VideoAnalysisEngine/src/domain/analyses.py - Evidence media
VideoAnalysisEngine/src/infrastructure/evidence.py - Analysis contract
VideoAnalysisEngine/src/schemas.py
Other components
- Investigator
Connections 23
- Investigator → Workspace app: uses
README.md - Workspace app → Camera setup: renders
Frontend/src/app/App.jsx - Workspace app → Job workspace: renders
Frontend/src/app/App.jsx - Workspace app → Sighting search: renders
Frontend/src/app/App.jsx - Workspace app → Evidence review: uses
Frontend/src/app/App.jsx - Workspace app → Review decisions: uses
Frontend/src/app/App.jsx - Sighting search → Investigation search: requests sightings
- Job workspace → Job orchestration: manages jobs
- Review decisions → Review service: submits decisions
- HTTP application → Camera service: registers
Backend/src/app/compositionRoot.js - HTTP application → Investigation search: registers
Backend/src/app/compositionRoot.js - HTTP application → Review service: registers
Backend/src/app/compositionRoot.js - HTTP application → Job orchestration: registers
Backend/src/app/compositionRoot.js - HTTP application → Engine client: configures
Backend/src/app/compositionRoot.js - HTTP application → Application data: configures
Backend/src/app/compositionRoot.js - Job orchestration → Engine client: dispatches attempts
Backend/src/modules/processing/application.js - Processing API → Attempt handling: submits attempts
VideoAnalysisEngine/app.py - Processing API → Video analysis: runs analysis
VideoAnalysisEngine/app.py - Video analysis → Person tracking: uses tracks
VideoAnalysisEngine/src/application/pipeline.py - Video analysis → Candidate sightings: qualifies tracks
VideoAnalysisEngine/src/application/pipeline.py - Video analysis → Evidence media: renders evidence
VideoAnalysisEngine/src/application/pipeline.py - Video analysis → Analysis contract: validates batch
VideoAnalysisEngine/src/application/pipeline.py - Candidate sightings → Person tracking: reads track data
VideoAnalysisEngine/src/domain/analyses.py