Repair defective items
How repair defective items are reshaped as AGI capability advances.
The bottom line
Only about 10% of Repair defective items is information work today — the rest is physical, and moves slowly. The exposure is concentrated in the back office: the books, the paperwork, the scheduling, the marketing.
Why: With no child occupations seeded, I relied on the process name and industry context ('Motor Vehicle Manufacturing' and 'Automobile Dealers'). The process 'Repair defective items' involves inherently hands-on, physical manipulation and fixing of automotive parts, placing it firmly in the physical band where AI is limited to orchestration and diagnostic coordination.
grounded in the economy graph · digital scalar 0.10 · physical
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Repair defective items 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 Repair defective items inherits.
Where Repair defective items 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 defective item or component is identified during quality inspection, end-of-line testing, or a customer return.
- Isolate and tag the defective item
- Diagnose the root cause of the defect
- Determine repair feasibility versus scrap
- Perform required rework or component replacement
- Re-test the repaired item against quality standards
- Log repair actions and update system records
Outcome: The item is successfully restored to required quality specifications and returned to active inventory, the assembly line, or the customer.