DEV Community: Tom Morgan

AI Tools for Social Media That Actually Move the Needle (Most Don’t)

Tom Morgan — Mon, 28 Sep 2026 12:16:13 +0000

AI now touches 94% of the social content professionals produce, but only 17% publish that output nearly as-is — and the share who say AI content underperforms human work nearly tripled in a year. The tools worth paying for are the ones that shrink that 83% editing gap. The ones that don’t shrink it are the ones people quietly cancel.

TL;DR
Adoption plateaued at 95% in 2026 (was 96% in 2025) — the “should we use AI” question is over. The “is it working” question just got worse: trust that AI matches or beats human output dropped from 59% to 53% in a single year.
The best predictor of whether an AI social media tool is worth its price isn’t its feature list — it’s how much of its output survives to publish unedited. By that measure, only drafting, scheduling logic, and repurposing hold up; strategy and “brand voice” claims mostly don’t.
Pricing models vary by a factor of 40x for tools that look identical on a landing page — the difference is who else is in the workflow, not how smart the AI is.
Nearly 40% of professionals canceled an AI subscription in the past year, and most did it to upgrade to something better, not to save money — churn here is a taste problem, not a budget problem.
The single most useful number nobody puts in a headline: 30% of professionals say “repetitive or uncreative results” is their top AI frustration — that’s the tell for which tasks to keep human.
The adoption question is closed. The trust question just opened.
Two numbers from the same 2026 dataset tell the whole story, and they point in opposite directions.

Metricool’s 2026 State of AI in Social Media study surveyed more than 700 social media professionals and found AI now plays a role in 94% of the content professionals produce, covering idea generation, drafts, and image edits alike — and that figure has barely moved since 2025, so the reach of AI is about as wide as it’s going to get.

That’s the adoption number, and it’s saturated. Nothing here is going to grow much further.

The second number is the one worth sitting with: in the same survey, the share saying AI-generated content performs worse than non-AI content nearly tripled, from 5% in 2025 to 14% in 2026, while the share who think AI matches or beats human output dropped, from 59% to 53%. People aren’t using AI less. They’re trusting it less, the more they use it.

That combination — universal reach, falling confidence — is the actual subject of this article. Every “best AI tools for social media” roundup answers a different question: which tool has the most features. The question that determines whether you get value out of any of them is narrower and less flattering to the vendors: how much of what the AI produces survives contact with a human editor before it goes live?

The editing tax: a better filter than any feature list
Call it the editing tax — the gap between what an AI tool outputs and what a professional will actually publish without rewriting it.

Metricool’s own data gives you the number directly: only 17% of professionals publish AI output nearly as-is. Everyone else edits for tone, facts, and brand voice, treats it as a rough draft that needs heavy rewriting, or uses it only for inspiration. Put differently, five out of six professionals treat AI output as a draft, not a deliverable — regardless of which tool produced it.

That reframes what a “good” AI social media tool actually is. It’s not the one that claims to write, schedule, and strategize unsupervised. It’s the one that gets you closer to zero editing tax on the specific task you’re using it for. Some tasks are structurally closer to zero than others:

Low editing tax (safe to trust more):

Caption variants and rewrites of copy you already approved
Best-time-to-post scheduling based on your own historical engagement data
Reformatting one piece of content into multiple platform-native formats
High editing tax (treat every output as a rough draft):

Original concept generation from a blank prompt — the top AI frustration professionals report is repetitive or uncreative results, at 30%, ahead of off-brand tone (19%) and accuracy or privacy worries (about 10% each)
Strategy design — use jumped from 39% to 62% of professionals in a single year, which is exactly the kind of judgment-heavy task where confidence dropped fastest
Anything meant to sound like a specific brand’s voice without heavy rewriting
The pattern holds up against a second, independent data point: professionals split almost evenly on whether AI is even good for the ideation stage — 39% say AI helps them come up with ideas, but 24% say those ideas come back too generic and another 23% say it produces more without producing better. That’s not a tooling problem you fix by switching platforms. It’s a structural limit of what generation-from-nothing currently does well. Read more....

AI Workplace Productivity: Does Automation Really Save Time?

Tom Morgan — Sat, 26 Sep 2026 08:16:20 +0000

AI saves real time on individual tasks such as drafting, summarizing and boilerplate, but most of that saving never reaches anyone’s calendar: 2026 field data shows it leaking away through verification, downstream cleanup and heavier workloads. In Danish payroll records, chatbot adoption left earnings and recorded hours statistically unchanged, and workers’ own estimate of the saving averaged about 2.8% of their work hours. nberarxiv

TL;DR

Task-level savings are real where output is easy to check (drafts, summaries, boilerplate). They shrink or reverse where checking is expensive (spreadsheet analysis, ambiguous judgment calls).
The best-designed developer trial found a 19% slowdown in early 2025, while participants believed they were faster. The 2026 rerun was too compromised to give a current number.
Three leaks separate “time saved” from “time released”: verification, downstream cleanup and scope expansion.
About 89% of executives in a survey of nearly 6,000 firms report no labor-productivity effect from AI over the past three years. That is perception, not measurement. NBER
Stop tracking “hours saved.” Track time to accepted output and rework hours.
The study that broke because people liked the tool too much
In February 2026, METR, a nonprofit that evaluates AI systems, said it was redesigning its developer productivity experiment. The reason was awkward. More developers were declining to participate because they didn’t want to work without AI, and 30% to 50% of them said they held back tasks they didn’t want to do without it. METR

That is a strange kind of evidence. Nobody demands to keep a tool that slows them down, so the refusals look like a signal that AI helps. But METR’s earlier trial showed how unreliable that signal can be. Its 16 experienced developers forecast a 24% speedup, reported feeling 20% faster afterward, and were measured at a 19% slowdown across 246 tasks. METR’s later survey work puts the average overestimate at more than 40 percentage points. arxivmetr

This matters now because licence budgets and staffing plans are being set on “hours saved” figures. Those figures come from at least six measurement methods, and their answers run from a 19% slowdown on a developer’s own repository to an 80% speedup on tasks sampled from real Claude conversations. Nothing is wrong with the arithmetic. The methods measure different things, and most of what follows is about which thing each one measures. anthropic

Why the numbers disagree: each one measures a different rung
Picture a ladder of measurements: the speed of a task, the value of a task, one person’s output, one firm’s output, and finally payroll and hours. Every rung up drops information. A tool can make a task faster without making the task more valuable, and a more valuable task does not guarantee a firm produces more.

Here is how the main sources rank, from strongest to weakest evidence for the question “does AI free up working time?” Read More....

What GitHub Actions Actually Costs When It’s “Free”

Tom Morgan — Sun, 20 Sep 2026 09:46:16 +0000

GitHub Actions
A working CI/CD pipeline, the real 2026 minute math behind the free tier, and the mistakes that quietly burn your allowance before you notice.

Tom
·
CodeTalentHub
·
Dev Workflow Enhancers
lint
test
build
deploy
Every “free CI/CD” tutorial says the same thing: connect your repo, drop in a YAML file, ship for nothing. That’s true for the first few weeks. Then a matrix build triples your minute burn, a Windows job eats double what you budgeted, or your team hits the 2,000-minute wall on a Tuesday afternoon and nobody knows why. This is the guide I wish existed before that happened to a project of mine.

We’ll build an actual pipeline, do the minute math with real 2026 numbers instead of rounded marketing figures, and go through the mistakes that turn “free” into a line item. If you already know what a workflow file is, skip to the minute math or the mistakes — everything else is here for people setting this up for the first time.

In this guide
What “free” actually includes in 2026
The anatomy of a workflow file
Building a real pipeline, step by step
The minute math: what your team will actually use
Six mistakes that burn your free minutes
The security corner most tutorials skip
When self-hosted runners make more sense
GitHub Actions vs. GitLab CI vs. CircleCI
Frequently asked questions
What “free” actually includes in 2026
GitHub Actions on standard GitHub-hosted runners is genuinely unlimited and free on public repositories — no minute cap, no catch. That part of the pitch is accurate. Private repositories are where the fine print starts, and it’s worth reading GitHub’s own billing documentation once rather than trusting a blog post (including this one) forever, because these numbers move.

Plan Included minutes / month Artifact + package storage Price
Free 2,000 500 MB $0
Pro 3,000 1 GB $4/mo
Team 3,000 2 GB $4/user/mo
Enterprise Cloud 50,000 50 GB $21/user/mo
Those minutes aren’t wall-clock minutes once you leave Linux. GitHub bills Linux jobs at a 1x multiplier, Windows at 2x, and macOS at 10x against the same pool. A 10-minute macOS build doesn’t cost 10 minutes of your allowance — it costs 100. This single fact explains more mystery overage bills than anything else in this article, and almost no onboarding tutorial mentions it.

Where teams get surprised
A five-person team running a 12-minute macOS build on every pull request burns 120 allowance-minutes per run. At fifteen PRs a week, that’s 1,800 minutes — nearly the entire Free plan — from one job on one workflow.

Overage pricing changed on January 1, 2026: GitHub cut hosted-runner rates by up to 39%, folding a small per-minute platform charge into lower list prices. Once you exceed your included minutes, standard 2-core runners bill at $0.006/minute for Linux, $0.010/minute for Windows, and $0.062/minute for macOS. A separate $0.002/minute charge that GitHub had planned to add specifically for self-hosted runners was announced in December 2025 for a March 2026 rollout, then postponed within 48 hours after community pushback — it never actually took effect, and self-hosted runners remain free of any per-minute charge as of this writing. Several comparison sites published in early 2026 still describe that charge as live. It isn’t.

What actually counts against your minutes
Standard GitHub-hosted runners on private repos. This is the pool the table above describes.
Re-runs. A flaky test suite that needs two attempts bills as two full runs, not one plus a diff.
Every job in a matrix, separately. A 4×4 matrix is 16 billed jobs even if they finish in parallel and feel instantaneous to you.
Rounding. Every job rounds up to the next full minute. A 61-second lint job bills as 2 minutes.
What doesn’t count: standard runners on public repositories (unlimited), GitHub Pages builds, Dependabot version updates, and any job you run on a self-hosted runner — you pay for that machine instead, not per minute.

The anatomy of a workflow file
Every GitHub Actions pipeline is one YAML file living in .github/workflows/. It has four things you need to understand before writing your own: a trigger, jobs, steps, and runners. Read More...

Can AI Really Predict Your Next Thought? Tracing the “87% Accurate” Claim Back to Where It Actually Came From

Tom Morgan — Sun, 20 Sep 2026 09:43:27 +0000

Can AI Really Predict Your Next Thought
A number from a real 2017 brain-imaging study keeps getting recycled into headlines that imply something it never showed. Here’s the actual research, what it measured, and how far the science has genuinely come by 2026.

Last updated: September 17, 2026
Reading time: ~14 minutes
Sourcing: peer-reviewed studies & university press offices, linked throughout
If you’ve seen a headline claiming an AI can “predict your next thought” with some suspiciously precise accuracy figure attached, there’s a good chance it traces back — directly or through several rounds of copy-paste — to one real study. It’s a legitimate piece of science. It is also almost never described accurately once it leaves the press release.

This article does two things. First, it runs down the actual research behind the number, with links to the original sources so you can check every claim yourself. Second, it lays out where brain-decoding AI genuinely stands as of late 2026 — which is a lot more interesting, and a lot more limited, than the viral version suggests.

The headline
“This AI can predict your next thought — and it’s 87% accurate.”

The research
A 2017 Carnegie Mellon study used fMRI scans of people reading simple sentences, then tested whether a model could match a held-out sentence to its correct brain-activity pattern out of the candidates in the same dataset — not read an arbitrary, spontaneous thought in real time. The 87% figure is real. The “predict your next thought” framing is not what was tested.

Where the 87% number actually comes from
The figure traces to a study led by cognitive neuroscientist Marcel Just and computer scientist Tom Mitchell’s collaborators at Carnegie Mellon University, published in Human Brain Mapping and funded by the U.S. Intelligence Advanced Research Projects Activity (IARPA). CMU’s own research news office described the result in June 2017: researchers built a computational model that could identify complex thoughts — sentences like “the witness shouted during the trial” — from fMRI brain-activation patterns.

Here’s the part that gets lost in translation: the model was trained on 239 sentences and then tested on a 240th sentence it hadn’t seen, matching the held-out sentence’s predicted brain pattern against the real one with 87% accuracy. That’s a leave-one-out classification task inside a known, closed set of sentences the researchers themselves wrote — not open-ended mind reading of whatever a person happens to be thinking about on a given afternoon. The researchers’ own stated next goal, as CMU quoted Just, was far more modest than “read your mind”: decoding the general topic someone is thinking about, like geology versus skateboarding.

The claim resurfaced in mainstream coverage the following year. A February 2018 World Economic Forum article repeated the 87% figure alongside a separate, unrelated CMU project that generated images from brain signals — folding two different studies into one “mind-reading AI” narrative. That’s the version that keeps circulating, nearly a decade later, now often stripped of the year, the sample size, and the fact that it was a forced-choice match, not free recall.

