WordPress Core AI stops being an experiment in 6.9
Six months in, WordPress Core AI has a stable shape: the Abilities API lands in 6.9, WP Client AI abstracts the LLM providers, and the MCP adapter turns a site into a server that agents can call.
Six months in, WordPress Core AI has a stable shape: the Abilities API lands in 6.9, WP Client AI abstracts the LLM providers, and the MCP adapter turns a site into a server that agents can call.
Junk topics usually mean the pipeline is wrong, not the data. Here is how seeded KeyNMF and an LLM summarization step keep a topic model focused without burning the whole compute budget.
Package installs crawl because the client parses one giant metadata file before it does anything useful. Sharded indexing (CEP-16) splits that file per package, and there is a PHP example here for internal plugin repositories.
Running your own VPS looks cheaper right up until the traffic spike. Here is what managed WordPress hosting actually handles for you: server-level caching, a persistent Redis object cache, brute force filtering at the edge, and the patching you stop doing.
WooCommerce 10.5 drops the AccessiblePrivateMethods trait that let private methods act as hook callbacks. Extensions still using it will throw a fatal error. The replacement is a public method carrying an @internal annotation.
Ninety percent accuracy sounds fine until the wrong JOIN lands on a production database. This covers why Execution Accuracy beats Exact Match, what Spider 2.0 exposed about enterprise schemas, and how to ground an LLM on the schema you actually have.
Notes on building a data-driven goal tracker with Python, Streamlit and Neon: one schema for daily habits and quarterly milestones, ISO-8601 week boundaries so the weekly numbers do not drift, and a REST API bridge when the data has to land in WordPress.
Notes on porting statistical models into WordPress: where research gets diluted instead of distilled, how real-time aggregates in user meta leak data through race conditions, the atomic SQL fix, and why a bigger LLM is the wrong answer to arithmetic.
A knowledge graph has three layers: an ontology, controlled vocabularies and observational data. This post walks through what each one does, and shows the WordPress version of the shift from flat meta_query lookups to taxonomy-based entity relationships.
Retrieval-augmented generation is past the demo stage. Notes on chunk size as an experimental variable, why HNSW precision degrades as the index grows, the latency cost of extra retrieval layers, and a transient wrapper for caching retrieval in WordPress.