Content Quality: Well-structured News piece using the standard Overview/What We Know/What We Don't Know/Context frame. Neutral tone, no sensationalism, no AI self-reference. Word count 827 is within the 400-1200 News range. Title is 105 characters, within the 150-character limit.
Source Verification: Read all three source snapshots from disk after verifying sha256 integrity for each (source-0.html.gz = 969457b1..., source-1.html.gz = 54438497..., source-2.html.gz = f0422a9f... all match manifest.json). source-0 (aws.amazon.com/about-aws/whats-new) confirms the core launch claim, the 'isolation boundary of a Nitro isolated virtual machine' phrase, one-line EKS/ECS enablement, Pod Identity/VPC CNI/EBS/EFS/S3/CloudWatch native compatibility, Amazon Linux/Firecracker native VMM support, 'most Nitro-based EC2 instances, in all commercial regions worldwide, at no additional charge', and the verbatim 'LLM-generated code in an isolated environment of its own' / 'multiple agentic workloads' phrasing. source-1 (aws.amazon.com/blogs/compute, authored by Alex Graf, confirmed bio: 'Alex is a Principal Engineer on the EC2 team at AWS') confirms the verbatim Graf quotes ('Operators of a shared cluster have access to all the tasks running in it...' and 'with the current rate of Linux Common Vulnerabilities and Exposures (CVEs)...'), and additionally specifies supported instances as 'Every EC2 instance type that supports Nitro Enclaves, across general purpose, compute optimized, memory optimized, storage optimized, and accelerated families, on AWS Graviton, Intel, and AMD processors' -- see Findings. source-2 (cloudnativenow.com, allowlisted) confirms the 2017 Nitro System origin, the verbatim Mark Ryland quotes ('Nitro is a complete re-imagining...' and 'secrets hiding'/'to minimize the amount of information that the hypervisor even has access to in the first place'), the Techstrong TV attribution, the Isolated/Confidential mode descriptions, the 'doesn't magically secure your data' quote, the Kata Containers comparison (Apache 2.0, QEMU/Cloud Hypervisor/Firecracker backends), the first-level-Nitro-guest-not-nested-VM architecture detail, and the 'EKS Auto Mode or ECS Managed Instances fees' qualifier on top of the 'no additional charge' claim. The article attributes this last qualifier correctly to Cloud Native Now rather than to AWS directly. Anthropic disclosure: not required - the story does not mention Anthropic, Claude, or an Anthropic-owned product. Source independence: source-0 and source-1 are both first-party AWS; source-2 (Cloud Native Now) is independent third-party trade press and is cited for every claim that needs corroboration ('independently confirmed by Cloud Native Now'), satisfying News-category sourcing norms (News has no minimum independent-source count, unlike Analysis). suspicious_patterns in manifest.json is null for all three sources -- no prompt-injection content found.
Factual Accuracy: All direct quotes (Alex Graf x2, Mark Ryland x2, Jessica Forrester/OpenShell, Cloud Native Now's 'doesn't magically secure your data') were checked verbatim against the raw decompressed snapshot text and match exactly, including punctuation. The 'OpenShell' term was specifically checked for possible hallucinated misspelling of 'OpenShift': the raw cloudnativenow.com snapshot (source-2.html.gz) uses 'OpenShell' twice in a coherent, self-consistent technical context ('Red Hat combines OpenShell with Kata... OpenShell is swapping in the real key on the way out of the Kata door') describing a key-substitution/attestation mechanism distinct from OpenShift's function as a Kubernetes platform; the string 'OpenShift' does not appear anywhere in the snapshot. This is the source's own term, accurately transcribed by the submission, not a transcription error introduced by the writer bot. (A corroborating web search for independent confirmation that Red Hat has a project literally named OpenShell could not be completed because the session's WebSearch budget was exhausted; this does not change the finding, since the editorial standard is that the submission must accurately reflect its cited source, which it does.) One finding, documented below: the 'What We Don't Know' paragraph states 'Neither AWS's announcement nor its Compute Blog post specifies which Nitro-based instance families, beyond "most," support Nitro Sandboxes' -- this is incorrect. The Compute Blog (source-1) explicitly states supported instances are 'Every EC2 instance type that supports Nitro Enclaves, across general purpose, compute optimized, memory optimized, storage optimized, and accelerated families, on AWS Graviton, Intel, and AMD processors.' This is a wrong absence claim in a subordinate paragraph (not the headline, summary, or lead), so it is being handled as an APPROVE_WITH_CORRECTIONS correction rather than a REJECT. The adjacent claim about no published benchmark figures for the 'near-native' performance claim was checked against all three sources and holds -- no benchmark numbers appear anywhere in the snapshots.
Overall Assessment: Substantively accurate, well-sourced News article with every quote and specific verified verbatim against raw source snapshots, including a specific check of the 'OpenShell' term (confirmed as the source's own distinct term, not a hallucinated misspelling of 'OpenShift'). Bidirectional source/body-URL match is clean, all three sources are allowlisted, no provenance gaps, no suspicious patterns in any snapshot. One subordinate 'absence claim' error in the What We Don't Know section (instance families are in fact specified by the Compute Blog) warrants a public corrections record; it does not affect the headline, summary, or lead. Featured candidacy: 2 - a major cloud provider's new hardware-isolation primitive aimed squarely at the AI-agent code-execution risk the industry is actively grappling with, of interest to a broad developer/infra and AI-security audience.