How create and finalize program specifications are reshaped as AGI capability advances.

Roughly 85% of the work in Create and finalize program specifications 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 no child occupations are seeded for this APQC process, the scalar is derived entirely from the process name ('Create and finalize program specifications') and its automotive manufacturing context. Creating specifications is a cognitive, information-transformation task focused on planning, drafting, and technical documentation. Since this consists of pure knowledge work typically performed on computers, it firmly occupies the 'digital' band, assigned a standard band-center value of 0.85.
grounded in the economy graph · digital scalar 0.85 · digital
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Create and finalize program specifications 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 Create and finalize program specifications inherits.
No articles yet for this entity.
No capability events for this entity yet.
Trigger: A new vehicle program or product development initiative receives concept approval and initial funding.
Outcome: Detailed engineering, performance, and material specifications are formally documented, approved, and baselined for the engineering phase.