The Braided River: Designing Work for 2050

Nov 12, 2026 · @Samuel R Lammie

The river

From Bear Creek, the Bitterroot River does not run in one channel. It spreads across its gravel floodplain in a dozen threads that split, rejoin, and shift with every spring runoff. No single strand is the river. The river is the braid.

That is the shape of the change coming to work. No single technology will carry it, not AI, not robotics, not anything else on the list. The work of 2050 will come from many strands braiding together: energy, biology, machines, sensing, intelligence, and people themselves.

Make no mistake about the force involved. These technologies will arrive less like a spring rise than a tsunami, and unless we start planning now, the cost to displaced Americans will be severe. But this post is not a lament. It is a design brief. If we are honest about what is coming, and lead rather than react, we can shape where the channels run.

The design window

It is tempting to measure this moment against a century of change: the motor car, the steam engine, the light bulb. But 2050 is 24 years away, not 100. The fairer comparison is 1926 to 1950. A worker from 1926 set down in 1950 would have recognized most jobs, even with electricity, automobiles and radio already in wide use.

The lesson is in how electricity actually changed work. Economic historian Paul David showed that electric motors took roughly 40 years to show up in factory productivity. Owners first simply swapped a large electric motor in for the steam engine. The gains came only when factories were redesigned around many small motors, one per machine, with new floor plans and new jobs.

We are in the swap-the-engine stage now, with several technologies at once. The deep reorganization of work likely falls between about 2035 and 2050. That makes the next decade a design window: the institutions, training paths and habits we build now will decide what that reorganization looks like.

A Pittsburgh lesson

Steel runs on both sides of my family. My mother's father worked more than 25 years at U.S. Steel's Homestead Works. On the Lammie side, a mill-newsletter clipping I still keep records a family with a 126-year service record at the By-Product Plant of Jones & Laughlin's Pittsburgh Works, the coke ovens in Hazelwood on the Monongahela. My great-grandfather, James Lammie I, put in 40 years before his pension in 1922. My grandfather, James Lammie II, put in 52. His sons followed: my uncle James III for 22 years before he left for California in 1942, and my father, Benjamin, 12 years and still on the job when the clipping ran. Soon after, he traded the coke ovens for the Navy Seabees, serving with the 41st Naval Construction Battalion in World War II: a builder still, on a different front. After the war he came home to J&L and worked there until his death in 1969, so the family's record kept growing long after the clipping's 126 years.

"By-Product Record," J&L mill newsletter, c. 1942. James Lammie II, the central figure of a family with a 126-year service record at the Pittsburgh Works.

He never saw the mills fall. In the 1970s the mills along the Monongahela still looked permanent. Within a decade most of them were gone.

US Steel closed its Duquesne Works in 1984 and Homestead Works in 1986. Estimates vary by source and period, but the region lost more than 100,000 manufacturing jobs in the steel collapse, and area unemployment exceeded 18%. Communities organized as best they could, founding the Mon Valley Unemployed Committee in 1982 and the Rainbow Kitchen in Homestead in 1984. That was relief after the wave, not planning before it.

Pittsburgh the city did reinvent itself. In 1979, while the mills were failing, Carnegie Mellon founded its Robotics Institute with a $3 million grant from Westinghouse. It became the world's first academic department devoted entirely to robotics. Universities, hospitals and research became the new mills. Today, at Hazelwood Green, on the grounds of Jones & Laughlin's Hazelwood Works, where the by-product plant that employed three generations of Lammies ran until 1998, Mill 19 houses Carnegie Mellon's manufacturing research and the Advanced Robotics for Manufacturing Institute, alongside Catalyst Connection's workforce training floor. Steel frame on the outside, robotics and training on the inside.

But the mill towns did not all come back. Monessen, one reporter wrote, never recovered from the collapse of the steel industry in the 1980s. The city's recovery was largely organic, carried by institutions that happened to be there. The workers and towns in its path were mostly left to absorb the shock on their own. One analysis argues that American steel had failed to make the essential investments to remain competitive long before the closings.

I find that hard to read without a lump in my throat, and full of hope. The ground where my family made coke for steel for 126 years now trains people and builds robots for the economy that comes next. The transition happened. The open question is always who it carries along.

