FlashFeed

Full text

At the time of her death in 2019, the late Mary Oliver was one of the most successful American poets to ever publish. She wrote dozens of collections, and several highly quotable bangers that a reader would be as likely to encounter on the family bookshelf as the SAT.

With champions like Oprah and Maria Shriver, Oliver bypassed the cultural barrier that’s often left poetry siloed from the other letters, tethered to the academy.

Her greatest hits—”Don’t Hesitate,” “ Wild Geese “—were that rare thing: recognizable, which helped her curry a reputation as a people’s poet. Beloved for writing accessible, romantic odes to the natural world.

A new documentary from Sasha Waters, the filmmaker behind Garry Winogrand: All Things are Photographable , aims to stir up that genteel impression, and complicate an artist who’s sometimes been dismissed as a “nature poet.”

Waters, a filmmaker with avant-garde origins, discovered Oliver’s work more than 30 years ago care of Garrison Keillor’s Writer’s Almanac. She was drawn to film Oliver’s life story care of a lifelong fascination with images. “There’s a relationship between representational photography and poetry,” she told me in a recent phone interview.

“In the best case scenario they both draw from the actual world—the visual world, the social world—and then transform their materials through metaphor.”

Oliver in her adopted Provincetown.

Produced by Kino Lorber, Mary Oliver: Saved by the Beauty of the World uses Mary’s “materials” to show the poet’s unruly side. This was no easy task, for Oliver was notoriously fierce about guarding her private life. And very little filmed footage of the artist exits.

That plus a predilection for writing about untrendy animals combined to give the impression that Oliver was—as Waters told me—”a sweet little old lady,” more accessible than sophisticated. But in Saved by the Beauty of the World , a more dynamic picture emerges.

Composed of interviews with Oliver’s close friends (John Waters, David Keplinger) and admiring peers (Major Jackson, Ariana Reines), and interspersed with recitations from celebrity fans (Stephen Colbert, Lucy Dacus), there’s an ekphrastic quality to the film. We drift between homage and analysis.

In early scenes, weight is given to Oliver’s eccentricity and ambition, two under-sung traits. Casual fans may be surprised by the film’s categorization of the poet: this Mary is bohemian, dogged, and desirous.

A young Mary Oliver, surrounded by books.

This reader did not know, for instance, that Mary Oliver was a teenage runaway—though she forsook the charms of a major city for the wild. (“Some people go into the library,” Mary narrates at one point. “I went into the woods.”) I also did not know that she left home again at 17 to talk her way into an internship at Steepletop, the home of Edna St. Vincent Millay.

I did not know that Oliver had a bohemian era in Greenwich Village, or that she was a lifelong smoker. Or that for most of her life, she lived at the poverty line so her devotional practice could be structured around daily walks in the woods surrounding her home in Provincetown.

Mary and her partner of decades, Molly Malone Cook. In the film, Oliver refers to their incredible bond. “We were talkers. It was a 40 year conversation.”

I also did not know that Oliver was a lesbian poet, partner to the gallerist and photographer Molly Malone Cook for thirty years. In the film, John Waters (no relation to the filmmaker), offers an especially fond reflection on their love story, which shaped Oliver’s early work and facilitated her career.

And though Oliver never wrote about bodily lust the way certain peers did, Saved by the Beauty of the World insists over and over that love was the writer’s guiding star.

More than nature, her true subject—both Waters’s suggest—was awe. Oliver trafficked in deep feeling, and insisted on honoring life in every gesture. She measured a poem’s success by a three question metric: if a work served a spiritual purpose, had a sincere energy, and a genuine body, she felt she could stand behind it.

Mary Oliver with her two dogs.

The film works well enough as a detailed homage with flashes of lyricism (see: celebrity recitations). But for all its revelations, Saved… is not full blown hagiography. This is to its credit. There are the dotty, endearing asides—as when John Waters relates the time when Mary was bitten by a badger on a woodland stroll.

Then there are darker mysteries.

Space is given to Oliver’s detractors, who wish she we would have weighed in on the AIDS crisis as a queer woman writing during its heyday. Another hole in the poet’s life circles a late in life relationship Oliver commenced after Cook’s death. The film casts Mary’s second partner Anne in angry shadow, as friends question the couple’s compatibility, and a late life move to Florida.

