An Idea Journal and an interface for external agents

Generating a page of text is only one part of automating a website. Before that, the site needs a way to collect material, decide which pieces belong together and keep an idea around long enough to develop it. I have started building an Idea Journal to give that work a place in WordPress.

Sources and ideas

The Journal separates source material from the ideas it may support. Its first implementation includes source and idea management, connector and watchlist interfaces, run records, matching components and a vector-store abstraction with a Qdrant implementation. Keyword, vector and model-based matching provide different ways to compare incoming material with an existing idea.

The admin screens give me somewhere to inspect sources, ideas, watchlists and runs. The initial code also contains drafting components for briefs, outlines, sections and assembly. These are foundations for a workflow that will need further refinement; a match or a generated draft is not the same as a verified article.

Connecting an agent

In parallel I added a token-managed REST interface and an OpenAPI schema, followed by MCP server support. This exposes a separate agent-facing surface rather than relying on the chat interface inside WordPress. Authentication and discovery are part of that surface: the agent needs to know what operations exist and the site needs to control access to them.

One of the first workflows is a staged post plan. A plan can be saved, inspected and rendered into post content using the admin or agent tools. Keeping the plan as an explicit intermediate step makes its structure available for revision before rendering, instead of treating a single model response as the finished article.

These pieces are an early foundation for the larger goal of a site that can gather information and manage its own publishing. The practical challenge is connecting them without losing visibility into the sources, decisions and draft along the way.