Felix Arntz 9:06 pm on February 3, 2026
Tags: #core-ai ( 2 )

Proposal for merging WP AI Client into WordPress 7.0

This proposes merging the WP AI Client into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for WordPress 7.0.

WP AI Client is developer infrastructure: a provider-agnostic APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. for WordPress code to call generative AI models via a consistent interface, with WordPress integrations for HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. transport, event handling, caching, credentials, and a browser-friendly REST/JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. layer.

Providing this foundation, in collaboration with the Abilities API that is already part of Core, will make WordPress ready for AI, both as a consumer and as a tool.

This merge does not ship any AI providers or automatically enable AI calls. Without explicit configuration and explicit calling code, WordPress will not send prompts or data to any external service. Site owners will be able to install plugins to enable usage of specific AI providers, built on top of this foundation.

Purpose & Goals

Goals

Provide a stable, provider-agnostic AI client foundation in Core, with seamless integration with the Abilities API
Reduce duplicated SDKs/settings pages by centralizing common infrastructure (transport, auth storage, prompt invocation, access controls).
Enable plugins to detect availability and gracefully disable AI features when no model is configured.

Non-goals

No bundled credentials or providers.
No end-user “AI assistant” UIUI User interface in core.
No product-level experiences standardized in this merge (those remain pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/ecosystem territory for now, e.g. AI Experiments plugin).

Proposed Scope

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher API + Prompt Builder – A WordPress-friendly API to construct prompts and invoke model capabilitiescapability A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).. The underlying PHP AI Client will be bundled as an external library, while the WordPress specific wrapper code will become a direct part of Core.
Provider/model abstraction – A consistent interface so hosts/site owners can choose providers via plugins, and plugins that use AI can remain vendor-neutral.
Discoverability – Plugins can dynamically enable AI features, based on detecting whether any configured model on the site is able to respond to the relevant prompt(s).
WordPress HTTP integration – Transport aligned with WP HTTP conventions and WP_Error behavior.
Credentials management in wp-adminadmin (and super admin) – Admin UI/storage for provider credentials, used across plugins.
REST endpoints + JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. API – A REST-backed JS API for browser contexts (wp-admin/editor use cases).
Simple control mechanism for prompt execution – A filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. allows allowing or disallowing certain prompts or prompt configurations, or even AI use in general.

Security, Privacy, Performance

Security: REST/JS execution must remain capabilitycapability A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).-gated; secrets must not leak via REST/script data/logging.
Privacy: no outbound AI calls by default; calls only happen via explicit configuration + explicit invocation.
Performance: minimal footprint when unused; admin-only work should avoid affecting typical frontend requests.

Call for Feedback and Testing

Feedback is welcome via comments on this proposal or on the Trac ticket which has been opened for this change.

In particular, feedback is needed for:

Is the REST/JS surface area and capability model appropriate for long-term support?
Any missing core requirements for transport, errors, or credential storage?

As of now, there is no pull request yet. Please follow the Trac ticket to be notified when a pull request has been opened. Here are the steps you will need to follow for testing:

Apply the core PR (install a test build or utilize the WordPress Playground instance from the PR) and confirm the admin credentials UI is access-limited.
Configure a provider (or install/register a provider integration as needed).
Run a minimal prompt test:
- server-side (small MU plugin/snippet)
- browser-side (JS API), verifying capability checks
Verify behavior with no provider configured:
- no unexpected networknetwork (versus site, blog) calls
- no UI regressions
- plugins can detect and gracefully disable AI features

Props to @isotropic @jason_the_adams @jeffpaul for collaborating on this post.

#core-ai

Paul Shryock 9:30 pm on February 3, 2026