In another key moment of wobble, the poet Nick Flynn offers a summary critique of the guardedness Oliver was known for on the page. “She always presented herself in the light,” he says, seemingly when asked about the limits of his fandom. There was “no wrestling with her own shadow.” Which feels fair, given highlights in her canon.

Oliver at her typewriter.

But in the film’s final chapter, as Oliver is collecting laurels and the profound public recognition she would die with, the poet comes into speech about sexual abuse she experienced in childhood.

This ability to speak about her own life at last is framed as an artistic victory—though the poems selected to frame this revelation were not necessarily written during Mary’s later years.

In general, the work is presented as a kind of thematic thru-line, a non-chronological companion to Mary’s biography. And as for the darkness circled, Waters (Sasha) told me that all unflinching light in the film was included by design, as a testament to Oliver’s most sacred covenant: attention is tantamount to love.

“I think she genuinely was indifferent to the trends of the literary establishment,” said Waters. “She was playing the long game. She wrote for an audience she always believed was out there, and also for the future…in her lifetime and beyond.”

As a viewer who went into Saved… a general but maybe not-so-rapturous Oliver fan, I can tell you I left stirred up and tender, with poetry on my tongue. I wanted to yell at a canyon or walk in the woods—and these activities did not strike me as prosaic or gentle so much as sensual and profound.

I hope you can find Mary Oliver: Saved by the Beauty of the World playing in limited release near you.

Images via Kina Lorber

Full text

Enterprise companies are running AI agents ahead of the controls needed to manage them — and they deployed that way knowingly. That is the central finding from VentureBeat Research's June survey of 573 technical leaders at companies with 100 or more employees, fielded across five parallel surveys of the agentic stack.

Enterprises are now retrofitting to catch up with their own standards, and they are budgeting for it: Roughly six in 10 enterprises plan to switch or add vendors in each of five control layers within the next 12 months, and roughly a third — depending on the layer — plan to move within the quarter, the research finds.

There are five main layers where enterprises are building: identity for agents (which agent is allowed to do what, under whose credentials); evaluation of agent output (whether the work is any good); cost telemetry (what each agent costs to run); the context layer (the business data and definitions agents draw on to answer); and the orchestration control plane (the software that coordinates multi-step agent work).

Enterprises are already paying the price for deploying agents ahead of adequate control functions. Fifty-four percent of companies had an agent security incident or near-miss caught before harm in the past 12 months. Twenty-seven percent exercise only reactive control of agent spend — they learn what an agent costs when the invoice arrives, with no per-agent budget or ceiling in place.

Here are the five findings that anchor the set — one finding per layer of the tech stack — and what the data suggests doing first in each.

Expensive hardware is idle: 86% of GPU operators report utilization of 50% or less

Eighty-six percent of enterprises that run their own GPUs report utilization of 50% or less. Wall Street has spent the quarter debating whether the AI buildout is overbuilt. This is buy-side measurement, from the enterprises doing the buying, and the research says the most expensive hardware in buildings of these enterprises runs at no more than half its capacity.

The measurement gap compounds it: A minority 44% rigorously track what their AI compute actually costs and returns. Everyone else is only estimating. And the enterprise shopping process continues regardless: 45% of these enterprises say the emerging compute option they are most likely to evaluate in the next 12 months is an AI-specialized cloud (CoreWeave, Lambda, Crusoe, Nebius). However, under 2% of these enterprises report using one of these neoclouds today.

Moreover, roughly one in three companies appears to be considering a hedge against Nvidia: Asked which emerging compute option they are most likely to evaluate in the next 12 months, 32% of enterprises named non-Nvidia accelerators (AWS Trainium, Google TPUs, AMD), while 28% named next-generation Nvidia GPUs. The data suggests that enterprises should measure the utilization and per-workload cost of the GPUs they already own before committing budget to new compute — whether that's an AI-specialized cloud contract, new accelerators, or more GPUs.

Most deployed "agents" do single-prompt work: 71% say a quarter or fewer complete multi-step tasks on their own

