AI Enthusiast Log :: AI Engineering & Dev Tools

AI Enthusiast Log

Sign in Subscribe

Latest — 30 Jul 2026

Scoped credentials alone won't secure AI agents: NTT DATA AIVista and Snowflake frame action-level governance as the missing layer

A VentureBeat survey found that 69% of enterprises running AI agents still share credentials across agents and users. NTT DATA AIVista and Snowflake argue that scoped credentials are necessary but not sufficient, and that enterprises deploying autonomous systems at scale need action-level authorization and tamper-resistant audit trails woven

More issues

Survey says AI ROI expectations hit 17%, but the gap between reported and measured value remains wide

The SAP Value of AI Report 2026 finds that AI now supports roughly 30% of tasks in the average organization, up from 25% a year ago, and that expected ROI for agentic AI has climbed from 10% to 17% in the same period. Those are the headline numbers the report

Fingerprinting ~900 open models is a start, not a solution to provenance gaps

The verification gap Cisco addresses is structural, not accidental. Hugging Face's base_model tag is a text field the uploader populates, and the platform does not require weight-level substantiation of the claimed lineage. The ATOM Report, published by Nathan Lambert and Florian Brand at Interconnects AI in

Waymo's eval-centric AI development: useful framework, unverified safety claims

Waymo presented eval-centric AI development as its core engineering philosophy at VB Transform 2026, and the approach deserves attention from teams building production AI systems. The company treats evaluation not as a final gate before deployment but as a continuous design constraint that shapes how projects mature. That framing

VB Transform 2026: Five startups tackle enterprise agent infrastructure gaps

Enterprise AI agents have outpaced the infrastructure needed to coordinate them safely in production. Coverage from VB Transform 2026 profiles five startups positioning themselves at the intersection of orchestration, observability, security, and auditability. The problems they identify are legitimate, but the source presents vendor claims without independent validation. The gap

Nimble's Web Search Agents claim 51% token cuts, but the methodology gap matters

Nimble has released Web Search Agents, a retrieval system the company says delivers 21% better accuracy and 51% lower token usage compared with leading AI search alternatives. The company frames the product as a solution to a specific enterprise AI problem: general-purpose search APIs return too many irrelevant results,

Target's SVP frames agent governance architecture as the real AI moat

At VB Transform 2026, Target senior vice president Siobhán Mc Feeney stated the company's AI edge does not come from the models it runs. Everything built around them does. "There's a lot in it. That to us is the moat," she said. "The

Visa open-sources AI bug-hunting harness, but the real news is the metric it leaves behind

Visa put Anthropic's Claude Mythos to work on the infrastructure behind billions of daily transactions, then released the governing harness as open source. The move gives any security team a reference implementation built at payment-network scale. That is useful. What the announcement does not fully establish is

Instacart's AI engineering claims: what the numbers don't establish

At VB Transform 2026, Instacart CTO Anirban Kundu presented a picture of an engineering organization where machines handle most code generation and engineers rarely look at what those machines produce. The specific numbers are attention-grabbing: 97% of cases where builders do not read code, 7,000 automatic evaluations per

Runway's drift bug became a feature. The harder question is what that workflow actually transfers.

At VB Transform 2026, Ryan Phillips, head of enterprise product at Runway ML, described how the company handled a persistent problem during development of Runway Characters: characters would drift off-center during real-time generation. The fix was not a backend patch to the model. The fix was a frontend