That is the lesson for 2050. Some change will come organically, and some places will land well. But the new technologies will arrive as a tsunami, not a tide, and this time the wave reaches every sector and every region at once. Proactive leadership, planning for displaced workers before the plants close, is what separates a Pittsburgh from a Monessen. We know how the story ends without it. We have a decade to write a better one.

The strands

Each strand is best read not as a threat to jobs but as a new capacity: something people will be able to do that they could not do before. Seven strands matter most.

Strand	The new capacity	The work it calls for
Energy	Rebuilding the grid around clean power, storage and transmission	Electricians, line workers, grid engineers: skilled, local, physical work
Biology	Making things by growing them rather than extracting them	Bio-manufacturing, engineered crops and soils, new medicine
Machines	Handing off the dangerous, the repetitive and the remote	Robot technicians, operators, and the people who design the hand-off
Sensing	Seeing the whole planet continuously, from orbit to soil	Interpreters who turn signal into stewardship decisions
Intelligence	Amplifying human judgment across every other strand	People who frame questions, check answers and own decisions
People (demographics)	An aging workforce that makes human contribution scarcer and more valued	Care, teaching, mentoring, and workforce design itself
Planet (sustainability)	Sustainability as the organizing goal for the whole system	Restoration, adaptation, and nature-based infrastructure

The last two rows are different in kind: they are not technologies at all. People, meaning demographics, may shape the 2050 workforce as much as AI does, because many economies face too few workers, not too many. And Planet, meaning sustainability, is less a strand than the floodplain the other five braid across.

Where the strands braid

The most interesting work of 2050 will sit where strands join. No forecast in 1926 listed "radio repairman," and no forecast today can list the jobs these junctions will create. Four junctions are already visible.

Wildfire. Satellites, drones and AI fire-behavior models now see a fire's growth in near real time. Crews are still on the line. The new work is the bridge between the two: people who read the models, know the ground, and make the call.

Discovery. AI and biology together are speeding the search for new drugs, crops and materials. The bottleneck moves from finding candidates to testing them wisely, which is human, laboratory and field work.

The grid. Robotics and energy together: inspection drones and maintenance robots on transmission lines, with skilled technicians directing them across rough country.

Nature-based infrastructure. This is where biology does the work, and it is the junction I find most hopeful. The Corps of Engineers' Engineering With Nature program describes its aim as the intentional alignment of natural and engineering processes. Wetlands that absorb floods, living shorelines, floodplains reconnected to their rivers. In the West, low-tech process-based restoration uses hand-built wood structures and beaver dam analogs to let beavers and the stream rebuild wet meadows themselves. Practitioners describe these methods as often inexpensive and low-tech, and potentially more scalable than heavy engineered alternatives. Beavers are the original civil engineers. People design, site and tend the work; the animals and the water do much of the building.

New tools for designing with nature

A new generation of tools makes this kind of design practical at scale:

Tool	What it does	Who offers it
Satellite Embedding dataset (AlphaEarth Foundations)	An AI model fuses optical, radar, LiDAR and climate data into compact summaries of every 10-meter square of land and coastal water, for mapping ecosystems and tracking change	Google DeepMind, through Google Earth Engine
InVEST	Free, open-source models that map and value what nature provides (flood protection, water purification, pollination, carbon) and compare management scenarios	Natural Capital Project, Stanford
Beaver Restoration Assessment Tool (BRAT) and Riverscapes models	Estimates where streams can support beaver dams and assesses riparian condition and recovery potential	Riverscapes Consortium, Utah State University
Engineering With Nature guides and Proving Grounds	Practice guides, project atlases and a 2026 innovation handbook for natural and hybrid infrastructure	U.S. Army Corps of Engineers
AI bioacoustics and eDNA monitoring	Listening devices and water or air samples, read by AI, show which species are present and when, without disturbing them	Research groups and firms such as Rainforest Connection and NatureMetrics

Each of these tools creates work rather than removing it: someone must collect ground truth, interpret results for a community, and decide.

Designing humans in

Three critical questions frame the human role in 2050. Where in the system do we want people, and why? What do people contribute there that nothing else can? And how will they be prepared to get there? These are design questions, and we can answer them on purpose. Human participation (our judgment, our care, our presence on the land) should be placed deliberately, not left over after the machines are done.

Four roles stand out.