Seventy-one percent of enterprises say a quarter or fewer of their deployed "agents" can complete multi-step work on their own; the rest are single-prompt chatbots. Only 10% say true agents are the majority of what they run. To be sure, the respondents reported that they are in a position to know these things: 81% said they recommend or decide AI purchases at their companies.

That finding — that most agents are actually just chatbots in trenchcoats — lands amid adoption claims across the industry running well ahead of what enterprises are actually running. Gartner predicted 40% of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% in 2025. It also warned that the most common misconception is referring to these AI assistants as agents, a misunderstanding known as "agentwashing."

Meanwhile, Zapier's enterprise survey said 72% reported deploying or testing autonomous agents; and Writer's 2026 survey has 97% of executives saying their company deployed AI agents in the past year.

Those surveys asked whether companies have deployed something called an AI agent, and companies said yes. Our survey asked the people running those deployments a harder question: Of the agents you have in production, how many can complete a multi-step task without a person driving each step? The gap matters for two practical reasons. First, the inflated adoption figures are the benchmark boards and vendors use to pressure technical leaders into moving faster — and this data says the real bar is far lower than the headlines suggest. Second, the label determines the bill: A single-prompt chatbot with a human reading every answer needs none of the identity, evaluation, and cost controls this report covers, while a true multi-step agent needs all of them.

66% let agents push to production on automated evals alone — or are engineering toward it. 5% fully trust those evals

Two-thirds of enterprises fall into one of two camps: 34% already allow an AI agent to push a code or system change to production based on automated evaluation results alone, with no human reviewing it, and another 33% are actively engineering their pipelines to allow that within the next 12 months. Only five percent fully trust the automated evaluations that would make that decision.

The distrust is earned. Half of enterprises shipped an agent that passed internal evaluations and then caused a customer-facing failure in the past year; a quarter watched it happen more than once. Asked to name the biggest weakness in their current evaluations, more enterprises chose “poor alignment with real-world outcomes” than any other answer — 29% of respondents.

And most of the checking happens before an agent ships, then stops. Once agents are live with real users, only 23% of enterprises run real-time quality checks on the answers those agents produce. Another 51% monitor system health only — uptime, request traces, and gateway logs — which tells them the agent is running, and nothing about whether its answers are right. The first move: Before removing human review from any workflow, test your evaluations against production outcomes rather than internal benchmarks, and instrument answer quality, not just uptime.

This finding is explored in more depth in VentureBeat's related coverage of the evaluation gap , which found that larger enterprises are moving faster toward zero-human deployment while also failing more often — and outlines a regression-testing framework built on production outcomes rather than internal benchmarks.

69% run credential sharing somewhere in the agent fleet — and those companies get hit far more often

Sixty-nine percent of companies allow agent credential sharing somewhere in their agent fleet during runtime – meaning multiple agents operating under one API key or service account. Those companies were far more likely to get hit: Organizations with credential sharing anywhere in the fleet experienced a security incident or near-miss at a 63.5% rate (47 of 74), against 40.9% (9 of 22) where every agent has its own scoped identity.

The takeaway for enterprises is this: Give every agent its own scoped identity, starting with the agents that touch production systems.

57% traced a confident, wrong agent answer to their own missing or inconsistent business context

Fifty-seven percent of enterprises traced at least one confident, wrong agent answer in the past six months to missing or inconsistent business context: wrong metrics, stale definitions, absent documents. Most of them watched it happen more than once.

Most enterprise companies are fixing this, even though they’ve moved forward with agent deployment already: 25% already run a governed semantic layer, or one governed definition of the business that every AI reads from, in production. However, 34% are still building one, and 41% haven't started. The takeaway: Govern the definitions your agents answer from, metrics and entities first, before scaling the agents that depend on them.

The quarter where agent technology “portability” became a priority

One more shift is worth reporting with its limits stated plainly. In our spring orchestration survey wave, the top concern about provider-controlled orchestration was security and permissioning limits (32%). By June, vendor lock-in led at roughly a third, with security limits at 28%.

