How identify customer requirements are reshaped as AGI capability advances.

Roughly 85% of the work in Identify customer requirements 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: Because there are no seeded child occupations, the scalar is derived from the process name 'Identify customer requirements' and its provided lens. In the context of aerospace and defense, identifying requirements is an information-transformation activity—analyzing technical specifications, reviewing client needs, and writing documentation. This relies heavily on cognitive knowledge work and digital-document tools rather than physical labor, placing it solidly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Identify customer requirements 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 Identify customer requirements inherits.
No articles yet for this entity.
No capability events for this entity yet.
Trigger: A customer request for proposal, statement of work, or new program initiation triggers the need to define system capabilities.
Outcome: A validated and baselined set of technical, operational, and compliance requirements is approved for downstream engineering and design.