• Stewards. Someone must own the outcome. When I served as an acting district ranger, the authority lay in the signature, not the analysis. Law, medicine, land management and finance all assign accountability to a person. In 2050 that will still hold, and it should.
• Interpreters. Machines produce signal in abundance. Telling true signal from noise takes tacit knowledge: of the ground, the community, the history of a place. The field crew that once collected the data becomes the crew that checks whether the map matches the forest.
• Caregivers and teachers. Work built on relationship (nursing, teaching, mentoring, ministry) grows as societies age. Technology can lighten its load; it cannot be its heart.
• Integrators. The people who braid strands together. In my career, GIS did exactly this: it joined data, disciplines and agencies on a common map. The integrator who can speak to the engineer, the ecologist, the machine and the town council will be among the most valuable workers of 2050.

This also reframes human resources. In a system of people, machines and living landscapes, HR becomes workforce design: deciding where human judgment sits, how people grow into those roles, and how the gains are shared. That is strategic work, not administration.

Building the ladder forward

There is one honest difficulty worth naming. Every senior professional of 2050 has to start somewhere in the 2030s, and the starting rungs are the ones new tools absorb first. Early evidence points the same way: Stanford's Digital Economy Lab reports that young workers in the most AI-exposed occupations now trail their less-exposed peers in employment by 19%, mainly through slower hiring. Economists still dispute how much of that is AI, but the design signal is clear.

The answer is to build the ladder forward, not pull it up:

• Pair beginners with the tools, don't replace them with the tools. A junior forester with AI-assisted inventory can learn in two years what once took five, if someone designs the job that way.
• Bring apprenticeship back on purpose. Paid, structured, mentored entry roles in the trades, in restoration, in health care and in the professions.
• Credit what people can do. Demonstrated skill should count as much as a degree, so people can move between strands as the river shifts.

Design principles for 2050 work

1. Lead before the wave. Plan for displaced workers and communities before the closings, not after. Pittsburgh's mill towns are the cost of waiting.
2. Keep a human hand on every consequential decision. Accountability is the anchor of trust.
3. Grow, don't extract. Prefer work that builds living capital (soil, forest, wetland, skill) over work that draws it down.
4. Let nature do what it does well. Beavers, floodplains and forests are infrastructure. Design with them.
5. Build the ladder before you need the senior people. Every tool rollout should include a plan for how beginners learn.
6. Measure what matters. Use the new sensing tools to account for natural capital and human growth, not just output.
7. Keep work rooted in place. The most durable jobs will be tied to a watershed, a community, a landscape.

Sidebar: the odds on a good outcome

These are judgment calls, not measurements, written as probabilities so they can be argued with.

Outcome by 2050	Estimate	What it rests on
Energy and restoration work becomes a major source of skilled US jobs	60–75%	Directionally anchored on current grid and restoration buildout; politics can swing the timing
Nature-based infrastructure becomes a standard option in US flood and water projects, not a pilot	55–70%	Anchored on the Corps' growing practice guides and atlases; slower in budgets than in guidance
Human sign-off remains legally required for most high-stakes decisions	70–85%	Rests on how slowly law changes; medium confidence in the range itself
Deliberate apprenticeship paths are rebuilt in most AI-exposed fields	40–60%	Unanchored; depends on choices not yet made, which is the point of this post

Confidence that each direction is right is higher than confidence in the exact ranges.

Working with Mother Nature

I began this thinking "if Mother Nature allows us to live as we are now." I end it with a different phrase: if we work with Mother Nature. She sets the floodplain every channel must cross. The braid of energy, biology, machines, sensing and intelligence will run where we let it, and where we design it to.

The Bitterroot reshapes its channels every spring and is still the Bitterroot. Work in 2050 will look different in nearly every detail, and it can still be recognizably human: people tending the land and water, caring for one another, and signing their names to what they decide. That is not a prediction. It is a choice still open to us.

This piece was produced in collaboration with Claude, an Anthropic AI assistant. The argument, the sources, and the editorial judgments are the author's. 

Sources