No thank you.
- Birgit Pauli-Haack 7:38 am on February 4, 2026
  
  Care to elaborate?
  - Jer Clarke 4:03 pm on February 4, 2026
    
    I will: WP doesn’t need permanent dependencies in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for things that many don’t want and are currently a moving target.
    
    People who want this can install a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, and have been, clearly. Plugin territory if I ever saw it.
    
    It’s also a huge attack surface, and I don’t trust people using AI to build it well.
    
    WP is about making decisions, and saying “no” to most things is the correct decision.
    
    Add this once multilingual support is added in core, as promised a decade ago, then I’ll agree there’s time for this.
    - Jason Adams 6:56 pm on February 4, 2026
      
      Hi there!
      
      I hear what you’re saying. We want to be careful about what we add to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., especially to your point about chasing technologies. MCP is a good example of this. We’re purposely not adding this to core because we don’t know where that will be, so having the MCP Adapter as a canonical pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party makes more sense for folks that have a purpose for it now.
      
      On the other hand, I think it’s fair to say that AI, specifically LLMs, aren’t going anywhere anytime soon. It’s transforming the entire tech industry, and we want to empower plugin developers and users with a low bar way of interacting with the AI model of their choice. The ownership remains with the site owner. They can disable AI entirely, use a model compliant with their needs (e.g. HIPAA compliance), and lock it down to things like specific user roles.
      
      As far as trusting folks implementing AI, you’re right that this remains in the categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. that it’s important that site owners are discerning about which plugins they install on their sites. AI isn’t introducing the importance of this.
      
      So I agree that for folks that want to say “no”, they still can. This won’t ship with any providers, so by default it’s disabled. For folks able and willing to press into what AI is enabling, this expedites that process while maintaining site owner control.
      
      I’m not necessarily trying to convince you, but I hope this at least makes sense. 🙂
Jb Audras 9:49 pm on February 3, 2026

I really appreciate the way this set of features is introduced into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: opt-in, agnostic, privacy compliant, and non-obstructive / not degrading the experience for websites that don’t need these features.
That sounds like a nice work, can’t wait to see the related PR (especially since we’re so close to betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1!).
Thanks for putting this proposal together Felix 👍
Jeffrey Paul 3:01 am on February 4, 2026

+make.wordpress.org/ai/
Kadim Gültekin 5:50 am on February 4, 2026

It should definitely be in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Also MCP Adapter should be in Core.
- David Levine 9:09 pm on February 5, 2026
  
  Not just should MCP Adapter not be in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but MCP probably shouldn’t be in your workflow.
  
  https://www.anthropic.com/engineering/code-execution-with-mcp
  https://blog.cloudflare.com/code-mode/
Matt Medeiros 3:19 pm on February 4, 2026

Long term WordPress advocate and short term vibe coder here:

I think it’s great that we’re building something that (hopefully) keeps native AI integration agnostic across providers. The general talk around WP + AI is with what we can do with frontier models. From where I’m sitting, I’m not sure how they sustain meteoric growth while keeping costs as low as they are in the year 2026.

I rarely hear about the open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. models being paired up with WordPress, and that’s a bit concerning for a flagship open source project. But I do appreciate our approach isn’t as heavy handed as “paste your OpenAI, Anthropic, or Gemini APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. key here”

On one side of the coin, I see the urgency to push WP into this new era, keeping the software relevant. The other side of the coin is to question if we are moving _too_ fast. There’s no easy answer.

For the last 15 years WordPress has had a bit of an identity crisis. Blogging tool? Website builder? The framework for an app? Headless backend?

I think we accelerate the loss of identity if we’re simply building for machines. I’m not saying that’s what this proposal is, but it would be the catalyst moment for me.

A strength of WordPress is its familiarity — it looks the same 100/100 times I install the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. I know it, I trust it, I modify from there. And while there’s no way back from AI at this point, are we only helping lose our identity by building for machines?

So, what makes WordPress…WordPress?

How do we protect the ideals around that before it’s just a collection flavorless code?
Mateus Machado Luna 5:42 pm on February 4, 2026

I’m really excited about this!

Currently we have a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party that we’re planing to release on the WordPress repo but we feel it is worth hanging a bit to take advantage of some of the work being done in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and avoiding releasing extra stuff that we would have to maintain.

One of this points was the model credentials UIUI User interface. So when this is merged, will we have that same screen that the AI Experiments plugin contains in Core? The one where you can add your api keys? Does it makes sense for our plugin to have this UI and if it does, could we consider migrate in the future to core’s?

I also saw in a recent AI Experiments post the idea of a logging UI where you can track costs of usage. We have built that already, but I feel it is too much and again something that many others might have. It would be great to have this tracked globally taking account of multiple plugins usage.

