| A | B | C | D | E | ||
|---|---|---|---|---|---|---|
1 | Consideration | Composer | WORG Plugin | AI Module | Notes | |
2 | Can be used as Composer dependency | Yes | Yes | No | Requiring the entire AI plugin would conflict with the canonical plugin installation | |
3 | Can be used as a Plugin dependency | No | Yes | Yes | ||
4 | Installable from WordPress backend | No | Yes | Yes | ||
5 | Requires a manual user install | No | No | No | If a plugin is hosted on .org the same AI Module to "Enable the MCP Adapter" can install the MCP Adapter plugin if it isn't already installed | |
6 | Only present on the site if used | No | Yes | No | ||
7 | Can be (auto)-updated by site owner | No | Yes | Yes | ||
8 | Can be disabled temporarily | No | Yes | Yes | ||
9 | Can cause dependency conflicts | Yes | No | No | This isn't hypothetical, but has already been affecting early adopters. | |
10 | Requires repository-maintaince overhead | Yes | Yes | No | ||
11 | Can be developed independently | Yes | Yes | No | Partial features can't be merged the AI plugin without delaying the release cadence, and bugs can become blocking | |
12 | Requires release stability | No | No | Yes** | An Experiment could undergo more breaking changes than a stable Feature, but that may be interpreted as a downgrade | |
13 |