Ethan Mollick's (Wharton) consistency test: we'll know AI labs truly believe in ASI the day they dissolve their *Forward Deployed Engineering* (FDE) teams. Public debate with roon (OpenAI) on LinkedIn: roon objects that this is a **hayekian problem** (intelligence does not automatically resolve organizational information flow) and revives the term "**Gentle singularity**". Consensus in the comments: technology is the easy part; internal politics / legacy workflows / contractual liability are the real bottleneck. Marker phrase: *"Curing cancer might be easier than replacing Accenture"*. Epistemic **East Coast vs West Coast** opposition on the trajectory of AI adoption.
#ASI (Artificial Super Intelligence)#Forward Deployed Engineering (FDE)#AI consulting
Manifesto-style article by **Thariq Shihipar** (Engineer & serial entrepreneur, Claude Code team at Anthropic) announcing a **change in the default output format for agents**: replacing **Markdown with HTML**. Thesis: Markdown has been the dominant format between humans and agents (simple, portable, editable, readable) but has become **a bottleneck** as agents produce longer and richer artifacts (specs, plans, reports, code review). Beyond ~100 lines, no one reads a Markdown file anymore. HTML solves six limitations simultaneously: **information density** (tables, CSS, SVG, scripts, canvas, images), **visual clarity** (navigable, mobile-responsive layout), **ease of sharing** (an S3 link directly openable in a browser), **two-way interactivity** (sliders, knobs, "copy as JSON/prompt" buttons to loop back into Claude Code), **native contextual ingestion** (Claude Code reads the codebase + MCP Slack/Linear + git history + Chrome) and **enjoyment** (the author explicitly claims *"it's joyful"*). Five canonical uses detailed: (1) **specs/plans/exploration** in a comparative grid, (2) **PR review** with inline annotated diff, (3) **design & prototypes** with animation sliders, (4) **reports/research/learning** (the author had a prompt-caching explainer generated from git history), (5) **custom throwaway editors** (drag-and-drop of Linear tickets, feature-flag editors, side-by-side prompt-tuner) that produce a re-injectable "copy as markdown/diff/JSON" export. Explicit anti-pattern: *"I'm a little bit afraid that people will read this article and turn it into a /html skill"* — the author **rejects premature skill-ification**, recommending prompting from scratch ("make a HTML file"). Pragmatic FAQ: token cost absorbed by **Opus 4.7**'s 1MM context, 2-4× longer generation, noisy HTML diffs (a real downside), style kept in check via a reference HTML design system.
#HTML#Markdown#output format
Thariq Shihipar (Engineer & serial entrepreneur, équipe Claude Code chez Anthropic — site : thariqs.github.io/html-effectiveness ; X : @trq212)
Editorial by Andrew Ng in The Batch n°352 of May 8, 2026 — **"There Will Be No AI Jobpocalypse"** — which dismantles the narrative of mass unemployment caused by AI, drawing on the **healthy 4.3%** US unemployment rate and robust tech hiring. Ng identifies **three drivers** of the jobpocalypse narrative: **(1) tech incentives** — AI labs benefit from presenting themselves as transformative-disruptive (funding rounds, valuations, talent); **(2) pricing power** — vendors charge **$10,000+/year** to enterprise clients by **anchoring their pricing on the salary of the replaced employee**, rather than on traditional SaaS pricing (per seat / per usage); **(3) corporate messaging** — companies reframe their layoffs as *"AI efficiency"* rather than acknowledging the **pandemic-era overhiring** of 2020-2022. Honest acknowledgment: *"AI disrupts work"*. But Ng flips this into **"AI jobapalooza"** (a play on Lollapalooza) — job creation in AI engineering and adjacent fields with evolving skill sets. Implicit tension with **Amodei** (50% of white-collar jobs eliminated by 2030) — Ng points out, without naming him, that **Anthropic benefits from promoting this narrative** (tech incentives). Published **the same day** as **Wallace-Wells's "AI Populism" NYT Magazine** piece: a perfect mirror reading — Ng = cold economic analysis / Wallace-Wells = popular panic. Pricing-power convergence with **Bain's "$100B cross-system labor"** (same thesis: pricing anchored on salaries).
#Andrew Ng#The Batch#DeepLearning.AI
Andrew Ng (fondateur DeepLearning.AI, Stanford, ex-Google Brain, ex-Baidu, ex-Coursera)
**David Wallace-Wells** publishes in the **NYT Magazine** on **May 8, 2026** a major political pivot article (~16 min audio) that formalizes and names the populist backlash against the AI industry: ***"A.I. Populism Is Here. And No One Is Ready."*** Scathing subtitle: *"Silicon Valley oligarchs worried about the risks their technology posed to the world. They forgot about people."* **Pivot thesis**: AI founders (Altman, Amodei, Musk, Zuckerberg, Hassabis) spent a decade obsessed with the **existential** risks of their technology while **neglecting the political risk** of a human backlash — which they thought *"wouldn't materialize in time, would be quickly outmaneuvered by machine intelligence or could be bought off by talk of basic-income payments or thin promises of curing cancer"*. **The backlash struck literally**: April 2026, a **Molotov cocktail** thrown at Altman's property in San Francisco, then a few days later a **firearm attack** on his house. Wallace-Wells picks up **Jasmine Sun**'s phrase (NYT Opinion 2026-04-30, already on file): ***"A.I. populism's warning shots"*** — an analogy with the assassination of UnitedHealthcare CEO Brian Thompson by Luigi Mangione. **Five labs as new faces of American oligarchy**: *"a fearsome concentration of economic and social power producing a self-compounding pattern of extreme inequality"* — Sam (Altman), Dario (Amodei), Elon (Musk), Mark (Zuckerberg), Demis (Hassabis), nearly all billionaires, *"several of whom are widely described as sociopaths"*. **Shock statistics**: Pew Research 2025 — **50% of Americans more concerned than enthusiastic**, **only 10% more enthusiastic**; recent Quinnipiac — **only the >$200k income bracket holds an optimistic view of AI for daily life**; Heatmap polling — data-center support/opposition swing from **+2 points (Sept 2025) to −24 points (Feb 2026)**, a **26-point swing in 4 months**; Northern Virginia 2023-2025 — **69-point swing against data centers** (+45 → −24). **Loudoun County**: data centers will generate **$1.3B out of $2.9B** in tax revenue in 2027 (~45%). **Investment-housing asymmetry**: the United States **spent more on AI infrastructure than on single-family homes** in 2025, **10× more data centers than Germany** (#2), **20× more AI investment than China** (#2), amid a **housing shortage of 10 million missing units**. **Central Ted Chiang quote (BuzzFeed 2017)** invoked: *"When Silicon Valley tries to imagine superintelligence, what it comes up with is no-holds-barred capitalism."* **Dario Amodei quote (Anthropic, 2024)**: *"People outside the field are often surprised and alarmed to learn that we do not understand how our own A.I. creations work. They are right to be concerned: this lack of understanding is essentially unprecedented in the history of technology."* **Political pivot flagged**: the **White House** proposes forcing a **federal review of all new proprietary models before release** — a major shift after a pro-industry stance. **Catalyst**: **Anthropic**'s public refusal in **April 2026** to release **Claude Mythos**, a model capable of *"find[ing] and exploit[ing] security vulnerabilities in every tested piece of software, including those used in critical pieces of global I.T. infrastructure"* (already on file via the **AISI UK GPT-5.5 / Mythos** entry, 2026-04-30). **Dean Ball quote (original architect of Trump AI policy, Palantir Foundation Yale conference)**: *"This giant acid vat which would dissolve the mediating institutions most Americans see as society. It will not be A.I. in government. It's going to be A.I. as governments."* **Jeffrey Ding concept**: *"diffusion marathon"* (vs. winner-take-all race) — AI as a *general-purpose technology* (steam, electricity, internet) where **diffusion** matters more than the **state of the art**. **Pivot conclusion**: *"We still know the names of the robber barons, and live still somewhat in their shadows. But we are not their serfs. Are we sure A.I. will be different?"* Major relevance for the 2026 dossier: **conceptual formalization of the political backlash** anticipated by Sun (April) and flagged by Ng The Batch (Molotov cocktail at Altman's, ~$64B in blocked data centers, Maine 20MW+ moratorium). To be mobilized for AI-geopolitics executive briefings, regulatory debates, strategic presentations on the societal and political risks of AI, and FR/Europe framing of AI's political feedback loop.
#David Wallace-Wells#NYT Magazine#AI Populism Is Here
**David Wallace-Wells** — NYT Magazine staff writer · journaliste américain reconnu pour son travail sur le climat (livre *The Uninhabitable Earth* 2019, ancien deputy editor de *New York Magazine*). Connu pour des essais long-form combinant reportage · prospective et critique politique des technologies. **Article publié dans le NYT Magazine** le **8 mai 2026** (édition online, ~16 minutes audio) · section politique-tech.
Podcast by Greg Isenberg × Meng To (designer, founder of Design+Code, creator of the products Aura / New Form / Dream Cut) on **`design.md`** — Google's open-source convention, equivalent to `agents.md` / `skills.md` / `soul.md` but **for the design system** (typography, colors, spacing, WebGL/Three.js animations, reveal rules). Central idea: carrying the "**soul of design**" in a markdown file that is handed to an agent (Claude Code, Codex, OpenClaude, Gemini, Stitch, Aura, V0, Lovable, Cursor) to preserve **cross-medium consistency** (web, mobile, Replit slides, Hyperframes/Remotion motion design). Triad taught: **HTML = finished dish, design.md = recipe, skills = ingredients** (typography, lasers, skeuomorphic, 3D skills — 63 in New Form). Major diagnosis: **design drift** on one-shot workflows (`v0`, Lovable, Framer) that start strong then drift into generic output. Meta-message: *taste* is the only remaining **moat** — *"if something looks like another thing, its value drops by 10× to 100×"*. Workflow: **Reference → Design.md → Generate → Inspect → Systemize → Iterate (up to 1000+ prompts) → Remix → Expand → Export**. Critique of **purple gradients** ("you just run") as the generic post-vibe-coding baseline. Meng To claims to have spent ~$500,000 in tokens, run 1,000–10,000 iterations per product, and managed 4 products in parallel solo.
#design.md#Google#design system
Greg Isenberg (host — podcast Late Checkout / The Greg Isenberg Show, 12 mai 2026 livestream workshop ideabrowser.com) ; **Meng To** (guest — designer, fondateur Design+Code 2014, créateur Aura / New Form / Dream Cut, autodidacte parti à 18 ans, dropout, francophone d'origine canadienne)
Televised debate on BFM Business (*Tech & Co Business* program, "The Debate" segment, 17 minutes) with **Rémi Jacquet** (CEO of Cast Software France, founder in 2023 of a think tank of about a hundred CIOs on the impact of generative AI on development, partnership with Cigref / Epita) and **Didier Girard** (CTO and CEO of **SFEIR**, a French IT services company (ESN) of about 1,000 people). Strong theses: *"writing code has become an anti-pattern"* (Girard), AI produces code of higher quality than most engineers and is *"2 to 10× more efficient"* — this is a reality, but the profession is not disappearing. The developer becomes a **conductor / agent manager / arbiter**, 14-day sprints are replaced by one-hour to half-day ***bolts***, the **Pizza Team** (8-10 people) no longer works in the agentic era, a new role is emerging — the ***product engineer*** —, the lifespan of a skill drops from **10 years to 1 year**, and **token** consumption becomes the *fuel* of value creation (NVIDIA anecdote allegedly paying bonuses in tokens, taxi driver metaphor for a driver who doesn't consume gas). SFEIR claims *"1,000 people, production capacity of 10,000"*. On the Cast side: positioning on ***harness engineering*** (deterministic vs probabilistic AI, control and guardrails), aligned with Sylvain Duranton's (BCG X) op-ed in *Les Échos* stating that *"an agent = an LLM + harnesses"*. Historical pivot: 2024 *prompt engineering* → 2025 *context engineering* → 2026 *harness engineering*. Key warning: *"the stronger AI becomes, the more we let our guard down — the more risks there are"* (Jacquet). Pivotal role of HR in the transformation, complete overhaul of the SDLC, recommendation to juniors to solidify software architecture fundamentals (*"code is the score, you need to master the symphony"*).
Interview with Boris Cherny (creator of Claude Code, Anthropic) at a Sequoia event (hosts: Asia, Lauren Reader). Cherny states ***"coding is solved"***: he himself has written **0 lines of code** since late 2025, the model writes **100%**, *"a few dozen PRs/day, 150 PRs in a single day record"*. Account of the genesis of Claude Code (Anthropic Labs incubator late 2024, Mike Krieger in charge of round 2, pre-PMF build *"for the next model"*, a first release that didn't take off, **exponential growth started with Opus 4 in May 2025**, accelerating with each new model 4 → 4.5 → 4.6 → 4.7). Current personal setup: **"most of my work I do from my phone"** (iOS), 5-10 sessions, **"a few hundred agents going, a few thousand at night"**, **`/loop` is the future** (cron + repeat jobs, agents babysitting CI, rebasing PRs, clustering Twitter feedback). **Routines** = the server-side equivalent, running with the laptop closed. SaaS outlook: no apocalypse, but a **reshuffling of Helmer's 7 Powers framework** (switching costs ↓, process power ↓, network effects/scale economies/cornered resources unchanged) and **10× more disruptive startups** over the next 10 years. Pivot analogy: the **Gutenberg press** (10% literacy in the 1400s → 70% over the following centuries, books 100× cheaper within 50 years), *"software will be similarly democratized, but faster than 50 years"* — *"the best person to write accounting software is not an engineer, it's a really good accountant."*
#Boris Cherny#Anthropic#Claude Code
Boris Cherny (créateur de Claude Code, Anthropic) interviewé par Lauren Reader (Sequoia) avec introduction d'Asia (Sequoia).
LinkedIn Pulse op-ed by Alexandre Frizzo after a year of daily use of Claude Code, offering a **nuanced assessment** rare in the 2026 corpus — productivity **multiplied by 3-5×** in his case (consistent with Wescale, and in line with the median of committed practitioners; the elite tail goes much higher, cf. Cherny *few dozen PRs/day + 150 PRs record* and Karpathy *"peaks much higher than 10×"*), but **hidden cognitive costs** acknowledged. Pivot thesis: ***"the new bottleneck is supervision"*** — the job has changed shape, one no longer *writes* code, one *decides* about code generated by agents. Gains: 3-5× output, previously infeasible projects now achievable (yak-shaving, boilerplate), near-zero cost of experimentation. Acknowledged losses: ***"writing muscle"*** atrophied (manual code now feels *effortful*), **rare deep flow state** (constant context-switching between supervisions), **diminished ownership satisfaction** (*"code is good, but isn't quite mine"*). Unresolved tensions: **FOMO** (*"every hour I'm not at the keyboard is an hour an agent could be earning for me"*), **review quality** at 3-5× volume, **skill atrophy**. Statistics cited: median 3-4h effective coding out of an 8h day, **23 min** context recovery per interruption (Gloria Mark study), 15-25 min flow entry, 500% productivity in flow (McKinsey). Exemplary epistemic position: simultaneously rejects the *"AI is bad"* narrative and uncritical enthusiasm. A welcome counterweight to Cherny's *"coding is solved"* (2026-05).
#Alexandre Frizzo#LinkedIn Pulse#year with Claude Code
Alexandre Frizzo (auteur LinkedIn Pulse, identité tech non précisée par le post au-delà du nom — auteur d'une tribune one-year retrospective Claude Code).
Methodology article by Antoine HABERT (WEnvision) that formalizes **PROJ-AI**: a lightweight methodological layer so that collective projects become transferable rather than dying with their deliverable. Structuring triad: a **version-controlled git repo** (single source), an **AI agent** (Claude Code, Cursor) that reads the doctrine at every session, and a **markdown doctrine** specifying decision protocols and agent behaviors. Six directory zones (DOCS/, IDEAS/, DR/, OUT/, DOCTRINE/, AGENT/), operational **DPEV** cycle (Decide → Promise → Execute → Verify), Decision Records scored across 7 dimensions, dual interface (business Studio + tech CLI/IDE), five agent directives, and a shared **proj-ai-commons** library that bootstraps a project in 30 minutes vs. 1 week. Metrics across 3 engagements: onboarding **3 weeks → 2 days**, structural decisions tracked **30% → 100%**, architecture doc compilation **6 weeks → continuous**. Central aphorism: ***"The project is not a byproduct of the deliverable. The project IS the deliverable."*** Explicit stance: technology 20%, **team discipline 80%**.
#Antoine HABERT#WEnvision#PROJ-AI
Antoine HABERT (WEnvision — cabinet français de conseil en stratégie et IA agentique).
Doctrinal article by Addy Osmani (Google) that establishes a foundational distinction for the 2026 debate on AI and cognition: **Cognitive Offloading** (healthy — delegating the *how* while retaining judgment over results) vs **Cognitive Surrender** (toxic — accepting AI output wholesale without forming parallel reasoning, *"borrowing the model's confidence as substitute for personal understanding"*). Solid scientific grounding: the **Shaw & Nave (Wharton/UPenn)** study of 1,372 participants — **73% accept demonstrably wrong AI answers**, with confidence rising despite a 50% error rate. **MIT *Your Brain on ChatGPT*** — reduced neural connectivity among AI-assisted writers. **Anthropic Skill-Formation** — engineers using AI to generate code score **17% lower** on comprehension versus those using it for conceptual inquiry. Four concrete examples of surrender (reviewing 600-line PRs on surface signals, shallow debugging, architectural decisions made without reasoning, degraded learning). Five personal heuristics (pre-generating expectations, junior-engineer-standard review, adversarial prompting, fatigue awareness, verification of the source of confidence). Six structural guardrails (verification exit criteria, anti-rationalization tables, **PRs ~100 lines max**, interrogative over generative mode, scaffolded friction, **regular solo keyboard time**). Two new concepts: ***Comprehension Debt*** (the growing gap between total codebase volume and human understanding) and ***Mutual Amplification*** (a cooperative prompt-refine loop vs surrender-delegation). Pivot thesis: ***"the choice between thinking with AI versus not thinking at all remains entirely human"***. A structural and operational counterweight to *"coding is solved"* (Cherny 2026-05) and an analytical complement to Frizzo (2026-05-05).
Addy Osmani (Software Engineer at Google, Cloud + Gemini, ex-Chrome — déjà au dossier veille avec *Agent Harness Engineering* 2026-04-19, *How to write a good spec for AI agents* 2026-01-13, *Conductors to Orchestrators* 2025-11-01).
Medium op-ed by **Hryhorii Tatsyi** (CTO, **Raiffeisen Bank Ukraine**, ~900 IT engineers) reporting a **12-month longitudinal study** (May 2025 → April 2026) on the real impact of generative AI in a large European bank. Pivot thesis: ***"AI didn't make our engineers just faster. It made them different."*** Unlike individual accounts (Frizzo, Cherny) or meta-level ones (Curran/Intercom), this is a **quantified organizational assessment from a traditional regulated bank** — a corpus still rare in 2026. Results: **−75 people (−8% headcount, including 64 engineers)** over 12 months, yet **more code shipped, fewer incidents, improved security**; AI adoption **62% → 83%**; **68% of engineers receive ≥50% of their code via AI assistance**; **new-engineer onboarding 60-90 days → ~40 days** (consistent with Anthropic data of 82→40 days). Three emerging archetypes: (1) **Copilot-only** +10-25% on PRs, same scope; (2) **Multi-tool** story points ×1.5-3, cross-repo scope +50-80%; (3) **Claude on corporate stack** code volume ×4.5, radically expanded scope. **Seven AI products built** that did not exist before: Service Knowledge Hub (57 microservices, 83 releases/month), Mobile Android workflow CI plan/implement/test, AI Agent Portal (2,085 users / 649 MAU in 87 days, MCP generation via OpenAPI specs), Shift-left Security Plugin (−82% exposed secrets), DevPortal Backstage + Kubernetes diagnostics agents (−68% critical incident resolution time), DRAIF MCP text-to-SQL Data Lake with 10,000 tables (embedding fine-tuned 2× OpenAI), Call Evaluation (>97% transcription accuracy, voted best product in the Raiffeisen group). Stability: **blocking incidents −70%, critical resolution −68%, high-severity security alerts resolved +155%**. Central strategic insight: ***"AI expanded our production possibility frontier, and we deliberately allocated the freed capacity"*** — AI does not do the same thing faster, it shifts **what one can decide to do**. The evaluation question to reframe: not *"by how much % did existing KPIs increase"* but ***"what your engineers built that didn't exist before"***. AI lifts underperformers to baseline more than it accelerates top performers; **senior architects return to active development** after years away from it. Major relevance for banking/insurance/regulated-sector executive committees (Raiffeisen = bank, Ukraine = wartime context + operational resilience).
#Hryhorii Tatsyi#Raiffeisen Bank Ukraine#CTO bank
**Hryhorii Tatsyi** — CTO de **Raiffeisen Bank Ukraine** (filiale ukrainienne du groupe bancaire autrichien Raiffeisen Bank International, RBI). Auteur Medium @milhibisidek. Profil discret côté visibilité publique (25 followers Medium au moment de la publication) · mais position institutionnelle de premier plan : il dirige une organisation IT d'environ 900 ingénieurs dans une banque systémique opérant en contexte ukrainien (économie de guerre depuis 2022, résilience opérationnelle critique). L'article est sa première contribution publique d'envergure documentée sur cette plateforme.
GitHub repo `techygarg/lattice` that formalizes a framework of **composable skills** for installing an *engineering discipline* into AI coding assistants (Claude Code, Cursor). Distinctive three-tier architecture: **Atoms** (single-principle guardrails: clean code, DDD, security, test quality, design-first), **Molecules** (multi-step workflows composing the atoms: design, implement, refactor, fix, review), **Refiners** (guided interviews producing project-specific standards that customize the atoms' behavior). Operational pipeline `lattice-init` → `design-blueprint` → `code-forge` → `review`, with `refactor-safely` and `bug-fix` as offshoots. Three pivotal principles: *"Skills over prompts"*, *"Composability over monoliths"*, ***"Living context over static config"*** — the `.lattice/` folder grows smarter with every feature cycle. MIT, pure shell, 18 stars / 52 commits, a series of articles on martinfowler.com explaining five *collaboration patterns*. Strong convergence with Vincent *Superpowers* (2026-04-02), Habert *PROJ-AI* (2026-05-05), Wescale *Usine Logicielle Augmentée* (2026-05-03), and — the highest doctrinal convergence with no declared lineage — **Compound Engineering** by Every (Shipper/Klaassen 2025-12-11): isomorphic pipelines (lattice-init→design-blueprint→code-forge→review ↔ ce:brainstorm→ce:plan→ce:work→ce:review), living context layer (`.lattice/` ↔ `docs/plans/+solutions/+brainstorms/`), a shared design-first stance, mandatory review at the end. 2026 *coding agent harness* doctrine converges on a stable vocabulary, without direct influence.
#lattice#techygarg#composable AI skills
techygarg (auteur GitHub, identité réelle non précisée dans le README ; auteur d'une série d'articles publiée sur martinfowler.com).
**Jessica Talisman MLS** (Semantic Engineer + Information Architect, 25+ years of experience, formerly Adobe RDF knowledge graphs + formerly Amazon information architecture, founder of the **Ontology Pipeline Framework** + **Contextually LLC**) publishes on **Modern Data 101** (Substack, ~20,000 members) on **May 4, 2026** a major revision of her **Ontology Pipeline™** framework initially published in January 2025. **Pivotal thesis**: since November 2022 (ChatGPT), demand for *semantic infrastructure* has exploded but has created **massive confusion** — *"vendors offering shortcuts that bypass essential foundational work, creating liabilities disguised as assets"*. The original **5-stage** pipeline (controlled vocabulary → metadata standards → taxonomy → thesaurus → ontology → knowledge graph) remains valid but **must be completed with 2 critical additions**: **(1) Governance** as an ongoing engineering practice (not post-project documentation); **(2) AI Partnership** with a clear distinction between augment and replace. **Market diagnosis**: *"a structurally invalid taxonomy is not a taxonomy"*, *"lists are not knowledge infrastructure"*, AI-generated taxonomies sold as strategy, vendors misusing the term *"ontology"*, cookie-cutter solutions presented as methodology. **Educational crisis**: demand for semantic engineers massively exceeds the supply of trained practitioners; the gap is filled by people *"who know vocabulary without methodology"*. **Explicit normative position**: *"AI that generates a taxonomy wholesale is producing a liability disguised as asset; AI that assists trained engineers is just plain smart."* **Acceptable AI roles**: entity extraction, gap analysis, drafting candidate vocabularies for review, population/validation support. **Unacceptable AI roles**: *wholesale taxonomy generation without human validation against standards*. **Referenced standards**: SKOS, OWL, RDF, SPARQL. **Credibility**: framework validated across **6 institutions over 10 years**. **Recommendations for 3 audiences**: (a) Organizations — invest in formal education, treat knowledge infrastructure as the AI backbone, governance as ongoing, AI as an accelerator not a replacement; (b) Practitioners — competency questions before modeling, validate against SKOS/OWL/RDF, definitional difficulty signals a pause, maintenance is continuous; (c) Leaders — workforce upskilling without self-funded education, allocate resources to knowledge infrastructure as a strategic necessity, governance before deployment. **Striking quotes**: *"the work cannot be skipped"*, *"governance is the engineering practice that keeps an ontology coherent across change"*, *"teaching this is hard. Learning it is harder."* **Major relevance** for data leaders / CDOs / architects building the semantic foundations of their AI agents. To be read alongside: Seale Semantic Agent (2026-04-17) — *(Model+Harness)+(Ontology+Data) — ontology as the only moat*; Foundation Capital Context Graphs (2025-12-22); Bain part 2/5 *redesign data foundations for agent readiness* (2026-05); DORA ROI 2026 *AI-accessible internal data + healthy data ecosystems* (2026-04-21); Habert PROJ-AI six-zone doctrine (2026-05-05). Convergence with the 2026 corpus on *"data foundations as moat"*.
#Jessica Talisman MLS#Ontology Pipeline framework#Modern Data 101
**Jessica Talisman MLS** — Semantic Engineer et Information Architect avec **25+ ans d'expérience** en enterprise architecture · e-commerce systems et knowledge management. Fondatrice de l'**Ontology Pipeline Framework** et de **Contextually LLC**. Roles précédents : **Adobe** (RDF-based knowledge graphs) · **Amazon** (information architecture). Auteure de la newsletter **Intentional Arrangement** (Substack) et d'un **livre éponyme à paraître en 2026**. Le framework initial *Ontology Pipeline* a été publié en janvier 2025 et **validé sur 6 institutions sur 10 ans**.
Wescale (France) presentation formalizing the ***Augmented Software Factory*** doctrine: a software value chain entirely orchestrated by specialized AI agents across six production lines (Intent/PRD-ADR → Plan/User Stories → **human sign-off** → 24/7 Production → Independent audit verification → DevOps Deployment), where humans intervene at only two precise moments. Strong theses: the return of the **predictable V-cycle** against Scrum, realistic **3-4x** gains (not 10x), the shift from *code producer* to ***Strategic Judge*** and from *solo developer* to ***Agent Manager***, DORA metrics replacing velocity, maximum ROI on legacy modernization and costly SaaS replacement, and above all ***injected governance*** as a "near-military layer" that constitutes the central innovation and the real barrier to entry. Built by eating its own dogfood: *"What we learned building Solario on Solario."*
#Wescale#Augmented Software Factory#augmented production chain
Wescale (cabinet français de conseil tech / cloud / DevOps) — auteurs collectifs (présentation corporate, pas d'auteur individuel cité dans le deck).
Brief by **Bain & Company**, **May 2026** (David Crawford, Chris McLaughlin, Greg Fiore — part of a **five-part series on the software industry in the age of AI**), which puts the still-untapped SaaS opportunity in *cross-system labor* — the human work of coordinating across systems that AI agents can now automate — at **~$100B in the US (~$200B including Canada/Europe/AU/NZ)**. **Current capture: $4-6B (10% of the opportunity)** — so **>90% still up for grabs**. Pivot thesis: the major opportunity in agentic AI **is not to replace existing SaaS** but to **automate cross-system coordination labor** (employees pulling data from ERPs, checking inventory in a spreadsheet, interpreting free-text responses, exercising judgment). Distribution: Sales ($20B) + COGS/operations ($26B) + R&D/engineering ($6-12B) + support ($6-12B) + finance ($6-12B). **Six automation factors**: output verifiability, consequence of failure, digitized knowledge availability, integration complexity, process variability, physical world dependency. **Automation potential by function**: Customer support & R&D **40-60%**, Finance & HR **35-45%**, Sales & IT **30-40%**, Legal **20-30%**. **Strategic shift**: competitive advantage moves from *system of record ownership* (Salesforce, SAP, Workday) to ***cross-workflow decision context*** — the ability to see and act across multiple integrated systems. **Examples**: Sierra (autonomous customer issue resolution), Glean (cross-function employee request coordination), GitHub Copilot (extended beyond source control), **Cursor** (ARR doubled in a quarter, $2B). **Durable moat**: *"accumulated execution data that grows more valuable over time and becomes harder for competitors to replicate"*. **Three-phase playbook**: Assessment (six factors + market sizing) → Strategic Positioning (data assets + adjacent workflows + actual operational maps) → Execution (build/buy/partner + restructure org + redesign data foundations for agent readiness). Major relevance for CIOs/CDOs/Strategy leaders in B2B SaaS and enterprise customers: reframes the *"AI vs SaaS"* conversation as ***"AI = SaaS that finally automates coordination labor"***. To be read alongside: DORA ROI (financial framework), Tatsyi/Raiffeisen (bank case study creating 7 unprecedented AI products), Wescale (realistic 3x-4x), MIT NANDA (95% of pilots fail), Foundation Capital *Context Graphs trillion-dollar opportunity* (2025-12-22), Menlo Ventures *State of Generative AI Enterprise* (2025-12-09).
**David Crawford · Chris McLaughlin · Greg Fiore** — partners et experts Bain & Company spécialistes industrie logicielle / SaaS. Article publié en **mai 2026** sur bain.com/insights · partie 2/5 d'une série sur *"the software industry in the age of AI"* (la partie 1 traite du Rule of 40, fiche `bain-ai-rule-of-40-headwinds-tailwinds-saas-2026-04.md`).
Google whitepaper (the "Day 1" installment of a series, by Addy Osmani, Shubham Saboo and Sokratis Kartakis) mapping the transformation of the software development lifecycle (SDLC) in the age of coding agents. Thesis: the fundamental shift is not a new language but the move from writing code to **expressing intent**. The document sets out a spectrum ranging from *vibe coding* (prompting and accepting) to *agentic engineering* (AI implements under constraints, tests, and feedback loops designed by humans), with **context engineering** as the central skill, the **software factory** model (the developer's deliverable = the system that produces the code), **harness engineering** (Agent = Model + Harness), and a CapEx/OpEx economic analysis of total cost of ownership.
Major investigative op-ed by Jasmine Sun (NYT Opinion, April 30, 2026) on the *San Francisco consensus*: fear of the *permanent underclass* — a viral theory that AI could freeze economic mobility and create a class rendered useless by automation. The article documents the labs' internal dissonance (Amodei on "white-collar blood bath" and 50% of junior white-collar jobs gone by 2030; Altman 2021 → Lehane silence → white paper *Industrial Policy for the Intelligence Age* April 2026; Anthropic Institute March 2026 led by Jack Clark), the benchmarks steering R&D toward human replacement (A.I. Productivity Index, OpenAI's GDPVal: *"over 80% win rate compared to human professionals"* within a few months), corporate actions (Block/Dorsey -50% headcount with Opus 4.6 + Codex 5.3, Anthropic ARR $30B versus $9B end of 2025), and the Shor political strategy (79% of voters worried, jobs guarantee > UBI, *"They work for the bots. We work for you."*). Reference for the *AI labor 2026* dossier.
#Jasmine Sun#NYT Opinion#permanent underclass
Jasmine Sun (Ms. Sun écrit sur l'IA et la culture Silicon Valley sur Substack)
Analyst note by **Mitch Ashley**, VP and Practice Lead for *CIO & Technology Buyers* and *Software Lifecycle Engineering* at **The Futurum Group**, published on **April 29, 2026** in the *Market Coverage News* section: short format, roughly **9,500 characters**, opening with five summary bullets and closing with five watch-list items. Subject: the deal announced on **April 21, 2026** under which **SpaceX** gains the right to acquire **Cursor** for **$60 billion** within the year, or to pay **$10 billion** for a compute partnership backed by **xAI**'s **Colossus** cluster in Memphis, described as equivalent to **1 million H100 GPUs**. (A) The two-need reading: Cursor was carrying both a compute ceiling and margin compression — the company pays market-rate prices for **Anthropic**'s and **OpenAI**'s models, which it routes to its customers while competing with them via its **Composer** line; SpaceX was seeking AI revenue and a narrative ahead of an IPO targeted for June. (B) The structure reading: a $10 billion floor and a $60 billion purchase option exercisable in publicly traded stock after the listing, which, Ashley writes, *"allocates risk more honestly than a straight acquisition."* (1) For buyers, it sets a **six-month** window to re-verify zero-data-retention clauses and vendor identity. (2) For providers, it distinguishes three exposures — **Google** shielded by **Antigravity**, **AWS** dependent on Anthropic, **IBM** lightly exposed but well positioned on the governance angle. The corpus already holds [[beck-starving-genies-usage-limits-ai-coding-2026-04-03]] on the resource constraint imposed on coding tools and [[nyt-musk-promises-spacex-ipo-track-record-2026-06-02]] on SpaceX's announcements.
#SpaceX#Cursor#Anysphere
Mitch Ashley · VP et responsable des pratiques CIO & Technology Buyers et Software Lifecycle Engineering chez The Futurum Group · ancien CIO et CTO.
Product announcement published on the **Stripe** blog on **April 29, 2026** by **Dan Hill** (Product Manager, Link Consumer Product), following on from the **Stripe Sessions 2026** keynote: the launch of **Link's wallet for agents**, built on a new building block, **Issuing for agents**. **The diagnosis fits in one sentence, and it is the most important one in the text**: *"While machine payments protocols are still gaining adoption, agents need to work with the payment options sellers and consumers use today."* → **Stripe acknowledges that machine-native payment protocols are not ready, and delivers a workaround for existing rails rather than a bet on new ones.** **The mechanism**: a consumer grants an agent access to their Link wallet via a **standard OAuth flow**; the agent then issues a *spend request* and receives either a **single-use card**, or a **Shared Payment Token** — backed by the cards and bank accounts already present in the wallet. Cardinal point: *"The agent never gets access to your raw payment credentials."* The credential is **scoped** (amount, currency, merchant) and the agent must supply the **transaction context** so the human understands what they are approving — the example given in the CLI is explicit: `amount 3500`, `merchant-name "Powdur"`, `context "Purchasing the Powdur Glow Renewal Vitamin C Serum as a gift for $35."`. **The structuring constraint is temporal, and it is owned as such**: *"Today, each request requires the person's review before the credential is shared with your agent"* — **human** approval, **transaction by transaction**, on the web or in the **new Link iOS and Android apps**. Spending limits and cases where the agent would act **without additional approval** are announced, not delivered. **The second layer is the real infrastructure product**: **Issuing for agents** opens the full set of Issuing APIs to anyone building their own agentic wallet — single-use virtual cards, fund storage, spend controls, card-level permissions, **at-authorization** antifraud controls, real-time visibility. Four use cases are cited: internal spend automation, agentic cards embedded at **fintechs**, **vertical SaaS** platforms issuing cards to SMBs under their own brand, **marketplaces** whose selling agents pay suppliers and logistics. **Distribution argument**: Link claims **more than 200 million consumers**, and the article cites **OpenClaw** as an example of a personal agent that benefits. **Two reservations worth flagging up front**: per-transaction approval is presented as a design convenience when it is actually **an admission that delegated agent authorization is not solved**; and stablecoin, *agentic tokens*, and "other payment methods" are all in the **future tense** (*"coming soon"*).
#Stripe#Link#wallet for agents
**Dan Hill** — Product Manager · **Link Consumer Product** chez Stripe. Auteur de l'annonce sur le blog Stripe · rubrique *Product*. Le rattachement au produit *Link Consumer* est significatif : l'annonce est écrite depuis le **portefeuille grand public** · pas depuis l'équipe protocole ni depuis Issuing — ce qui explique que le consentement de l'utilisateur final structure tout le texte.