Search the evidence

Find the signal.

Search titles, impact clusters, countries, organizations and the full text of every analysis.

2 stories found

An imagined multidisciplinary safety meeting faces a protected stop switch in a data-center control room.
Systemic riskUnited States / Global+2 clusters01

AI labs are asking philosophers for guidance as a safety leader calls for a harder brake

A Hindu monk says Anthropic invited him to discuss AI ethics and the training of Claude. The striking image is not a machine acquiring a religion; Anthropic says it has consulted scholars, clergy, philosophers and ethicists from more than 15 religious and cross-cultural groups, and explicitly rejects making Claude follow one tradition. The company says those conversations may inform its constitution, values and evaluations. We do not know what this particular discussion changed. At the same time, a former OpenAI employee who led writing for launch safety reports has resigned, arguing that a sprinting, trial-and-error culture is inadequate for more capable systems. He says he helped draft OpenAI's Preparedness Framework and oversaw reports for 12 frontier launches. OpenAI told Reuters that it pauses training or holds back models when needed. His essay is an informed first-person critique, not an independent finding that a specific launch was unsafe. The pair of stories asks a sharper question than whether AI companies care about ethics. Whose concern can delay a release, require a new test or change an agent's permissions? A diverse conversation can reveal blind spots; a documented decision process can act on them. Without both, advisers may be heard sincerely and still have no leverage. Readers should look for concrete examples of consultations changing evaluations and of safety objections reaching an accountable go/no-go decision, rather than inferring either safety or danger from a meeting invitation or resignation alone.

6 min
A university promotional banner emerges from an AI editing station with one student silhouette replaced while an unsigned consent form remains in the foreground.
PrivacyCalifornia, United States+3 clusters02

Stanford’s AI-edited banner replaced a real student and exposed a consent failure

Stanford University has acknowledged that a campus dining operation used generative AI to alter real students in a promotional photograph and published the result without disclosure. The original image was taken during a 2024 Lunar New Year dinner and had already appeared in university material. In the new banner, one Hispanic male student was replaced by a synthetic Black woman; reporting also found that two students’ faces or body shapes were changed and their clothing was converted into Stanford merchandise. The banner appeared in student housing before being removed. Stanford said both the alteration and lack of disclosure violated university rules and promised additional training and review. Its current communications guidance already contains the relevant protections: staff must obtain written permission before publishing an individual’s likeness, clearly identify materially manipulated media when omission could mislead, and may not create synthetic depictions of real people without explicit consent. The document also says a human must approve any automated workflow that produces public-facing content. That makes this more than an image-generation mistake. It is a control failure between policy and publication. The university has not publicly identified which tool was used, who approved the prompt or edit, whether the original releases permitted synthetic alteration, or how the banner passed review. The incident also exposes a crude temptation in institutional communications: instead of representing the people who are present, generative tools can manufacture the appearance an organization wants. Removing the banner addresses distribution. Rebuilding trust requires an auditable consent record, a review owner, and a way for people to know when their bodies or identities have been digitally changed before the file leaves the workflow.

9 min