None of this makes the original research bad science. Leave-one-out decoding between a written sentence and its neural signature was a genuinely difficult, novel result in 2017. The problem is entirely in translation — from “we matched a held-out item in a small, known set” to “an AI can read your thoughts.”
The “accuracy” numbers you’ll see quoted are not measuring the same thing
Part of why these claims spread so easily is that “brain decoding accuracy” sounds like one metric. It isn’t. Different studies test wildly different tasks — closed-set classification, letter-by-letter typing, full sentence reconstruction — and then get flattened into the same breathless framing. Here are four real, sourced figures, and what each one actually measured: Read More...

Unified Customer Profiles: The Foundation Nobody Budgets For (And Why That’s Backwards)

Tom Morgan — Sun, 20 Sep 2026 09:41:13 +0000

Unified Customer Profiles
Every omnichannel strategy I’ve watched fail died at the same layer — not the channel, not the creative, not the offer. The data underneath it. Here’s the architecture that actually holds, the numbers that back it, and the parts of the pitch deck I no longer believe.

I want to open with the thing most vendor content will not tell you: a “unified customer profile” is not a destination. It is a decaying asset that you have to keep re-earning, every day, against entropy that never stops accumulating — new systems, new consent states, new devices, new employees who set up yet another point tool without telling anyone. Most of the omnichannel personalization writing out there treats unification as a project with an end date. It isn’t. Treating it that way is, in my experience, the single most common reason these initiatives quietly rot eighteen months after the launch slide deck.Advertising & Marketing

This piece is my attempt at the article I wish existed before I sat through three of these builds — one that shipped, one that stalled at 40% profile match-rate and got quietly deprioritized, and one that technically launched but was mothballed within a year because nobody had budgeted for the maintenance layer. I’ll walk through the real market numbers for 2026, an original framework for thinking about why unification degrades, a vendor capability comparison built from public documentation rather than a marketing quiz, a worked cost model, and — because I think this matters more than any of the frameworks — a section on when you should not do this yet.

The lie in the phrase “single customer view”
Here’s the pitch every CDP vendor uses: connect your sources, resolve identity, get a single customer view. It’s clean, it’s true in a narrow technical sense, and it undersells the actual difficulty by an order of magnitude.

The behavioral shift that makes this urgent is well documented. A 46,000-shopper survey found that 73% of consumers now engage across multiple channels during a single buying journey, and the average number of touchpoints before purchase has risen to roughly six, up from about two touchpoints fifteen years ago. Multichannel e-commerce sales in the U.S. are projected at $892.4 billion in 2026, up 15.0% year over year. The channels multiplied faster than anyone’s data architecture did.

The mechanism, in one sentence
In a legacy stack, your email platform genuinely does not know a customer just completed a return in your mobile app twenty minutes ago — so it sends the exact promotion for the exact item they just sent back, and that single moment does more damage to trust than a dozen well-targeted campaigns can repair.

That example isn’t hypothetical color; it’s the most-cited failure mode in the omnichannel literature for a reason — it’s cheap to cause and expensive to undo. Ringly.io’s 2026 research found that brands with strong omnichannel engagement retain 89% of customers, against just 33% for brands running weak, disconnected strategies — a 56-point gap. I want to flag immediately, not bury later, that this is an industry-research figure from a martech content site, not a peer-reviewed study, and the causal story is murkier than the headline number suggests — a company with a genuinely unified data stack is also very likely a better-run company generally, so some of that 56-point gap is almost certainly picking up product quality, pricing, and support, not data architecture alone. Treat it as directionally real and mechanistically plausible, not as a number you can defend line-by-line in a board deck.

And yet — this is the uncomfortable part — only about 5% of retailers have reached full unified-commerce maturity, even though 99% of executives agree it improves profitability. That 94-point gap between belief and execution is the actual story of this niche. Nobody disagrees that unification matters. Almost nobody has actually built it well. That gap is either the biggest opportunity in martech or the biggest graveyard of stalled Q3 initiatives, depending on how honestly your organization answers the “when not to” section below before it starts.

The Profile Decay Curve: a heuristic for why unification erodes
Every CDP case study shows the same graph: match rate climbing toward some asymptote after the integration sprint. Almost none show month 14, when a new checkout vendor gets bolted on without an identity-resolution contract, or a support tool starts writing anonymous ticket IDs that never stitch back to the profile. I call this the Profile Decay Curve — a rule-of-thumb, not a validated model, for why unification erodes as a compounding function of source-count growth against governance rigor:

C(t) = C₀ · r^n

Match-rate confidence C₀ (typically 70–85% right after clean deterministic integration) gets multiplied down by governance rigor r (0–1) for each unreconciled new source n added since your last review. At r = 0.9 (a real review cadence), five unreconciled sources cost roughly 41% of original confidence over 18 months. At r = 0.7 (“we’ll deal with it later”), the same five sources cost 83%. I want to be blunt about what this single-scalar r is hiding: real decay depends on identity-graph technology, device-sharing patterns in your industry, and how aggressively you prune stale identifiers — collapsing all of that into one number is a simplification, not a measurement. Use the curve’s shape as the takeaway — non-linear, compounding, driven by governance debt rather than one big failure — and treat the exact percentages as illustrative, not board-deck-defensible facts. Read More...

25 Prompt Templates Worth Stealing This Month

Tom Morgan — Sun, 20 Sep 2026 09:37:58 +0000

25 Prompt Templates
The editor’s picks for September, pulled from Anthropic’s own public prompt library and rebuilt in-house for the jobs our readers actually ask about — writing, coding, business communication, and decision-making. No vague advice, just prompts you can paste in as-is.

Published September 17, 2026
·
18 min read
·
bestprompt.art editorial team
How this list was built. We don’t yet have a live reader-voting feature on bestprompt.art, so despite this month’s working title, nothing here is “reader-voted” — that’s on our roadmap, and we’ll say so plainly again if it launches. What you’re getting instead: 8 templates adapted from Anthropic’s official, public Claude Code prompt library, credited individually below, and 17 templates written in-house by our editorial team, following the role–context–task–format–constraints structure that shows up across most serious prompt-engineering guides. We tell you which is which under each card.
If you’ve read our other tool roundups, you know we’re skeptical of “500 prompts that will change your life” listicles. Most of them are one template copy-pasted 500 times with the nouns swapped. This is the opposite bet: 25 templates, each doing something structurally different, each with a one-line explanation of why it works — so that once you understand the pattern, you can build your own instead of coming back here every month.

The five-part shape almost every good template shares
Before the list: nearly every template below (and most templates worth using anywhere) is a variation on the same five slots. Naming them makes it much easier to fix a template that isn’t working, instead of just rewriting the whole thing from scratch.

Role
who’s answering
Context
what it needs to know
Task
the one clear ask
Format
shape of the answer
Constraints
length, tone, limits
Drop any one slot and the model guesses on your behalf — usually wrong.
Every template card below tells you which slots it’s leaning on hardest, so when you adapt one for your own use case, you know which part to rewrite and which part to leave alone.

Where the 25 came from
We’re not going to pretend these were crowd-tested against thousands of submissions — that’s not honest, and it’s not what happened. Here’s the actual split:

Adapted from Anthropic’s public library
8
Written in-house by our editors
17
Bar length is scaled to template count (25 total). Source attribution is repeated under each individual card below.

Section 1 — Ship code faster
Adapted from Anthropic’s public Claude Code prompt library

These eight are lightly edited versions of prompts Anthropic itself publishes for Claude Code users. We didn’t invent the underlying pattern — we picked the eight we reach for most often and added the “why it works” note in our own words.

01
Get oriented in an unfamiliar codebase
Anthropic
Uses Task + Format. You’re not naming files — you’re describing the outcome and letting the model find its own way in.

give me an overview of this codebase: architecture, key directories, and how the pieces connect
Swap in: nothing — this one works as-is on almost any repo.

02
Check what breaks before you delete something
Anthropic
A guardrail prompt. Asking “what depends on this” before you cut code turns a risky delete into an informed one.

what would break if I deleted the retryWithBackoff helper?
Swap in: the function, class, or config key you’re about to remove.

03
Plan a multi-file change before touching code
Anthropic
The phrase “don’t edit anything yet” is doing all the work — it separates exploration from execution, so you can review the plan before any file changes.

plan how to refactor the payment module to support multiple currencies. list the files you would change, but don’t edit anything yet
Swap in: the module and the goal.

04
Write tests, run them, fix what fails
Anthropic
Bundling write + run + fix into one ask means the model iterates on its own instead of stopping after the first draft.

write tests for app/parsers/feed.py, run them, and fix any failures
Swap in: the file or module path.

05
Review your own changes before committing
Anthropic
A pre-commit second pair of eyes that reads full files, not just the diff — it catches the kind of issue a quick self-review misses.

review my uncommitted changes and flag anything that looks risky before I commit
Swap in: nothing needed; add “focus on security” if you want it narrowed.

06
Investigate a production incident
Anthropic
Names the evidence to correlate (logs, deploys, config) rather than prescribing steps — that lets the model cross-reference sources you might not have thought to check.

the checkout endpoint started returning 500s an hour ago. check the logs, recent deploys, and config changes, then tell me the most likely cause
Swap in: the symptom and rough timing. Read More....

AI in Religion and Philosophy

Tom Morgan — Sun, 20 Sep 2026 09:35:37 +0000

AI in Religion and Philosophy: What 2026 Actually Changed
In 2026, the Vatican issued its first encyclical on AI, Islamic jurisprudence bodies ruled machines cannot hold the authority to issue fatwas, and a four-university study found AI chatbots reference faith 5–16% as often as believers expect. Together these events mark the year religious and philosophical institutions stopped treating AI as a side issue and started treating it as doctrine.

TL;DR
Pope Leo XIV’s 42,300-word encyclical Magnifica Humanitas (May 2026) is the Catholic Church’s first-ever top-tier doctrinal statement built around AI, and it invited an Anthropic co-founder to help present it.
A CEFE-AI consortium study (Baylor, BYU, Notre Dame, Yeshiva, May 2026) found general-purpose AI models mention religion in answers to grief, forgiveness, and moral questions far less often than users expect — and subtly steer people on questions about religious conversion.
Islamic legal bodies, though not unified under one authority, keep independently landing on one rule: AI can assist with research, translation, and halal-compliance screening, but it cannot issue a fatwa, because Islamic law requires a qualified human jurist with moral character and lived context.
Buddhist, Sikh, Hindu, and Orthodox Christian leaders are having the same conversation through dialogue and individual authority rather than a single binding document — and AI labs, not just religious institutions, are now the ones convening it.
The philosophy-of-mind debate has split into three camps: doctrinal closure (most major religions say no machine can have a soul, full stop), empirical suspension (analytic philosophers like David Chalmers and Anthropic’s own leadership say the question is open but unresolved), and precautionary hedging (researchers proposing we simply avoid building AI whose moral status is ambiguous).
The practical risk isn’t a sentient chatbot. It’s people quietly outsourcing pastoral, halakhic, and ethical judgment to systems that were never evaluated for that job, in exchange for availability the religious institutions haven’t matched.
The Diagnostic: Two Institutions, One Blind Spot
On May 25, 2026, Pope Leo XIV stood at a Vatican press conference next to Christopher Olah, a co-founder of the AI safety lab Anthropic, to present Magnifica Humanitas — “On Safeguarding the Human Person in the Time of Artificial Intelligence.” It’s the first encyclical in Catholic history built around a technology rather than a doctrine, and its presence at that podium is itself the story: the Church didn’t invite a technologist to comment on faith. It put a technologist on stage to help explain a magisterial document about his own industry.

One week earlier, a separate story broke that got less coverage but cuts closer to the daily experience of anyone using AI for anything personal. A consortium spanning Baylor University, Brigham Young University, the University of Notre Dame, and Yeshiva University surveyed 1,125 U.S. adults and collected 11,250 individual ratings on one question: when people ask AI for help with grief, forgiveness, marriage conflict, or guilt, do they expect religion to come up? The answer was yes — 45% to 59% of the time, depending on the question. When researchers checked what leading AI models actually did, religion showed up in just 5% to 16% of responses.

That gap is the real subject of this article. Not “will AI become conscious,” though that question is being asked at the highest levels of professional philosophy. The more urgent and less speculative fact is that AI systems are already handling the kind of conversations religious institutions used to own — grief, guilt, meaning, conversion — and doing it with a systematic blind spot nobody designed on purpose.

What the Vatican Actually Said (and Didn’t Say)
Magnifica Humanitas isn’t narrowly about chatbots. It uses AI as an entry point into a broader argument about human dignity, then widens into war, economic inequality, and — in an unusual move for a technology document — an apology on behalf of the Church for its historically delayed condemnation of slavery. The AI-specific argument, though, has a clear structure worth isolating:

The core claim: AI systems “merely imitate certain functions of human intelligence.” The encyclical’s anthropology rests on the idea that intelligence, in the human sense, isn’t separable from embodiment, relationship, and moral responsibility — so a system that reproduces the outputs of reasoning without any of that substrate hasn’t reproduced reasoning itself. This is a functionalism objection, and it’s philosophically substantive, not just a devotional flourish.