Those are two snapshots one quarter apart, and here’s one possible explanation for why portability became a top issue for enterprises. Our June survey went into market after a June 12 U.S. Commerce Department export order took Anthropic's Claude Fable 5 offline for enterprises for roughly three weeks. Meanwhile, Chinese company Z.ai released GLM-5.2's open weights under an MIT license on June 16 at roughly one-sixth of GPT-5.5's price; and Tencent's Hy3 arrived July 6 under Apache 2.0; and OpenAI previewed GPT-5.6 on June 26 to a small group of government-vetted partners, opening it broadly on July 9 after the government's review cleared. The open-weight releases in particular promise enterprises more control over their agents, and while we haven't established a causal link here, the timing is worth noting.

The posture data matches the mood: 51% now expect their primary control plane for enterprise agents to be hybrid — provider-native plus external orchestration — by the end of 2026, up from 34% in the spring survey wave. Enterprises reporting that they rely purely on provider-managed agent services fell from 12% to 7%.

Five layers, no incumbents, 12 months

The synthesis across all five surveys reveals a huge “buying” window. In each of the five control layers, 57% to 64% of enterprises plan to switch or add vendors within 12 months — 64% in infrastructure and in evaluations, 59% in agent security, 57% in retrieval and context — and 26% to 38%, depending on the layer, plan to move within a quarter. No layer has an established incumbent: The most common evaluation tooling is the model provider's built-in evals, tied with no dedicated tooling at all (17% each); 82% of respondents name provider-native or hyperscaler controls as their primary agent security layer; and provider-native retrieval leads the context technology layer (RAG, etc) as well.

Most enterprises are defaulting today to the built-in tools that ship with the big AI platforms they already use: Anthropic, OpenAI, Google, Microsoft, and AWS. That holds true across every one of these agentic technology layers: enterprises are looking to their primary cloud and model providers to supply the guardrails, evaluations, and retrieval solutions already bundled into those providers' offerings.

Those defaults are winning on convenience, and they're also what the coming spending decisions will test. The survey didn't ask which direction that money moves — toward the platforms' built-in tools or toward the specialists challenging them — which is exactly why every contract in these five layers is worth watching over the next four quarters.

The Q3 survey wave will measure whether the enterprises made good on these budget plans: whether their agents gained scoped identities, whether evaluations got tested against production outcomes, whether GPU utilization rose, and whether the semantic layers under construction shipped.

VentureBeat will release the full Q2 reports across all five VB Pulse trackers at VB Transform , July 14–15 at Hotel Nia in Menlo Park, where we convene enterprise technical leaders building autonomous agents in production.

Disclosure: VentureBeat produces both this research and VB Transform

Full text

Early Christian communities in Sweden often buried children in the same grave with adults, but archaeologists have found that these individuals rarely shared close biological ties, raising the question of how medieval people interred their dead.

In a new study, researchers analyzed the DNA of 142 skeletons from three cemeteries in Sweden dating to the 10th to 14th centuries, focusing on collective burials in which two or more people were buried in the same tomb.

"We often assume that adults and children sharing a grave were parents and children or other close family members," study first author Maja Krzewińska , a paleogeneticist at Stockholm University, said in a statement . "In most cases, that was not what we found."

The researchers determined that most burials containing multiple individuals held both adults and children and that the people buried together were usually of the same sex — a woman buried with a girl or a man buried with a boy. But the DNA analysis held a surprise: People buried together rarely exhibited close biological kinship, the researchers wrote.

When Christianity spread across Scandinavia starting in the late 10th century, burial practices became more uniform. Graves were oriented east to west, and people were buried in a simple shroud without any grave goods. Baptized individuals were allowed to be interred in consecrated cemetery grounds, while babies who died before they could be baptized were excluded.

"We have previously analyzed a burial containing an adult and the remains of a fetus, which we believe represents an unbaptized individual," Krzewińska told Live Science in an email.

A photograph of the Västerhus church ruin, Frösö parish, in Jämtland, Sweden, before 1951, where archaeologists have found many burials of children who weren't interred with close family members. (Image credit: Riksantikvarieämbetets arkiv ) These unusual burial arrangements likely point to early Christian traditions. For instance, some of the children buried with adults in the new study may have been unbaptized. Normally ineligible for burial in the cemetery, the children may have been opportunistically interred with an adult to get around religious norms. Other burials may reflect unrelated people buried together in the spring after passing away in the winter, when burial in the frozen ground was impossible.

