[SESSION_127] SecurityAgent: Implement Cross-Camera Correlation (Phase 23)

Resolved šŸ’¬ 3 comments Opened Nov 20, 2025 by ragdm Closed Jan 19, 2026

Feature: Cross-Camera Threat Correlation

Component: SecurityAgent (/agents/security_agent/)
Severity: šŸ”“ CRITICAL BLOCKER
Session: SESSION 127 (Definition of Done)
Current Status: Stub returns None immediately
Target Phase: Phase 23

Context

Multi-camera threat detection requires correlating suspicious behavior across camera boundaries. Currently, cross-camera analysis returns None, missing critical multi-zone threats.

Requirements

  • Track person/object movement across camera boundaries
  • Detect impossible transitions (e.g., teleportation)
  • Correlate events across time and space
  • Generate cross-camera incident reports
  • Handle camera topology and FOV overlaps

Impact

Without this feature:

  • Cannot detect multi-camera threats
  • Each camera analyzed in isolation
  • Multi-zone sophisticated attacks undetected

Effort Estimate

  • Cross-camera matching: 8-10 hours
  • Temporal correlation: 3-4 hours
  • Testing: 2-3 hours
  • Total: 12-15 hours

Technical Approach

  • Camera topology mapping
  • Person re-identification across views
  • Temporal window correlation (0-5 seconds transit)
  • Threat propagation across camera network

---

Generated by SESSION 127 FASE 2.7

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