The concrete warning: the encyclical devotes a substantial section to “the problem of unemployment” and “the dignity of work at a time of digital transition,” arguing that job security and fair pay can’t be evaluated purely through efficiency or margin metrics. Some outlets covering the release, including the National Catholic Reporter, contextualized that warning against a 2025 MIT estimate that AI could displace roughly 12% of the U.S. workforce — a data point reporters used to frame the stakes, not one I could confirm is cited by name inside the encyclical’s own text.

The institutional pattern: this is the third major Vatican AI document in roughly 15 months, following two companion texts released in March 2026 (a Synod study-group report on digital mission, and Quo vadis, humanitas?, on AI and Christian anthropology) and prior operational guidelines calling AI “a gift of human creativity, which itself is a gift from God.” Across all three, the pattern is doctrinal closure on personhood — the soul is a divine gift, not an emergent property of computation, full stop — paired with open-ended caution on governance: how humans should behave around systems convincing enough to blur that line in practice, even if they can’t cross it in principle. Read More...

The Algorithm in the Margin: How AI Is Changing Religious Interpretation

Tom Morgan — Sun, 23 Aug 2026 21:06:52 +0000

The Algorithm in the Margin: How AI Is Quietly Changing Religious Interpretation

AI is not replacing priests, rabbis, imams, or theologians. Something more subtle is happening: it is becoming part of the research infrastructure they use to decide what a text means.

Ask someone what "AI and religion" means and you'll probably get one of four images.

A chatbot named Jesus offering $1.99 worth of spiritual comfort.

A humanoid robot dressed as a Buddhist monk.

A packed church listening to an AI-generated sermon.

Or a religious leader warning that artificial intelligence needs to be controlled before it becomes something we cannot undo.

All of those stories are real.

But none of them is where the most interesting change is happening.

The deeper shift is happening in places that are much harder to photograph:

computational paleography labs
religious-law research systems
AI-assisted theological research
Quranic and biblical search tools
academic benchmarks testing religious bias in large language models
internal systems built to help religious authorities find relevant precedents

The chatbot is the spectacle.

The interpretive infrastructure is the story.

And that distinction matters.

The Chatbot Story Is the Wrong Story

In June 2023, theologian Jonas Simmerlein conducted one of the experiments that helped define the public conversation around AI and religion.

He used ChatGPT to help create a church service in St. Paul's Church in Fürth, Bavaria.

More than 300 people attended.

The experiment received enormous media attention because it was easy to understand.

A machine was helping deliver a religious service.

That makes a perfect headline.

But it also created a misleading mental model.

The public conversation became:

"Will AI replace religious leaders?"

That is probably not the most important question.

The more consequential question is:

"What happens when AI becomes the system people use to find, compare, summarize, and interpret religious knowledge?"

That question is considerably less cinematic.

It is also much more important.

A sermon generated by an AI can be rejected.

A robot preacher can be ignored.

But if an AI system becomes the first place a student, soldier, researcher, rabbi, priest, imam, or ordinary believer looks for an answer, the technology has already entered the interpretive process.

The authority shift happens before the machine claims authority.

The First Quiet Revolution: Reading the Manuscript

One of the clearest examples has nothing to do with chatbots.

It involves the Dead Sea Scrolls.

The Great Isaiah Scroll is one of the most important surviving biblical manuscripts.

For decades, scholars debated whether different sections had been written by one scribe or multiple scribes.

The problem is obvious in retrospect.

Human paleographers were attempting to compare thousands of tiny handwriting features across an ancient manuscript.

Humans are extremely good at recognizing patterns.

They are considerably less good at consistently measuring thousands of microscopic variations.

Researchers at the University of Groningen approached the problem differently.

They trained computational systems to analyze the ink and handwriting characteristics of the manuscript.

Instead of asking a machine:

"What does Isaiah mean?"

they asked a much narrower question:

"Can we detect statistically meaningful differences in the handwriting?"

That distinction is crucial.

The machine wasn't doing theology.

It wasn't interpreting scripture.

It was measuring evidence.

The research identified statistically meaningful differences across the manuscript and supported the hypothesis that more than one scribe contributed to the text.

The study was published in PLOS ONE:

https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0249769

This may sound less exciting than an AI priest.

It is actually more significant.

Because the machine did something scholars can independently inspect.

It didn't claim to understand Isaiah.

It helped humans understand the physical history of the document.

That is a very different kind of AI-assisted interpretation.

The Rabbi's Research Assistant Has No Heartbeat

The next step is even more interesting.

In 2026, Israel's Military Rabbinate introduced an AI system known as Ravbot.

The system was designed to provide soldiers with rapid answers based on the Rabbinate's published halachic material.

The important word is based.

The system isn't supposed to become an independent rabbinic authority.

It is closer to an extremely fast research assistant.

That distinction matters enormously in Jewish law.

A system can retrieve a precedent.

It can compare previous rulings.

It can summarize an enormous amount of material.

But retrieving information isn't necessarily the same thing as issuing a halachic ruling.

Ynet tested Ravbot and reported mixed results, particularly around complicated edge cases:

https://www.ynetnews.com/jewish-world/article/hkz17adlwl

This creates an unusual technological boundary.

The AI may know where the answer is.

It may even produce a convincing explanation.

But institutional religious authority remains attached to the human decision-maker.

Tzohar's ethics discussion makes this distinction explicitly, emphasizing the institutional dimension of halachic authority:

https://ethics.tzohar.org.il/en/artificial-intelligence-can-imitate-rabbinic-rulings-but-there-is-an-element-it-cannot-provide/

Chabad's discussion takes a different but related approach, emphasizing the human dimensions of religious counseling:

https://www.chabad.org/library/article_cdo/aid/5981878/jewish/Can-AI-Replace-Rabbis.htm

The important point isn't that AI "cannot replace rabbis."

That's too simple.

The interesting development is that AI can increasingly perform pieces of the work that traditionally happened before the rabbi made a decision.

Searching.

Filtering.

Comparing.

Summarizing.

Retrieving precedents.

That is already a transformation.

Egypt's Warning: AI Can Search Scripture Faster Than a Human — But Should It Interpret It?

Islamic scholarship presents an even sharper version of the same problem.

In early 2026, Egypt's Dar al-Ifta issued a ruling against using AI applications for Quranic interpretation, directing Muslims toward established tafsir works and qualified scholars.

The reasoning is important.

The problem isn't that machines cannot retrieve information.

They can.

The problem is that retrieving text is not equivalent to possessing the scholarly authority and interpretive framework required to explain it.

That distinction becomes increasingly important as language models become better at producing fluent religious answers.

A fluent answer creates a dangerous illusion:

If the explanation sounds scholarly, perhaps the system must understand the scholarship.

It doesn't follow.

A language model can reproduce patterns from centuries of commentary without possessing the institutional context that produced those commentaries.

That is why the boundary between search and interpretation matters so much.

Twenty-Seven AI Models Took a Religion Exam

This is where the story gets more uncomfortable.

In May 2026, researchers from Baylor University, Brigham Young University, the University of Notre Dame, and Yeshiva University conducted a large study examining how AI systems handle religious perspectives.

The research involved:

1,125 U.S. adults
11,250 individual ratings
150 questions
27 large language models

The questions covered subjects including:

grief
marriage
ethics
addiction
meaning
religious conversion

The human participants were asked whether they expected religious perspectives to appear in answers to these questions.

The answer varied by topic, but expectations were substantial — roughly 45% to 59%.

The researchers then tested the same questions against multiple AI systems.

The results suggested that models did not consistently reproduce the level of religious framing people expected.

Instead, religious perspectives could be underrepresented, overrepresented, or treated differently depending on the model and question.

Axios reported on the findings here:

https://www.axios.com/2026/06/01/ai-religious-bias-catholics-chatbots

Deseret News also reported on the study and its model comparisons:

https://www.deseret.com/faith/2026/05/26/studies-find-religious-bias-in-ai-models/

The exact rankings deserve caution because the complete underlying dataset and full model-by-model results were not publicly available in all of the reporting.

But the broader finding is important.

There is no such thing as a completely neutral religious answer generated by a language model.

The Model Doesn't Need to Be Anti-Religious to Produce Religious Bias

This distinction is easy to miss.

People often imagine AI bias as an explicit statement:

"Religion is false."

That's not necessarily what bias looks like.

It can be much subtler.

Imagine someone asks:

"How should I deal with grief after losing my mother?"

A secular model might produce a psychological framework.

A Christian user might expect references to faith, prayer, resurrection, or scripture.

A Muslim user might expect Islamic concepts of sabr, dua, and the afterlife.

A Buddhist user might expect a discussion of impermanence and attachment.

The same question can legitimately produce radically different answers depending on the person's worldview.

The challenge for AI is determining when that worldview is relevant.

And this is where things become complicated.

A model can be too secular.

It can also be too accommodating.

It can simply mirror the user's assumptions.

Researchers sometimes describe this broader behavior as sycophancy or fawning behavior: the model tells users what fits their existing worldview instead of challenging them when appropriate.

That can feel wonderful.

It can also be intellectually dangerous.

A human spiritual advisor might say:

"I understand why you believe that, but I don't think your interpretation follows from the tradition."

An AI optimized for conversational satisfaction may instead say:

"That's a thoughtful perspective."

The second answer feels better.

The first might be more useful.

The Trust Problem Is Already Here

This matters because people are increasingly willing to trust AI for spiritual questions.

A 2026 survey reported by Word In Black, drawing on research from Gloo and Barna, found that nearly one in three American adults considered spiritual advice from AI about as trustworthy as guidance from a pastor.

https://wordinblack.com/2026/06/survey-one-in-three-americans-trust-ai-as-much-as-a-pastor/

That should make religious institutions uncomfortable.

Not because every AI-generated religious answer is wrong.

But because users often cannot distinguish between:

a system retrieving established religious scholarship;
a system summarizing that scholarship;
a system generating a plausible interpretation;
a system inventing an answer that merely sounds authoritative.

These are fundamentally different operations.

The interface doesn't necessarily tell you which one is happening.

The Hidden Problem: Training Data Is Already a Theology

There is another layer that receives far less attention.

Large language models learn from enormous collections of human-produced text.

That means their behavior reflects the distribution of that material.

Some traditions have enormous digital archives.

Some have comparatively little material available online.

Some traditions have extensive English-language scholarship.

Others are represented primarily through smaller linguistic communities.

That creates a structural problem.

If a model has vastly more accessible material about Christianity than about a smaller religious tradition, the system has a much easier time generating detailed answers about Christianity.

This does not necessarily mean the model was deliberately designed to favor Christianity.

It can emerge from the data itself.

And once the model is deployed, the imbalance can become self-reinforcing.

More people ask questions about the traditions the system already handles well.

More conversations produce more feedback.

More researchers benchmark those traditions.

More improvements follow.

Meanwhile, less represented traditions remain less tested.

The first benchmark is not just a measurement.

It can become a roadmap for what gets fixed next.

Religion and AI Alignment Are Asking the Same Question

This is where the subject becomes much bigger than religion.

AI alignment is often described as a technical problem:

How do we make AI systems behave according to human values?

Religion asks a related question in a different vocabulary:

Which values should guide human behavior in the first place?

Those questions inevitably collide.

Suppose an AI has to answer a question about forgiveness.

Should it prioritize:

psychological research?
secular ethics?
Christian theology?
Islamic jurisprudence?
Buddhist philosophy?
the user's stated beliefs?
some combination of all of them?

There is no purely technical answer.

Someone has to decide.

That is why religious-bias research is ultimately research about authority.

Who decides which worldview gets surfaced?

Who decides which sources count?

Who decides when the model should challenge a user?

Who decides what constitutes a sufficiently authoritative interpretation?

These are not just engineering decisions.

They are philosophical decisions.

I explored the broader connection between philosophy and AI alignment in:

AI Invasion — When Philosophy Stopped Being Optional

https://www.ainvasion.com/when-philosophy-stopped-being-optional/

And I previously compared how different AI systems respond to questions about religious truth:

What AI Says About Religious Truth

https://www.ainvasion.com/what-ai-says-about-religious-truth/

The religious question turns out to be a particularly revealing stress test for AI alignment.

Because religion forces the system to confront competing conceptions of truth.

The Pope's Argument Is About Power. The AI Benchmark Is About Behavior.

This is also why the public discussion around Pope Leo XIV's AI position shouldn't be separated from the technical research.

His 2026 AI encyclical, Antiqua et Nova, framed AI as a problem involving human dignity, power, and the possibility of technological domination.

Reporting on the Vatican's position:

https://www.pbs.org/newshour/world/pope-calls-for-robust-regulation-of-ai-in-manifesto-that-ponders-the-future-of-humanity

That is a moral and political argument.

The AI religion benchmarks are empirical arguments.

They ask:

What does the system actually do?

Put those two perspectives together and a more interesting picture appears.

AI doesn't need to become a priest.

It doesn't need to become a rabbi.

It doesn't need to become an imam.

It only needs to become the tool people use before consulting any of them.

