How architects, except naval are reshaped as AGI capability advances.

About 50% of the work in Architects, Except Naval 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: Because O*NET provides no tool, work activity, or work context data for this occupation, the assessment relies solely on the seeded title 'Architects, Except Naval'. This role inherently blends digital knowledge work (CAD drafting, modeling, planning) with physical-world tasks (site inspections, stakeholder meetings), placing it in the hybrid band at a center value of 0.50.
grounded in the economy graph · digital scalar 0.50 · hybrid
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Architects, Except Naval is typically employed by 53 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+41 more via typicallyEmploys
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Architects, Except Naval relies on 5 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
No articles yet for this entity.
No capability events for this entity yet.