• Stanford Digital Economy Lab update on young workers in AI-exposed jobs (GCN)
• Engineering With Nature: An Atlas, Volume 3 (USACE)
• Engineering With Nature Proving Grounds Innovation Handbook, 2026 (USACE)
• Riverscapes Models & Tools, including BRAT (Utah State University)
• A New Framework for Assessing Beaver-Related Restoration (NW CASC)
• AlphaEarth Foundations (Google DeepMind)
• InVEST (Natural Capital Project, Stanford)
• Combining bioacoustics and eDNA (Fugro)
• Paul A. David, "The Dynamo and the Computer: An Historical Perspective on the Modern Productivity Paradox," American Economic Review 80, no. 2 (May 1990): 355–361

• Devastation in Pittsburgh: US Steel closures (ASM International)
• Mon Valley manufacturing job losses (Medill)
• Post-industrialization and community response (University of Pittsburgh Library)
• Pittsburgh is building an embodied future (Mercury)
• Pittsburgh: From Dying Steel Town to Global Robotics Hub (Asian Robotics Review)
• Carnegie Mellon and Mill 19 at Hazelwood Green (BD+C)
• Monessen after steel (WSWS)
• The Mon Valley's long reckoning (PublicSource)

• Industrial relics and Mill 19 at Hazelwood Green (PublicSource)
• Jones and Laughlin historical marker (HMdb)
• "By-Product Record," mill newsletter clipping on the Lammie family, c. 1942 (family collection)

Oversight That Holds Load

A design test for AI governance, written for the committees that will hold the oversight pen

Nov 11, 2026 · Samuel R. Lammie, with Claude (Anthropic) and ChatGPT (OpenAI)

Disclosure: the co-authors of this piece are large language models built by companies that profit from AI adoption and whose systems would fall under the oversight it describes. Weigh its contributions accordingly.

The 120th Congress convenes in January with new committee chairs and new oversight priorities. Whoever holds those gavels will hear a great deal about artificial intelligence: frameworks, pilots, task forces, guardrails. This piece offers them one test to apply to all of it. For any AI provision, ask where it binds. A governor slows the machine itself. A stamp is a named person's approval before the irreversible step. An after-action review learns from what already happened. Most of what is sold as AI oversight is an after-action review dressed as a stamp. The difference decides whether anyone can actually stop a system once it is running.

I write as a retired federal land manager, not as a partisan. My federal career ran from Bureau of Indian Affairs forestry on Apache reservations in Arizona, through the National Park Service, to more than two decades in the Forest Service, ending as the Northern Region's geospatial program manager. In 2025 I completed Carnegie Mellon's certificate in Managing Artificial Intelligence Systems, so I come to this from both sides: as someone who ran the systems agencies depend on, and as someone trained in how AI systems should be governed. The test below is the one I would want any committee to apply, whichever party chairs it.

Where things stand

Federal AI policy now runs on three instruments, and none of them is a statute.

The first governs how agencies use AI. OMB Memorandum M-25-21, issued April 3, 2025, requires each agency to name a Chief AI Officer and identify "high-impact" AI, meaning systems whose output is a principal basis for decisions that significantly affect rights or safety. For those systems it sets minimum risk practices, including "human oversight, intervention, and accountability" and a "timely human review and a chance to appeal." It also contains the strongest sentence in current federal AI policy: if a high-impact use case does not comply, "the agency must safely discontinue use of the AI functionality."

The second governs who may regulate AI at all. Executive Order 14365, signed December 11, 2025, created a Justice Department AI Litigation Task Force to challenge state AI laws. It directed Commerce to list "onerous" state laws within 90 days, tied some federal funding to state alignment, and asked for a legislative proposal to preempt conflicting state rules. It carves out child safety, data center infrastructure and state procurement. An executive order cannot preempt state law on its own; that takes Congress.

The third is still a draft. In June 2026, Representatives Lori Trahan (D) and Jay Obernolte (R) released a discussion draft of the Great American AI Act that would preempt state laws on AI model development for three years while leaving states free to regulate deployment and use. It drew fire from both directions: from Democrats, civil rights and labor groups for preempting too much, and from many Republicans for preempting too little. In July the two sponsors introduced one piece of it as a stand-alone bill requiring independent audits of large frontier developers.

That is the ground the new chairs inherit: a use-side memo with a real brake in its text, a preemption push with no statute behind it, and a bipartisan draft that splits development from use. All three can be read with the same test.

The test: governor, stamp, or after-action review

