Find articles, news, tools and templates by subject or by the work you need to do.
137 results for “Set a release policy” · 73–84
News · Platform engineering ·
The alliance supports storage, generation and flexible AI workloads as ways to change grid demand. For a scheduled evaluation, a safe pause can still miss the deadline the job serves.
Read news: AI energy alliance backs data centers that can vary grid demandNews · AI in production ·
Claude’s on-demand compaction lets an application replace older conversation history with a signed summary. A conditional restart shows why the summary must preserve relationships between instructions.
Read news: Claude adds on-demand compaction for long-running agentsNews · AI in production ·
Claude Enterprise’s Compliance API beta now includes Chrome-session transcripts. Tool exchanges help locate an attempted action; the destination’s records establish whether it took effect.
Read news: Claude’s Chrome transcripts enter the enterprise audit trailCommentary · AI in production ·
Version checks, durable operation records and independent service checks give a production agent a recovery path when approval or execution becomes uncertain.
Read commentary: How production agents handle stale approvals and uncertain writesExplainer · Platform engineering ·
A stalled rollout shows how platform repair and application recovery depend on different teams, with a handoff that keeps both investigations moving.
Read explainer: Where SRE and platform engineering need an explicit handoffExplainer · AI in production ·
A short answer can conceal document retrieval, repeated context and retries. Task-level accounting connects those costs to the work the answer actually saves.
Read explainer: Where an AI task’s tokens, time and cost goGuide · Incident response ·
Evidence can split a 5 Whys investigation into several contributing causes. A concurrency example shows how to turn those explanations into useful tests.
Read guide: Why a 5 Whys investigation can branchGuide · AI in production ·
Conflicting restart instructions show where a source-backed notebook helps: finding the relevant passages, dates and exceptions for the runbook owner.
Read guide: Comparing incident sources with NotebookLMGuide · AI in production ·
A rollback exception tests whether Opus 4.6 preserves decisive evidence across a long session, and whether the resulting answer arrives in time to help.
Read guide: Evaluating Claude Opus 4.6 for incident workExplainer · Platform engineering ·
Model loading and checkpoint recovery stress storage differently. Reference configurations help explain which workload and failure conditions their results cover.
Read explainer: AI storage and recovery in NetApp and NVIDIA architecturesGuide · Platform engineering ·
Directory conventions orient the investigation. Mounts, namespaces, inodes and service permissions explain which storage the failing process actually encounters.
Read guide: Finding a Linux write failure through paths and mountsGuide · AI in production ·
An approved summary task can take a new data path when a connector is added. Account controls, retention and output sharing apply at different points along that path.
Read guide: Where workplace ChatGPT data goes