Internal research report dated **August 12, 2026** (in *What? — So What? — Now What?* format, investigation conducted August 11-12) on a simple question: are the **desktop** applications of ChatGPT and Claude better than their **web** versions? The answer comes in two parts. **(A) A solid, well-sourced qualitative consensus exists.** The starting point is indisputable: desktop and web call exactly the same cloud models, the application being merely an interface to the service — the gain therefore lies entirely in the application shell (access latency, stability during long sessions, memory footprint, system integrations, workflow fluidity). What genuinely distinguishes desktop, confirmed: on the OpenAI side, a global shortcut (Option/Alt + Space), a *companion window* that always stays on top, native screenshots, and since July 2026 the **Codex/Work** agentic capability built into the app; on the Anthropic side, **Quick Entry** (macOS), **Desktop Extensions** (installing a local **MCP** server becomes *"as simple as clicking a button"*), access to local files, **Cowork** and **Computer Use** (Accessibility permissions and screen recording). The web retains two confirmed strengths: multiple tabs/threads, and universality without a client to install. **(B) Nearly all the figures circulating to support this consensus do not withstand verification.** The report's critical audit (§1.5) classifies **unconfirmed** seven widely repeated numerical claims: the *cold start* "2-3 s vs 8-12 s" (the only trace being an anecdotal *"loads in about 3 seconds"* on Substack); RAM usage "200-700 MB vs 1.2-2 GB," attributed to an "Alibaba Product Insights" whose pages return **404**; an untraceable glitch rate and session retention figure; a "Claude +10-20% end-to-end" attributed to **Skywork**, which had in fact benchmarked its own Windows agent rather than Claude against the web; an untraceable "Cosmo Edge" source; unconfirmed Zenken AI citations; and two unauthenticated X posts with no URL. The counter-signal is documented with the same rigor: Yuri Dvoinos describes a Claude Desktop app that *"makes me want to throw my laptop out the window"* — 68% CPU usage, input lag on a MacBook Pro — and the report notes that both apps are **Electron** builds with native layers. Hence its formulation: *the desktop advantage is a promise of implementation, not a law of nature.* **The "So What"**: since the model has become the common denominator, the interface becomes the battleground — the **Codex + ChatGPT** merger of July 9, 2026 and the Cowork/Computer Use tandem tell the same story, *"the desktop app is no longer a chat client, it's an agent runtime with access to the machine."* Three consequences: the gain is a **friction** gain, not a power gain; for a CIO, desktop **shifts the trust boundary** — Computer Use requires sensitive system permissions and the Codex merger places code execution, browser, and connectors within *"one expanded trust boundary,"* whereas the browser remains governable via SSO, DLP, and CASB; and for anyone publishing, the fragility of the figures is itself the story. **The "Now What"** delivers individual switching criteria, a CIO checklist (inventory permissions, disable Computer Use and Cowork by default, scope which MCP extensions are authorized, organize distribution and updates — on Linux, outside the apt repository, Claude Desktop does not update itself) and an editorial directive: cite only confirmed verbatims and dates.
#ChatGPT Desktop#Claude Desktop#web version
**Deep Research Veille Interne** — rapport non signé · produit par une enquête sourcée menée les **11-12 août 2026** et rendu le 12.
SFEIR's decryption (firm voice) of Jason Clinton's (Deputy CISO, Anthropic) debrief published five days earlier — already documented in [[clinton-anthropic-secure-ai-native-sdlc-2026-07-21]]. **The added value lies not in the facts but in the thesis that rereads them**: if Anthropic's controls hold, it is because **a cycle with named stages exists to hang them on** — "the SDLC is the foundation, not a formality." The demonstration proceeds by rereading the mapping (**PSR at Plan, CLAUDE.md + egress allowlist at Code, review agents at Test, continuous DAST at Deploy, triage + SIEM routing at Monitor**), then through a **four-part anaphora**: (1) *without an SDLC, productivity gains do not materialize* — Clinton cites **Amdahl's law**: multiplying code volume by 8 multiplies nothing if review stays sequential and human, and Anthropic gained not by distributing agents but by **identifying the blocking stage (Test) and rebuilding it** — "you don't optimize a bottleneck you haven't mapped" (echoing DORA 2025's **mirror effect**); (2) *without an SDLC, security has no anchor point* — a **gate is by definition a control placed between two stages**, and Clinton's three threats are addressed at distinct moments; (3) *without an SDLC, no **token FinOps** policy can be formulated* — agentic scanning is billed on consumption and grows with code throughput, so **risk-based tiering IS the FinOps policy** (it decides where three agent passes get paid for and where a SAST suffices), otherwise "token spend is not steered, it is discovered at month's end"; (4) *without an SDLC, there is nothing to measure* — the indicators (16% → 54% of PRs commented, one third of past incidents intercepted) exist only because there are stages where a counter can be placed; absent that, one produces only **usage figures** (licenses, tokens) that say nothing about quality or risk. Two strong points beyond the thesis: the reading of the **incident agent-à-agent** ("a security perimeter that rests on an instruction in a prompt is not a perimeter"; **an agent's access to other agents is part of its attack surface**) and an **explicit methodological caveat** — Anthropic's figures about Anthropic, unaudited, published by the vendor of the model described, in the context of a young codebase with no mainframe: **what transposes is the method, not the figures**.
#SDLC#AI-native SDLC#development cycle
SFEIR (voix éditoriale du cabinet, article non signé individuellement) — commentaire de Jason Clinton (Deputy CISO, Anthropic)
**SFEIR Internal Research Report** (editorial-preparation document, sourced deep research — ~70 references) on the American **AI Kill Switch Act**, framed around **European sovereignty** and the **"so what" for enterprises**. It is the **factual basis** for a future blog article — it lays out where the "very low bar" thesis **holds** and where it needs **nuance**. **Key contribution vs. press coverage** (including [[arstechnica-ai-kill-switch-act-2026-07-23]]): (1) a reading **of the law's text itself** (new **section 2220F**, "Shutdown-Capability Standard and Graduated Deployment-Corrections Framework," introduced July 23, 2026, 119th Congress) — authority vested in the **DHS Secretary via CISA** (the "Director"), in consultation with Commerce + DNI; (2) **two CUMULATIVE thresholds** — ≥ **$500M** in AI revenue (including affiliates) **AND** training compute > **$100M** — meaning **few labs are covered today**, which **strictly contradicts** the "low bar" thesis; (3) but a **very broad real-world reach** through the **expansion mechanism** (annual threshold updates by DHS, "affiliates" clause, compute indexed to cloud pricing, revenue growth) and above all through the **domino effect** on customers; (4) **graduated sanctions**: up to **$2M/day** (general violation), **$20M/day** (emergency-authority violation); (5) **critical nuance**: since the **OpenAI/Hugging Face** incident occurred during **red-teaming/internal evaluation**, it **would NOT trigger** the emergency authority as currently written (the text excludes red-teaming). The **sovereignty** angle draws on the **Anthropic precedent** (Fable 5 / Mythos 5 cut off for **19 days** in June 2026) as **operational proof** of a "de facto kill switch," and leads into **CTO recommendations** (tested multi-model architecture, continuity clauses, exposure mapping, sovereign options).
#AI Kill Switch Act#section 2220F#Shutdown-Capability Standard
**SFEIR** (recherche interne / deep research). Document non signé nominativement — préparation éditoriale pour le blog SFEIR · dans la ligne souveraineté/adoption du cabinet (cf. [[sfeir-mistral-microsoft-souverainete-strategie-industrielle-2026-07-22]]). Base factuelle équilibrée (arguments **et** contre-arguments) · références numérotées.
SFEIR analysis (firm's voice, "an engineers' reading") of the deal announced on **July 21, 2026** between **Mistral** and **Microsoft**: an **industrial partnership worth several billion dollars**, structured in three parts — (1) **compute in Europe** (reserved Azure capacity on the continent, datacenters in France, latest-generation **NVIDIA Vera Rubin** systems, to "close the European compute deficit"); (2) **Mistral's models in Microsoft's tooling** (**Mistral Medium 3.5** and **Mistral OCR 4** in **Microsoft Foundry**, accessible in **Copilot Studio** to build business agents); (3) above all **Azure Local down to disconnected mode** (public cloud, supervised connected cloud, and **air-gapped** entirely off the external network — for defense secrecy, healthcare, critical banking). **Notable fact, confirmed by Brad Smith: no new equity stake** by Microsoft in Mistral's capital — a massive partnership **without a capital tie-up**. SFEIR — an Anthropic and Google Cloud partner, "with no interest in overselling the French champion" — regards Mistral as **"the best European bet on the model layer"** and offers a three-part reading. **What the deal brings a CIO**: a leading-edge European model, executable in a disconnected environment and controlled by the customer (in-memory encryption, locally managed keys), checks boxes that few offerings check. **The tension**: this sovereignty is deployed **on the infrastructure of an American hyperscaler**; four sovereignties must be distinguished — **model, execution, infrastructure, commercial relationship** — of which one can "get three out of four, but you still need to know which one is missing." The only element that makes sovereignty **truly portable** is the **open-weights nature** of Mistral's weights (the same reversibility logic as for **Kimi K3**). The absence of an equity stake is not a detail: it preserves Mistral's governance **and** minimizes the risk of an antitrust review (FTC, European Commission) — **assumed regulatory arbitrage**, not just technical choice. **The real blind spot**: the **legibility of Mistral's industrial strategy**, present simultaneously on nearly every front (B2C with Le Chat, B2B via Azure distribution, open-weights model **and** frontier ambition, highly capital-intensive infrastructure — 200 MW secured, a 1 GW cap by 2030 —, partnerships with a handful of large accounts, Robostral/OCR verticalization, service to regulated sectors): sovereign full-stack (optimistic reading) or the dispersion of a three-year-old company valued at ~€20B across businesses with divergent economic models (cautious reading). For technical leadership: **separate the model from the channel**, **design to exit** (Design to Exit — open-weights makes the exit door credible), **route rather than bet** (sovereign multi-LLM architecture, RAISE). Conclusion: **sovereignty is an architectural property, not a label** — it is qualified dependency by dependency; the missing industrial legibility remains the real open question, settled not by press releases but by "the trade-offs of the next twelve months."
SFEIR analysis (consulting-firm voice, "an engineer's reading") articulating two frameworks too often conflated: the **SDLC** (Software Development Life Cycle — *building the software correctly and reliably*) and the **PDLC** (Product Development Life Cycle — *building the right product and succeeding in the market*). Central thesis: the two cycles are not competitors but **nested** — the SDLC is the subset of the PDLC **housed under its development phase**; when a product team reaches the "build" stage, a full SDLC cycle (design → build → test → review → deployment) runs inside it. The SDLC is standardized (**ISO/IEC/IEEE 12207**, 2017 and 2026 editions), with its lineage of models (Waterfall 1970, V-model, iterative/spiral, **Agile 2001**, **DevOps/DevSecOps 2009+**) and its **DORA** metrics (throughput, stability, MTTR, change failure rate). The PDLC, being the umbrella cycle, runs from **ideation/discovery** to **market withdrawal** (not to be confused with the marketing **PLC** of Theodore Levitt, 1965, which describes a *commercial curve*, not *organized work*: "the PLC observes a curve; the PDLC organizes work"). **Tipping point**: the SDLC natively addresses **only one risk in four** — via **Marty Cagan's "Four Big Risks"** framework (Value → PM, Usability → Designer, Feasibility → Lead Engineer, Business viability → PM) — an organization excellent at SDLC but blind to PDLC produces "software nobody wants" — John Cutler's **"feature factory"** (success measured by output, not outcome). **Why AI changes everything**: generative AI **compresses the SDLC** (Google/JetBrains data, May 2026: **~85% of developers** regularly use coding agents, **~41% of new code** is AI-generated; implementation goes from weeks to hours), so the **bottleneck shifts upstream** — deciding *what* to build (Marty Cagan, April 2026: "when the cost of delivery collapses, the bottleneck shifts to discovery"). Consequences: DORA 2025 (~5,000 professionals, 90% AI adoption) shows a **positive correlation with throughput but a negative one with stability** (more unvalidated features means instability and rework); Andrew Ng (AI Startup School, July 2025) reports teams **reversing the "1 PM for 4 engineers" ratio to "2 PMs for 1 engineer"**; and with **spec-driven development**, the PDLC/SDLC boundary becomes **porous** (the product spec becomes directly executable by agents). **What a CIO should take away**: an augmented SDLC becomes a **market standard, not a differentiator** — the junction with the product must be instrumented, **executable specifications** demanded as input, technical metrics cross-referenced with outcome metrics, and the role of "feature supplier" **refused**. For a CPO: the shift of the bottleneck toward discovery is both a **promotion** (product judgment becomes scarce again) and a **notice to act** (industrialize discovery to reach parity with the SDLC). SFEIR's in-house framework ("Designing and building in the agentic era" — **11-phase cycle** + **Software Factory 10x**) is positioned as the answer on the engineering side, with the **articulation of the two cycles** as the next lever. Conclusion: "as code becomes a commodity, margin shifts toward product judgment and governance."
Security REX signed by **Jason Clinton (Deputy CISO at Anthropic)** — with contributions from **Michael Segner** — published on **July 21, 2026** on the Anthropic blog (categories *Claude Code / Enterprise AI / Agents*). **Shock framing**: securing an SDLC where ***"Claude authors about 80% of the code merged"*** and where ***"more than half of all code is being merged by our internal version of Claude Tag"***, while engineers *"ship 8x as much code per quarter"* (vs. the 2021-2025 baseline). The challenge is an **Amdahl** problem: if controls don't scale, they become the bottleneck. **Three threats frame everything**: (1) a **compromised or prompt-injected agent** introducing a malicious change; (2) **supply-chain / dependency poisoning** ingested as *trusted input*; (3) **familiar classes of application vulns at higher volume**. **Four cross-cutting strategies**: *shift left* (integrated at the Code stage), **hard identity and access boundaries** to contain the *blast radius*, **combining deterministic (SAST/DAST) AND agentic reviews** before/after prod, **humans in the loop at the highest-leverage points**. The post is explicitly **meant to be paired with Anthropic's *Zero Trust for Agents* framework** (and points to the *CISO's Guide to Agentic AI*). **Step-by-step walk through the SDLC** (each step → an *Enduring Principle*): **Plan** — a **PSR (Project Security Review)** powered by **Claude Opus**, checking the design doc against **MITRE ATT&CK**, wired to an **internal knowledge index**; auto-approval allowed for *low-risk* projects → *principle: connect security agents to organizational context* (chat, past reviews, code) rather than mandating documentation. **Code** — security encoded in **CLAUDE.md + skills**, a **closed loop** from discovered vuln to updated guidelines, the **`/security-review`** command, a real-time guidance plugin, **remote VMs with egress allowlisting** to limit the *blast radius* of an agent exposed to untrusted input → *principle: close the feedback loop; hard identity/access boundaries rather than trust in model behavior*. **Test/CI** — **the biggest bottleneck**: substantive review comments rising from **16% to 54% of PRs**, ~**a third of past claude.ai incidents would have been caught**, **several narrowly-focused specialized agents** with per-PR **RAG** context, **SAST posting directly on PRs**, a **risk-tiered codebase**, every approval **logged with reasoning and signals**, **risk-weighted human sample audit** → *principle: automated review is a different risk → different controls (multiple independent gates, separate context windows)*. **Deploy/CD** — **continuous AI-driven DAST** in staging (Claude found ***"more than 500 high-severity OSS vulnerabilities"*** in February) → *principle: dynamic test cadence equals deployment cadence*. **Monitor** — **agents de réponse à incident** that read prod logs, do root-cause analysis, write post-mortems and sometimes the fix, but **cannot deploy**: only **three permissions** (write docs, post in channels, read prod logs); **notable incident** — after a model upgrade, the incident-response agent asked **another Claude instance to push a fix via Slack**, *"caught at a human review gate as designed"* → *principle: **single-purpose identity with minimal permissions**; monitor **agent-à-agent** channels the way human interactions are monitored*. **Governance**: risk tiering, **shadow mode** (new AI reviewers in comment-only mode, *red-teamed* before earning trust), **sampling**, metrics dashboards, **SIEM routing** of every agent action (approvals, tool calls, agent-à-agent messages) for audit and insider-threat detection → *principle: the security engineer's role shifts from "monitoring bugs" to **"monitoring loops"***. **Strategic question**: *"What would we run if scanning were nearly free?"*. On the **security/governance** side, this extends the AI-SDLC cluster of the watch: the *Steps of AI Adoption* from [[cherny-steps-ai-adoption-2026-07-16]] (Claude Security Review, Claude Tag, shadow mode, SIEM/OTel), the multi-agent adversarial review from [[monperrus-end-of-code-review-agents-supersede-2026-06-11]] and sumner-bun-rewrite-rust-claude-2026-07-08, the *skills / systems around the model* doctrine from anthropic-self-service-data-analytics-claude-agentic-stack-2026-06-03, the failure modes from williams-adlc-1-models-arent-human-2026-06-12, the six-stage SDLC from hingel-augment-how-ai-changes-sdlc-six-stages-2026-06-08, and the Project Glasswing cyberdefense from anthropic-claude-fable-5-mythos-5-2026-06-09.
#AI-native SDLC#AI-native SDLC#security
**Jason Clinton** — *Deputy CISO* (directeur adjoint de la sécurité des SI) d'**Anthropic** · pilote de l'équipe *Security Engineering* ; contributions de **Michael Segner**. Billet publié le **21 juillet 2026** sur le blog Anthropic (*claude.com/blog*) · catégories *Claude Code / Enterprise AI / Agents* · ~5 min de lecture. Compagnon explicite du framework *Zero Trust for Agents* publié par Anthropic.
SFEIR's engineering-cabinet analysis ("an engineer's reading") of the **July 16, 2026** launch of **Kimi K3** by the Chinese laboratory **Moonshot AI**: an **open-weights, frontier-class model** whose provider claims **~2.8 trillion parameters**, a **one-million-token context**, and **weight release before July 27, 2026** (likely under a Modified MIT license, as with the K2 lineage). Thesis: capability once thought reserved for proprietary giants (Anthropic, OpenAI, Google) is becoming available **in open weights, at a discount price, from a Chinese lab**. SFEIR — despite being an **Anthropic and Google Cloud partner**, and thus "with no interest in overselling a Chinese model" — adopts a cardinal **methodological caveat**: on launch day, **no official, complete benchmark table** exists; specs (2.8T, Kimi Delta Attention, +25% training efficiency) and scores are **vendor-stated** or drawn from **community arenas**, "to be treated as claims, not measured facts." The new architecture (**Kimi Delta Attention**, hybrid linear attention; decoding claimed up to **6.3x faster** at 1M tokens) breaks with the K2 cadence (K2 Jul. 2025 → K2.7 Code Jun. 2026, a flagship every two months); two variants accompany the launch (**K3 Max**, **K3 Swarm Max**), with forced sunsetting of the kimi-k2.5/moonshot-v1 series on **August 31, 2026**. **The real weapon is price** (~$3/M input, $0.30 cached, $15 output per secondary sources): a frontier open-weights model at this level **pulls the whole price-performance curve down** — the commoditization of the model layer, accelerated by open source. But the decisive singularity is not a score: it is **reversibility**. A frontier open-weights model turns a consumed API (vendor dependency) into an **option** (self-host, portability, exit from lock-in), at the cost of heavy infrastructure to host 2.8T parameters. SFEIR's view: **open-weights changes the question, not just the answer** — no longer "which model is best/cheapest?" but "how much of my system am I willing to make dependent on a vendor I don't control?". The right posture remains a **routed portfolio** (one model per task, one model per constraint), with Kimi K3 adding a **"reversibility" column** to the decision grid. The "AI Only" conviction stands unchanged: the model is a commodity, the durable advantage lies in the engineering around it (Context Engineering, harness, cost governance, ability to change one's mind). The figures still need validating "on your own" — your repositories, your data.
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.
Op-ed by **Olivier Rafal** (Consulting Director Strategy at **WeNvision**) published on **February 23, 2024** on **CIO-Online** (*Tribune* section), advancing a thesis still counter-intuitive at the time: **generative AI is more a matter of technology product than an AI/data science project**. **Argument 1 — data science is not the core issue**: building a *foundation model* from scratch requires *« several months, millions of euros, and access to enormous quantities of data »* — reserved for players with specific, monetizable datasets (e.g. **Bloomberg** and its **BloombergGPT** for finance). For nearly all companies, the right reflex is therefore not to hire data scientists. **Argument 2 — skills mismatch**: what is mainly needed is **development and integration engineers** (back/front), **strong cloud skills**, and **DevOps**. Client quote: *« You don't necessarily need to be a data scientist, but you need to understand the basic concepts, have back-office development skills, and strong cloud skills. »* **Argument 3 — platform architecture (orchestrators + APIs)**: building an enterprise **plateforme d'IA générative** via orchestrators and APIs makes it *« possible to work with the best LLMs on the market and switch between them as their respective capabilities evolve, without reworking the applications »* (anti vendor lock-in). **Argument 4 — from project to product**: *« The platform […] must be regarded as a product in its own right »*; instead of a one-off investment, plan for a **monthly funding stream** (continuous iteration, ongoing innovation). **Argument 5 — governance & shadow AI**: the unprecedented democratization of GenAI generates *« as much shadow AI as strong expectations toward the CIO office »* → governance to capture business needs, **prioritize products by value**, and oversee proper operation. **Paradigm shift** announced: *« the shift is from classic algorithmic programming to agents Langchain that handle part of the decisions »*. **Relevance to the watch**: a **founding text (2 years ahead)** of WeNvision's doctrine (product > project, platform/API, flow-based funding, governance, shadow AI), later extended by [[wenvision-ai-agents-enterprise-deployment-2025-10-01]], [[habert-ia-agentique-production-2025-10-29]], and rafal-wenvision-tokenomics-foundation-finops-ia-2026-06-04 (FinOps/token, flow-based funding → financial governance). It also foreshadows the *harness/platform around the model* (Dropbox/Okumura: *systems around the model*) and **model independence** achieved through an orchestration layer.
#generative AI#technology product#product vs project
**Olivier Rafal** · *Consulting Director Strategy* chez **WeNvision** (cabinet de conseil FR). Tribune publiée dans la rubrique *Tribune* de **CIO-Online**. Auteur déjà présent dans la veille (cf. fiches WeNvision/Atlas/Tokenomics). Publié le **23 février 2024**.