AI News Archive: July 22, 2026 — Part 7
Sourced from 500+ daily AI sources, scored by relevance.
- Unlock Real Value: Agentic AI in Supply Chain Planning
Unlock Real Value: Agentic AI in Supply Chain Planning Gartner
- Substack’s new tool tells you who’s been writing their newsletters with AI
Substack is giving readers a way to estimate how much of a newsletter was written by AI, signaling a broader shift toward transparency around AI-assisted content.
Score: 58🌐 MovesJul 22, 2026https://techcrunch.com/2026/07/22/substacks-new-tool-tells-you-whos-been-writing-their-newsletters-with-ai/ - Chinese robot maker AgiBot pursues Hong Kong IPO, hiring 3 sponsors: sources
Fast-growing Chinese robot maker AgiBot is pursuing an initial public offering in Hong Kong and has hired Citic Securities as a sponsor, according to two people familiar with the matter. Additionally, China International Capital Corporation (CICC) and Morgan Stanley have also been tapped as joint sponsors, one of the people said. Shanghai-based AgiBot had shown signs that it was looking to list following its restructuring from a limited liability company to a joint-stock limited firm last year,...
- Powering the Future of Cosmology With AI
Powering the Future of Cosmology With AI Carnegie Mellon University
Score: 57🌐 MovesJul 22, 2026https://www.cmu.edu/news/stories/archives/2026/july/powering-the-future-of-cosmology-with-ai - ServiceNow pushes back on AI threats, reporting a 25% jump in subscription revenue
ServiceNow pushes back on AI threats, reporting a 25% jump in subscription revenue Business Insider
Score: 57🌐 MovesJul 22, 2026https://www.businessinsider.com/servicenow-q2-2026-earnings-counter-ai-threat-narrative-strong-growth-2026-7 - A Once Wary Hollywood Slowly Warms To AI
A Once Wary Hollywood Slowly Warms To AI Barron's
Score: 57🌐 MovesJul 22, 2026https://www.barrons.com/news/a-once-wary-hollywood-slowly-warms-to-ai-c5c72607 - 78% of Filipino workers use AI at work but few receive training — study
Filipino workers use AI at work but lack role-specific training.
Score: 56🌐 MovesJul 22, 2026https://www.philstar.com/headlines/2026/07/22/2543892/78-filipino-workers-use-ai-work-few-receive-training-study - Thwarting the hidden resume hacks that target AI hiring tools
In an increasingly competitive job market, some applicants are quietly trying to outsmart AI hiring tools. Now, new research focused on rooting out the practice of "prompt injection" shows how widespread this tactic is.
Score: 55🌐 MovesJul 22, 2026https://techxplore.com/news/2026-07-thwarting-hidden-resume-hacks-ai.html - Solix Technologies Launches Enterprise AI Platform That Transforms Business Data into Trusted Knowledge
Solix Technologies Launches Enterprise AI Platform That Transforms Business Data into Trusted Knowledge azcentral.com and The Arizona Republic
- OpenAI’s Codex Context Cut Puts Enterprise AI Coding Workflows on Notice
OpenAI’s Codex Context Cut Puts Enterprise AI Coding Workflows on Notice DevOps.com
Score: 55🌐 MovesJul 22, 2026https://devops.com/openais-codex-context-cut-puts-enterprise-ai-coding-workflows-on-notice/ - Review investigates effects of automation on the mining industry in South Africa
South Africa's mining industry risks increased inequality through the adoption of fourth industrial revolution technologies unless automation is matched by stronger governance and workforce support, according to a review published in the International Journal of Mining and Mineral Engineering. The fourth industrial revolution refers to the growing use of digital technologies to improve industrial operations.
Score: 55🌐 MovesJul 22, 2026https://techxplore.com/news/2026-07-effects-automation-industry-south-africa.html - Most AI projects don’t fail on technology, they fail on the workflow nobody fixed first
Artificial intelligence has become Southeast Asia’s favourite business conversation. Boardrooms are discussing it. Investors are asking about it. Startups are building around it. Established companies are scrambling to integrate it. In many ways, AI has become the defining technology race of this decade. But after working with businesses across different industries, an uncomfortable pattern continues […] The post Most AI projects don’t fail on technology, they fail on the workflow nobody fixed first appeared first on e27 .
Score: 55🌐 MovesJul 22, 2026https://e27.co/most-ai-projects-dont-fail-on-technology-they-fail-on-the-workflow-nobody-fixed-first-20260721/ - Swimlane launches AI security operations center for managed security services providers
Agentic artificial intelligence cybersecurity automation company Swimlane Inc. today announced the launch of an AI security operations center for managed security service providers. The company said it built the new service to support its customers and partners rather than compete with them. It serves third-party cybersecurity providers that outsource security monitoring, threat detection, and infrastructure […] The post Swimlane launches AI security operations center for managed security services providers appeared first on SiliconANGLE .
- Zoom Revenue Accelerator unveils AI that drives revenue action, not just insights
Zoom Revenue Accelerator unveils AI that drives revenue action, not just insights Toronto Star
- Synagie Unveils Geene 2.0 - BytePlus, SingData and FLY Entertainment Among 12 Founding Partners Building Trusted AI Commerce
Synagie Unveils Geene 2.0 - BytePlus, SingData and FLY Entertainment Among 12 Founding Partners Building Trusted AI Commerce The Straits Times
- At Myntra, AI is moving beyond pilots to rewrite the speed of enterprise execution
As enterprises move beyond experimentation, Myntra's AI strategy illustrates how competitive advantage is increasingly being built through AI-enabled operating models rather than isolated copilots. The post At Myntra, AI is moving beyond pilots to rewrite the speed of enterprise execution appeared first on Express Computer .
- How a contextual AI fabric turns organizational memory into AI advantage
Across industries, a version of the same conversation is playing out in technology leadership meetings. Enterprises have deployed AI broadly, and foundation models keep getting more capable. Yet the outputs still feel generic, shaped by industry patterns rather than by the organization producing them. McKinsey’s AI Trust Maturity Survey found that while overall AI maturity scores have improved, only about a third of organizations have reached a mature level of strategy and governance. Technical capability is advancing faster than organizational alignment. In my view, the gap is not a model problem. It is a context problem. Enterprises are feeding generic inputs into powerful models because sharing organizational context seamlessly with AI is neither easy nor intuitive today. Building the analytical and creative capabilities to scale AI, something I explored in a recent piece on the left-brain and right-brain approach to enterprise AI, is necessary but not sufficient. Before either can function effectively, the enterprise needs something more fundamental. AI that actually understands the contextual fabric of the organization it is operating in. A frontier model has processed everything written about your sector, your competitors and your regulatory landscape. It cannot access the reasoning embedded in years of delivery decisions, the patterns encoded in how your teams scope and deliver work over time. That knowledge is organizational memory, and frontier models can’t get that easily. It exists inside every enterprise but has never been structured, connected or made available to any AI system. Without it, even the most capable model answers a generic version of your question. The next competitive advantage in enterprise AI will not come from a better model. It will come from a better organizational context. One global technology enterprise set out to solve this across its own operations, building a modular ecosystem of domain-specific agents grounded in its own data across contracting, talent and vendor management workflows. What emerged was not just operational efficiency but a shared intelligence layer connecting decisions across functions for the first time. Competitive differentiation was never about the tools Consider what actually separates high-performing enterprises from the rest. In a regulated industry like financial services or healthcare, organizations cannot meaningfully differentiate on product. A bank cannot offer substantially different products or services. A health system uses the same clinical protocols and the same electronic health record (EHR) platforms as its peers. What varies is everything underneath: the rigor of processes, the coherence of cross-functional decisions and the people who carry years of accumulated organizational judgment in how they make those decisions. An organization with a proper context layer in place can say with precision that for this type of engagement, in this sector, with this risk profile, our institutional history tells us exactly where we stand. That level of specificity is what most enterprises have never made available to AI. The enterprise AI brain that every organization has but has never assembled Every enterprise already possesses what I think of as an enterprise AI brain. The problem is that it has never been assembled in one place. The data exists across contracts, project documentation, talent records, delivery metrics and the operational communications of daily execution — the informal reasoning that rarely makes it into formal systems. None of the standard enterprise platforms were designed to connect this. A customer relationship management (CRM) system captures customer interactions. An enterprise resource planning (ERP) system captures transactions. A project management tool captures tasks and timelines. None of them captures the reasoning behind decisions and none of them surfaces a coherent picture of how the organization actually thinks and operates. BCG’s study across hundreds of companies found that only 10% of AI value comes from the algorithms and another 20% from the technology that implements them, meaning the remaining 70% depends on people, processes and organizational change. The organizations extracting real value are those that have made their institutional knowledge available to AI in a structured, governed way. Building a contextual AI fabric A Contextual AI Fabric is the technical and organizational layer that makes the Enterprise AI Brain usable. It brings together unstructured data ingestion, semantic structuring, retrieval pipelines and governed model access to give AI systems the organizational context they need to produce outputs that are genuinely specific to your enterprise rather than generically accurate about your industry. It rests on three pillars. Core is the secure, governed and interoperable foundation that AI operations run on. Context is reliable, traceable access to the organization’s data, processes, knowledge and history. Coordination connects people, agents, applications and systems into process-driven workflows with clear controls and accountability, so the organization acts as one rather than a set of disconnected functions. The data layer is where most organizations underestimate the work. Contracts, project reports, talent assessments and operational communications require extraction, chunking, embedding and indexing before a model can retrieve and reason over them meaningfully. The semantic layer is what makes retrieval meaningful. Even well-ingested data fails if functions use different terminology for the same concepts. What legal calls a contract, delivery calls a scope. Without a shared ontology, AI systems remain precise about the wrong thing. And retrieval alone, however well-structured, only takes an organization so far. Retrieval surfaces the right information at the moment of a query, but it does not give a model genuine memory of the organization. The real source of unique, organization-level relevance comes from training domain-specific small language models on this context directly, models that carry organizational memory forward rather than fetching it fresh every time. That is what ultimately separates a Contextual AI Fabric from a well-organized database. The governance layer is not an add-on. Access controls, data lineage, approval thresholds and human checkpoints need to be designed in before any agent goes into production. Security is not a layer you add afterward. It is the condition under which organizational AI is worth building. If the institutional intelligence that makes your enterprise distinct gets absorbed into a frontier model’s training data, it becomes everyone’s baseline. That is an architectural decision made, or avoided, at the point of deployment. Proprietary by design The institutional knowledge that makes up a contextual AI fabric — delivery history, commercial patterns, talent intelligence and operating culture — is proprietary in ways no external model can replicate. This is as much a security imperative as it is a competitive one. Organizational context, once exposed, cannot be unexposed. Most enterprises are using AI to automate existing processes rather than questioning whether those processes should be redesigned entirely. The organizations extracting the most value are those willing to ask whether their current operating model, built before GenAI existed, is the one they would build today. That question is harder than any technology decision, and it is also the most consequential one. From context to coordinated action Context alone is not enough. When a delivery risk surfaces in project data, the talent function needs to respond. When a commercial signal changes in contract data, operations need to recalibrate. This kind of cross-functional coordination, driven by shared organizational intelligence rather than siloed data, is where the real value of enterprise AI shows up and where the absence of a shared context layer becomes most visible. A global leader in digital payments and business services found its AI deployments across payroll, HR and risk compliance, each running in isolation, with no shared governance or common data foundation. Once the organization established a unified governance backbone connecting its operational data through a shared retrieval layer, business users could query across domains in plain language and new use cases across fraud analytics, forecasting and policy extraction became extensible without rebuilding infrastructure for each one. The shift was not in the models. It was in the shared foundation underneath them. The leadership question behind the technology question The enterprises pulling ahead in AI are not winning on model quality but on organizational memory. The ones that have done the hard work of structuring their institutional knowledge into a governed, secure Contextual AI Fabric are giving their AI something no competitor can replicate: the accumulated intelligence of how the business actually operates. For CIOs, the question is no longer which model to deploy. It is whether the organization has built the foundation that would make any model worth deploying. This article is published as part of the Foundry Expert Contributor Network. Want to join?
- AI for Marketing Decision Support: How CMOs Drive Enterprise Growth
AI for Marketing Decision Support: How CMOs Drive Enterprise Growth Gartner
- Agibot Expands Embodied AI Portfolio With Four New Products
The Chinese robotics company is targeting commercial, industrial and research applications as it looks to move embodied AI from one-off demonstrations to full-scale applications.
Score: 55🌐 MovesJul 22, 2026https://aibusiness.com/robotics/agibot-expands-embodied-ai-portfolio-new-products - The Interpretability Debt Nobody’s Budgeting For
In 12 days, the EU AI Act makes explainability mandatory. Most enterprises still can’t tell you why their AI said no. created by Gemini Twelve days from now, on August 2, 2026, the EU AI Act’s high-risk obligations become enforceable. Article 13 requires that providers design their systems so a human deployer can understand the rationale behind an individual output — not the system in general, that specific decision, for that specific person. Article 14 requires human oversight to be built into the architecture, not bolted on as a review step. As of April 2026, 78% of organizations subject to these obligations had not taken meaningful steps toward compliance. That is not a story about slow legal teams. It is a story about engineering organizations that spent three years optimizing model performance while treating the ability to explain a decision as someone else’s problem — a compliance deliverable, a slide in a governance deck, never a line item in the architecture review. That gap has a name, and it behaves exactly like the technical debt categories engineering teams already know how to reason about. Call it interpretability debt: the accumulating distance between how complex your decision systems have become and how well anyone — including the team that built them — can explain any single output they produce. Like all debt, it’s invisible while you’re accruing it and expensive the moment someone calls it in. This isn’t an ethics problem. It’s an unbudgeted engineering cost. The AI engineering discourse has a habit of filing explainability under “responsible AI” — alongside fairness audits and ethics boards, nice-to-haves that live in a separate workstream from the actual system design. That framing is why the debt exists. Every other category of technical debt gets priced into engineering decisions somewhere: security debt shows up in threat models, reliability debt shows up in SLOs, prompt debt shows up in regression suites. Interpretability debt rarely shows up anywhere, because most teams never treated it as an engineering property with a cost curve. It was a policy question, so it got a policy answer: a values statement, not a design constraint. But interpretability has always had a real, measurable engineering cost, and it has always traded off against the things teams actually optimize for. A gradient-boosted ensemble or an LLM-based scoring pipeline will usually outperform a logistic regression or a shallow decision tree on raw accuracy. Teams pick the ensemble, ship it, and defer the explainability question to “we’ll add a dashboard later.” Later is now the week of an audit, a subpoena, or a regulator’s information request — and retrofitting explainability into a system that was never architected to produce it is a materially different, more expensive engineering problem than designing for it up front. The forcing function arrived before most teams noticed The EU deadline is the loudest signal, but it isn’t the only one, and treating it as the only one is exactly the mistake that leaves teams exposed everywhere else. In the US, a class action against Workday’s AI-driven applicant screening tool has already survived a motion to dismiss on a disparate-impact theory — a court finding that plaintiffs adequately alleged the tool disadvantaged older and Black applicants, despite Workday’s role as a vendor rather than the employer making the final call. The “we just used a vendor’s tool” defense is eroding case by case. The EEOC has been explicit that “the algorithm did it” is not a defense under Title VII. California’s automated-decision-system regulations, in force since October 2025, bring AI-driven hiring decisions squarely into state fair-employment law. None of this required an EU regulation to happen — it required a plaintiff, a court, and a system nobody could adequately explain. The EU AI Act formalizes the same expectation with real teeth: penalties for high-risk violations run up to €15 million or 3% of global annual turnover, and the top tier for other prohibited-practice violations reaches 7% of global turnover — a ceiling that deliberately exceeds GDPR’s. Article 13 specifically requires explaining the rationale behind individual outputs, which is a stricter bar than system-level transparency. A model card that describes how the system works in general does not satisfy a requirement to explain why this applicant was rejected or this claim was denied. Here’s the detail that should worry engineering leads more than the deadline itself: the CEN/CENELEC harmonized technical standards that are supposed to define exactly what “compliant” explainability implementation looks like are themselves behind schedule, with first publications not expected until late 2026 — after the enforcement date. Teams are being asked to build against a target that regulators haven’t finished drawing. That’s not a reason to wait. It’s a reason to build interpretability as a general engineering capability rather than a checklist item keyed to one document, because the document keeps moving and the legal exposure doesn’t wait for it to stabilize. Why you can’t patch this in with SHAP and call it done The standard answer to “how do we get explainability” is to bolt on a post-hoc method — SHAP, LIME, attention visualization — and generate a plausible-looking attribution chart per prediction. This helps, but it doesn’t retire the debt, for three reasons worth being precise about. First, post-hoc attribution methods are approximations of the model’s behavior, not descriptions of its actual reasoning. SHAP values tell you which features correlated with a shift in output for a local perturbation of the input; they don’t tell you the model’s decision procedure, and two different attribution methods run on the same model frequently disagree with each other. Presenting a SHAP chart to a regulator as “the explanation” is technically defensible only if your team understands, and can articulate, that it’s an approximation with known failure modes — most compliance documentation doesn’t get that far. Second, none of this scales cleanly to the systems most enterprise teams are actually shipping in 2026. A single scikit-learn classifier is a reasonable target for SHAP. An agentic pipeline that routes a decision through a retrieval step, a tool call, an LLM-based reasoning step, and a downstream scoring model is not one model to explain — it’s a decision chain, and the explanation has to hold across every hop. If you’ve been following this publication’s coverage of durable execution and agent-to-agent protocols, you’ll recognize the shape of the problem: the same orchestration complexity that makes agentic systems powerful is exactly what makes them unauditable by default. Interpretability debt and agent sprawl are compounding in the same architectures simultaneously, and most governance frameworks are still pricing them as separate problems. Third, explanations drift the same way models drift, and usually more quietly. An attribution profile generated against a model at training time can silently stop matching reality after a routine fine-tune, a vendor’s silent model swap, or a shift in the production input distribution — the explanation keeps rendering the same confident chart while the underlying decision logic has moved. A dashboard that was accurate in Q1 and never revalidated is worse than no dashboard, because it produces false confidence in an audit rather than an honest gap. What actually pays this down Treating interpretability as an architecture requirement rather than an audit-week scramble changes what gets built, and when. Price it at model-selection time, not after. When a design review compares a black-box ensemble against a more interpretable alternative, the explainability cost of the higher-accuracy option should be an explicit line in that decision — engineering hours to build and maintain an explanation pipeline, not a footnote. For genuinely low-risk decision paths, that cost may be worth paying. For anything touching credit, hiring, healthcare triage, or benefits eligibility, the calculus changes, and it should change on paper, in the design doc, before the model ships. Version explanation artifacts alongside the model, not alongside the documentation. An explanation is only trustworthy if it’s tied to the exact model version, exact feature pipeline, and exact input distribution it was generated against. That means your model registry needs an explanation artifact as a required field, not an optional attachment — the same discipline teams already apply to model cards and eval results. Put explainability regression tests in the eval harness. If your evals check accuracy, latency, and safety on every deploy, they should also check that attribution outputs for a fixed set of reference cases haven’t silently shifted. This is the direct extension of the eval-debt problem this publication has covered before: an eval suite that doesn’t test for explanation drift isn’t actually testing the property regulators and courts are going to ask about. Assign an owner who isn’t legal. Every high-risk decision path needs a named engineering owner who can answer “why did the system decide this” for a specific case, on short notice, without routing the question through a vendor’s support ticket. If that person doesn’t exist today, that’s the actual finding of this audit, and it’s worth surfacing before an external one does it for you. Budget for it like observability, because it is observability. Nobody ships a production service without logging and monitoring anymore; teams accepted that cost a decade ago because the alternative — debugging blind — became unacceptable. Explainability infrastructure for consequential AI decisions is the same category of cost, arriving a decade later and with a regulator attached. The deadline is a symptom, not the disease It’s tempting to read the August 2 date as the reason to act and treat US operations, or anything outside EU jurisdiction, as lower priority. Mobley v. Workday says otherwise — that case is proceeding under decades-old US civil rights law, with no EU regulation involved at all. Interpretability debt gets called in by whichever mechanism reaches it first: a regulator, a plaintiff’s attorney, an internal audit, or a customer who asks a question your system genuinely cannot answer. The EU Act just happens to be the mechanism with a published date on it. Teams that treated security debt as a compliance checkbox learned, the expensive way, that the checkbox and the actual capability are different things, and that the gap between them gets measured in breach costs, not audit findings. Interpretability debt is heading toward the same lesson, on a shorter timeline than most engineering roadmaps currently account for. The organizations that come out ahead won’t be the ones with the best-looking SHAP dashboard in August. They’ll be the ones that stopped treating “can we explain this” as a question for later, sometime around the point where the debt was still cheap to pay down. The Interpretability Debt Nobody’s Budgeting For was originally published in Towards AI on Medium, where people are continuing the conversation by highlighting and responding to this story.
- Detecting Vulnerabilities in Agent Skills with SkillSpector: From Green Checkmark to Real Security Judgment
Static analysis nailed the malicious skill and over-flagged the useful one. The gap between those results is where human judgement actually earns its keep. The post Detecting Vulnerabilities in Agent Skills with SkillSpector: From Green Checkmark to Real Security Judgment appeared first on Towards Data Science .
Score: 55🌐 MovesJul 22, 2026https://towardsdatascience.com/from-green-checkmark-to-real-judgment-auditing-ai-agent-skills-with-skillspector/ - What is Buzz, Jack Dorsey’s new app to take on Slack in the AI workplace era?
What is Buzz, Jack Dorsey’s new app to take on Slack in the AI workplace era?
- How Google Cloud’s Gemini Enterprise is helping MSMEs build AI agents without writing code
How Google Cloud’s Gemini Enterprise is helping MSMEs build AI agents without writing code YourStory.com
- Google Cloud and NVIDIA power microagi's embodied AI ambitions
Robotics deployment company microagi today announced a collaboration with Google Cloud to accelerate the development of models and robotics capable of understanding and interacting with physical envir...
Score: 55🌐 MovesJul 22, 2026https://tech.eu/2026/07/22/google-cloud-and-nvidia-power-microagis-embodied-ai-ambitions/ - Anthropic Investor in Talks to Fund New Lab Run By Two Stanford AI Professors
Anthropic Investor in Talks to Fund New Lab Run By Two Stanford AI Professors The Information
Score: 55🌐 MovesJul 22, 2026https://www.theinformation.com/articles/anthropic-investor-talks-fund-new-lab-run-two-stanford-ai-professors - From Substack to YouTube, here are the social platforms cracking down on AI slop
From Substack to YouTube, here are the social platforms cracking down on AI slop Business Insider
Score: 55🌐 MovesJul 22, 2026https://www.businessinsider.com/ai-slop-substack-youtube-tiktok-pinterest-facebook-instagram-threads-2026-7 - Samsung's North America CEO says the smartphone is just an entry point to ambient AI of the home
Samsung's North America CEO says the smartphone is just an entry point to ambient AI of the home Fortune
Score: 55🌐 MovesJul 22, 2026https://fortune.com/2026/07/22/samsung-smartphone-entry-point-ambient-ai-home/ - ServiceNow Posts Strong Sales and Bookings, Touts AI Strength
ServiceNow Inc. reported better-than-expected quarterly sales and bookings, boosting Wall Street’s hopes that the software maker’s new artificial intelligence tools will spur growth.
Score: 55🌐 MovesJul 22, 2026https://www.bloomberg.com/news/articles/2026-07-22/servicenow-posts-strong-sales-and-bookings-touts-ai-strength - AI by Zapier: Add agentic AI steps to your workflows
Guilty of tokenmaxxing? I get it. Now that AI is ubiquitous in all of our work, it's easy to let an agent harness take the reins for every workflow. But tossing your important tasks into the agent void and letting it run amok in your wallet isn't always the cheapest—or smartest—way to go. Some work requires determinism, which means the same input produces the same output every time. Conventional automation handles that more reliably than AI. And it's also less expensive. There's no reason to pay
- What Makes Up The Universe? AI Will Help CMU Scientists Find Out
What Makes Up The Universe? AI Will Help CMU Scientists Find Out Carnegie Mellon University
Score: 55🌐 MovesJul 22, 2026https://www.cmu.edu/dietrich/news/news-stories/2026/doe-genesis-grant-chad-schafer - Enterprise AI Agents for the Era of Agentic AI
Explore how enterprise AI agents, real-time data, and agent orchestration are reshaping commerce, supply chains and store operations.
Score: 55🌐 MovesJul 22, 2026https://www.snowflake.com/content/snowflake-site/global/en/blog/enterprise-ai-agents-agentic-ai - Cursor Releases Cursor Router: A Request-Level Classifier Delivering Frontier Coding Quality at 30–50% Lower Cost
Cursor Releases Cursor Router: A Request-Level Classifier Delivering Frontier Coding Quality at 30–50% Lower Cost MarkTechPost
Score: 55🌐 MovesJul 22, 2026https://www.marktechpost.com/2026/07/22/cursor-releases-cursor-router-a-request-level-classifier/?amp - Ramp, FIS make AI moves
The two payments companies this month embarked on separate artificial intelligence initiatives, with one focused on managing AI spending and the other using the technology to mitigate cybersecurity risks.
- EverMind Launches Raven Agent: The Self-Improving Harness That Defines L3-Level Digital Life
EverMind Launches Raven Agent: The Self-Improving Harness That Defines L3-Level Digital Life USA Today
- When data speaks your language: How Gemini Enterprise is helping businesses move faster
When data speaks your language: How Gemini Enterprise is helping businesses move faster YourStory.com
- CIOs no longer want to manage networks, they want networks that manage themselves: HPE's Sajan Paul
CIOs no longer want to manage networks, they want networks that manage themselves: HPE's Sajan Paul Techcircle
- Election, trade and AI chaos
Welcome to our press review of events in the United States. Every Wednesday we look at how the Swiss media have reported and reacted to three major stories in the US – in politics, finance and science. Everything appeared chaotic in the US over the last week – from elections to trade policy and AI – according to the Swiss media. The US mid-term elections in November could shift the balance of power in both the House of Representatives and the Senate away from President Donald Trump. The Swiss media does not believe he means to play fair. In an address to the nation on July 17, Trump spoke of Chinese interference in the 2020 election, which he lost to Joe Biden. He also mentioned that voting machines are highly vulnerable to foreign interference and voter fraud. What does this all mean? Given that the Democrats look set to win back seats in three months’ time, Swiss public broadcaster SRF suspects that Trump could be preparing the nation for another bout of election chaos. “Even ...
- Macaron-V1: How RL Made GLM 5.2 Great Again — MindLab Mixture-of-LoRA Post-Training Pushes Trillion-Parameter Models With 64 GPUs
MindLab releases Macaron-V1: Mixture-of-LoRA post-training on GLM 5.2 with 4 specialized 1B-parameter expert adapters, 2M token context extension, and 748B Venti variant trained on just 64 GPUs.
- Menlo Ventures’ Matt Murphy explains why Anthropic is winning (and it’s not the model)
Anthropic leaped to a $47 billion revenue run rate by May, compared to $9 billion in 2025. It’s the kind of growth that Menlo Ventures’ Matt Murphy says he’s never seen in 25 years of investing, not in the internet wave, not in mobile, not in the first cloud boom. Menlo led Anthropic’s $500M Series D, and Murphy has had a front-row seat as the company went from a pre-revenue, […]
Score: 52🌐 MovesJul 22, 2026https://techcrunch.com/video/menlo-ventures-matt-murphy-explains-why-anthropic-is-winning-and-its-not-the-model/ - AI-Powered Startups Are Smaller and Flatter
Plus, every conversation is recorded now and not all 401(k) plans are created equal.
Score: 52🌐 MovesJul 22, 2026https://www.wsj.com/tech/ai/ai-powered-startups-are-smaller-and-flatter-3749d83b?mod=rss_Technology - Why Autonomous AI Requires A New Operational Foundation Grounded In Trust
From my observations, the organizations making the fastest progress are treating business context as shared enterprise infrastructure rather than rebuilding it for every AI application.
- A computational perspective on incentives in multi-agent systems - ORA
A computational perspective on incentives in multi-agent systems ORA - Oxford University Research Archive
- The compound effect your AI adoption strategy is missing
For many engineering teams, AI adoption means individual engineers write code faster while overall team velocity remains stagnant. Individual speed and team speed are produced by different things, and AI has mostly accelerated the first but not the second. The step from individual AI adoption to team advantage is one many organizations haven’t taken yet, but it’s the step where real ROI lives. Make the leap and every individual gain starts compounding into something the whole team feels. Faster individuals, but the same team pace A developer with a good AI assistant can produce more and produce faster, but ten developers all doing that, each in their own way, with their own tools and their own context, don’t add up to a team that is ten times better. More often they add up to a team moving faster in ten different directions. The speed stays with the person who created it. The reasoning, context, and decisions that the rest of the team would need to build on that speed gets lost. These three structural problems explain why: Problem #1: Context evaporates at scale An engineer spends an hour with an AI agent working through a hard design decision. They land somewhere good. The code ships. But the reasoning, the alternatives they ruled out, and the constraints they discovered stay in a chat history nobody else will ever open. Six weeks later a teammate touches the same system, has no idea any of that thinking happened, and starts over. You can’t prompt your way out of a context vacuum. Agents and teammates alike are only as good as the context they start with, and right now most of that context is being generated and immediately lost. The teams that pull ahead will be the ones that treat the reasoning around the work as something worth capturing. Problem #2: Misalignment creates duplicative work When individuals move fast in parallel without a shared source of truth, they start stepping on each other’s toes. Two people solve the same problem two different ways. An agent generates a change against a spec that quietly went stale last week. A confidently written pull request follows the wrong internal standard because the standard lived in someone’s head, not in the workflow. This problem gets worse as more of the work becomes agent-driven. Agents overwrite each other. Specs drift out of date faster than anyone updates them. The faster the individual pieces move, the more expensive the collisions become. Problem #3: Trust doesn’t scale The quiet tax on AI-assisted work is review. If an individual developer can’t see how a piece of work was produced, what the intent was, what the agent was told, what standards it was working against, then they can’t confidently build on it. So, they re-check it, or rewrite it, or route around it. The individual saved an hour. The team spent two earning back the trust. Trust transfers when intent is legible. When a teammate or a reviewer can see what was meant, what was decided, and what guardrails applied, they can accept the work and move on. When they can’t, every handoff becomes a re-litigation. Turning adoption into advantage The through-line across all three problems is the same. The value of AI at the team level does not live in the code any single person or agent produces. It lives in whether the intent and context around that work is captured, shared, and reusable by everyone else, human and agent. That reframes the leadership job. It’s not about driving more adoption, because your teams already handled that. It’s about building the connective layer that turns individual output into team capability. The window is now This matters more every month, because the individual productivity story is about to become an agent orchestration story. The organizations that turn individual adoption into team advantage now, while the habits are still forming, will be the ones whose agents actually compound. See how engineering leaders are building the connective layer between individual AI adoption and team-level compound returns at jira.dev.
Score: 52🌐 MovesJul 22, 2026https://www.cio.com/article/4200064/the-compound-effect-your-ai-adoption-strategy-is-missing.html - Attitudes toward autonomous service robots at real-life events reveal social behaviors
When a robot offers you candy, it is hard not to be curious. In an experiment conducted by ethologists at ELTE, visitors at public events noticed an autonomous service robot more often than a human server, and the candy on the robot's tray disappeared faster. The study also suggests that the presence of robots may influence the way people behave in social situations.
Score: 52🌐 MovesJul 22, 2026https://techxplore.com/news/2026-07-attitudes-autonomous-robots-real-life.html - PAG eyes deals amid market dislocation, remains cautious over AI disruption
PAG eyes deals amid market dislocation, remains cautious over AI disruption DealStreetAsia
- 4 recs for CIOs to optimize AI budgets and improve sustainability
In the client-server era, the penalty for inefficient programming, such as unoptimized database calls, was largely confined to application responsiveness. Today, in the AI era, code, architectural, and platform inefficiencies are no longer just a performance issue, they’re a financial and environmental liability. Left unchecked, poor code cascades into soaring token costs and spikes data center power consumption, directly undermining both cloud budgets and corporate sustainability goals. AI’s impact on sustainability By 2029, IDC projects that the number of actively deployed AI agents will exceed 1 billion worldwide, which is 40 times more than in 2025. And these agents will perform 217 billion actions per day. To deliver on this demand, AI data centers are being built out at an unprecedented rate, with Gartner forecasting that global spending on data centers over the next three years will increase 31.7% to surpass $650 billion, driven primarily by hyperscaler cloud providers building out AI foundations, and optimizing servers for heavy AI workloads. All this presents a significant strain on the energy grid as well as environmental sustainability, including: The power double-down: The International Energy Agency (IEA) projects that global data center electricity consumption will more than double from about 415 to 945 TWh by 2030, primarily fueled by energy-intensive accelerated computing for AI. The inference premium: AI workloads are vastly more demanding than standard web activities. A gen AI query consumes roughly 10 times the electricity of a conventional keyword search, or roughly 2.9 watt-hours as opposed to 0.3 watt-hours. Water consumption: Cooling these dense clusters is highly resource intensive. Global AI-related water demand is expected to reach 4.2 to 6.6 billion cubic meters by 2027 . The good news, however, is it’s not all out of the control of end user organizations and CIOs. Just as in the client-server era, through careful planning and execution, CIOs have the potential to significantly improve the performance, costs, and sustainability impacts of their AI application portfolio. Here are four recommendations to maximize value as you look across your AI applications and infrastructure estate. Revisit business objectives in light of AI AI applications and platforms bring several new headaches for CIOs and CFOs in terms of FinOps. The variable nature of AI vendor billing due to variable monthly token costs is just one well-known example. To avoid unpleasant surprises, be sure to carefully review vendor contracts to decipher pricing models. Look for what’s included in seat-based license fees and what’s added as variable charges for agentic AI usage. In addition, explore new metrics and KPIs such as intelligence per watt to help make sense of your return on AI. Just as miles per gallon helps us evaluate new car purchases, IPW can help to measure the computational efficiency of a system. It quantifies how much intelligence — typically measured in AI inferences, tokens processed, or model training iterations — a processor can deliver for every watt of electrical power it consumes. According to Max Romanenko, chief engineering officer at sovereign data and AI company EDB, cost per query tells you almost nothing in an agentic world where autonomous systems are spinning up databases, pipelines, and queries around the clock. “The metric that matters is intelligence per watt, how much useful AI you get for every unit of energy you spend,” he says. “It isn’t just an environmental number, it’s also a performance indicator.” With the measurements in place, you can then start to manage and optimize each layer in the AI stack from the infrastructure, or hyperscaler, layer to your own data and application layers. It’s important to bear in mind that high token usage isn’t necessarily a bad thing. It depends on the net value delivered by each AI application and use case. Managing and optimizing the AI stack is important, but you’ll also want to measure the business value being delivered by each of these applications so you can measure your return. Take a sovereign AI approach when evaluating hyperscalers As you work with hyperscalers like Amazon, Google and Microsoft, it’s important to understand how they charge and how much, but also their environmental footprints. For example, by reading their sustainability reports, you can find out their annual water consumption across their global data centers and compare them with other providers. In 2025, Amazon’s global data center operations used 0.12 liters of water per kilowatt-hour , which amounts to 2.5 billion gallons, or 5% of the annual water consumed by the metro Seattle area. The company has been able to operate more than seven times better than the industry average and have improved their water efficiency by 52% since 2021. As demand for cloud computing and AI grows, water efficiency is another important metric for CIOs to monitor within hyperscaler ESG reports. While not at the same level of regulation as scope 2 and 3 greenhouse gas (GHG) emissions reporting, enterprises need to pay increasing attention to water use efficiency (WUE) with water scarcity becoming a growing risk for hyperscalers. The key requisite at the infrastructure layer, though, is to ensure sovereign AI. This doesn’t mean you need to own everything, but you need control over your AI-driven operations when conditions change. With 71% of global executives stating that switching their primary AI vendor or model would be difficult if required today , it’s important to understand AI dependencies and be able to avoid vendor lock-in. Control efficiency at the data layer The AI energy conversation has fixated on models and GPUs, but every agent, model, and inference call runs on the data layer beneath them, and that’s the one place a CIO can actually move the numbers. “You can’t control consumption at the model layer,” says Romanenko. “Agents consume what they consume. But you can control efficiency at the data layer, and for most enterprises that’s the only real lever they have. Optimize search, retrieval, and vector indexing where the work actually happens and you cut compute, cost, and carbon at the same time. Ignore it, and it’s like running the heat with every window open.” Ann Dunkin, distinguished professor of the practice at Georgia Tech, adds that CIOs who bring models in house and run them in their own infrastructure, or in the cloud infrastructure of their choosing, can have more control over the sustainability of inference, as well as of their costs and how their data is used. Fine tune the application layer When balancing a mix of commercial AI packages and custom-built code, costs can quickly spiral due to inefficient design and orchestration, redundant APIs, and unoptimized model routing. With inference calls costing approximately 10 times that of conventional web queries, for custom AI applications, it’s important to design them to only use probabilistic code where necessary. Since many custom applications utilize a combination of both probabilistic and deterministic code , this is exactly where software developers need to make smart choices in their designs. Other techniques to fine tune the application layer include semantic caching, intelligent model routing, and internal AI capability registries. “CIOs can implement intelligent routing solutions to select the most cost-efficient model for every prompt,” says Dunkin. “The most flexible routing solutions can drop into a user’s existing environment and orchestrate the actions of the company’s existing models.” For CIOs looking to maximize the business value of every AI application in their portfolio, these new considerations, including new metrics, tools and approaches from the infrastructure layer all the way up to the application layer, should be an essential part of the equation.
Score: 50🌐 MovesJul 22, 2026https://www.cio.com/article/4192312/4-recs-for-cios-to-optimize-ai-budgets-and-improve-sustainability.html - Robot AI company Noetra is 'last chance' for Japan, CEO says
Robot AI company Noetra is 'last chance' for Japan, CEO says Reuters
Score: 50🌐 MovesJul 22, 2026https://www.reuters.com/business/media-telecom/robot-ai-company-noetra-is-last-chance-japan-ceo-says-2026-07-22/ - Tesla's Summer Update makes Grok the smart assistant it was always meant to be
Tesla's latest update makes Grok much more useful behind the wheel
- S’pore proposes focus on AI, STEM and student development under new five-year ASEAN education plan
S’pore proposes focus on AI, STEM and student development under new five-year ASEAN education plan The Straits Times
- Datavault AI (NASDAQ: DVLT) to Tokenize $1B Project Qestrel Edge AI Infrastructure Program
Datavault AI (NASDAQ: DVLT) to Tokenize $1B Project Qestrel Edge AI Infrastructure Program USA Today