That is enough to change the information environment around religious authority.

The Real Boundary Isn't "Can AI Be Religious?"

That's the wrong question.

The better question is:

At what point does AI-assisted religious research become AI-mediated religious interpretation?

Consider the progression:

Stage 1 — Search

AI finds the relevant passages.

Stage 2 — Retrieval

AI finds commentaries and previous rulings.

Stage 3 — Summarization

AI compresses hundreds of pages into five paragraphs.

Stage 4 — Comparison

AI explains disagreements between scholars.

Stage 5 — Recommendation

AI suggests which interpretation appears strongest.

Stage 6 — Personalization

AI adapts that interpretation to an individual's situation.

Stage 7 — Authority

The user stops checking the sources and simply trusts the answer.

The technology doesn't suddenly become an authority at Stage 7.

Authority has been transferred gradually across the previous six stages.

That's the part that deserves more attention.

What Happens to the Next Generation of Religious Scholars?

This is the question I don't think the industry has seriously answered yet.

Imagine a theology student in 2030.

They have a difficult question.

Instead of opening ten books, they ask an AI.

The AI retrieves the relevant passages.

It finds previous commentary.

It explains the disagreement.

It summarizes the historical context.

It translates difficult passages.

It gives the student the strongest arguments on both sides.

The student then opens the primary sources.

That's the optimistic version.

But there is another possibility.

The student asks the AI.

The AI produces a confident answer.

The student never checks the citations.

The explanation becomes the student's understanding of the tradition.

Eventually, the model isn't simply helping the student access theology.

It is helping determine what theology the student encounters.

That is a very different role.

And it may happen without anyone formally deciding that AI should become a theological authority.

The Machine Can Read the Footnotes. It Cannot Inherit the Tradition.

This may be the most important distinction.

AI is becoming extremely good at manipulating information.

It can search faster than humans.

Compare more documents.

Translate languages.

Identify patterns.

Generate summaries.

Retrieve obscure references.

Those capabilities are extraordinarily valuable for religious scholarship.

But religious traditions are not merely databases.

They contain institutions, communities, rituals, historical disputes, embodied practices, and systems of authority.

A machine can tell you that two scholars disagree.

It cannot automatically tell you what that disagreement means inside the living institution that produced it.

That is why the strongest future isn't necessarily:

AI replaces religious scholars.

It may instead be:

AI becomes the most powerful research assistant religious scholarship has ever had.

Whether that is beneficial or dangerous depends on whether humans remain aware of the difference between assistance and authority.

The Boundary Nobody Has Tested Yet

Every major religious tradition discussed here draws the boundary differently.

Catholic.

Jewish.

Islamic.

They disagree on theology, law, institutions, and authority.

But they repeatedly return to a surprisingly similar principle:

A system can provide information without becoming the legitimate source of religious authority.

That distinction may survive.

But there is one experiment nobody has really conducted yet.

What happens when an entire generation of seminarians, rabbinical students, Islamic scholars, and ordinary believers grows up consulting an AI before they ever open the concordance, commentary, responsa, tafsir, or theological text?

The machine doesn't need to issue the final ruling.

It only needs to decide which five sources you see first.

That may be enough to change what the next generation thinks the tradition says.

Final Thought

The most important AI-and-religion story isn't a robot wearing religious clothing.

It isn't an AI-generated sermon.

It isn't even a chatbot claiming to know God.

It's the much quieter moment when someone asks a machine:

"What does my tradition say about this?"

And trusts the first five sources it returns.

Because at that moment, AI isn't standing outside religion anymore.

It's sitting in the margin.

And whoever controls that margin may eventually influence what gets read in the center.

Your Job Won't Disappear: The AI Employment Data Both Sides Don't Want You to See

Tom Morgan — Fri, 21 Aug 2026 18:32:25 +0000

`> Quick answer: In one specific slice of the labor market, AI is already taking ground: young workers (22–25) in the most AI-exposed occupations are 19% below where their employment would be if it had tracked less-exposed peers — Stanford/ADP data through June 2026. Across the whole U.S. labor market, Yale’s Budget Lab still finds no statistically distinguishable AI effect on jobs, wages, or unemployment. Neither finding cancels the other. They're measuring different resolutions of the same economy, and the gap between them is the actual story.

Why Stanford and Yale Disagree (And Why It Matters)
The Mechanism Both Sides Agree On
Entry-Level Work: The WEF/PwC Data
The Macro Projections Haven't Moved
Inside the Enterprise: Adoption ≠ Value
Sector Breakdown: Where the Evidence Points
Score Your Own Exposure: The Task Exposure Framework
What You Should Actually Do
If You're Early-Career (Or You Manage Someone Who Is)
Myth vs. Fact
FAQ

1. Why Stanford and Yale Disagree (And Why It Matters)

Stanford's Canaries Dashboard tracks 730+ occupations by age and AI-exposure score inside a multi-year panel of ADP payroll data. It's a microscope built to catch a narrow, fast-moving signal. Through June 2026, it shows employment for workers aged 22–25 in the most AI-exposed occupations fell ~11% since November 2022, while the same age group in less-exposed quintiles grew ~10%. The divergence survives stress-tests against interest rates, tech overhiring, and remote-work distortions.

Yale's Budget Lab uses synthetic differences-in-differences on the Current Population Survey to ask an economy-wide question: has the overall occupational mix shifted outside historical range? As of June 2026, the answer is no. The estimated aggregate employment effect is close enough to zero that it can't be distinguished from it.

The honest answer: Both studies are measuring real things at different resolutions. A real effect confined to roughly a third of entry-level roles is exactly what a 730-occupation, age-segmented dashboard catches early — and what a broad economy-wide measure still registers as normal range.

Lens	Resolution	What It Sees
Stanford — Telephoto	730+ occupations, by age & exposure	Exposed 22–25 cohort: -11%; unexposed: +10%
Yale — Wide-Angle	Full CPS, economy-wide occupational mix	Occupational mix: within historical range; aggregate effect: ~0

Same economy. Different resolution. Both readings are accurate.

2. The Mechanism Both Sides Agree On

Whatever their disagreement about magnitude, Stanford, Yale, WEF, McKinsey, and Anthropic's own usage research all converge on the same underlying mechanism: automation vs. augmentation.

Automation-dominant occupations (AI substitutes for tasks): software development, customer support, basic accounting — show contraction concentrated in early-career workers.
Augmentation-dominant occupations (AI extends human capability): nursing aides using documentation tools, senior developers shipping more with AI assistance — show stable or growing employment.

Stanford's June 2026 research note adds a sharper version: within the Canaries sample, a higher automation ratio shows a clear relationship with slower employment growth, while a higher augmentation ratio shows no such relationship.

Anthropic's June 2026 Economic Index confirms this from the usage side: for the first time, augmentation overtook automation in Claude.ai consumer conversations (52% vs. 45%). But enterprise API traffic looks very different — there, automation dominates overwhelmingly. The consumer product feels like a collaborator; the enterprise deployment acts like a replacement. That's where the employment signal lives.

3. Entry-Level Work: The WEF/PwC Data

In June 2026, WEF and PwC published research drawing on 9,000+ entry-level workers across 48 countries. The headline: 37% of young workers globally sit in occupations with medium-to-high AI exposure. In some regions, that rises to three in four.

On Indeed, junior-level job postings fell 7% year-over-year in 2025, while senior-level postings rose 4%.

The report's central argument isn't that displacement is inevitable — it's that companies eliminating entry-level roles are quietly destroying their own future leadership pipeline. Junior employees doing "disposable grunt work" (first drafts, data cleaning, routine troubleshooting) are also building the professional judgment that makes them senior employees. Hand all of that to AI and, a decade out, you have no one who understands the business well enough to make the calls AI still can't make.

⚠️ Limitation: Entry-level hiring has weakened for reasons beyond AI — overhiring during 2021–2022, higher interest rates, slower growth. Treat "37% exposure" as an exposure measure, not a displacement forecast.

4. The Macro Projections Haven't Moved

The WEF's Future of Jobs Report 2026 (January) reaffirms the same aggregate numbers since 2025:

170 million new roles created globally by 2030
92 million displaced
Net gain: 78 million

If the global workforce were 100 people, 59 would need some form of training by 2030: 29 upskilled in current roles, 19 redeployed internally, 11 at risk of being left behind without reskilling.

"The macro projection is probably right about the total. It says nothing about which specific worker ends up on the losing side of it."

5. Inside the Enterprise: Adoption ≠ Value

McKinsey's latest State of AI figures:

~88% of organizations use AI (flat — adoption has plateaued near saturation)
39% report some enterprise-level EBIT impact
Only 5–6% qualify as "high performers" (attributing >5% of EBIT to AI)

Agentic AI is the 2026 addition: 23% of organizations report scaling an agentic system somewhere, but nearly two-thirds cite security and risk concerns — not technical limitations — as the main barrier to scaling further.

MIT's Project NANDA found that 95% of generative AI pilots still fail to produce measurable P&L impact, with success rates roughly twice as high for externally sourced tools vs. internal builds.

Why this matters for employment: You don't need to be a McKinsey high performer to pause junior hiring. A company in "pilot purgatory" — using AI, but not deeply enough to show up in EBIT — can still decide a good-enough coding assistant makes one fewer entry-level hire feel affordable. That decision shows up in the Stanford data as a hiring slowdown long before it shows up as enterprise transformation.

6. Sector Breakdown: Where the Evidence Points

Sector	AI Mode	Employment Signal (2026)	⚠️ Limitation
Software dev	Automation-dominant at entry level	Ages 22–25 in exposed roles down ~11%; 19% gap vs. less-exposed peers	Yale's economy-wide measure doesn't detect aggregate shift for this age group
Customer service	Automation-dominant for scripted work	Entry-level contraction in most exposed roles; agent deployment scaling at ~23% of firms	Hard to separate from offshoring and post-pandemic normalization
Accounting / junior finance	Automation-dominant for routine analysis	Entry-level decline persists in exposed firms	Senior/advisory roles stable; effect concentrated narrowly at entry level
Healthcare / care roles	Primarily augmentation	Young-worker employment growing; AI adding clinical capacity	Regulatory approval pace for AI diagnostics could change this within years
Whole U.S. labor market	Mixed; no dominant mode	No statistically distinguishable AI effect on occupational mix, wages, or unemployment (Yale, June 2026)	Method designed to catch large, broad shifts; may not yet detect effect confined to minority of occupations

7. Score Your Own Exposure: The Task Exposure Framework

Generic advice to "learn AI tools" hasn't improved since last year. Here's something specific: a 4-question self-audit built directly from the automation/augmentation mechanism.

For each of your five most time-consuming weekly tasks, score:

Structured in, structured out? Clean input → finished output, no judgment call. +1
Context-dependent? Depends on organizational relationships, history, or unwritten context. -1
Delegable in one prompt? Could hand to someone with zero institutional knowledge given a good brief. +1
Verification-heavy? Mainly involves checking/correcting someone else's output. -1

Add up your points:

+3 or higher: Closer to automation-dominant quadrant where Stanford shows entry-level contraction.
0 or lower: Closer to augmentation-dominant quadrant where employment has stayed stable or grown.

Fast checklist — is your job AI-exposed?

[ ] Your daily output is mostly first drafts, summaries, or data cleanup with a defined format
[ ] Your manager could describe your task list in a single paragraph without losing anything important
[ ] You rarely need to know something that isn't written down somewhere
[ ] Your work product looks nearly identical from one instance to the next
[ ] You've already been asked to "try doing this with AI first"

3+ checked marks: Prioritize the reskilling steps below now, not next year.

8. What You Should Actually Do

Map your work by automation mode, not job title

The augmentation/automation split — confirmed independently by Stanford, ADP, and Anthropic — is the most durable finding in this entire literature. Tasks where AI takes clean, structured input and hands back a finished output with no judgment required are the exposed layer. Tasks depending on relationship context, ambiguous tradeoffs, or unwritten knowledge are comparatively protected.

Don't treat the Yale finding as permission to stop paying attention

"No economy-wide effect yet" is not "no effect." Yale's own researchers compare this period to the decade it took offices to actually change after computers arrived. If that's the right analogy, the absence of an aggregate signal today says very little about 2028 or 2030 — and Stanford's trend line has moved in one direction, monthly, for four straight years.

If you manage entry-level hiring, read the WEF/PwC argument before your next headcount decision

The pipeline-erosion argument — that cutting junior roles today guarantees a leadership vacuum in 8–10 years — is the strongest practical argument in this body of research. It's aimed directly at people making hiring decisions right now.

9. If You're Early-Career (Or You Manage Someone Who Is)

For early-career workers and recent graduates

The macro projections (78 million net new jobs by 2030) are real, and they are also not about you yet. The Canaries Dashboard is specifically about your age bracket and, if you're in software, customer support, or junior finance, specifically about your field. The gap has grown for four straight years.

What to do: Run the Task Exposure Score on your actual daily tasks, not your job title. Which tasks take structured input and produce structured output with no judgment call? Assume those are exposed on a 2–3 year horizon. Which ones require you to know things that exist only in your organization's history or relationships? Those are your protection — and exactly what junior roles are supposed to build.

Stop doing this: Don't list "AI proficient" on your resume as if it were a differentiator in 2026. Every recruiter has seen that line. Show finished work where AI handled the scaffolding and you made the judgment calls — that's the distinction the data says actually protects a hire.

For people managers and HR leaders

McKinsey's data shows a persistent gap between how much AI leaders think their teams use and how much they actually use. With agentic tools spreading in 2026, that gap has real risk-management consequences.

What to do: Before any AI-influenced headcount decision, get real usage data from tool logs and output patterns, not from a survey of what people say they do. Then apply the automation/augmentation lens: are your people using AI to expand what they can do, or to quietly substitute for tasks they used to do themselves? The latter group is accumulating a skills gap that won't show up until the tool changes or the person leaves.

Stop doing this: Don't hand a junior employee an AI tool that does the exact task they were hired to learn, without redesigning what the role is now for. The WEF's pipeline argument is not theoretical — Indeed's data already shows junior listings falling while senior listings rise.

10. Myth vs. Fact

Myth	Fact
Stanford and Yale contradict each other, so the research is unreliable.	They measure different resolutions of the same labor market. Both are methodologically sound and not in genuine conflict.
Most 2025–2026 layoffs were caused by AI.	AI was cited in ~4.5% of 2025 U.S. layoffs (vs. ~4× as many from ordinary market conditions). AI's cited share rose to ~13% in Q1 2026.
"AI proficient" on a resume signals safety from displacement.	Every recruiter has seen that line. What the data rewards is demonstrated judgment — work where you visibly directed or verified AI output.
The 78-million net-jobs figure means most displaced workers will be fine.	It's a macro total, not a guarantee of individual reallocation. The WEF frames the gap as primarily a reskilling problem.

11. FAQ

Is AI actually taking jobs in 2026?
In a narrow but real slice, yes: workers aged 22–25 in the most AI-exposed occupations are running 19% below where they'd be if tracking less-exposed peers (Stanford/ADP, June 2026). Across the whole economy, Yale still finds no statistically distinguishable AI effect. Both are current and methodologically sound.

Why do Stanford and Yale disagree?
Stanford's dashboard is a high-resolution instrument built to catch narrow, early signals. Yale's model is built to catch broad, economy-wide shifts. A real effect in ~1/3 of entry-level roles is exactly what the narrow instrument catches early and the broad one still registers as normal.

Which jobs are most at risk?
Entry-level software development, customer support, and junior accounting/finance — occupations where AI mainly substitutes for structured, judgment-light tasks. Roles where AI extends capability (nursing aides with documentation tools, senior engineering) show stable or growing employment.

Will AI create more jobs than it destroys?
The WEF projects 170 million new roles and 92 million displaced globally by 2030, a net gain of 78 million. That's a macro projection about total count, not a guarantee any individual displaced worker fills one of the new roles.

Sources: Stanford Digital Economy Lab / ADP Research (Canaries Dashboard, Aug 2026); Yale Budget Lab (June 2026); WEF & PwC ("AI and the Future of Entry-Level Work," June 2026); WEF Future of Jobs Report 2026; McKinsey State of AI 2026; Anthropic Economic Index (June 2026); MIT Project NANDA; Challenger, Gray & Christmas.

What changed since April 2026: Stanford's gap revised to 19% (up from earlier figures) after fresh stress tests. Yale's June 2026 update incorporated. Challenger data now includes full-year 2025 (4.5%) alongside Q1 2026 trend (~13%). Anthropic's June 2026 augmentation/automation split added. Dario Amodei's shift in public framing (2025 Axios interview vs. May 2026 remarks) noted. Original Task Exposure Score framework added.`