A governor on an old steam engine did not report that the engine had run too fast. It closed the throttle before the engine could. That is the first stage: friction built into the system itself, through permissions, rate limits, spending caps and required confirmations. A governor slows the machine. It does not decide.

The second stage is the stamp: a named, accountable person's final approval before the irreversible step. Engineers stamp drawings; surveyors stamp plats. A stamp says a qualified person looked, judged, and will answer for it. It is the only stage where refusal lives.

The third stage is the after-action review, the wildland fire community's term for learning from what happened: an audit, a report, an inspector general finding, a hearing. By then the agent is already out the door. In earlier pieces I called this a gate. After-action review is the more honest term, because a gate implies it stops something.

All three have their place. Governors buy time, and after-action reviews are how institutions learn. But only the stamp puts a person between the system and the harm, and AI systems increasingly act faster than any review can follow.

Applied to the current instruments, the test sorts quickly. M-25-21's discontinue clause is a governor at the program level: noncompliant systems must stop. Its compliance reporting is an after-action review. Its human-oversight requirement is a stamp only if the human approves before an AI-driven decision takes effect; afterward, it is a review. Executive Order 14365 is neither, because it governs who may regulate rather than how systems behave. The Trahan–Obernolte draft would remove state-level governors on model development for three years. The federal instrument offered so far is an independent audit, which is an after-action review. Audits are worth having. They are not a stamp.

The question for a committee is never "does this provision mention oversight?" It is "does this provision bind in the machine, at the stamp, or only in the review afterward, and on whom?"

The rate problem

Stability is a rate, not a state. Living systems run at nested speeds: a leaf turns over in a season, a hardwood stand in a century, a soil in millennia. Systems fail when one part runs at a speed the parts that govern it cannot match. A forest plan revised every fifteen years cannot govern a beetle outbreak that moves in two seasons.

AI oversight has the same flaw. An agent acts at machine rate, in seconds. The instruments that oversee it run at document rate: annual inventories, compliance reports, hearings scheduled months out. A human "in the loop" who reviews a weekly digest of decisions already executed is not in the loop. That human is conducting an after-action review, inspecting what has already happened.

The design response is not to make hearings faster. It is to put the governor where the rate is: in the system's permissions, its spending limits, its required confirmations before irreversible actions. Those are engineering choices, and they can be written into procurement contracts and agency policy. Committees can ask for them by name. And for every irreversible action, they can ask who holds the stamp.

Voluntary in name

The NIST AI Risk Management Framework is voluntary. So are most industry safety commitments. But "voluntary" describes the text, not the effect. When a framework is written into procurement requirements, cited by courts as the standard of care, or demanded by insurers, it becomes mandatory in effect. When a mandatory requirement carries no audit, no consequence and no published compliance record, it becomes voluntary in effect.

The test is the same in both directions: follow the instrument to the point where someone bears a cost for ignoring it. If no one does, it is guidance, whatever the cover page says.

This matters for M-25-21 directly. Its discontinue clause is mandatory in text. Whether it holds in practice depends on whether anyone outside the agency can see which high-impact systems were found noncompliant, and whether any were actually switched off. A committee can ask that question with a single letter.

The Petrov clause

In September 1983, Stanislav Petrov, a Soviet duty officer, watched an early-warning system report incoming American missiles. He judged it a false alarm and did not pass it up the chain as an attack. He was right. The system had a human in the loop, and at the moment of action the human held.

Petrov's case is usually told as a story about courage. For a committee, it is better read as a design specification. Three things had to be true for his refusal to count. He had to be positioned before the irreversible step, not after it. He had to have enough time and information to judge. And he had to be able to refuse without the refusal being overridden by procedure.

Every human-oversight provision in AI policy can be held to those three conditions. Is the reviewer placed before the action or after it? Is the reviewer staffed, trained and given the time to actually review, or is one person approving hundreds of outputs a day? Is a refusal protected, so that a federal employee who halts a system is backed rather than disciplined? A requirement that fails any of the three is not a stamp, however it is worded. It is an after-action review.

The second condition is already failing. In remote sensing, a classifier that maps forest cover from satellite imagery is only as good as its ground truth: field plots where a person walked in, measured the stand and recorded what was actually there. Without those plots the map still looks finished. It is simply unverified. Every Petrov clause assumes a reviewer with that kind of field knowledge and the time to use it.

