An AI Stack With Distinct Roles: My September 2026 Setup
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: An AI Stack With Distinct Roles: My September 2026 Setup on ThorstenMeyerAI.com

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get tech for your team delivered free — and shop member deals

  • Fast, free delivery on millions of items
  • Access to Prime Big Deal Days deals on October 6–7
  • Prime Video, Amazon Music and more included
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

With six frontier AI models clustered within about 20 index points on the Artificial Analysis Intelligence Index but differing roughly 100-fold in cost per task, developer Thorsten Meyer outlines a September 2026 stack that assigns distinct roles: Claude Opus 5.5 as main builder and newly released GPT-6.1 Sol as low-cost detail and review model.

Developer Thorsten Meyer has published his working AI stack for 29 September 2026, built around a frontier-model field where six leading models sit within roughly 20 index points of each other on capability while their cost per task differs by about 100×. His setup assigns Claude Opus 5.5 as the main builder and the just-released GPT-6.1 Sol as a low-cost model for detailed work and code review, a division of labor driven less by raw intelligence than by price-performance at the task level.

According to Meyer’s write-up, the core question has shifted from “which model is smartest?” to “which model clears my quality bar at the lowest cost per task?” He cites data from the Artificial Analysis Intelligence Index v4.3.x, which he describes as “a map of general capability, not a verdict on your workload,” urging readers to shadow-test before switching models.

Three findings stand out in his data. First, Opus 5.5 (released 22 September, index 58 at max) outscores its more expensive sibling Fable 5.1 (53) by 5 points while costing less per task — $5.98 against $7.63. Second, Sonnet 5.5 at max effort costs $7.60 per task for 56 points, more than Opus at max for 2 fewer points, making it hard to justify at that setting. Third, GPT-6.1 Sol at xhigh costs $0.39 per task — roughly one-eighth of Astra’s $3.26 and one-twentieth of Fable’s $7.63 — for a score only 1 to 2 points lower.

Meyer also reports that the effort setting is a bigger cost lever than model choice. On Opus 5.5, moving from xhigh to max adds 2 index points and 73% more cost per task; from medium to max, cost rises 4.46× for 7 points. He runs Opus at high (54 points, $1.82 per task) for development and reserves xhigh for architecture, migrations, and trust boundaries.

At a glance
analysisWhen: published 29 September 2026
The developmentThe release of GPT-6.1 Sol on 29 September 2026 and a frontier-model field now differentiated far more by price than capability prompted a documented, role-based AI model stack.

Opus builds. Sol reviews. Jev decides.

The September 2026 AI stack in one page: six frontier models on one price curve, and a decision model for the high-volume judgements that do not need a sentence.
Scores: Artificial Analysis Intelligence Index v4.3.x. Data as of 29 September 2026.
BuildsClaude Opus 5.5 at high or xhigh effort
Digs and reviewsGPT-6.1 Sol at high or xhigh effort
DecidesJev on high-volume yes/no and routing calls

One price tape, six models

Put every model on the same cost-per-task ruler and capability looks compressed. The bill does not.
Price tape: cost per task of six models on a log scale, from GPT-6 Luna at $0.07 to Fable 5.1 at $7.63$0.05$0.10$0.50$1$5$10cost per task, log scale: each tick is a different order of magnitudeGPT-6 Lunaindex 37 · $0.07GPT-6.1 Solindex 51 · $0.39 (xhigh)GPT-6 Astraindex 53 · $3.26Opus 5.5index 58 · $5.98Sonnet 5.5 · index 56 · $7.60Fable 5.1 · index 53 · $7.63about 100× from the cheapest to the priciest, but only 21 index points between them

Score against cost, at every effort setting

Each dot is an effort level. Opus 5.5 at high already matches Astra and Fable at max on this index, for less money.
Intelligence Index score against cost per task for each effort setting of six models$0.01$0.10$1$102030405060cost per Intelligence Index task, log scaleindexOpus high / xhigh: my defaultOpus 5.5Sonnet 5.5Fable 5.1GPT-6 AstraGPT-6.1 Sol (new)GPT-6 Sol (Sep 22), dashedGPT-6 Lunaup and to the left is better
Astra and Fable are shown at their top published setting. Luna starts at $0.0045 per task. GPT-6.1 Sol has no low or max setting published yet.

The effort dial moves the bill more than the model

Going from medium to max on Opus costs 4.46× more for 7 points. That is why I run high or xhigh.

