Skip to content

root / tags / manifeste

#manifeste

2 fiches

Philosophy & Society Auto-verified translation

The Future is for Everyone: The Path to a Positive AI Future

Doctrinal manifesto published on **meta.com** on **August 10, 2026**, signed with only a first name (*"– Mark"*) by **Mark Zuckerberg**, under the title *"The Future is for Everyone: The Path to a Positive AI Future"*, ~6,500 words. Three principles are announced from the outset: individual empowerment as a source of prosperity, invention as the primary purpose of superintelligence, balance of power as the foundation of safety. **(A) The central argument is a political argument**, stated as a short chain: *"Humanity is not a monoculture"* — people's values encode opposing trade-offs, no technical solution can align simultaneously with conflicting interests, so any singular superintelligence would have to prioritize certain values over others and would thereby be incapable of being benevolent toward everyone. Hence the formula: *"There is no such thing as a singular benevolent superintelligence."* Safety is reframed as a problem of power distribution, illustrated by a thought experiment repeated three times (a single superintelligent lawyer versus everyone having one; the same for cybersecurity, then for business). **(B) A redefinition of alignment**: *"Solving alignment is necessary for billions of people to adopt personal superintelligence agents. But it also implies that if we reach a state where billions of people are using and scrutinizing personal superintelligence agents, then we will have solved alignment with their interests."* The corollary targets the rest of the industry without naming it: *"the most dangerous scenario would be leading labs training powerful models and keeping them for themselves."* **(C) Datable commitments**: a **fully private** mode where *"even Meta"* cannot see or grant access (a WhatsApp analogy); **free** versions for billions of people paired with a **dynamic bidding mechanism** for paid compute; the announced **resumption** of open source releases — *"we will soon resume releasing some open source models"*; and a structure giving the **independent board** the power to approve release safety criteria and verify each release's compliance, with the author acknowledging that Meta is a founder-controlled company. **(D) Two public-policy proposals**, repeated three times: that labs share **intermediate training checkpoints** and engineers with the government rather than an end-of-cycle review, and that the **physical production** of dangerous materials be regulated rather than the spread of knowledge. The text's sourcing is nearly nonexistent.

#Mark Zuckerberg#Meta#Meta Superintelligence Labs

**Mark Zuckerberg** — fondateur et PDG de **Meta**. Texte signé du seul prénom (*« – Mark »*) · publié le **10 août 2026** sur un domaine dédié de meta.com. La signature n'est pas « Meta » · et l'alternance des pronoms est régulière : **« we » pour les engagements de l'entreprise** (*« we will offer free versions »*, *« Meta is implementing a governance structure »*) · **« I » pour les affirmations normatives ou contestables** (*« I think this view of alignment is fundamentally flawed »*, *« I propose that companies developing frontier AI should… »*, *« My honest guess, and it is a guess »*). Les engagements produits et de gouvernance sont au « nous » · les propositions de politique publique au « je ».

AI Coding Agents & Skills Auto-verified translation

Agent Plugins package your skills, tools, and more

Announcement from **Google** on **August 6, 2026**: Google joins as **Core Maintainer** the **Agent Plugins 1.0.0** specification, an open, *vendor-neutral* packaging format for distributing **Agent Skills** and **MCP servers** together. The specification was published by a **TSC** whose Core Maintainers come from **Amazon, Cursor, Microsoft, OpenAI, and Vercel**; Google joins them, represented by **Kevin Hou** (Senior Staff Engineer, Google DeepMind). The two packaged building blocks — Agent Skills and MCP — originate from **Anthropic**, which does not appear on this list of maintainers. **The diagnosis** fits in one sentence: *"The core problem isn't the components. It's the manifest."* A skill is portable, an MCP server is portable; the box they go in is not, and every client had to invent it for itself — hence the forks, the copies of identical components, and their drift. **The format** fits in one constraint: *"A plugin is a directory. That's the whole idea, and the restraint is the point."* A `plugin.json` with two useful lines (`$schema` and `name`), skills in `skills/` in the Agent Skills format, servers declared in `mcp.json` with an **explicit `type` on each entry** (stdio, Streamable HTTP, or the legacy HTTP+SSE) — no more transport guessed from the shape of the config object. The strength of the design lies in what the manifest **cannot** do: neither relocate components nor declare them inline, so there is no discovery path to configure and no precedence order to learn. Operational corollary: components **fail independently** — an `mcp.json` server that fails to start does not take down the plugin's skills, the client skips the entry, keeps going, and reports the failure. The accepted escape hatch is the **reverse-domain** directory (`com.example.client/`), an extension space owned entirely by one client (hooks, agents, commands) that other clients ignore: *"the portable core stays small because the non-portable parts have somewhere legitimate to go."* A section is dedicated to cases where the format is not warranted — *"Not every skill should be a Plugin"*: a single MCP server to a single client, `mcp.json` suffices; a single skill needs no plugin. What v1 explicitly excludes, under *future considerations*: **no installation mechanism, no distribution protocol, no permissions model, no sandboxing requirement, no trust or provenance verification, no UX**. All of this fits into an independently adoptable four-layer stack — **find** (Agentic Resource Discovery), **describe** (AI Catalog, which would register the `application/agent-plugins+json` type), **package** (Agent Plugins), **run** (MCP + Agent Skills). Two Google products already ship: **Agents CLI** and **Data Agent Kit** (BigQuery, Spanner, Cloud SQL).

#Agent Plugins#Agent Plugins 1.0.0#open specification

Trois signataires · répartis sur trois entités Google :