In October 2026, USDA's IT program manager told a Washington panel, of keeping people overseeing AI work: "I think that's untenable in our industry or in government — we just don't have the resources anymore." That is the second condition conceded in public, before anyone has tested the first or the third.

I managed geospatial work for the Forest Service's Northern Region, 25 million acres across Montana, Idaho and the Dakotas. An oversight framework that requires human review without staffing the reviewers has a stamp on paper and no one to hold it. Committees overseeing AI deployment should also oversee the workforce that has to check it.

The question is not whether a document names someone who may refuse. It is whether that refusal holds load at the moment the system acts.

The first 90 days

None of this requires new legislation to begin. A committee with oversight jurisdiction can start with four requests.

Ask for the discontinue ledger. Request from each major agency its inventory of high-impact AI under M-25-21, which systems were found noncompliant, and which were actually discontinued. The memo's compliance deadlines have passed, so the answers should already exist. A clause that has never been exercised has not yet been shown to hold load.

Ask where the human sits. For each high-impact system, ask whether human review happens before the AI-driven decision takes effect or after. Ask how many decisions each reviewer handles per day. The answers sort stamps from after-action reviews faster than any policy document.

Ask what protects a refusal. Ask whether any agency has written guidance protecting an employee who halts an AI system in good faith. If none exists, that is the cheapest way to make a stamp real: one paragraph of policy.

Put the verification workforce in the same frame. When an agency reports AI adoption, ask in the same hearing what has happened to the field and technical staff who would catch its errors. Adoption and verification capacity should be reported together, because one is meaningless without the other.

Any preemption bill can then be read through the same test. If it removes state governors, what replaces them: a federal governor, a stamp, or only an after-action review?

The throttle

The ridges above Leading Creek are bare this week, and with the leaves down you can see how the hillside is actually built. Oversight is the same. Strip away the vocabulary of frameworks and principles, and the structure underneath is simple: at some point between a request and a result in the world, either someone can stop the machine or no one can. The new committees will decide where that point sits. They should decide it on purpose.

---

Sources

• OMB M-25-21, Accelerating Federal Use of AI through Innovation, Governance, and Public Trust (govinfo)
• Akin Gump summary of M-25-21
• White & Case on Executive Order 14365
• Global Policy Watch on the Great American AI Act draft
• Washington Examiner on the stand-alone audit bill
• Tech Times on USDA and human oversight of AI
• Forkast on the M-25-21 deadline

---

Layers of the Machine

What AI, language models, and the application actually do — and where human judgment still has to sit

Nov 5, 2026 - Samuel R. Lammie, with Claude (Anthropic)                                                                                          

                                                               "Three Layers of the Machine"  

Disclosure: one co-author of this post is a large language model built by a company that profits from AI adoption. Read "The black box" with that in mind.

Two words doing too much work

When I made a small investment in Teknowledge in the mid-1980s, at the height of the expert-systems boom, "artificial intelligence" meant hand-written if-then rules captured from human specialists. Today the same two words cover a satellite-imagery classifier, a chatbot, and an agent that can search, calculate, and act across several programs. The vocabulary has flattened distinctions that matter.

Three layers are worth keeping apart. The first (1) is the field: artificial intelligence, the whole discipline. The second (2) is the model: a large language model, one kind of AI among many. The third (3) is the application: the model wrapped with an interface and tools so people can actually use it. In the plate at the end, the field is the outer frame, the application sits inside it, and the model is the core. Most confusion about these systems, and most misplaced trust in them, comes from treating the three as one thing.

Layer one: the field

Artificial intelligence is the broad discipline of building computer systems that do things we associate with human intelligence: recognizing patterns, interpreting language, solving problems, planning, deciding. Some systems follow explicit rules. Others learn statistical patterns from examples.

The family is older and wider than the current conversation suggests. Rule-based and expert systems apply rules people wrote, the way a screening tool flags a permit application when specified conditions are met. Traditional machine learning learns from data to classify or predict, the way a model estimates wildfire susceptibility from terrain, vegetation, and weather. Computer vision reads images, picking roads, forest cover, or damaged buildings out of satellite scenes. Speech systems transcribe a meeting or read text aloud. Reinforcement learning develops strategy through trial, action, and reward. Robotics joins perception, planning, and physical motion. Generative AI, the newest branch in public view, produces text, images, audio, video, and code.