Is there any guidance regarding taking this type of decision? When to build something by our own, when to wait for core… is putting the AI Experiments plugin as a dependency plugin something we should consider? Things are moving fast but we always feel we’re a bit of sync.
- Jason Adams 6:11 pm on February 4, 2026
  
  Sharing my two cents, the goal of WP AI Client being in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is to expedite pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developers’ ability to run AI prompts against a broad range of providers. Plugin developers are welcome and encouraged to use this to speed them up to a certain point and then run past it. We’re being careful about what goes in core because we’re also trying not to introduce something that may become outdated or even abandoned later.
  
  We’re planning on including the credentials setting screen as part of core, but that will be its own PR with its own discussion. There’s so far been no further discussion around screens beyond this in core, at least for 7.0.
  - Felix Arntz 10:33 pm on February 4, 2026
    
    To add some context, an important consideration for this project is that it has two primary integration points:
    1. The one that the majority people will develop against is to use AI, i.e. invoke an AI model to respond to/generate/do things. We have been referring to these developers as AI implementers.
    2. The other one that much fewer people will develop against is to implement AI provider connections, e.g. for cloud based providers, local providers, or even company-internal self hosted providers. We have been referring to these developers as AI extenders.
    
    No providers will be included by default, which is important for a project like WordPress, being a neutral party. At the same time, the AI client only becomes effectively usable for the AI implementers if there’s one or more providers configured.
    
    Both AI implementers (who build features) and AI extenders (who build provider connections) put their code into plugins. For an ecosystem friendly approach, ideally they should be decoupled, so that end users are free to choose which provider(s) they like and still can use more or less all kinds of AI features that exist in the ecosystem.
    
    But in order for that to work at scale, the integration point has to be central – i.e. in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Without it, plugins have to bundle the package, but the proper way to do this (to avoid conflicts with other plugins also bundling the package) is to prefix the code structures. But then that leads to the problem that everybody ships their own version of the centerpiece at which point it’s not a centerpiece at all. We have built a few “smart” workarounds to cater for this constraint, but it’s not possible to fully resolve the issues, without having an actual centerpiece.
    - David Levine 8:51 pm on February 5, 2026
      
      > Without it, plugins have to bundle the package, but the proper way to do this (to avoid conflicts with other plugins also bundling the package) is to prefix the code structures. But then that leads to the problem that everybody ships their own version of the centerpiece at which point it’s not a centerpiece at all. We have built a few “smart” workarounds to cater for this constraint, but it’s not possible to fully resolve the issues, without having an actual centerpiece.
      
      This feels like a strawman. Keeping it out of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. isn’t the same as making it a package.
      
      As noted repeatedly when I was lobbying the team to avoid Composer for MCP/Abilities, Plugin Dependencies was specifically created to solve this problem so folks don’t need to bundle a copy themselves. I’m not seeing anything currently in the codebase, proposal, or our broader roadmap and Experiments that cannot be accomplished by releasing wp-ai-client as a canonical pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
      
      I’m all for bringing `wp-ai-client` into core, but if there’s justifiable reasons to hold off for 7.0, we shouldn’t feel pressured prematurely because of a false premise regarding integration DX.
Sergio Scabuzzo 6:33 pm on February 4, 2026