"We also believe, based on more distant genetic affinity, that some co-burials represent more distant family relations, or even non-biological kin group relations," Krzewińska said.

In early medieval Scandinavia, households often included extended relatives, servants, employees and enslaved individuals, the researchers wrote. While biological kinship played a large role in the organization of society, membership in the local Christian community may have been equally important in determining where and with whom to bury a deceased person.

"Archaeologists have debated the relationships between people buried together in this type of grave for a long time," study co-author Anna Kjellström , an archaeologist at Stockholm University, said in the statement. "Ancient DNA has finally given us the tool we have been waiting for to test these interpretations directly."

We are family

In addition to collective burials of unrelated people, the archaeologists discovered evidence that some families were buried within the same cemetery over several generations. One burial, known as Lady 56, was a Christian pilgrim who anchored three generations of relatives.

A photograph of a pilgrim shell found at the Västerhus cemetery. This type of scallop shell is a symbol of Christian pilgrimage to Santiago de Compostela in northwestern Spain. (Image credit: Christer Åhlin, Historiska museet, 2012 ( CC BY 4.0 )) Lady 56 died when she was around 30 years old. She was buried with a rare scallop shell, a symbol of the apostle James, that she obtained after completing a pilgrimage to Santiago de Compostela , a town in northwest Spain on the edge of Christian Europe.

The researchers also identified Lady 56's kin group, which was of particular importance to the community and stretched over generations in the Västerhus cemetery, Krzewińska said. The DNA analysis revealed that Lady 56's parents, brother and daughters were also buried in the same cemetery, but in different places.

Related Stories

1,000-year-old burials of 'first Christians' in Poland discovered near medieval settlement

Medieval grave of 'very, very powerful' man and his 4-foot-long sword unearthed in Sweden

Up to 20,000 coins from Early Middle Ages discovered by man digging for worms near Stockholm

Västerhus was part of a wealthy landowner's farm from the 11th to 14th centuries, and the cemetery contained the remains of more than a dozen members of a biologically related group, many of whom were interred with members of a different kin group.

The DNA connections between the main Västerhus family and other kin groups in the cemetery support the special status of the main family. These close-kin burials highlight the importance of ancient-DNA testing, as different burials from the same time and region can follow very different traditions.

What do you know about Jesus Christ, the man? Test your knowledge of biblical archaeology with our Jesus Christ quiz!

Full text

Keep our news free from ads and paywalls by making a donation to support our work!

Notes from Poland is run by a small editorial team and is published by an independent, non-profit foundation that is funded through donations from our readers. We cannot do what we do without your support.

Soldiers in Poland will be able to pick up their uniforms from their nearest parcel locker rather than having to collect them from military stores under a new scheme being rolled out by the armed forces, with private logistics giant InPost responsible for deliveries.

The move is a “simple, practical change” that will make life easier for troops, said a deputy defence minister. The CEO of InPost, which is Europe’s largest operator of parcel lockers, praised the decision to make “dual use” of private infrastructure for national-security purposes.

📦 Żołnierze odbiorą umundurowanie w paczkomacie. Trwa pilotaż nowego systemu.‼️

🔊W Siłach Zbrojnych RP trwa pilotaż nowego systemu, który rozszerza możliwości zaopatrywania żołnierzy. Już od przyszłego roku funkcjonować będzie Platforma Wysyłkowa Przedmiotów Umundurowania i… pic.twitter.com/NGUAQognYX

— Inspektorat Wsparcia Sił Zbrojnych (@IWsp_SZ) July 9, 2026

Under the new system, military personnel can order equipment via an online system and collect it from parcel lockers, which are devices that allow users to collect packages independently at any time.

“We want soldiers to be able to order their equipment in a modern, simple, and convenient way, without having to adjust to the opening hours of stores, and to be able to do so at any time they choose,” said General Dariusz Mendrala, the head of the Armed Forces Support Inspectorate (IWsp SZ).

A small pilot scheme began last year and has now been expanded to over 20,000 soldiers. That figure will rise to around 60,000 by the end of this year, before the system is fully rolled out in 2027.

Click here to help us continue providing news free from paywalls and ads