Claude Opus 5.5

$0.55
42
$1.34
51
$1.82
54
$3.46
56
$5.98
58
low
medium
high
xhigh
max
Solid bars are where I run it. Max adds 2 points over xhigh for 73% more cost.

Claude Sonnet 5.5

$0.41
36
$0.59
41
$1.08
47
$2.74
52
$7.60
56
low
medium
high
xhigh
max
Best value is high. At max it writes about 193k output tokens per task, the most measured.

GPT-6.1 Sol: near-Astra scores at a fraction of the price

Launched 29 September at $2 in and $10 out per 1M tokens. It sits 1 to 2 points under Astra and Fable, and Opus xhigh still leads it by 5.

Three published settings

SettingIndexCost per taskOutput tokensFirst token
medium48$0.2115M5.3 s
high50$0.3225M57 s
xhigh51$0.3936M69 s
Median for comparable models is 82M output tokens. High and xhigh are not interactive: plan for a wait before the first token.

Same score band, very different bill

GPT-6.1 Sol xhigh
$0.39index 51
Opus 5.5 high
$1.82index 54
GPT-6 Astra max
$3.26index 53
Opus 5.5 xhigh
$3.46index 56
Fable 5.1 max
$7.63index 53
Cost per Intelligence Index task. A one-point gap is inside the noise.

My stack: who builds, who reviews

Opus does the work. A second model family reviews it, because a different reviewer catches what the author cannot see.
Stack diagram: Opus 5.5 builds at high effort, escalates to xhigh, and sends every change to GPT-6.1 Sol for review; Astra or Fable give a second opinionOpus 5.5 · xhighhard problems: architecture,migrations, trust boundariesOpus 5.5 · highMAIN BUILDERfeatures, APIs, multi-filework, refactorsescalate when it gets hardGPT-6.1 Solhigh or xhighdigs into details andreviews every change$0.32–0.39 per taskdifffindingsAstra or Fablesecond opinion, 8 to 20×the cost per taskif they disagreeSonnet 5.5 · Lunaside work: scopedsubtasks, bulk checksand routingFailed review? Hand Opus the failing case and the evidence.Never just “try harder”: effort cannot supply a missing requirement.
Effort is not capability. Turning the dial up does not make a model smarter.
Effort cannot fill gaps. A missing requirement stays missing at any setting.
Different model, same spec. That is not independent review if both read the same flawed brief.
Green tests are not approval. Passing tests only prove what the tests cover.

Cheaper tokens are not cheaper work

Illustrative, not measured: $1 of model time plus 4 minutes of review at $45 an hour. Halving the model price saves 12.5% of the total. One extra minute of review erases it.
$4.00
review $3.00
model $1.00
Baseline
$3.50
review $3.00
model $0.50
Model price cut 50%
$4.25
review $3.75
model $0.50
Cheaper model plus 1 extra minute of review
Track cost per accepted result: model, tools, review and rework, divided by the results someone actually uses.

Read the numbers with four warnings

The index movesFable scored 66 on an earlier version and 53 on v4.3. Compare within one version only.
Fallback is includedFlagged cyber and biology tasks route to older Anthropic models, now on Sonnet 5.5 too.
Max is not productionReal deployments run medium or high, where gaps narrow and costs fall.
Your work decidesShadow-test on your own tasks. Budget cost per task, not per token.

Part 2: Jev, the model that decides instead of writing

Jev cannot write, summarise or extract. It answers narrow typed questions with a probability and an honest confidence, in under a second, for about $0.04 per million input tokens.

One call in, typed answers out

Your code, not Jev, decides what to do with each answer, usually by confidence band.
Jev flow: state and typed questions go into one Jev call; typed answers with confidence come out; code acts alone, escalates the gray zone, or logsStatea ticket, a story,a site profile,a log line …+ typed questions,many per callJevone call0.3 to 0.9 s$0.042 / M tokens inAnswersnoul: 0.03choice: billing p 0.91, conf 0.86score: 2.7 of 3 conf 0.64code branches on thisAct aloneconf ≥ 0.8Escalategray zone toLLM or humanLogmeasure first

Three question types

noul
A yes/no question. Returns the probability of yes, 0 to 1.
gates, flags, filters
choice
Pick one option. Returns the choice, a probability per option, and a confidence.
routing, classification, taxonomy
score
Rate on your ordered levels. Returns a position (it can fall between levels) plus a confidence.
quality, fit, severity, priority