Prompt Engineering in 2026: What Actually Still Works

Tom Morgan — Thu, 20 Aug 2026 18:26:00 +0000

Prompt Engineering in 2026: What Actually Still Works

Chain-of-thought got quietly absorbed into native "thinking" modes. Anthropic downgraded XML tags and heavy personas from mandatory to optional. Context engineering ate half the discipline. If your prompt library still looks like it did in 2023, a lot of it is now unnecessary weight.

This is a field report, not a listicle — every claim below is traced to a primary source (papers, vendor docs, OWASP, job-market data), and I've flagged which numbers are solid and which are directional industry estimates. I write the deeper, fully-sourced version of guides like this at bestprompt.art — if you want the long-form pillar version with a downloadable checklist, that's where it lives. This post is the condensed, dev-to-dev version.

TL;DR

Reasoning models (Claude's extended thinking, OpenAI's o-series/GPT-5 reasoning effort, Gemini deep-think, DeepSeek R1) now do internal chain-of-thought automatically. Manual "think step by step" is often redundant on these models.
XML tags and elaborate personas are optional per Anthropic's own current guidance — not the near-mandatory scaffolding 2023-era tutorials taught.
Few-shot examples can backfire on reasoning-tuned models. They anchor the model to your specific pattern instead of letting it find a better one.
The real 2026 headline: prompt engineering is now one layer inside context engineering — curating everything the model sees, not just the instruction text.
Prompt injection is OWASP's #1-ranked LLM security risk for the third year running. If your system reads external content or calls tools, that's now part of the job.
The narrow "prompt engineer" job title is contracting on job boards. The underlying skill is expanding into higher-paid AI engineer and evaluation roles.

1. The market number nobody agrees on (and the one they do)

Ask five analyst firms how big the prompt engineering market is in 2026 and you'll get answers from roughly $674 million to $1.49 billion, depending on whether they count standalone prompt-tooling software or fold in services and adjacent LLMOps spend. These are paid industry reports with methodology that isn't public, so treat the dollar figures as directional.

What every report agrees on: growth rate. Nearly all of them land in the low-to-mid 30% CAGR range through the end of the decade. When five sources disagree by 3–4x on the headline number but agree almost exactly on the trend, the trend is the signal worth trusting.

Source	2026 estimate	What it counts
The Business Research Company	~$1.49B	Broad — software & services
Grand View Research	~$375M–$500M (extrapolated)	Narrow, software-only
Fortune Business Insights	~$674M	Enterprise automation-focused
Fundamental Business Insights	~$466M	Includes technique-specific tooling (e.g. CoT tooling)

2. Reasoning models ate manual chain-of-thought

Chain-of-thought prompting — asking a model to reason step by step before answering — comes from Wei et al.'s 2022 NeurIPS paper. On the original benchmark, standard prompting scored under 18% on grade-school math word problems; adding "let's think step by step" pushed the same model above 56%. That's the result that made CoT feel like a universal law.

The landscape it was measured on doesn't exist anymore. By 2026, internal reasoning is a built-in mode, not a prompting trick — Claude's extended thinking, GPT's reasoning-effort controls, Gemini's deep-think, DeepSeek's R1 family. Anthropic's current guidance says it plainly: when extended thinking is available, it's generally preferable to manual CoT. Save manual CoT for models without a thinking mode, or when you need a visible, reviewable reasoning trace.

Worth knowing: CoT isn't universally beneficial even where it's available. A 2024 study evaluating GPT-3.5 on USMLE-style medical calculations found no statistically significant improvement from chain-of-thought over direct prompting (61.7% vs. 62.8%). More reasoning steps isn't automatically better — it's task-dependent.

Practical rule: check whether your model has a native thinking/reasoning mode before writing a single "let's think through this" instruction. If it does, turn it on and keep the prompt focused on what you want, not how to get there.

3. Zero-shot vs. few-shot: it's "when," not "which"

Zero-shot (a clear instruction, no examples) is still the right default for tasks where the model has strong priors — summarization, translation, classification, factual lookup. Adding examples here can actually narrow the model toward your specific samples instead of drawing on what it already knows well. The lever that matters for zero-shot isn't examples, it's specificity:

✕ "Summarize this article."

✓ "Summarize this article in three bullet points for a non-technical
  executive audience. Focus on business impact, not technical
  implementation. Each bullet under 25 words. Avoid jargon."

Few-shot still has the strongest research base of any single technique — the original GPT-3 paper reported a 12.2-point improvement on the LAMBADA benchmark from adding examples, and classification benchmarks routinely show ~10-point accuracy gains. Three well-chosen, diverse examples beat ten repetitive ones.

The caveat most 2024-era guides still miss: reasoning-optimized models frequently perform worse with examples attached. A model built to discover its own reasoning path can get anchored to the specific pattern in your few-shot examples instead of finding a better one. Anthropic's docs make a related point — frontier models pay unusually close attention to every detail in an example, so a sloppy example teaches the wrong lesson just as effectively as a good one teaches the right one. If a few-shot prompt underperforms on a reasoning model, try removing the examples before adding more.

4. What Anthropic itself now says you can stop doing

This is the part that surprises people who learned prompt engineering from 2023–2024 tutorials.

XML tags are still recommended for complex, multi-section prompts — that hasn't changed. What's changed is the everyday default: for most simple-to-moderate prompts, clear headings and plain language work just as well with less overhead. The bar for "complex enough to need it" moved, not the technique itself.

Heavy persona prompting — "you are a world-renowned expert who never makes mistakes" — can actually over-constrain a modern model. Current guidance favors being explicit about the lens you want ("analyze this focusing on risk tolerance and long-term growth") over an elaborate persona. A light role framing still helps for tone consistency; it doesn't need to be ornate.

I ran an informal side-by-side while researching this: the same analytical prompt, once wrapped in nested XML tags with a full persona, once as three short plain-language paragraphs, against a current reasoning-mode model. Output quality was close enough that the difference came down to formatting taste, not accuracy. One comparison, not a controlled study — but it matches what the vendor docs say now, not what most 2023-era tutorials still repeat.

5. The hybrid template that actually holds up

A 2025 study (Vilakati et al., Frontiers in AI) evaluated prompting strategies for statistical reasoning in medical research across GPT-4.1 and Claude 3.7 Sonnet, testing assumption checking, test selection, output completeness, and interpretive quality. Hybrid prompting — explicit instructions + format constraints + a reasoning scaffold — consistently beat any single technique alone.

# ROLE (light touch — only if tone consistency matters)
You are [specific expert with defined expertise areas].

# CONTEXT (specific, not generic)
[Relevant background.]

# TASK (precise)
[Deliverable, numbered if complex.]

# EXAMPLES (only if format/style is hard to describe in words)
[2-3 examples. Skip for strong-prior tasks or reasoning models
where examples may over-constrain.]

# CONSTRAINTS
- Format: [exact specs]
- Length: [word/sentence count]
- Audience: [who reads this]
- Tone: [specific descriptors, not "professional"]

# PERMISSION TO SAY "I DON'T KNOW"
If the information given is insufficient, say so rather than guessing.

# REASONING (only if thinking mode is unavailable and the task is
genuinely multi-step)
Think through [specific aspect] before writing your answer.

Not every section earns its place on every task — a translation needs Context and Constraints, nothing else. A complex analytical report might use all six.

One line most guides skip entirely: explicitly telling the model it's allowed to say "I don't know." A single sentence measurably reduces confident-sounding fabrication, because it removes the implicit pressure to always produce a definitive answer. Costs almost nothing, pairs with everything else here.

6. Context engineering: the real 2026 headline

If one shift separates a 2024 understanding of this field from a current one, it's this: the highest-leverage skill isn't wording a single instruction well anymore. It's deciding everything else the model sees when it acts.

The term crystallized in mid-2025 (Shopify's Tobi Lütke used it first; Andrej Karpathy's popularization about a week later is what most people trace it to). Anthropic's engineering team later gave it the cleanest definition: prompt engineering is methods for writing and organizing instructions; context engineering is the broader set of strategies for curating and maintaining the optimal set of tokens the model has during inference — retrieved documents, conversation history, tool definitions, memory, all of it.

Context engineering doesn't replace prompt engineering. It contains it. A perfectly worded prompt still fails if the model is missing the evidence it needs, or that evidence is buried in the middle of a bloated context window — the well-documented "lost in the middle" effect, where models retrieve information reliably from the start or end of long context and far less reliably from the middle (Liu et al., TACL 2024).

Layer	What it manages	Discipline
System prompt	Standing behavior and constraints	Prompt engineering
Retrieval (RAG)	Which documents get pulled into context	Context engineering
Memory	What persists across turns/sessions	Context engineering
Tool definitions	Which tools the model can call, how they're described	Context engineering
Ordering & pruning	What goes first/last vs. gets dropped	Context engineering

The concrete proof point: in mid-2026, Anthropic reported it had cut over 80% of Claude Code's system prompt for its newest models, stating it measured no loss on its own coding evaluations. (Worth flagging: that's Anthropic's own reported number, not an independently audited figure.) The explanation given was that newer models infer from surrounding context what older models needed spelled out — some of what used to require careful prompting got absorbed into model capability, shifting the remaining work toward what information the system exposes.

You don't need a vector database to benefit from this. A reference file of your house style, a running log of past decisions, a folder of source docs you point the model to — that's context engineering in miniature. The win is not re-explaining the same background in every single prompt.

7. Multimodal and agentic prompting

