What happened
Per Search Engine Journal, a proposal to merge a Knowledge Custom Post Type into WordPress Core sparked near-unanimous developer pushback. The feature - formally proposed for WordPress 7.1 by Greg Ziolkowski on June 22, 2026 via Make/Core - introduces a new wp_knowledge post type as a storage primitive for structured site knowledge, together with a wp_knowledge_type taxonomy. The three built-in types are: guideline (a standard such as voice, tone, or image direction), memory (durable context explicitly saved for future use), and note (private freeform working text). The feature was first proposed in February 2026 and landed in the Gutenberg plugin as an Experimental feature in March 2026 (Gutenberg 22.7).
What the proposal actually ships
The Make/Core proposal is explicit about its scope: no AI provider, no model, no retrieval algorithm, and no autonomous memory system. The core change is the storage primitive. Guidelines Settings in wp-admin provides per-scope guideline records across UI sections called guideline scopes (Site, Copy, Images, Blocks). These scopes are not knowledge types - they are UI sections that map to reserved slug guideline records (e.g., guideline-copy), while the wp_knowledge_type taxonomy handles type classification (guideline, memory, note). The GitHub implementation is in wordpress-develop PR #12201, tracked in Trac #65476. Names freeze at WordPress 7.1 Beta 1 on July 15, 2026, making wp_knowledge, wp_knowledge_type, the three type slugs, and the capability namespace long-term compatibility commitments.
Developer pushback
Per Search Engine Journal, developers responded with near-unanimous pushback, characterizing the feature as out of touch with user needs and raising questions about platform priorities and whether structured site metadata belongs in core or should remain a plugin-layer concern. The governance tension mirrors past WordPress debates between expanding core capability and preserving a lightweight, extensible foundation for third-party plugins. The proposal's own call for feedback asks: Is wp_knowledge the right long-term name? Are the capability boundaries correct? Is anything missing before these names become core compatibility commitments?
Context and significance
The proposal frames the AI angle carefully: AI tools are one consumer among several. The Knowledge CPT is also designed for plain note-taking and draft syncing with no AI involved, and the Guidelines experience serves any multi-author site wanting consistent editorial standards. Whether the storage primitive's AI-agent utility justifies core inclusion - or whether it should ship as a plugin - is the central debate. For practitioners and plugin developers, the Beta 1 freeze on July 15 is the critical window to weigh in before the names and API surface become long-term commitments.
What to watch
Whether the proposal is revised or moved out of core following developer feedback; how plugin authors building their own knowledge/context storage respond; and whether migration, API stability, and export/import details are published before the July 15 freeze.
Scoring Rationale #
A WordPress Core governance debate with a genuine AI-adjacent angle - the Knowledge CPT is designed partly as substrate for AI agents, though the proposal ships no AI components. Significant for CMS developers and practitioners tracking WordPress 7.1 architecture decisions, but scope is confined to the WordPress ecosystem, not a broad AI/ML/DS industry event.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.