Confidence is the superpower

In my own measurement on a 31-topic classification, Jev agreed with a frontier LLM almost every time it was sure, and rarely when it was not. So: decide the clear cases, route the gray zone.
confidence 0.8 or higher
97–99%
all answers
89%
confidence below 0.5
42%
Agreement with a frontier LLM, my production data, September 2026, rounded.

Three uses running in my publishing operation

About 90,000 decisions so far. Checks I could only afford on a sample now cover everything.
$2.01
Language check
78,889 articles scanned overnight. 1,576 in the wrong language found, 1,553 fixed in place.
22%
Relevance gate
About 10,000 story-to-site pairings judged in 3 days. Only 22% were clearly on-topic.
89%
Classifier fallback
Agreement with the primary LLM across 31 topics, used when that LLM errors.

The fit test, then the shadow test

Use Jev only when all four hold. Then prove it on past decisions before it acts on anything.
High volumeThousands of small calls, not a handful of big ones.
Narrow questionNo multi-step reasoning needed.
Cheap errorsOr unsure cases go to something smarter.
Heuristic failsVisibly, and measured, not assumed.
  1. Replay 300 to 500 past decisions
  2. Compare overall and per confidence band
  3. Read 20 disagreements, decide who was right
  4. High band at 95% or better?
  5. Own flag, off by default
  6. Canary on 5 to 10 units
  7. Roll out in the confident band only

24 use cases, sorted by how well they fit

Start from the strong fits. The amber ones need a measurement before you trust them, and the red ones fail one of the four conditions.
in productionstrong fitmeasure firstpoor fit

Proven in production

  • 1Relevance gate
  • 2Language check
  • 3Classifier fallback

Publishing and content

  • 4Thin-source detector
  • 5Same-event dedupe
  • 6Product fits roundup
  • 7Disclosure present
  • 8Headline quality
  • 9Comment moderation

Commerce and support

  • 10Support-ticket routing
  • 11Return-reason coding
  • 12Review to feature complaints
  • 13Catalogue taxonomy
  • 14Order-fraud pre-triage

Software and AI systems

  • 15LLM guardrail
  • 16RAG passage filter
  • 17Citation check
  • 18Tool and intent routing
  • 19Log-line triage
  • 20PR risk triage

Business ops and home

  • 21Inbox triage
  • 22Expense categorisation
  • 23Lead qualification
  • 24Smart-home intent

Limits, cost and one hard rule

No writing, summarising or extractionPair it with an LLM for the write step.
No world knowledgePut a snippet in the state; a bare name means nothing.
Reads your wording literallyA rewording moved my results about 2 points. Freeze it, re-measure after changes.
Weaker on non-English, maths, datesKeep those checks on an LLM. Early access, hosted API only.
100,000 decisions ≈ $2.50
About 60M input tokens at $0.042 per million, output free, roughly 600 tokens per three-question call. Latency 0.3 to 0.9 seconds.
Never the sole decision-maker for consequences about people. Hiring, credit, medical and legal outcomes stay with a human. Jev can sort and flag. A person decides.
Sources. Model scores, cost per task and speeds: Artificial Analysis, Intelligence Index v4.3.x, including the GPT-6.1 Sol medium, high and xhigh pages, checked 29 September 2026. Astra and Fable scores from the Artificial Analysis v4.3 announcement. Jev figures are my own production measurements, September 2026, rounded. The review-bill example is illustrative. Read the full article on thorstenmeyerai.com.

Why Price-Performance Now Beats Model Loyalty

The stack illustrates a broader shift in how practitioners choose AI tools: as capability gaps between frontier models narrow to single index points, cost per task becomes the deciding factor. A review pass at $0.32 to $0.39 per task is cheap enough to run routinely on every meaningful change, which changes quality-assurance economics for development teams.

Meyer argues the review seat matters most: a different model family reviewing Opus’s output is a better check than Opus reviewing itself. He pairs that with four working rules, including “effort is not capability,” “a different model is not an independent review if both read the same flawed spec,” and “passing tests are not approval to ship.”

He also cautions that cheaper tokens are not cheaper work: halving model price saves only 12.5% of real cost, and one extra minute of human review can erase the saving — an example he flags as illustrative, not measured.

A Compressed Month of Frontier Releases

