55
30
55
30
Linux Foundation takes on TRACE, a hardware-backed runtime evidence specification for AI agents
The Linux Foundation adopts TRACE, an OPAQUE-contributed spec giving AI agents hardware-attested, cryptographically verifiable runtime and compliance evidence.
The Linux Foundation accepted the TRACE (Trust, Runtime Attestation and Compliance Evidence) specification contributed by OPAQUE, developed with AMD, Intel, Microsoft, and the Technology Innovation Institute. TRACE binds runtime environment, software, policies, data classifications, and tool usage into a portable, cryptographically verifiable artifact, composing existing standards such as RATS, EAT, SLSA, SCITT, SPIFFE, and EAR. It recorded nearly 135,000 PyPI downloads within 10 weeks of its June 2026 introduction, and its technical workstream will be hosted by the Coalition for Secure AI.
45
30
55
55
55
55
30
30
Exclusive: Linux Foundation's Akrites to Go Live in September
The Linux Foundation's Akrites initiative will go live in September, accepting AI-powered vulnerability reports for open-source projects.
The Linux Foundation's Akrites initiative will become operational in September 2026, when it begins accepting AI-powered vulnerability reports for open-source projects. The launch was exclusively reported by Infosecurity Magazine. The program is aimed at handling vulnerability disclosures across the foundation's open-source ecosystem using AI capabilities.
32
Linux Foundation Introduces TRACE Standard for AI Runtime Evidence
The Linux Foundation introduced TRACE, an open standard providing hardware-attested runtime and compliance evidence for AI agents.
The Linux Foundation announced TRACE, an open standard designed to generate hardware-attested runtime evidence for AI agents. The standard aims to give auditors and regulators verifiable proof of what AI agents actually executed. It targets compliance and assurance needs for organizations deploying autonomous AI systems.
50
30
55
55
55
55
55
30
30
30
42
Agent Harness vs Agent Framework vs MCP: Which Layer Owns the Loop, State, Tools, Permissions, and Recovery
Architecture explainer separates agent harnesses, frameworks, and MCP by which layer owns the loop, state, permissions, and recovery.
The article distinguishes agent harnesses (OpenAI Codex, Claude Agent SDK), which own the execution loop, sandbox, permission model, and recovery; frameworks (LangGraph, OpenAI Agents SDK, Microsoft Agent Framework), which supply composable primitives; and MCP, a stateless JSON-RPC wire protocol governed by the Linux Foundation's Agentic AI Foundation since December 2025. An ownership matrix maps the execution loop, state, tool transport, permissions, recovery, sandboxing, and multi-agent orchestration to each layer. The 2026-07-28 MCP specification made the protocol fully stateless, retiring the initialize handshake and session headers.
35
60
55
55
55
60
30
42
55
60
55
55
60
55
55
55