No. 165 / 339
When AI can run the calcs and generate the design, does the civil/structural PE stamp get more valuable or become a bottleneck?
The shift
The analytical and drafting labor that fills most of an engineer's day — running the calcs, iterating the design, producing the sheets, roughly 55% of task-time — goes from scarce human hours to abundant machine output. The one thing that doesn't move: personal legal liability for public safety, which can't be assigned to a model and so concentrates entirely in the PE signature. The stamp and the labor decouple, and they were priced as if they were the same thing.
The axioms
- Engineering fees track analytical and drafting hours — rests on producing calcs and design being scarce, slow, and expensive, so hours are a fair proxy for value delivered.
- The stamp is a personal legal warranty: a named, licensed human is liable to the public and the courts for the design's safety — rests on accountability being scarce, because only a suable, insurable, disbarrable person can carry it.
- Novel, ambiguous, or off-precedent conditions (unusual soil behavior, atypical load paths, construction-sequence risk, a site that doesn't match a textbook case) require judgment, not lookup — rests on judgment-under-novel-stakes being scarce.
- An engineer earns the right to stamp by personally deriving calcs across many projects until they can feel when a number is wrong — rests on the junior-grind training pipeline being the only route to calibrated senior judgment.
- The stamp certifies work performed "under the responsible charge" of the stamping engineer — rests on the derivation being human, supervised, and traceable to a decision the engineer actually made.
Invalid axioms
- Engineering value is measured, and billed, by analytical and drafting hours. The calc-and-draft grind was the visible bulk of the work, so hourly (or hours-derived lump-sum) fees used it as the proxy for value. When that 55% collapses toward near-zero marginal cost, the proxy breaks: the hours vanish but the liability the client is really buying does not. The habit-trap: firms still scope and price by projected labor hours, so as AI compresses those hours, fee revenue falls in lockstep — even though the thing that makes the deliverable legally usable (the stamp, and the exposure behind it) hasn't gotten one dollar cheaper. Pricing the signature as a byproduct of the calc hours means giving away the only part that stayed scarce.
Unchanged axioms
- The stamp is a personal liability instrument, and only a licensed human can carry it. This is the load-bearing one, and it hardens rather than weakens. A model can't be sued, can't hold a license to revoke, can't carry E&O insurance, can't be found personally negligent. When the calcs are cheap, what the client, the AHJ, and the courts are paying for is precisely the assignable liability — the part of the transaction that AI cannot touch by construction. Cheaper production makes the signature the whole product, not a smaller one.
- Novel and off-precedent conditions need judgment, not generation. A model produces a confident, plausible design for a load path or soil condition it has no dense precedent for — and confidently-wrong is the default failure mode, which is the worst possible mode for something with collapse consequences. The engineer's judgment on where the generated design is quietly outside its envelope stays scarce, and rises in value as more of the routine work is automated away.
- Interpreting a design against a specific jurisdiction's requirements requires standing the AHJ will accept. Getting a marginal or negotiated position past a plan reviewer is a relationship and a judgment call informed by precedent, not a lookup a model can be the party to. The engineer is the one in the room whose stamp the jurisdiction is willing to accept.
New axioms
- The stamp is increasingly asked to cover work the engineer didn't derive. "Responsible charge" was built on the assumption that the stamping engineer, or their supervised staff, actually produced the analysis and can trace every number to a decision they made. When the design arrives from a model, the engineer's task silently shifts from deriving to auditing an output they'd have to reconstruct from scratch to fully vet — and reconstructing it defeats the point of generating it. The open problem: what does "responsible charge" mean when nobody in the firm derived the thing the stamp certifies, and no board or court has settled it. Moving fast and unresolved.
- Verification burden per stamp rises even as production cost falls. Each stamp now sits on top of more machine-generated content that has to be checked against ground truth, and a wrong model input (wrong load case, wrong code edition, wrong assumption buried three steps deep) produces a clean-looking, wrong result. If AI also lets each engineer take on more projects, total liability-bearing verification per licensed head goes up while the fee per project goes down — the exact wrong direction for the one scarce resource. This is the bottleneck the question asks about: the stamp doesn't slow down because it's ceremonial, it slows down because real verification per stamp is now larger and can't be delegated to the tool that created the work.
- Junior engineers stop doing the calcs that build the judgment a future stamp requires. The derivation grind wasn't only production — it was how a junior earned the calibrated intuition to know when a number is wrong, which is exactly the STILL HOLDS #2 skill. Automate the grind and you break the pipeline that produces the next generation of stampers. The open problem: how does anyone earn responsible-charge judgment when the practice work that taught it no longer happens, and the senior verifiers age out.
Where it breaks
Firms are already pricing and staffing as if the collapse of calc/drafting hours is pure margin or a fee cut (INVALID #1 acted on), while the thing that survived — the assignable liability — now has to cover more machine-generated content per stamp that the engineer didn't derive (NEW #1 and #2). The engineer is signing for more, verifying more, and being paid by a fee structure that thinks the work got smaller. That gap is invisible until a generated design fails and a deposition establishes that "responsible charge" meant "accepted the model's output on schedule."
The second collision is slower and worse: automating the derivation grind (INVALID #1's mechanism) removes the only pipeline that produces engineers with the judgment to catch a confidently-wrong generated design (STILL HOLDS #2, NEW #3). The stamp gets more valuable exactly as the supply of people qualified to give it credibly starts to thin — a bottleneck that doesn't show up in this decade's fee schedule but is being built into the next one's talent pool.
Related axioms
Other axioms
Engineering
Who's accountable for data quality when AI both generates and validates its own training data?
Engineering
Who owns a CI/CD pipeline once AI agents can write, debug, and modify it directly instead of a dedicated DevOps engineer?
Education
What changes for higher education with AI?
Society
What changes for social work with AI?
Education
What changes for vocational education with AI?
Product Management
Is product ops obsolete once AI dashboards self-generate the metrics reviews ops used to compile?