The stack caps an unusually crowded September 2026. According to Meyer’s timeline, Claude Fable 5.1 launched 1 September, GPT-6 Astra on 3 September, Claude Opus 5.5 and GPT-6 Luna on 22 September, Claude Sonnet 5.5 on 28 September, and GPT-6.1 Sol on 29 September — the same day as publication.

GPT-6.1 Sol launched at the same $2/$10 per 1M tokens (input/output) as its week-old predecessor. Meyer notes that even its medium setting matches the earlier GPT-6 Sol’s score of 48 at one-fifth the cost per task ($0.21 versus $1.06). Published per-token prices: Opus 5.5 at $4/$20 with cache reads at $0.20; Fable and Astra at $10/$50; Sol at $2/$10; Luna at $0.10/$0.50.

Meyer also deploys Jev, a decision model he describes as unable to write a sentence, for high-volume yes/no and routing judgements, alongside GPT-6 Luna for classification, extraction, and routing at $0.07 per task.

“In four weeks, the AI frontier stopped being a leaderboard and became a price curve.”

— Thorsten Meyer

Open Questions Around GPT-6.1 Sol

Several limits remain. Meyer reports that Artificial Analysis has not yet published low or max settings for GPT-6.1 Sol, and notes that a one-index-point difference is inside measurement noise. Sol’s high and xhigh settings take 57 to 69 seconds to produce a first token, which he says rules it out as an interactive model at those settings.

All scores come from a single benchmark family (Artificial Analysis Intelligence Index v4.3.x), and Meyer’s cost-per-task figures are specific to that index’s task set — real workloads may produce different ratios. His claim that model price is a small fraction of total cost is labeled illustrative, not measured. Whether Sol’s extremely concise output (25M tokens on the index against a median of 82M for comparable models) translates to shorter answers in production use is not established.

Watching Sol’s Benchmarks and Stack Evolution

Meyer expects to keep refining the stack as benchmarks mature. Immediate watch items include Artificial Analysis publishing low and max effort settings for GPT-6.1 Sol, which will show whether the price-performance gap widens or closes at the extremes.

He plans continued shadow-testing before any model becomes a default, and says Astra and Fable stay in the stack only as tie-breakers when Opus and Sol disagree — a role whose cost-effectiveness will be re-evaluated as cheaper models catch up. The larger open question for practitioners is whether the September compression of scores holds, which would push more decisions toward routing models like Jev and Luna rather than a single premium default.

Key Questions

What is the main idea behind this September 2026 AI stack?

With six frontier models within about 20 index points of each other but roughly 100× apart in cost per task, the setup assigns each model a role based on price-performance: Opus 5.5 builds, GPT-6.1 Sol handles details and review, and cheaper models like Luna and Jev handle classification and routing.

Why is GPT-6.1 Sol used for review instead of building?

According to Meyer, Sol scores 1 to 2 points below Astra and Fable but costs $0.39 per task instead of $3.26 or $7.63. That makes a review pass cheap enough to run routinely, while Opus 5.5 retains a 5-point lead at xhigh for demanding build work.

What are GPT-6.1 Sol’s main drawbacks?

Its high and xhigh settings take 57 to 69 seconds to first token, making it unsuitable for interactive use, and Artificial Analysis has not yet published low or max effort settings. Its benchmark scores also trail Opus 5.5 by about 5 points at comparable settings.

Does raising the effort setting make a model smarter?

No, per Meyer’s rule that “effort is not capability.” On Opus 5.5, going from xhigh to max adds only 2 index points for 73% more cost per task, and medium-to-max raises cost 4.46× for 7 points.

Where do the benchmark scores in the stack come from?

All scores come from the Artificial Analysis Intelligence Index v4.3.x, which Meyer describes as a general-capability map rather than a verdict on any specific workload. He recommends shadow-testing before switching models.

Source: ThorstenMeyerAI.com

HALLOWEEN

Halloween Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Explore 24 Ways Jev Can Fit Your AI Decision Process

A Sept. 29 guide maps 24 potential Jev uses, reports three live publishing applications and calls for measured tests before wider adoption.

How Warehouse Mobile Computers Support Faster Operations

Optimize warehouse efficiency with mobile computers that enable faster operations—discover how they can revolutionize your processes today.

Field service photo checklist for HVAC teams

HVAC teams are testing a new mobile photo checklist to improve job documentation, customer proof, and safety compliance, with initial validation underway.

Triple Your Completion Rates with a Multi-Step Form Strategy

Discover how breaking forms into smaller steps can triple your conversion rates. Practical tips, real data, and psychological tricks included.