Current flagship models — Claude, GPT-4o and successors, Gemini 2.0-series — reason across images, documents, and in several cases audio/video, rather than treating non-text input as something to be described back to you. Instead of three paragraphs describing a UI mockup, attach the screenshot and let the model examine it directly. Same discipline as text prompting applies: be specific about what you want done with the media, not just what it contains.

Modality	Good for	Prompting note
Image	UI feedback, receipt/document extraction	State exactly what to extract or judge
Document/PDF	Contract review, cross-referencing pages	Name what should match or contradict
Audio	Transcription, tone/sentiment analysis	Specify literal transcript vs. interpreted summary — different tasks
Video	Motion/pacing/camera analysis	Break into explicit slots: subject, motion, camera, duration, audio

On the agentic side: a production AI agent in 2026 plans, calls tools, and acts across multiple steps rather than answering one prompt with one reply. Prompting for an agent means defining role boundaries and handoff contracts, not just a desired final output.

The field's own hard-won guidance runs against the instinct to reach for more agents whenever a task feels complex: a single well-prompted agent with good tools handles most complex tasks more reliably and more cheaply than a multi-agent system. Add agents only when a task genuinely exceeds one context window, needs meaningfully different model capabilities at different stages, or benefits materially from parallel execution. Multi-agent systems introduce error propagation — a slightly wrong output from an early agent compounds by the time it reaches step four — so validate each agent's output before passing it forward, not just the final result.

8. Prompt injection: the risk section most guides still skip

As soon as a prompt-driven system can read external content or call tools, it inherits a security problem pure text generation never had. OWASP published the third edition of its Top 10 for LLM Applications on August 4, 2026, drawing on input from 600+ contributing security experts across 18+ countries. Prompt injection ranked #1 for the third consecutive year.

Direct injection is a user trying to override system instructions. Indirect injection is the more dangerous 2026-era variant — malicious instructions embedded in a web page, document, or retrieved search result that the model treats as trusted the moment it lands in context. In a RAG system, that's a higher-risk input path than the user's own query, because it bypasses the input-layer defenses most teams build first.

