Radar Daily Briefings

The Authors Guild has publicized newly released briefs in ongoing litigation against OpenAI and Microsoft. The Guild says the filings allege that the companies used copyrighted books, including material from LibGen, and understood the potential effects on authors.

The documents quoted in the briefing describe internal discussions about AI systems substituting for writers, Microsoft’s alleged awareness of LibGen use in 2019, and efforts to delete LibGen files from OpenAI systems and storage in 2022.

For engineers, the material highlights training-data provenance and copyright-governance risks. It is an advocacy account of litigation filings, not a court finding, and supplies no independent technical corroboration or training methodology.

AWS has released Dogwood, an Apache 2.0 open-source language for governing AI-agent tool use. Dogwood policy support is also available inside Amazon Bedrock AgentCore Policy.

Dogwood extends Cedar with temporal conditions over prior tool-call requests and responses. Its operators and standard-library macros can enforce prerequisites, ordering, sliding-window rate limits, distinct-value limits, and aggregate thresholds. Policies can use event schemas generated from Model Context Protocol tools.

Existing Cedar policies remain valid and reusable without migration. However, temporal evaluation requires stateful event tracking, may depend on event-log length, and does not currently provide Cedar’s automated reasoning analysis tools. Absolute-time windows, liveness, and multi-agent features are future directions.

Simon Willison’s 27 September 2026 retrospective surveys major developments in LLMs and coding agents during the year. It covers model releases, local open-weight models, personal-agent projects such as OpenClaw, and the changing role of software engineers.

Willison describes coding agents as increasingly capable when given clear goals, constraints, and tools. He also discusses vibe-coded JavaScript and WebAssembly projects, token costs, and attempts to generate games and other software.

The article emphasizes that rapid generation does not guarantee useful or engaging results. It also highlights agent-security incidents and unresolved questions around verification, safety, and responsible deployment. The comparisons and incidents are presented primarily as the author’s observations rather than systematic evaluations.

The essay proposes “pragmatic anthropomorphism” as a working stance for interacting with LLMs. It argues that developers can treat a model as a collaborator without claiming that it is conscious or possesses human-like feelings.

Its central mechanism is conditioning: detailed technical context supplies the material for useful work, while conversational register may steer generation toward patterns associated with pair programming, critique, or rushed compliance. The essay cites research on emotion-related representations but distinguishes functional behavior from subjective experience.

For engineers, the key boundary is accountability. Collaborative language may be an operational interface, but documentation should describe system functionality and preserve human agency. The argument remains conceptual and offers no controlled performance evidence.

An article recounts developer David Chisnall’s report that NeoVim changed Vim’s persistent-undo format and deleted an existing undo file, replacing it with one Vim could not read. The account led Chisnall to stop using NeoVim.

According to the account, the change neither upgraded nor renamed the older undo file. Chisnall says he was told the format was unstable and that users should not rely on persistent data being preserved.

The episode illustrates why editor migrations need careful handling of durable user data and format compatibility. The supplied evidence is an opinion article without version details, reproduction steps, an official response, or independent confirmation.

A WordPress Community post proposes resolving conflicting guidance about who may organize Meetup events. The author asks whether the current interpretation should be documented and recorded in the handbooks audit.

The post compares the Five Good Faith Rules, an “Any Member Can Organize an Event” page, and older Meetup group guidance. It reports that any community member may run an event without being a co-organizer, while co-organizers should coordinate and confirm trustworthiness and adherence to the rules.

The proposed resolution would retire the standalone page, place Group Tools details in group-management documentation, and keep operational expectations alongside the Five Good Faith Rules. The reported interpretation currently comes from private messages rather than published documentation.

The WordPress Training Team’s September 22, 2026 meeting recap documents work in progress across Learn WordPress education and contributor operations. It reports handbook updates, course development, lesson-thumbnail work, issue categorization, and onboarding opportunities.

The recap says the AI Literacy through WordPress course is live. It also describes prototypes for text-to-speech or read-aloud lesson content, with more team feedback requested before implementation work with Meta. A biweekly GitHub triage meeting is proposed, and volunteers are sought for content review, feedback validation, fixes, and thumbnail creation.

The document is a community update rather than a technical implementation report; it supplies limited detail about mechanisms, results, and completion status.

The official WordPress Gutenberg repository lists @wordpress/viewport 6.56.0 as a tagged release dated September 23, 2026. The supplied page confirms the release identifier and repository context.

No release notes, implementation details, migration guidance, compatibility information, or usage changes are shown in the supplied evidence. The available material therefore supports package availability, but not a description of what changed.

Gutenberg and WordPress integration maintainers can use the release identifier when checking dependencies, but should consult additional release documentation before assessing upgrade impact or required code changes.

The official WordPress Gutenberg repository records @wordpress/warning version 3.56.0 as a released package. The release entry is dated September 23, 2026, and references commit 56d8058.

The supplied page identifies the package and release tag but does not explain what changed in the implementation. It includes no changelog, compatibility information, migration instructions, benchmarks, or feature description.

Gutenberg package consumers can use the entry to confirm the released version, but the available evidence is insufficient to assess technical impact or determine whether action is required.