Conduct surveillance
How conduct surveillance are reshaped as AGI capability advances.
The bottom line
About 50% of the work in Conduct surveillance is information-shaped and increasingly AI-deliverable, with the rest a hybrid of judgment and hands-on work. The automation frontier runs straight through the middle of this role.
Why: The process 'Conduct surveillance' has no seeded child occupations. Operating within city government and petroleum upstream industries, surveillance work inherently mixes physical field operations (patrols, physical sensor placement) with digital monitoring (analyzing video feeds, SCADA data, and remote telemetry). Lacking specific component data, I am assigning a band-center hybrid scalar to reflect this blend.
grounded in the economy graph · digital scalar 0.50 · hybrid
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Conduct surveillance sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Conduct surveillance inherits.
Where Conduct surveillance sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A scheduled monitoring interval, an automated sensor alert, or a specific threat intelligence report initiates the need for physical or remote observation.
- Determine surveillance targets and required coverage
- Deploy personnel, cameras, or remote sensing equipment
- Monitor real-time feeds and environmental data
- Identify and classify anomalies, breaches, or safety hazards
- Document observations and compile surveillance logs
- Escalate critical threats to incident response units
Outcome: Targeted areas and assets are monitored, anomalies are documented, and intelligence is delivered to operational or security teams.