These categories overlap. Some describe how a system learns; others describe what it does. Neural networks sit underneath many of them, but not all: decision trees, rules, and plain statistics still carry a great deal of working AI. 

Layer two: the model

A large language model is one kind of AI, trained on vast amounts of text to learn patterns in language and the relationships among the concepts language carries. "Large" refers mainly to the scale of its neural network: billions of learned numerical values, called parameters. Training adjusts those values, over and over, to improve the model's predictions of text. Out of that process come capabilities nobody wrote down as rules: answering questions, summarizing documents, drafting letters, writing code, working through an argument.

When you type a prompt, the model converts your words into numbers and passes them through many layers of computation. It then writes its answer one token at a time, a token being a word, part of a word, or a punctuation mark. Each new token is shaped by your prompt, by whatever else is in the conversation, and by everything the model has already written.

That process can produce real analysis. It can also produce a convincing mistake, delivered in the same even voice.

The black box

Researchers understand how these networks are built and how they are trained. What remains hard is explaining why a particular network produced a particular answer. The learned patterns are spread across enormous numbers of interacting parameters. No single rule can be pointed to, and no single source can be traced. Interpretability research is making real but partial progress at locating some of the machinery; it does not yet let anyone audit an ordinary answer line by line.

A model's account of its own reasoning is the least reliable class of evidence it offers. When you ask a model to explain how it reached an answer, the explanation is itself generated text, produced the same way as the answer. It may be plausible, but it is not a faithful record of the computation. This consequence deserves its own sentence. Fluency is not accuracy, and a confident explanation is not a transparent one.

Layer three: the application

A chat application such as ChatGPT or Claude is the interface, not the model itself. Depending on how it is configured, the application can connect the model to other machinery: web search to retrieve outside sources, document retrieval to find material in files you supply, a calculator or code environment to run the numbers, image and speech capabilities, and connections that let it take actions in other software. The model interprets and writes; the tools fetch, compute, and act.

Each connection extends reach. Each also adds a place to fail. The system can pick a weak source, misread a document, or run the right calculation on the wrong figure, and the finished answer will read just as smoothly either way.

Two more terms round out the vocabulary. A multimodal system handles more than one form of information, discussing a photograph, reading a chart, answering a spoken question. An agent pairs a model with tools and a process for pursuing a goal across several steps: search, read the files, run the analysis, assemble the report. How independently it works depends on its design, its permissions, and who is watching. That last variable is the one worth asking about.

Oversight language tends to blur a distinction here. A governor binds before the action: the agent cannot spend, send, or delete until a person releases it. A gate works after the fact: a log, a review, a correction once the result is already in the world. Much of what is offered as oversight of AI agents is a gate dressed as a governor. The policy says a human is "in the loop," but the agent runs at machine rate and the review runs at document rate, so the human arrives to inspect what has already happened. The test is Stanislav Petrov's. In September 1983 Petrov, a Soviet duty officer, watched an early-warning system report incoming American missiles, judged it a false alarm, and declined to pass it up the chain as an attack. He was right, and the system had left him room to refuse. The question is not whether a document names someone who may refuse, but whether that refusal holds load at the moment the agent acts.

Where the value is

What language models changed is the interface. Ordinary language now works as a way into information and software. People can explain, summarize, draft, compare, organize,and explore at a speed and scale that was not available five years ago.

So the reliability of the whole depends on the task, the evidence, the tools, and the checks someone actually runs. The model can draft the script that delineates a watershed in minutes. It cannot walk the creek, and it does not answer for what gets decided downstream. Use it to extend your reach. Check the claims that carry weight against evidence, verify the arithmetic, and keep the consequential decisions in human hands.

 

“The three layers, and where verification and validation have to sit.”

Samuel R. Lammie, with Claude (Anthropic). Developed from an explainer first drafted with ChatGPT (OpenAI), then restructured and rewritten. Header illustration generated with ChatGPT (OpenAI); closing plate by Claude. Disclosure: Anthropic builds large language models and benefits from their adoption; the caution about a model's account of itself applies to the co-author of this post.

Tapadh leat.