This sounds interesting and quite powerful. However, there has only been four releases for the WP AI Client (First on Nov 14, 2025. The last on Dec 4, 2025). Historically, WordPress has set these kinds of things squarely in pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party territory, for a while, to make sure it’s working as expected and wanted. Then, eventually, maybe, merged to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Why are we forgoing that pattern here?
Aaron Jorbin 6:49 pm on February 4, 2026
Thanks for the work on this and especially thank you for writing a proposal for discussion! A couple of initial questions:
1. Right now, the documentation refers to two ways for error handling. Why is it necessary to have multiple ways of doing things and how does this align with the idea of decisions, not options?
2. How much of the code base is currently covered by automated tests? Are there any known gaps right now? (I’ve opened https://github.com/WordPress/wp-ai-client/pull/51 to help answer this)
3. If out of the box this isn’t going to expose anything to end users, why is this necessary in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? Plugins that use AI feature could set a dependency on a wp-ai-client pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and this could work in a consistant manner. This also would allow for more frequent updates.
- Jason Adams 7:05 pm on February 4, 2026
  Hi Aaron!
  
  Great questions! I’ll answer for what I know.
  1. We were experimenting with the two approaches, but from our last discussion are likely to move forward with using `WP_Error` instead of exceptions, as that better aligns with WordPress.
  2. I’ll follow up in this PR. We’ve tried to be quite thorough with our tests, especially in the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher AI Client — which also uses PhpStan strict mode.
  3. This is akin to the Abilities APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. in 6.9 and provides a single registry for providers. This enables folks like hosts to include a provider that’s available to hosted sites. That said, I think this will be a key part of the discussion moving forward!
  - Felix Arntz 10:35 pm on February 4, 2026
    
    +1 to answers 1 and 2. For answer 3, while it’s true that this matches previously landed features like the Abilities APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., some additional considerations I’m outlining here: https://make.wordpress.org/core/2026/02/03/proposal-for-merging-wp-ai-client-into-wordpress-7-0/#comment-48335
Kevin Batdorf 3:23 pm on February 5, 2026
Congrats on moving this forward. Some questions though. What sort of guardrails and protections are being discussed for users? For example, a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party unintentionally runs up the users openai api bill for the month. Do both the plugin author and user have any protections here?

Further:
- Should the plugin guidelines be expanded to include new best practices in handling this APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. key?
- Should there be some way to communicate to users which plugins have access to their API key, and how much monthly cost is estimated?
- Could WordPress itself aggregate this across all installs to understand the impact?
- Should users have the ability to see this usage in realtime?
- Jeffrey Paul 5:58 pm on February 5, 2026
  
  Some of those questions may be worthwhile extensions for the conceptual AI Request Logging experiment.
Jer Clarke 10:26 pm on February 5, 2026

Will there be some kind of “kill switch” that site operators can use to ensure the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. is never used? I’m imagining a constant that could be added in `wp-config.php`.

E.g. If a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party tries to access the API, the kill switch returns an error.

This would be a great way to control bloatware plugins adding AI where it isn’t wanted. For example Jetpack currently requires a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to disable AI features that junk up the editor. If it used this API, and the API had a kill switch, it would be a quick way for abstainers to get peace of mind.
- Jason Adams 11:44 pm on February 5, 2026
  
  Yup! There will be more discussion around this, but there is already a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. which returns true/false and prevents a prompt from running. One could use `__return_false` to just stop everything, limit prompt access to particular users, and so forth.
  
  The filter also works in such a way that plugins can respond to as it marks a prompt as “not supportable”. This allows the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to gracefully handle things like hiding the UIUI User interface that would otherwise use the prompt.
  
  As I said, it’s a filter right now, but there has been discussion around a constant.
Matt Mullenweg 9:55 am on February 7, 2026

What can we learn from OpenRouter and apply here? Very interested in the ability to send prompts to different providers or local providers based on the complexity of the prompt itself. It gets especially interesting with WordPress Playground as an app-creation and distribution platform.
Peter Wilson 3:12 am on February 9, 2026
I’ve been considering this over the last few days and come to the conclusion that it’s best not to include this in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Jason’s draft pull requests show that about 16.5K lines of codeLines of Code Lines of code. This is sometimes used as a poor metric for developer productivity, but can also have other uses. would be added to WordPress Core in order to include this feature. Even if this falls by 20% in the final form it is a lot of code for future contributors to maintain.
Non-goals
- No bundled credentials or providers.
- No end-user “AI assistant” UIUI User interface in core.
- No product-level experiences standardized in this merge (those remain pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/ecosystem territory for now, e.g. AI Experiments plugin).
As including AI features in core is a non-goal, I don’t see the user benefit in including this code in WordPress. The WordPress Philosophy states that core should be kept lean and included features should benefit the majority of users.

With the explicit statement that this code will not come with any user facing features, including this in Core fails this test. Contributors would be maintaining all this code without benefit to users.

It’s also an issue that maintaining these features comes with an expense: accessing these APIs generally costs money so many contributors would be maintaining the code blind. There are free plans now, for some providers, but free plans have a long standing habit of disappearing.

Welcome!

Communication

Proposal for merging WP AI Client into WordPress 7.0

Purpose & Goals

Goals

Non-goals

Proposed Scope

Security, Privacy, Performance

Call for Feedback and Testing

Welcome!

Communication

Purpose & Goals

Goals

Non-goals

Proposed Scope

Security, Privacy, Performance

Call for Feedback and Testing

Share this:

Site resources