Processes

Investigate damage cause

How investigate damage cause are reshaped as AGI capability advances.

ProcessesInvestigate damage cause
Investigate damage cause — illustrated

The bottom line

Roughly 75% of the work in Investigate damage cause is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.

Why: Without seeded occupations, the score is derived from the process description. 'Studying the causes of damage... at country level in order to institute better policies and regulations' points to high-level knowledge work—aggregating data, researching, and drafting policy—rather than hands-on physical cleanup, placing it in the digital band.

grounded in the economy graph · digital scalar 0.75 · digital

Related articles

No articles yet for this entity.

Recent capability events

No capability events for this entity yet.

How the work flows

Trigger: A significant damage event or a persistent pattern of property, environmental, or social damage is reported and flagged for root-cause analysis.

  1. Gather damage reports and preliminary incident data
  2. Examine physical, environmental, and social evidence surrounding the event
  3. Analyze collected data to determine root causes and contributing variables
  4. Document findings detailing the mechanisms and impact of the damage
  5. Formulate preventative policy or regulatory recommendations
  6. Submit the final investigation report to governance or regulatory bodies

Outcome: The root causes of the damage are definitively identified and actionable recommendations for policy or regulatory updates are issued.

Measured by

Investigation Cycle TimeRoot Cause Identification RateInvestigation Cost Per IncidentPolicy Recommendation Acceptance Rate