A thread circulating on r/math this week, picked up across Hacker News, reported that GPT-5.6 used a single prompt to close a 30-year open problem in convex optimization. The post was careful and technical, not hype. Researchers were debating the validity, not the sensationalism. That's worth paying attention to.

Convex optimization is not an obscure corner of academia. It underlies logistics routing, financial portfolio construction, machine learning model training, and supply chain scheduling. The people who work in those fields — operations researchers, quantitative analysts, industrial engineers — have long been considered safe from automation pressure because their work requires deep mathematical reasoning. That assumption is now shakier than it was last Monday.

What's actually changing

The honest answer is: we don't know the pace, but the direction is clear.

For years, the automation risk models used by labor economists drew a line between routine tasks (vulnerable) and expert cognitive tasks (protected). Recent BLS occupational data has already started to complicate that picture, showing wage pressure in some technical fields even before AI math capabilities accelerated. What the convex optimization result signals is that the line isn't a wall — it's a gradient, and it's moving.

The jobs most exposed aren't necessarily the ones that feel most exposed. Truck drivers and cashiers get the headlines, but the families with real medium-term vulnerability include households where one earner holds a job that is:

  • Primarily analytical, where the end product is a recommendation or a model rather than a physical action
  • Credential-gated rather than relationship-gated — meaning clients pay for certified expertise, not for a specific person's judgment they've come to trust
  • Legible to text — the work can be described in a prompt and the output can be reviewed by a non-expert

That describes a meaningful slice of white-collar professional work: certain legal research roles, actuarial modeling, mid-tier financial analysis, radiological screening, some software architecture tasks. These aren't jobs disappearing next quarter. But a household with a 10-year financial horizon that doesn't factor in capability risk is doing incomplete planning.

What we'd actually do

Audit which income in your household is relationship-dependent versus credential-dependent. If clients or employers pay specifically for your judgment and your continuity — they know your name, they trust your history, they'd notice if you left — that income is more durable than income where you're interchangeable with anyone holding the same certification. Know which category you're in. If you're in the second one, start building toward the first.

Add one human-network investment per quarter. This doesn't mean networking events. It means doing something that builds specific trust with a specific person: a referral, a piece of original analysis you share with a colleague, a coffee where you actually help someone solve a problem. Human relationships compound slowly. The time to start is before you need them.

Build a 9-month expense buffer, not the standard 3-6. If your role is in a technically sophisticated field with high AI exposure, the conventional emergency fund math undershoots the risk. A career disruption in a field undergoing structural change doesn't resolve in three months. Recent data on job search duration for displaced technical workers supports pushing that number higher. It's not glamorous preparedness, but it's the most protective thing most households can do.

Identify one technical skill adjacent to AI tools that your field hasn't absorbed yet. Not "learn to code" generically. Something specific: how to evaluate AI-generated legal citations for hallucinations, how to audit a model's optimization output for edge-case failure, how to structure a prompt that extracts reliable quantitative reasoning rather than confident-sounding nonsense. The people who survive technical disruption are rarely the ones who resist the tools — they're the ones who become fluent in their failure modes before their peers do.

The bigger picture

AI solving a hard math problem doesn't mean AI is smarter than mathematicians. It means the capability frontier is moving in a direction that will restructure which cognitive tasks humans are paid to perform. That has happened before — with calculators, with databases, with the first generation of expert systems — and the families that navigated those transitions best were the ones who saw the gradient early and adjusted incrementally rather than waiting for the disruption to feel urgent.

The goal isn't to be afraid of the tools. It's to have enough financial slack and enough human-network depth that you can absorb a transition without it becoming a crisis. That's durable. That's the whole point.