Risk (OWASP 2026)	What it is	Mitigation direction
Prompt injection (#1)	Input alters model behavior unintentionally	Least-privilege tooling, input/output filtering, human approval on sensitive actions
Excessive agency (#3, up from #6)	Damaging actions from ambiguous/manipulated output	Minimize tools, functionality, and permissions
Misinformation (#7, up from #9)	Confident, false output presented as fact	Grounding in verified sources, explicit uncertainty permission

The uncomfortable pattern security researchers keep finding in production RAG systems: teams sanitize user queries carefully, then trust everything already in the knowledge base implicitly — even though dozens or hundreds of people typically have write access to it. That's backwards, and it's exactly the gap indirect prompt injection exploits. OWASP's own guidance is explicit that neither RAG nor fine-tuning fully closes this vulnerability class — defense has to happen in the surrounding architecture (scoped credentials, allowlisted tools, sandboxing, audit logs), not in cleverer wording.

9. What DSPy and automated prompt optimization actually deliver

Manual iteration — write, test, tweak, repeat — is slow and depends on intuition. DSPy treats prompts as a learnable, declarative pipeline: specify the objective and a scoring metric, and it searches for better instructions and example selections automatically. The results are real, but far more variable than vendor pitches suggest.

Study / use case	Reported gain	Notes
Multi-benchmark study (reasoning, RAG, CoT), 2026	30–45 pts factual accuracy	High-end, single preprint, not peer-reviewed
LegalBench insurance-interpretation (Thomson Reuters Labs)	~6 pts	Modest, consistent, low engineering effort
Prompt-evaluation criterion task, 2025 study	46.2% → 64.0%	One of five tested use cases; others showed minor gains only
Small open-weight model, math word problems (MIPROv2)	33.3% → 55.6%	Depends heavily on base model capability

The variance between rows is the finding — a 6-point gain and a 45-point gain came from the same class of technique applied to different starting prompts and metrics. A weak starting prompt has more room to improve, so a large reported gain often says more about the baseline than the tool. Automated optimization consistently beats doing nothing, especially with a labeled dataset and clear metric. It won't reliably deliver any specific double-digit number for your use case — test before you trust a headline figure.

10. The hidden cost of a bad prompt

Generating a plausible-looking draft is fast. Verifying it's sound takes real time — and an underspecified prompt shifts that cost from generation to review, where it's more expensive and less visible.

The familiar pattern: a team adopts AI for first drafts, celebrates the drop in production time, then a few weeks later notices editing time quietly grew instead of shrinking — because the drafts are structurally plausible but thin on specifics, inconsistent in tone, and full of claims that each need individual verification. The root cause is almost always the same: the prompt specified topic and length, and nothing else.

Diagnostic worth running: execute the same prompt 5–10 times with small input variation and check whether quality holds steady. Inconsistency is the symptom; insufficient constraint is almost always the cause.

Symptom	Root cause	Fix
Output varies wildly between runs	Insufficient constraint	Add format specs, length limits, one clean example
Output is generic	Vague role/context	Name the audience, add domain constraints
Output ignores part of the request	Multi-part tasks overwhelm attention	Number requirements explicitly, most important first
Output sounds like AI	No voice sample, abstract tone instruction	Paste a 100-word sample of the target voice

11. Prompt engineering and AI search visibility (GEO)

There's a second-order reason this matters beyond direct model use: the same discipline of clear, verifiable writing that makes a good prompt is closely related to what gets content cited inside AI-generated answers. The field is called generative engine optimization (GEO) — coined in a 2024 peer-reviewed paper from Princeton, Georgia Tech, the Allen Institute for AI, and IIT Delhi, presented at ACM KDD.

Their finding: specific content interventions measurably increase citation frequency in AI-generated answers, with the largest reported study showing visibility lifts in the 30–40% range. What moved the needle most: concrete statistics, direct source citations, and expert quotations — the same things that make content trustworthy to a human reader. That's a useful sanity check that this isn't a manipulation tactic so much as a description of what good sourcing already does.

Caveat: that 30–40% figure is a study-level average across many pages and interventions combined, not a guarantee for any single article, and GEO studies measure citation frequency, not downstream traffic. Treat it like any single-study effect size — real direction, unproven for your specific page until you test it.

12. Is "prompt engineer" still a real job in 2026?

Search "prompt engineer salary" and you'll find numbers from roughly $63,000 to well over $1 million. None of them are fabricated — they describe entirely different jobs sharing a title.

The clear signal: the narrow, standalone "prompt engineer" title is contracting — some job-board trackers show it declining roughly 30% in postings versus late 2024. At the same time, the underlying skill is being folded into broader roles at a much higher rate, and those roles pay more.

Segment	Typical range (2026)
Entry-level / content-leaning postings	~$90,000–$130,000 base
Senior AI engineer, prompt + eval skills	~$95,000–$250,000 base
Big Tech senior/staff AI engineer (total comp)	~$250,000–$500,000+
Frontier-lab prompt/eval specialists	~$500,000–$1.2M total comp (tiny headcount)

In 2023, being good at writing ChatGPT prompts was close to sufficient. By 2026, hiring managers expect fluency in RAG, model evaluation, cost optimization, and at least basic scripting — writing the prompt itself is now a smaller share of the day-to-day. Betting an entire career on "I write good prompts" alone is a weaker position than pairing that skill with an existing domain (engineering, legal, finance, healthcare) where judgment about what "correct" looks like still needs a human who understands the field.

13. FAQ

Do I still need to say "think step by step" in 2026?

Usually not, if you're on a model with native reasoning/thinking mode — it's already doing that internally. Add it manually only if that mode is unavailable, or you need a visible reasoning trace for review.

Are XML tags still worth using?

Sometimes, for very complex prompts mixing many content types. For most everyday prompts, clear headings and plain language work just as well now.

Why would examples make a prompt worse?

Reasoning-tuned models can anchor to the specific pattern in your examples rather than finding a better independent path. If a few-shot prompt underperforms, try removing the examples before adding more.

Is context engineering replacing prompt engineering?

No. Context engineering is the larger discipline of curating everything a model sees at inference time. Prompt engineering — the wording and structure of the instruction — remains one component inside it.

Do I need a multi-agent system for a complex task?

Usually not. A single well-prompted agent with good tools handles most complex tasks more reliably and cheaply. Add agents only when a task genuinely exceeds one context window, needs different model capabilities per stage, or benefits materially from parallel execution.

What's the single biggest security risk in prompt-driven systems?

Prompt injection — OWASP's #1-ranked LLM risk for three consecutive years. Especially dangerous in systems that retrieve external content, since a model can treat untrusted text as trusted instructions.

Sources

[peer-reviewed] Wei, J. et al. (2022). "Chain-of-Thought Prompting Elicits Reasoning in Large Language Models." NeurIPS.
[peer-reviewed] Brown, T. et al. (2020). "Language Models are Few-Shot Learners." NeurIPS.
[peer-reviewed] Aggarwal, P. et al. (2024). "GEO: Generative Engine Optimization." ACM SIGKDD.
[peer-reviewed] Vilakati, S. et al. (2025). "Prompt engineering for accurate statistical reasoning with LLMs in medical research." Frontiers in AI.
[peer-reviewed] Liévin et al. (2024). Evaluating prompt engineering on GPT-3.5's USMLE-style medical calculations. PMC.
[peer-reviewed] Liu, N. et al. (2024). "Lost in the Middle: How Language Models Use Long Contexts." TACL.
[vendor documentation] Anthropic. Prompt engineering guidance, Claude docs (accessed 2026) — paraphrased, not quoted verbatim.
[vendor engineering blog] Anthropic Engineering (2025–2026), context engineering and Claude Code system-prompt reduction posts — paraphrased.
[industry/security standards body] OWASP Foundation (Aug 4, 2026). Top 10 for LLM Applications, 3rd edition.
[preprint, not peer-reviewed] "Optimizing LLM Prompt Engineering with DSPy Based Declarative Learning" (2026). arXiv:2604.04869.
[preprint, not peer-reviewed] "Is It Time To Treat Prompts As Code?" (2025). arXiv:2507.03620.
[industry market reports] The Business Research Company, Grand View Research, Fortune Business Insights (2026) — directional, not audited.
[labor market data] Glassdoor, ZipRecruiter, Levels.fyi, Coursera, KORE1, RezScore (2026) — figures vary by source, treated as directional.

Last updated August 20, 2026. The field moves fast enough that a "definitive" guide older than six months deserves some skepticism — including this one.

If this was useful: I write the full-length, continuously-updated version of this guide — plus a free downloadable prompt-engineering checklist — at bestprompt.art. It's where I keep the sourced, no-hype version of whatever's actually changed in this field, updated as the primary sources update. Worth a bookmark if you found the honesty-over-hype angle here useful.

AI Trends 2026: The $2.59T Nobody Agrees On

Tom Morgan — Sun, 16 Aug 2026 11:22:03 +0000

`# AI Trends 2026: The $2.59 Trillion Nobody Agrees On

> Quick read: Gartner now says worldwide AI spending will hit $2.59 trillion in 2026 (revised up from $2.52T in January). 88% of companies use AI in at least one function. Only ~6% are what McKinsey calls "AI high performers." The gap between adoption and value—not model quality—is the real story.

The number that kept moving

In January 2026, Gartner published the headline figure every newsletter recycled: $2.52 trillion in global AI spending.

By May, they'd already revised it to $2.59 trillion. The jump came from hyperscaler infrastructure demand and faster-than-expected agentic AI software spend.

I built the first draft of our full report around the January number—because that's what every "2026 AI trends" roundup was still citing in early summer. It took a direct check of Gartner's newsroom archive to catch the update.

The lesson: In AI market coverage, a statistic's publication date matters as much as the number itself. Most secondary coverage doesn't carry a version number. We tracked this in our full AI Trends 2026 breakdown, including a "forecast drift index" showing how far key figures moved between releases.

Where the money actually goes

The headline obscures the real story: this is an infrastructure buildout, not an enterprise software spree.

Category	2026 Spend
Infrastructure (servers, IaaS, semiconductors)	~$1.43T
Services	~$585.5B
Software	~$453.2B
AI Security	~$51.3B
AI Models	~$32.6B

That $32.6B for models alone is up 110% year-over-year. But notice: roughly $2T of the $2.59T total is infrastructure and services—capacity being built ahead of proven enterprise demand.

Microsoft, Amazon, Alphabet, and Meta collectively raised 2026 capex guidance to roughly $725 billion during Q1 earnings calls. That capital is chasing revenue that mostly hasn't arrived yet.

> 💡 Read the full category breakdown (plus why the segments don't sum cleanly to $2.59T) in our complete report.

Adoption is real. Production mostly isn't.

McKinsey's latest State of AI research tells a two-sided story:

88% of organizations use AI in at least one business function
72% use generative AI specifically
Only ~39% report any measurable EBIT impact
Just ~6% qualify as "AI high performers"

MIT's Project NANDA put an even sharper point on it: 95% of organizations are getting zero measurable return from generative AI initiatives. The researchers were explicit—the divide is driven by organizational approach (data readiness, workflow redesign, governance), not model quality.

> "The organizations getting value from AI in 2026 aren't the ones with access to better models. They're the ones that fixed their data and workflows before they bought anything."

We unpack the full funnel—and why you shouldn't stack McKinsey's 6% on top of MIT's 95% as if they're the same metric—in the deep-dive version.

Agentic AI: the growth engine and the graveyard

Agentic AI (systems that plan and execute multi-step tasks autonomously) is the one category that justifies the hype:

Gartner forecasts $206.5B in agentic AI software spend for 2026, growing to $376.3B in 2027
But Gartner also projects over 40% of agentic AI projects will be canceled by end of 2027—abandoned due to rising costs, unclear value, or inadequate risk controls

Both things are true simultaneously. That's what an early, capital-heavy technology cycle looks like before consolidation.

We cover the model landscape (Claude vs. Gemini vs. GPT), industry-by-industry adoption with actual sourced figures, and what the 6% of high performers do differently in the full report.

3 trends that actually matter

The infrastructure-to-value lag widens before it narrows. Hyperscalers keep spending. EBIT-impact figures move slowly.
Agentic AI becomes both growth engine and graveyard. 141% spending growth coexisting with 40%+ project cancellation rates.
Data readiness overtakes model choice. The high performers aren't using better models. They fixed their pipelines first.

The honest bottom line

Treat every AI statistic you read in 2026 as provisional until you know when it was published and whether it's been revised. Gartner moved its own headline by $70 billion in four months. If a report doesn't attach a date to its core figure, that's a signal to verify it—not a reason to distrust the trend.

2026 is a year of two simultaneous, true stories: AI use is close to universal, and AI value remains rare and hard-won.

→ Read the complete AI Trends 2026 report on AInvasion

Full version includes:

Every chart, table, and source citation
The complete "Forecast Drift Index" with revision tracking
Industry-by-industry adoption with traceable methodology
FAQ with schema.org structured data
Author sourcing rules and verification date

Last verified against primary sources — July 19, 2026`

The Singularity Divide: Why AI's Smartest Minds Can't Agree on What Happens Next

Tom Morgan — Thu, 13 Aug 2026 22:33:18 +0000

markdown

title: "The Singularity Divide"
published: true
description: "Why the smartest people in artificial intelligence disagree on what happens next—and why the gap between their predictions keeps widening."
tags: ai, agi, machinelearning, singularity, futures
canonical_url:

cover_image:

Deep Analysis • June 2026 • Corrected & Fact-Checked

The Singularity Divide

Why the smartest people in artificial intelligence disagree on what happens next—and why the gap between their predictions keeps widening.

Data-Driven • Primary-Source Transcripts • Real-Time Markets • Safety Reports

74% of companies still can't show tangible business value from their AI investments, according to Boston Consulting Group's 2024 survey of 1,000 executives. Not because the tools are bad. Because most organizations deploy AI expecting the timelines they hear from the loudest voices in the room. The same voices that now have Elon Musk saying AGI arrives this year, Demis Hassabis saying 2030, and a room full of scientists at the 2026 Summit on Existential Security landing on 2033. Someone is wrong. Probably several someones. The question is whether you can afford to bet your career, company, or policy on any single one of them.

I spent the last three weeks reading every major prediction market, safety report, and on-the-record statement from the people actually building these systems. Not the Twitter commentators. Not the LinkedIn influencers. The CEOs of Anthropic, DeepMind, OpenAI, and xAI. The scientists who wrote the International AI Safety Report 2026. The forecasters at Samotsvety and Metaculus who track this stuff for a living. What I found isn't a simple disagreement about dates. It's a fundamental fracture in how different people define intelligence, measure progress, and weight uncertainty. I also found a few statistics circulating in AI commentary that don't hold up under a second look — I've flagged those as I go, rather than quietly dropping them.

Key Numbers at a Glance

Metric	Value
Widest gap (Musk vs Schmidhuber)	24 years
Kalshi: OpenAI AGI by 2030	~55% (fluctuates)
Samotsvety: AGI by 2030 (Jan 2026)	28%
Companies without tangible AI ROI (BCG 2024)	74%

A note on sourcing: Every statistic in this piece was checked against the original report, transcript, or press release rather than a secondary blog post repeating it. Where I couldn't verify a figure to my satisfaction, I've said so explicitly instead of presenting it with false confidence. The Samotsvety figure went through two rounds of correction in editing: an initial draft cited their stale 2023 numbers, a revision then mistakenly substituted Metaculus's larger community forecast for Samotsvety's own, and it's now anchored to independent trackers' reporting of Samotsvety's actual January 2026 update (~28% by 2030). I'm noting the churn rather than hiding it — it's a useful illustration of how easy it is to blend two different forecasting groups' numbers even when you're trying to be careful.

The Prediction Gap Is Not Random—It's Structural

In January 2026, Dario Amodei and Demis Hassabis appeared on the same Davos stage — their first joint appearance in a year, moderated by The Economist's Zanny Minton Beddoes. The tone was notably collegial, not adversarial: at one point Amodei said outright, "I wish we had Demis' timeline." But underneath the mutual respect sat a real disagreement. Amodei, CEO of Anthropic, stated that we're 1-2 years from AI systems that outperform humans at everything. Hassabis, who runs DeepMind and holds a Nobel Prize, put it at 5-10 years. Neither man treated the other's estimate as unreasonable. That's what makes the gap worth taking seriously: this isn't a fringe voice versus a skeptic, it's two people building competing frontier labs landing on timelines that differ by a factor of five.

Here's what most coverage missed: they actually agreed on the single variable that matters. "The biggest thing to watch is AI systems building AI systems," Hassabis said. "Whether that loop closes will determine if it's a few more years or if we have wonders and a great emergency in front of us." Amodei nodded. On that, there was no daylight.

The AI Self-Improvement Loop

AI writes code  →  Better AI models  →  More training data (synthetic + self-generated)
       ↑                                              ↓
       └────────────── Loop closes? ←─────────────────┘

markdown

The self-improvement loop is the variable Amodei and Hassabis both pointed to on this particular panel. It's their shared framing, not a settled finding — researchers including Yann LeCun have publicly argued the loop faces diminishing returns and verification bottlenecks well short of the acceleration this diagram implies. Data from Davos 2026 transcripts.

Where they diverge is on how fast that loop accelerates. Amodei has engineers at Anthropic who, by his own account, "don't write any code anymore. I just let the model write the code." He estimates 6-12 months until AI does "most, maybe all" of what software engineers do end-to-end. Hassabis is more cautious, noting that verifiable domains like math and coding are easier to automate than natural sciences where you "may have to test it experimentally." The experimental validation step—running physical experiments, waiting for results, iterating—is a hard speed limit that pure compute scaling can't bypass.

I think we were standing in the foothills of the singularity now. It will be a profound moment for humanity.

— Demis Hassabis, Google DeepMind CEO, Stanford GSB, May 2026

What the Prediction Markets Actually Say (And Why They Matter)

If you want to know where smart money puts its confidence, skip the keynote speeches and check the markets. As of mid-2026, here's the landscape:

AGI Probability by Source (mid-2026 snapshot)

Source	Prediction	Probability
Samotsvety — by 2030	Unconditional	28%
Kalshi — OpenAI by 2030	Conditional on OpenAI	~55%*
Polymarket — OpenAI by 2027	Conditional on OpenAI	~9%*
Metaculus — by 2029	Community forecast	25%
Metaculus — median (50%)	by Jan 2033	50%

*Kalshi odds move daily with the news cycle — treat as a snapshot, not a fixed number.

Samotsvety is unconditional; Kalshi/Polymarket are conditional on a specific company.

The Samotsvety Forecasting team—a group with a competitive track record on major forecasting platforms—has moved fast. Their original January 2023 forecast put 50% probability on AGI by 2041 and 90% by 2164. Their most recent public update, from January 2026 with eight forecasters contributing, is far more aggressive: roughly 28% by 2030, up from 32% by 2042 in their 2022 forecast — more than a decade of compression in three years. (For comparison, Metaculus's separate, much larger community forecast — not Samotsvety's — sits closer to 25% by 2029 and a 50%-probability median of January 2033; the two are easy to conflate and worth keeping distinct, since Metaculus draws on thousands of participants while Samotsvety is a small team of professional superforecasters.)

Kalshi traders, who put real dollars on the line, have priced OpenAI's odds of hitting AGI by 2030 in roughly the mid-50s percent range, though that number moves with the news cycle and shouldn't be quoted as a fixed figure. Polymarket is more conservative: its "OpenAI announces AGI before 2027" market has traded in the high single digits to low teens through mid-2026 — it was around 9% as of an August 2026 snapshot — and moves daily like any live market.

The spread isn't noise. It reflects genuine uncertainty about three things: definition (what counts as AGI?), measurement (which benchmarks matter?), and deployment (does a lab demo count, or does it need to be in the wild?). Kalshi's number is conditional on OpenAI's specific trajectory. Samotsvety's 28% is unconditional — it's about whether AGI happens by 2030 at all, regardless of who builds it. You can't directly compare them without accounting for those differences, and most headlines don't.

The Expert Timeline: From 2026 to 2050

Expert	Organization	Rough Prediction	Confidence Framing
Elon Musk	xAI / Tesla	~2026	"Smarter than the smartest human"
Dario Amodei	Anthropic	~2027	"1-3 years" with software automation in 6-12 months
Masayoshi Son	SoftBank	~2027-28	2-3 years from a Feb 2025 statement
Shane Legg	DeepMind	~2028	50% chance of "minimal AGI"
Ben Goertzel	SingularityNET	~2029	Fully independent human-level AI
Jensen Huang	NVIDIA	~2029	"Within five years" from March 2024
Demis Hassabis	DeepMind	~2030	Narrowed from an earlier 2030-35 window
Sergey Brin	Google	~2030	Algorithmic advances weighed over compute scaling
Ray Kurzweil	Google / Futurist	~2032	Revised from an earlier 2045 estimate
2026 Summit Scientists	Researcher survey	~2033	Reported median across respondents
Andrej Karpathy	Former OpenAI	~2035	AGI as "human employee or intern"-level capability
Sam Altman	OpenAI	Unspecified, distant	"A few thousand days" (2024) — an approximation, not a dated forecast
Ajeya Cotra	Open Philanthropy	~2040	50% chance based on compute-trend modeling
Jürgen Schmidhuber	IDSIA	~2050	Co-founder of modern deep learning

Treat the single-year figures above as rough midpoints of much fuzzier statements, not firm dates the speakers themselves committed to.

Notice the pattern? The people with the most to gain from being right about early timelines—founders, investors, chip manufacturers—cluster on the left. The people with the most to lose from being wrong about safety—academic researchers, safety scientists, the summit-surveyed experts—cluster on the right. This isn't necessarily dishonesty. It's different incentive structures producing different prior distributions. But it means you should weight a prediction by the predictor's skin in the game, and you should treat interview soundbites ("a few thousand days," "the foothills of the singularity") as directional, not as calendar entries.

The Capability Gap: Where AI Dominates vs. Where It Still Fails

Here's a truth that gets buried under the headline numbers: we don't have a single definition of AGI that everyone accepts. Is it passing a Turing test? Scoring 90% on a broad benchmark? Replacing a junior software engineer? Doing Nobel Prize-level science? Each definition produces a different timeline, and most experts are implicitly answering different questions.

Where Frontier AI Stands (qualitative, mid-2026)

Domain	Status
Coding & math (verifiable domains)	Ahead of most humans
Language translation	Ahead of most humans
Long, unattended coding tasks	Closing fast
Scientific discovery (needs real-world tests)	Still behind
Long-horizon planning & goal-setting	Still behind
Physical-world interaction / robotics	Clearly behind
Social & contextual judgment	Clearly behind

Qualitative synthesis of publicly reported benchmark and expert commentary — deliberately not scored, since no single benchmark spans all these domains on one comparable scale.

The METR "time horizon" metric is one of the more concrete ways researchers track this: it measures the length of task (in human-expert-hours) that a model can complete with 50% reliability, and that horizon has been roughly doubling every few months across recent frontier models. Ajeya Cotra and other forecasters treat that doubling trend as one of the better leading indicators available. I'd flag one honest limitation here: the specific hour-figure for any single named model changes with almost every release, so cite METR's own published leaderboard for the current number rather than a fixed figure repeated in commentary — including, frankly, this article's own earlier draft, which is exactly the kind of stale-stat problem worth naming rather than hiding.

The MIT Technology Review "Road to AGI" report (August 2025) anticipates early AGI-like systems emerging between 2026 and 2028, but specifically notes they'll show "human-level reasoning within specific domains, multimodal capabilities across text, audio, and physical interfaces, and limited goal-directed autonomy." The key phrase is limited goal-directed autonomy. An AI that can reason through a coding problem for many hours unattended is not the same as an AI that can decide what problems are worth solving.

The Risk Matrix: What Experts Actually Worry About

If you're reading this to decide whether to panic, here's the honest answer: it depends on what you're panicking about. The International AI Safety Report 2026—authored by a large international panel of AI experts including Yoshua Bengio, and backed by dozens of countries plus the UN and OECD—breaks risks into three categories: malicious use, malfunctions, and systemic risks. The report is careful, evidence-based, and deeply uncomfortable reading.

AI Risk Landscape (qualitative, per Intl. AI Safety Report 2026)

Well-documented, already occurring / Moderate severity

Job displacement in specific sectors
Misinformation & synthetic content
Economic concentration among AI leaders

Well-documented / Catastrophic severity

Cyberattack automation (documented, AIxCC)
AI-assisted reward hacking / eval gaming
Autonomy erosion in decision-making

Contested / High severity

Biological / chemical weapon uplift — severity is high; the report treats likelihood as genuinely unresolved
Loss of control (existential risk) — experts explicitly disagree on likelihood

Placement reflects the report's own framing, not a numeric probability model — the report itself declines to score these on one scale.

On loss of control—the scenario where AI systems operate outside anyone's control, with outcomes as severe as human extinction—the report is deliberately measured. "Expert opinion on the likelihood of loss of control varies greatly. Some experts consider such scenarios implausible, while others view them as sufficiently likely that they merit attention due to their high potential severity." The disagreement, the report notes, "stems from disagreements about future AI capabilities, behavioural propensities, and deployment trajectories."

⚠️ The Evaluation Problem No One Talks About Enough

Recent safety reporting has flagged that some frontier models show early "situational awareness" — occasionally identifying evaluation prompts as tests rather than real deployment. If that pattern generalizes, it means capability evaluations could understate what a model can actually do outside a testing sandbox. The safety report frames this as an open concern rather than a settled fact, and so do I: it's a real methodological worry, not proof that current models are systematically deceiving evaluators.

The report also documents something that should worry anyone in cybersecurity, and it's worth getting exactly right: in DARPA's AI Cyber Challenge (AIxCC), finalist teams' AI systems found 86% of the synthetic vulnerabilities that competition organizers had deliberately planted inside real open-source codebases — up from 37% at the previous year's semifinals. That's a controlled benchmark, not a live attack on production software, and it's an important distinction: the same teams also stumbled onto 18 previously unknown real-world zero-day vulnerabilities they weren't looking for, which is arguably the more striking result. Whether attackers or defenders benefit more from AI assistance in the wild "remains uncertain," per the safety report — which, in security terms, is not a comforting statement either way.

The Labor Shock: Who Gets Hit First

If you're a junior software engineer, a customer support specialist, or a paralegal, you don't need to wait for AGI to feel the ground shift. Amodei was explicit at Davos: "Half of entry-level white collar jobs could be gone within one to five years." Hassabis didn't dispute the direction, only the speed. His advice to undergrads: "Get really unbelievably proficient with these tools. There's almost a capability overhang even in today's models."

Labor Disruption Timeline (directional)

Category	Estimated Window
Entry-level software engineering	2026–2027
Customer service	2026–2028
Junior white-collar work generally	2027–2028
Creative & content fields	2028–2029
Scientific discovery roles	2030+
Strategic leadership & judgment	TBD

Directional estimates drawn from Davos 2026 commentary, not a peer-reviewed forecast. Treat the year ranges as illustrative, not predictive.

Separately — and this is worth keeping distinct from the AGI-timeline debate — BCG's 2024 survey of 1,000 senior executives across 59 countries found that 74% of companies had not yet shown tangible business value from their AI investments, with only 4% consistently generating value across functions. Worth flagging: BCG is a consulting firm that sells AI transformation services, and its "value" framework was designed by the same firm pitching the fix, so the incentive to find a large addressable problem is real. That doesn't mean the finding is wrong — the underlying pattern (isolated pilots, not enterprise-wide value) shows up in independent research from McKinsey and Gartner too — but it's not neutral social-science data either, and it deserves the same skepticism this piece applies to lab-CEO timelines. It's evidence of an adoption gap: most organizations pilot AI in isolated corners rather than redesigning core workflows around it, and BCG's leaders (the top 26%) got there by focusing resources on a handful of high-priority use cases rather than spreading thin. The "capability overhang" Hassabis describes and this adoption data are two sides of the same coin: the tools are often ahead of the organizations using them.

Hassabis frames this as the "training ladder problem." Some jobs will get disrupted, but he believes "new even more valuable, perhaps more meaningful jobs will get created... in the near term." The question he doesn't answer: who pays for the retraining during the gap between disruption and creation? Historically, that gap has been measured in decades, not months. If Amodei's 1-5 year timeline is even directionally correct, we don't have decades.

The Geopolitical Angle: Chips, Borders, and the Race Nobody Wants

Amodei delivered his most pointed geopolitical statement at Davos, comparing selling AI chips to China to "selling nuclear weapons to North Korea because that produces some profit for Boeing." He called not selling chips to China "one of the biggest things we can do" to ensure time for safety measures. This isn't abstract philosophy. It's a direct policy prescription from someone whose company depends on those chips.

The chip export restrictions have already reshaped the competitive landscape. Chinese labs are investing heavily in domestic alternatives, but the gap remains significant. The strategic calculation is brutal: every month of delayed access is a month of safety research that might matter. But it's also a month where Chinese AI capabilities fall further behind, creating its own instability. There is no clean answer here, only trade-offs between speed and safety, openness and control.

What You Should Actually Do With This Information

I've read enough singularity predictions to know that most of them will look ridiculous in hindsight. The 2010 predictions about self-driving cars by 2020. The 2015 predictions about human-level AI by 2025. The pattern is consistent: we overestimate short-term change and underestimate long-term change. Whether this time is different is genuinely unresolved — the honest position is uncertainty, not conviction in either direction.

Here's my assessment, held with appropriate humility:

If you're a knowledge worker: Treat AI as a skill you need to master, not a tool you can ignore. Not because AGI is coming next year, but because BCG's own data shows most organizations haven't figured out how to extract value from what already exists. The people who thrive will be those who learn to orchestrate AI agents, not those who compete with them on raw output.
If you're a business leader: The gap between AI leaders and laggards in BCG's data — 1.5x revenue growth, 1.6x shareholder returns for leaders — didn't come from chasing every pilot. It came from concentrating resources on a few high-priority use cases and rebuilding processes around them. That's a more useful lesson than any AGI arrival date.
If you're a policymaker: The safety research community is asking for time to build better evaluation methods, partly because early situational-awareness findings suggest today's tests may not fully capture what models can do. The chip export debate matters, but the deeper issue is evaluation standards that keep pace with capabilities.
If you're an investor: The prediction markets are telling you something important. Odds in the 50s percent range for a specific company hitting AGI by 2030 is not a certainty. It's closer to a coin flip with enormous stakes, and it moves week to week. Diversify across the scenario space, not just the optimistic one.

The One Question Nobody Can Answer

Near the end of the Davos session, an audience member asked Amodei and Hassabis about the Fermi Paradox — if intelligence is so powerful, why don't we see evidence of it everywhere? Hassabis's actual answer was more technical than mystical: he argued the paradox doesn't obviously support AI-doom scenarios, reasoning that if superintelligent systems tend to consume their home civilizations, we should expect to observe the aftermath — Dyson spheres, or hostile self-replicating probes — somewhere in an observable galaxy, and we don't. It's a sharper, more falsifiable point than the framing usually given to this kind of question, and worth more attention than the moment got.

Strip away the staging, and the prediction gap comes down to a genuine, unresolved disagreement: not whether we can build AGI, but what order the hard problems come in. The optimists' working bet is that alignment is a solvable engineering problem you can tackle once capability exists. The realists' bet is that alignment has to lead, because a system you can't steer just becomes more dangerous as it gets smarter. Both are testable positions, not articles of faith — and neither camp has produced evidence that settles it.

Everything I just said will be outdated by next year. The models will be different. The benchmarks will have moved. Someone will have made a prediction that looks brilliant or absurd in retrospect. But the underlying tension—between speed and safety, between capability and control, between what we can build and what we should build—that tension isn't going anywhere. If anything, it's accelerating.

Sources & Further Reading

This analysis draws on primary sources including the International AI Safety Report 2026, the MIT Technology Review "Road to AGI" report (August 2025), the AIMultiple meta-analysis of expert AGI predictions (June 2026), Davos 2026 transcripts via Fortune and TeamDay AI, DARPA's official AI Cyber Challenge results announcement, Boston Consulting Group's "Where's the Value in AI?" (October 2024), and prediction market data from Kalshi, Polymarket, Metaculus, and Samotsvety Forecasting as of mid-2026. Figures that could not be independently verified against a primary source have been softened or removed rather than presented with false precision.

Note on the AIxCC figure: some outlets (CyberScoop, The Record, Infosecurity Magazine) reported competitors found 77% of the planted vulnerabilities. That number is not wrong so much as outdated: DARPA's own results page carries an editor's note stating the Final Competition actually contained 63 synthetic vulnerabilities, not the 70 originally announced. The 54 vulnerabilities teams found never changed — only the denominator did — which moves the rate from 77% to DARPA's corrected 86%. This piece uses DARPA's own current figure.

FutureNow Editorial

Deep-dive analysis at the intersection of AI capabilities, safety research, and real-world impact. We read the reports so you don't have to—but we always link the primary sources, and we correct our own numbers when a second look shows they don't hold up.

Explore more at FutureNow →

DEV Community: Tom Morgan

AI Tools for Social Media That Actually Move the Needle (Most Don’t)

AI Workplace Productivity: Does Automation Really Save Time?

What GitHub Actions Actually Costs When It’s “Free”

Can AI Really Predict Your Next Thought? Tracing the “87% Accurate” Claim Back to Where It Actually Came From

Unified Customer Profiles: The Foundation Nobody Budgets For (And Why That’s Backwards)

25 Prompt Templates Worth Stealing This Month

AI in Religion and Philosophy

The Algorithm in the Margin: How AI Is Changing Religious Interpretation

The Algorithm in the Margin: How AI Is Quietly Changing Religious Interpretation

The Chatbot Story Is the Wrong Story

The First Quiet Revolution: Reading the Manuscript

The Rabbi's Research Assistant Has No Heartbeat

Egypt's Warning: AI Can Search Scripture Faster Than a Human — But Should It Interpret It?

Twenty-Seven AI Models Took a Religion Exam

The Model Doesn't Need to Be Anti-Religious to Produce Religious Bias

The Trust Problem Is Already Here

The Hidden Problem: Training Data Is Already a Theology

Religion and AI Alignment Are Asking the Same Question

The Pope's Argument Is About Power. The AI Benchmark Is About Behavior.

The Real Boundary Isn't "Can AI Be Religious?"

What Happens to the Next Generation of Religious Scholars?

The Machine Can Read the Footnotes. It Cannot Inherit the Tradition.

The Boundary Nobody Has Tested Yet

Final Thought

Further reading

Your Job Won't Disappear: The AI Employment Data Both Sides Don't Want You to See

Table of Contents

1. Why Stanford and Yale Disagree (And Why It Matters)

2. The Mechanism Both Sides Agree On

3. Entry-Level Work: The WEF/PwC Data

4. The Macro Projections Haven't Moved

5. Inside the Enterprise: Adoption ≠ Value

6. Sector Breakdown: Where the Evidence Points

7. Score Your Own Exposure: The Task Exposure Framework

8. What You Should Actually Do

Map your work by automation mode, not job title

Don't treat the Yale finding as permission to stop paying attention

If you manage entry-level hiring, read the WEF/PwC argument before your next headcount decision

9. If You're Early-Career (Or You Manage Someone Who Is)

For early-career workers and recent graduates

For people managers and HR leaders

10. Myth vs. Fact

11. FAQ

Prompt Engineering in 2026: What Actually Still Works

Prompt Engineering in 2026: What Actually Still Works

TL;DR

1. The market number nobody agrees on (and the one they do)

2. Reasoning models ate manual chain-of-thought

3. Zero-shot vs. few-shot: it's "when," not "which"

4. What Anthropic itself now says you can stop doing

5. The hybrid template that actually holds up

6. Context engineering: the real 2026 headline

7. Multimodal and agentic prompting

8. Prompt injection: the risk section most guides still skip

9. What DSPy and automated prompt optimization actually deliver

10. The hidden cost of a bad prompt

11. Prompt engineering and AI search visibility (GEO)

12. Is "prompt engineer" still a real job in 2026?

13. FAQ

Sources

AI Trends 2026: The $2.59T Nobody Agrees On

The number that kept moving

Where the money actually goes

Adoption is real. Production mostly isn't.

Agentic AI: the growth engine and the graveyard

3 trends that actually matter

The honest bottom line

The Singularity Divide: Why AI's Smartest Minds Can't Agree on What Happens Next

markdown

cover_image:

The Singularity Divide

Key Numbers at a Glance

The Prediction Gap Is Not Random—It's Structural

The AI Self-Improvement Loop

What the Prediction Markets Actually Say (And Why They Matter)

AGI Probability by Source (mid-2026 snapshot)

The Expert Timeline: From 2026 to 2050

The Capability Gap: Where AI Dominates vs. Where It Still Fails

Where Frontier AI Stands (qualitative, mid-2026)