“This is a simple, practical change…that will make soldiers’ daily service easier,” said Cezary Tomczyk, a deputy defence minister, sharing details of the scheme on social media.

He indicated that the system covers other equipment in addition to uniforms, though neither he nor IWsp SZ have specified what types of gear are included.

Sharing Tomczyk’s post, Rafał Brzoska, the founder and CEO of Inpost, said that the scheme was a good example of the “dual use” of civilian and commercial technologies for national security purposes.

“Polish business has been calling for years: let’s use domestic technologies, infrastructure and enterprise to reinforce the state’s defence,” wrote Brzoska. He noted that Ukraine has shown, for example through its drone industry, how private enterprises can support the military.

Polski biznes od lat apeluje: korzystajmy z krajowych technologii, infrastruktury i przedsiębiorczości do wzmacniania obronności państwa. @MON_GOV_PL właśnie pokazuje, jak przejść od deklaracji do działania!!

I to jest właśnie realny dual use, o którym wszyscy mówią, tylko w… https://t.co/oXA8dmoVpE

— Rafał Brzoska (@RBrzoska) July 10, 2026

A spokesman for IWsp SZ, Lieutenant Colonel Piotr Płuciennik, confirmed to broadcaster TVN that InPost had been selected in a tender to manage the deliveries until December this year. He said that the system was set to cost around 2 million zloty (€462,00) a year.

InPost operates by far Poland’s largest network of parcel lockers: its almost 29,000 devices represent around half the total number in the country. The company has also expanded rapidly in western Europe, where it operates parcel lockers in the UK , France and Spain , among other countries.

Płuciennik said that the delivery company is given pre-packaged parcels that feature only the soldier’s phone number on the label. For security reasons, they are delivered only to parcel lockers, and not to home addresses.

With an estimated 233,800 military personnel in 2025, Poland’s armed forces are the third-largest in NATO , behind only the United States and Turkey. That figure has more than doubled in the last decade as Poland has ramped up defence spending in response to a growing threat from Russia.

Poland has NATO’s third-largest military and the alliance’s largest in Europe, new figures show.

For more, see our full report here: https://t.co/QBBVQ9cqzS pic.twitter.com/TA34KQrJ4k

— Notes from Poland 🇵🇱 (@notesfrompoland) July 16, 2024

Notes from Poland is run by a small editorial team and published by an independent, non-profit foundation that is funded through donations from our readers. We cannot do what we do without your support.

Main image credit: st.szer. Wojciech Król/CO MON (under CC BY-SA 4.0 )

Full text

Microsoft's cuts across Xbox studios, totaling 3,200 by later this year, included a massive reduction at id Software. The team lost 136 people (over half of the studio) just a day before its Doom: The Dark Ages expansion released, a bloodletting that had remaining and newly laid-off employees seriously concerned about the studio's capacity to make games and update its proprietary engine, idTech, going forward.

"Nothing says business success like nuking a team into the dirt and relegating them to support studio size while also throwing out massive technological achievements," one impacted worker said.

Today, the official id Software X account made a statement aimed at assuaging these worries.

"While our studio was impacted, those changes were spread across teams. We still have the crew we need to build the games and tech we're known for. The team today is about the same size we were when making DOOM (2016). We have always had a flat studio where everyone is a maker, and we will remain true to that philosophy moving forward," the post reads.

That bit about the current size of the team matches a Windows Central report that also claims the studio is not being forced to move to Unreal Engine in the immediate future, as employees have openly speculated about. The studio's statement also suggests that it will continue work on id Tech.

"We are focused on supporting each other and the team members impacted. We're going to keep building the great games and tech that have defined us for the past 35 years, and we're looking forward to seeing you at QuakeCon this August."

(Image credit: id Software on X) While it's encouraging to learn that id Software won't immediately join a Fallout assembly line, as is Obsidian's new charge , the statement is unlikely to change a growing impression that Microsoft is an unfit steward of the studio synonymous with PC gaming. Personally, knowing that id Software is the same size it was 10 years ago isn't an encouraging sign for its future—it takes more people and more time to make games of Doom's scale and fidelity than it did in the 2010s, hence why the team had grown to 200-plus for The Dark Ages.

Whatever id makes next, it will now do so with an axe hovering over its neck.