SFEIR analysis (consulting-firm voice) of the launch, on July 8, 2026, of **LLMD** by the Paris-based startup **ZML** (founded by **Steeve Morin**, former VP Engineering at Zenly): an inference server that runs LLMs across **five chip families** (NVIDIA CUDA, AMD ROCm, Google TPU, Intel oneAPI, Apple Metal) **from a single codebase**. Structuring thesis: training is ceding the spotlight to **inference**, where cost per token, latency, and above all **dependence on silicon** are now decided. ZML's bet — summed up by the motto *model to metal* — is to **decouple the model from the hardware** via a compiler written in **Zig + MLIR** that produces a hermetic native binary, with no Python in the execution path, exposed through an **OpenAI-compatible API**. Two components, two licenses: **ZML** (the framework, Apache-2.0, >90% Zig) is open source; **LLMD** (the server) is not, free at launch. The article reads the object through three consulting-firm lenses — **token FinOps**, **architectural freedom** (Design to Exit), **sovereignty** (emerging European chips, integration into the VSORA Jotunn8 processor) — then delivers an unsparing verdict: it is an **alpha**, to be placed "under active watch," not to switch to today.
X post by **Eric S. Raymond** (ESR, author of *The Cathedral and the Bazaar*, co-founder of the Open Source Initiative, ~50 years of coding) — **a frontal counter-testimony to the narrative that "LLMs produce crap code and hallucinate, useless for programming."** His thesis: this **almost never happens to him**, and **not at all anymore over the last two generations** of models he uses ("chat GPT 5.4 and 5.5" under **codex**). The former symptom — a model "going off the rails" as it approaches its context limit — has disappeared: codex now displays a **red warning** prompting the user to **clear the session** instead of spiraling. **Scope of use**: AI applied to **feature changes, refactoring and debugging across 63 projects** in **C, Go, Rust, Python and shell**; documentation writing; **decompiling a DOS binary into readable source**. An established **work routine**: when reopening a project, he first runs the **regression tests**, then starts codex and asks it to **audit the code** (bugs + improvement suggestions). Verdict: LLMs are **"excellent and tremendously empowering"**; their **worst limitation** is **"architectural tunnel vision"** — excellent at generating code to specification, but sometimes **blind to higher-level patterns** — which he takes to be the **job of his "meatbrain."** The strongest, counter-intuitive point: LLMs **do NOT get details and edge cases wrong**; he says he is **worse than them** on this front (despite 50 years of experience), because if a change must **touch five places**, the model **reliably finds all five**, whereas the human fixes four and **spends hours debugging** before finding the forgotten fifth. He then questions the **"downshouters"**: do they live in a **different universe**? Are they using **old, weak models**? Is there a **skill issue** he doesn't see because his **mental habits and communication** fit well with these tools' "handles"? An issue he considers important to settle, since "**billions of dollars would be wasted on misdirected token spend**." His recipe, "very simple": **"Be clear in your thinking, tell the model what you want with precision, and good things happen"** — closing with: "what am I missing here?" To be read as a **pro-LLM counterpoint from a historic figure of open source** to the recurring debate on the (de)valuation of coding agents — echoing the "skill issue" and specification discipline (cf. [[martignole-token-manifesto-2026-07-17]]), and forming a diptych with **Linus Torvalds'** doctrinal pro-AI-tool stance on behalf of the Linux kernel ([[torvalds-llm-outil-kernel-2026-07-14]]).
#Eric S. Raymond#ESR#esrtweet
Eric S. Raymond (ESR, @esrtweet sur X) — développeur · hacker et essayiste américain · **figure historique du mouvement open source**. Né le 4 décembre 1957 à Boston (Massachusetts) ; paralysie cérébrale de naissance · enfance en partie au Venezuela puis en Pennsylvanie. Auteur de l'essai très influent **« The Cathedral and the Bazaar »** (1997, livre 1999) · qui oppose le modèle « cathédrale » (développement centralisé et fermé) au modèle « bazar » (décentralisé et ouvert, à la Linux) ; il a **popularisé le terme « open source »** (contre « free software ») et contribué à convaincre **Netscape** d'ouvrir son code (naissance de Mozilla). **Co-fondateur de l'Open Source Initiative (OSI)** en 1998 · président jusqu'en 2005. A édité le **Jargon File** (*The New Hacker's Dictionary*) · maintenu des projets comme **Fetchmail** · écrit **« The Art of Unix Programming »** (2003). Se revendique **libertarien** · défenseur du port d'armes · ceinture noire de taekwondo ; commente régulièrement tech · politique et open source sur X. Se présente ici comme codeur « très · très bon » avec **~50 ans d'expérience**. (Post X personnel ; date de publication : 2026-07-08 ; date d'ajout à la veille : 2026-07-17.)
First-rate technical account by **Jarred Sumner**, creator of **Bun** (JS/TS runtime, >22M downloads/month), on the **complete rewrite of Bun from Zig to Rust in 11 days** (May 3→14, 2026) driven by **Claude** — an exceptional case study in AI-assisted software engineering **at industrial scale**. Motivation: a recurring class of bugs (use-after-free, double-free, leaks) arising from the mix of GC-managed memory (JavaScriptCore) and manual memory (Zig); in **safe Rust**, these bugs become **compile errors** with automatic cleanup (`Drop`/RAII) — "a better feedback loop than a style guide." Rejecting the dogma that "a rewrite is always a bad idea" (a year of bugfix freeze for 3 engineers), Sumner chooses a **mechanical port** (preserve the architecture, minimal behavior change) validated by the **existing test suite, written in TypeScript and therefore language-independent** (60,624 tests, 1.39M `expect()` assertions, 0 tests removed, 6 platforms). The harness: **~50 dynamic workflows** in **Claude Code**, *write → 2+ adversarial reviewers → apply* loops, up to **64 Claude instances in parallel** (4 worktrees × 16), with **PORTING.md** + **LIFETIMES.tsv** generated in preparation. Numbers: **6,502 commits** (peak 695/h, 58/min, ~1,300 lines/min), final diff **+1,009,272 lines**, ~16,000 compile errors treated as a queue, **5.9B uncached input tokens + 690M output ≈ $165,000**. Key methodological levers: **adversarial review** (a second Claude, separate context, sees only the diff, tasked with finding why it's wrong — catches subtle bugs that are *semantically* different but *syntactically* identical) and the principle **"fix the process that generates the code, not the code by hand."** Model used: a pre-release of **Claude Fable 5** (Mythos class). Since the merge: **11 rounds of Claude Code security review**, 24/7 coverage-guided fuzzing (100B executions → ~15 PRs), **4% `unsafe` code** (78% on a single line), **19** known regressions fixed. In production: Claude Code v2.1.181, the first release on Bun-in-Rust, **+10% faster startup on Linux**. Disclosed upfront: **Bun was acquired by Anthropic in December 2025**.
#Bun#Jarred Sumner#Zig-to-Rust rewrite
Jarred Sumner (créateur de Bun ; travaille chez Anthropic depuis le rachat de Bun en décembre 2025)
An essay by Jean-Paul Paoli (*The Intelligence Fabric*) that shifts the fear of AI at work: the real danger is not **replacement** (the job that disappears) but the **silent unraveling** of team bonds while *everyone stays employed*. Thesis: when every employee makes AI their **first confidant and collaborator**, three "threads" of the organizational fabric come undone without layoffs — **peer-to-peer bonds** (the transfer of tacit knowledge from junior to senior short-circuited), the **manager-employee bond** (early warning signals disappear, the manager becomes "the last to know instead of the first") and **professional judgment** (people stop training those who know how to *do* the work and assess whether the machine is wrong). Paoli names the phenomenon **shadow intimacy** (by analogy to *Shadow IT*) and prescribes not a ban but a deliberate "re-weaving," thread by thread. Domain: management, organizational transformation, AI at work, emotional dependency on models.
X thread (illustrated thread) by **Thariq Shihipar** (Claude Code team / Anthropic): a *field guide* to getting the most out of **Claude Fable 5**. Central thesis borrowed from Korzybski — *"the map is not the territory"*: the **map** = what you give Claude (prompts, skills, context); the **territory** = where the work happens (codebase, real-world constraints); the gap between the two = the **unknowns**. Fable is *"the first model where the quality of the work is bottlenecked by my ability to clarify its unknowns"*. The article provides a **4-quadrant framework** (known knowns / known unknowns / unknown knowns / unknown unknowns) and a **toolkit of techniques** ordered in time (before / during / after implementation) — blindspot pass, brainstorms & prototypes, interviews, references, implementation plan, implementation-notes, pitches & explainers, quizzes — each with example prompts. Domain: prompt engineering, coding agents, methodology for working with AI, HTML artifacts.
Short note from Simon Willison (weblog) relaying two tips heard during a *Fireside Chat* at AIE with Cat Wu and Thariq Shihipar (Claude Code team): **let the model (Fable, and to some extent Opus) exercise its own judgment rather than dictating rules to it** — illustrated with the decision of whether to write tests. Second tip, from Jesse Vincent: to **save precious Fable tokens** (ahead of an imminent price increase), ask Fable to **delegate small tasks to less powerful models**, letting it judge which one. Willison shows the exact prompt used (« *use your judgement to decide an appropriate lower power model and run that in a subagent* ») and the **memory file** that Claude Code wrote in response. Domain: prompt engineering, coding agents, token economics, multi-model orchestration.
#Model judgment#delegation to subagents#model override
Agent guide (Thinkroom, Kieran Klaassen's platform) documenting the **Compounding Knowledge Lifecycle** of the compound-engineering-plugin (Every): how a lesson learned once "keeps paying off" — captured, stored, retrieved, and kept true. Describes the anatomy of a *learning* (`docs/solutions/`), its capture via `/ce-compound`, the memory map (durable vs ephemeral), *grep-first* retrieval (learnings-researcher) wired into 5 skills at decision points, and the three counterforces that keep memory from lying. Directly relevant: it is the doctrine behind this repo's `docs/solutions/` convention. Domain: compound engineering, agentic knowledge management, skills.
**Recurring report from Mozilla**, *The state of open source AI*, **v1.0.1, July 2026**, introduced by a letter from **Raffi Krikorian** (CTO): seven sections, an interactive site, and a downloadable report. Thesis stated in the title of Section 1: *« The model layer has commoditized. Value accrues to the harness above it. »* **Capability state**: on the *Artificial Analysis Intelligence Index v4.1*, the best closed model scores **61** (Claude Opus 5) and the best open model **57** (**Kimi K3**), fourth overall and ahead of three of the largest closed labs; on the *Epoch Capabilities Index*, the gap is **6 points** (K3 at 156 versus GPT-5.6 Sol at 162), described as *« about one release cycle »*, with overlapping confidence intervals. **Sawtooth frontier**: open leads in frontend code (K3 at 1,679 Elo on LMArena Frontend Code Arena, six domains out of seven), contests agentic terminal work (88.3 versus 88.8 on Terminal-Bench 2.1), and cedes ground on professional knowledge work (Fable 5 leads K3 by 92 Elo on GDPval-AA v2). **Usage shift**: the share of OpenRouter tokens routed to open-weight models rose from a negligible level to a third by late 2025, then to a **majority by mid-2026**, with the seven highest-volume models all open-weight — the report itself noting that *« by request count, closed US providers still lead »*, the open lead being a token-volume lead concentrated in coding and agentic workloads. **The central contrast**: *« Open ships easy. Open deploys hard. »* — 79% of developers adding AI use open models versus 71% for closed, but only **53%** of open-model teams reach production **versus 63%**, and the gap widens with organization size (closed 54% → 73%, open 53% → 57%), which *« rules out a resources explanation »*. The stack maturity map (48 components, 9 layers) shows two consistently cold columns — **standardization** and ***enterprise readiness*** — identified as the operational gap. **Section 5**: *« The agentic harness is another user agent »*, and *« The model is eating the harness »* — on every model where both exist, the lab's own harness now wins, the 21.8-point gap having compressed to about 3. Hence the formula: *« A harness tuned tightly to one lab's weights… degrades on anyone else's model, so the tighter the tuning, the less swappable the weights underneath. Lock-in arrives as a side effect of optimization. »*
#Mozilla#state of open source AI#open weights
**Mozilla** — éditeur du rapport · avec une introduction signée **Raffi Krikorian** · *Chief Technology Officer*. Publié en **juillet 2026** (v1.0.1). Données issues de sources tierces créditées (Artificial Analysis, Epoch AI, OpenRouter, LMArena) et d'une enquête propre menée avec **SlashData** (*Mozilla / SlashData 2026 developer survey*, n = 1 410 sur la question des freins).
Analysis note **Trésor-Éco n° 391** (June 2026) from the **Direction générale du Trésor** (Ministry of the Economy), authored by **Martin Chopard, Elisa Cotet, Tristan Gantois and Eloïse Villani**. Institutional economic literature review on **the effect of AI (mainly generative) on employment**. **Three-part thesis**: (1) AI affects employment volume via **two opposing channels** — the **displacement** effect (substitution of automatable tasks) vs. the **productivity** effect (complementarity, lower costs, increased demand) — but the **aggregate effect remains, for now, weak/unmeasurable**, for lack of hindsight and adoption (≈20% of EU firms in 2025); (2) **heterogeneous effects** appear depending on **occupations** (exposure ≠ effect: everything depends on the degree of substitutability/complementarity and the **price elasticity** of demand), **workers** (biased technical progress, concerns for **young people**) and **sectors** (finance, IT, business services the most exposed); (3) in the **long term, the net effect remains uncertain** — between massive substitution (if agentic/physical AI becomes widespread) and **creative destruction** (lesson from past revolutions: innovations created more jobs than they destroyed). **Public policy** conclusion: support the transition (training, mobility — the "Osez l'IA" plan, France 2030) and **invest in AI to avoid falling behind** in international competition. Extensively sourced corpus (43 footnotes, estimate panels in Tables 1-3).
#AI and employment#generative artificial intelligence#displacement effect
**Martin Chopard · Elisa Cotet · Tristan Gantois · Eloïse Villani** — économistes de la **Direction générale du Trésor** (DG Trésor) · Ministère de l'Économie · des Finances et de la Souveraineté industrielle · énergétique et numérique. Directrice de la publication : Dorothée Rouzet. Le document engage la DG Trésor mais « ne reflète pas nécessairement la position du ministère ».
Third installment of Ashish Singh's « New Engineering Disciplines for the AI Era » series, devoted to **KDLC — Knowledge Development Life Cycle**: an **8-stage** life cycle for turning enterprise knowledge into an **engineered asset**, on a par with code or data. Thesis: AI initiatives fail not for lack of the right LLM choice or a deployed RAG system, but because they **do not address the underlying structure of knowledge** — « AI is only as effective as the knowledge it can discover, understand, retrieve, and trust ». The KDLC chains Discovery → Extraction → Structuring → Knowledge Graph → Embedding → Index Optimization → Retrieval Evaluation → Refresh. It contrasts **traditional RAG** (isolated documents, keywords) with the **Enterprise Knowledge Fabric** (Knowledge Graphs + Semantic Search + Vector DB + Hybrid Search), where agents understand « relationships, context, and business meaning ». Signature line: « Models provide reasoning. Memory provides continuity. Knowledge provides understanding. » Three examples (finance/compliance, software engineering, healthcare) illustrate the impact.
#KDLC#knowledge development life cycle#knowledge life cycle
Letter "Dear friends" from Andrew Ng in *The Batch* (DeepLearning.AI, issue 359) on **loop engineering** applied to **0-to-1** product development. Ng shares his **3 key loops** — agentic coding loop (~minutes), developer feedback loop (~hours), external feedback loop (~days) — nested by increasing time scale, connecting *coding agent → product spec/evals → developer vision → external feedback*. Central thesis: humans retain a **context advantage** (rather than a "taste") that makes human-in-the-loop indispensable; engineers take on a partial product management role. Domain: coding agents, product engineering, agentic methodology.
In-depth opinion piece (point of view) published on **sfeir.com** on June 24, 2026, by **Didier Girard** (Managing Director, SFEIR). **Central thesis**: in 2024 everyone was betting on **AI4Business** (AI in business processes) as the great value reservoir; by 2026 the picture has **reversed** — it is **AI4IT** (AI to produce the information system: code, SDLC, software factory) that is creating **measurable** value. The article *grounds* this thesis in the firm's tech watch: AI4Business disappointment (the MIT study "95% of pilots without ROI," contested but revealing; an **organizational** blockage / Mollick's Hayekian problem) versus quantified AI4IT evidence (Salesforce, Intercom, Raiffeisen, AWS/Bedrock, Atlassian, DORA). Mechanistic explanation: **code verifies itself** (compilation, tests, CI) whereas business processes have neither a compiler nor an immediate feedback loop. **2027 budget consequence**: a **CapEx→OpEx** shift, token price dynamics (rising peak — Fable 5 at 2× Opus — vs inference ÷280 and downward pressure from open weights/desktop), and **AI FinOps** driven by **cost per outcome**. Closes with **4 recommendations for the COMEX**.
#AI4IT#AI4Business#reversal
**Didier Girard** — Managing Director (CTO / DG) de **SFEIR** · ESN française (~1 000 personnes, France · Belgique · Luxembourg · Suisse). Auteur de l'article ; voix éditoriale du cabinet sur la transformation IA des DSI.
Benchmark announcement from **Artificial Analysis** (independent AI model evaluation platform, via X/Twitter + model page): **GLM-5.2** from **Z.ai** (Zhipu AI, @Zai_org) becomes **the leading open weights model** and climbs to **#3 in the overall ranking** of **GDPval-AA**, a real-world benchmark for *economically valuable knowledge work* (long-horizon, multi-turn, agentic tasks). GLM-5.2 scores **1524 Elo**, behind only **Claude Fable 5 (1783)** and **Claude Opus 4.8 (1615)**, and on par with **GPT-5.5 (xhigh, 1509)**. It leads the next-best open model (**MiniMax-M3, 1408**) by a wide margin, along with numerous proprietary models: **Gemini 3.5 Flash (1357)**, **Qwen 3.7 Max (1289)**, **Muse Spark (1158)**. The tasks are genuinely agentic: **~31 turns per task** on average across **1,999 matches**. The same ranking holds on the **Artificial Analysis Intelligence Index** (1st among open weights), the **Agentic Index** (#3) and **AA-Briefcase** (#3, ahead of GPT-5.5 xhigh, behind only Fable 5). Notable highlight: an **open weights** model under **MIT license**, **MoE with 753B parameters / 40B active**, **1M-token context**, priced at **$1.40/$4.40 per 1M tokens** input/output, rivals the proprietary frontier on agentic work — a real step forward for open models.
Long-form essay by **Shubham Saboo** (X/Twitter) advancing a thesis on the Product Manager role in the age of agents: the next key skill is **not prompt engineering** but **Loop Engineering** — designing a *system that improves with every run* rather than writing the perfect prompt every time. A **loop** is a repeated cycle: change what shapes the agent's behavior → run it → evaluate the output → keep the change if quality rises, revert otherwise → **compound the learning** so the next version starts ahead. For a PM, the entry point is not code but the **durable artifacts** that encode their judgment: PRD-review skill, customer-call *summarizer*, evaluation rubric, launch checklist, research workflow, `CLAUDE.md`, prompt template, prioritization framework. Because they are reused, these artifacts **compound in both directions** — and **drift** silently (a CLAUDE.md that keeps growing, a checklist that gets ignored…): the model has not regressed, the artifacts have drifted unwatched. A loop has **5 parts**: trigger, action, **proof**, memory, **stop condition** (the most critical). **Evals** become PM work (testing the artifact against known examples: 3 good / 3 bad PRDs, 5 understood calls, 2 past launches). **Memory** lives on **GitHub** (the repo becomes "product memory": commits, diffs, eval results, decision log, rollback). Recommended first loop: a **weekly product signal loop** (every Friday). Taste remains central — but it now needs **proof**. Cites Boris (creator of Claude Code): "he no longer writes prompts, he writes loops."
Podcast interview « À la French » (French-language tech channel, recorded at DevSummit) with Mathieu Grymonprez, Global CDO of the Adeo group (Leroy Merlin, Obramat, Weldom). How a century-old family retail group embraces the agentic AI wave: culture vs structure, accountability, token cost and FinOps, enterprise intelligence lock-in, company memory and agent orchestration. Domain: digital transformation, agentic AI, retail, IT strategy.
#Agentic AI#digital transformation#CDO
Mathieu Grymonprez (Global CDO, groupe Adeo) — invité ; Jean-Baptiste Kempf · Steeve Morin · Mehdi Medjaoui (hôtes du podcast « À la French »)
LinkedIn post by Fred Plais (CEO of Archie, ex-Platform.sh): AI made engineers so fast that the **bottleneck moved upstream**, to a place nobody is watching. With execution no longer the slow part, the thinking time that used to exist "while the code was being built" has vanished — the right vision now has to be formed and the right decisions made in a fraction of the time. Two rare profiles are emerging: the one who can **articulate a vision precise enough** for an agent to execute without derailing, and the one who knows how to **orchestrate agents** (anticipating their failures, chaining them, catching an error before it propagates). Hiring for "code output" is becoming obsolete: that is precisely what has stopped being rare. Final thesis: "thinking clearly was always the job — speed just made it impossible to fake".
Article by **Paul Sawers** published on **The New Stack** on **June 16, 2026**, about the **suspension by Anthropic** — *"on the very day it was scheduled to go live"* — of the billing split meant to separate **Agent SDK** usage from Claude subscription limits. **Anthropic's cited message**: *"We're pausing the changes to Claude Agent SDK usage described below. For now, nothing has changed."* **The article's contribution is not the announcement but the surrounding context**, in three circles. **Circle 1 — Anthropic's week**: on June 9, the release of **Fable 5 and Mythos 5**, the first generally available Mythos-class models with hardened cybersecurity safeguards; a few days later, a **US government export control directive** forces Anthropic to **withdraw both models for all its customers worldwide**. The pricing suspension is read as *"a little good news"* in this context. **Circle 2 — collateral damage from the timing**: companies that had already passed the change on to their own customers find themselves caught out; **Conductor**, a multi-agent coding tool built on the Agent SDK, has to issue a denial (*"Anthropic has delayed the subscription updates to Claude plans"*). **Circle 3 — the underlying tension, which extends beyond Anthropic**: a quote from **Boris Cherny** (head of Claude Code) in April, during an earlier restriction, stating that subscriptions *"weren't built for the usage patterns of these third-party tools"* — an admission that **flat-rate plans and open-ended agentic usage don't mix**; **GitHub** settled the matter the same way, removing in June **Copilot**'s flat-rate *premium requests* model in favor of **token-based billing**, despite protests. Added to this, **the same week**, a **proposed class action** was filed in a California federal court, alleging that **Max** tiers fall well short of the usage multipliers advertised for intensive coding sessions. Anthropic does not say when a revised approach will arrive, only that it *"works to update the plan to better support how users build with Claude subscriptions."* **The author's final take**: between government pressure on Fable and Mythos, a planned **IPO**, and **rumored price cuts at OpenAI**, Anthropic is trying to **keep its developer base on its side** — and the suspension is, for now, a means to that end.
#Anthropic#Claude Agent SDK#Claude subscription
**Paul Sawers** — journaliste tech · signe ici pour **The New Stack**. Registre de **presse spécialisée** : l'article ne relaie pas seulement l'annonce · il la replace dans une série (les changements de facturation successifs d'Anthropic) · la compare à un précédent sectoriel (GitHub Copilot) et l'articule à trois pressions concomitantes (export control, IPO, concurrence). Sourçage explicite et attribué — le billet de Zed · l'analyse de Matthew Diakonov · le post de Conductor · une déclaration antérieure de Boris Cherny.
SFEIR article (in French) that formalizes an **AI-driven SDLC in 11 phases (0 to 10)** and argues that the industry is converging toward it. Starting observation: in 2025, organizations added AI tools without transforming their operating model — producing a paradox of « everything changes… and nothing changes » (execution speed multiplies without proportional gain). The real answer is not the choice of tools but the **redesign of the cycle** for machine execution. The SFEIR cycle rests on **three immovable human gates** (Define, Plan, Ship), automatic phases between them, and **two capitalization moments** (Compound-1 pre-deployment, Compound-2 in production) that turn lessons into reusable rules. Three principles: **AI executes** (complete artifacts + proof of execution, never trusting the agent's own claims), the **human retains control of intent**, the **system learns cumulatively**. Measured results (redesign 6 months→1 day, **−30% of iterations** after ten cycles) and claimed convergence with ADLC, Google, and DORA 2025.
**Skill** entry (not an article): `grill-with-docs` by Matt Pocock is a structured interview technique that "grills" an architecture plan by methodically confronting it against the project's business vocabulary (the `CONTEXT.md` glossary) and already-documented decisions (ADRs). Rather than rushing into implementation, it challenges assumptions one by one through a question/answer dialogue, cleans up terminology, checks consistency against the actual code, and captures decisions on the fly in the right artifacts. An upfront-design skill, inspired by Domain-Driven Design.
Case study published by the **Cornell AI Innovation Hub** (June 15, 2026): how a two-semester collaboration between the AI Hub, graduate students, and Cornell's Treasury team turned a time-consuming manual investigation into an AI tool that **recovered $100,000** in unidentified payments on a first batch. A successful **AI4Business** use case (financial process) that illustrates the **Leader-Lab-Crowd** framework of **Ethan Mollick** almost point by point: the **AI Hub** plays the role of the **Lab** (a central, ambidextrous team of technologists plus students); **Treasury** (Cheryl Barnes, Marie Graves…) is the **Crowd** carrying business knowledge and the real pain point; and the **$100,000** constitutes the **visible reward** (vivid win) that anchors adoption — exactly the incentive lever Mollick considers decisive. Key method: **"context first, then plan, then build"** via **Claude Code Plan Mode**, a chain of **fuzzy matching → Gemini Enterprise Web Search → Claude synthesis**, all within the governed **Cornell AI Gateway**. *"The $100,000 is a start."*
#Cornell AI Innovation Hub#unidentified payments#payment reconciliation
**Pete Stergion** — Desktop Engineer au Cornell AI Innovation Hub · co-tech lead du projet (avec Phil Williammee). Article institutionnel signé de l'AI Hub.