What’s next for M7 Publisher
A release post tells you why the team changed something. Six months later, when someone asks how to do the thing, the answer had better be somewhere other than paragraph seven of that post. That's the job of a wiki. M7 Publisher brings those two kinds of writing into one workspace, and the next step is to help AI tools find the right one and show their sources.
What already works in Publisher
Blog and Wiki are both in Publisher today. Blog gives a release, announcement, or field note a place in the timeline. Wiki gives instructions and reference material a home you can keep up to date, with page history when you need to see what changed. Publisher also has built-in comments and reactions on posts and pages where the publication's policy and the reader's permissions allow them.
Say your team changes how people request access to a shared tool. The blog post explains why the old process was retired and what people should expect during the change. A comment points out that the new instructions leave out contractors. The team updates the wiki with the right steps for employees and contractors, and links to it from the post. The post still tells the story of the change. The wiki is where you send the next person who needs access.
What comes next for AI
The retrieval groundwork already works for blog posts and wiki pages. It finds relevant passages within the caller's permissions and checks them against the current source revision. That's the retrieval part of retrieval-augmented generation, or RAG: give the AI relevant material to read before it answers.
Next comes the Publisher connection for AI tools that speak the Model Context Protocol (MCP). The goal is for a connected assistant to search the material you're allowed to read and cite the post or page it used, so you can open it and check the answer yourself.
In that access example, ask, “How does a contractor request access now?” and the assistant should be able to give the current steps and cite the wiki page. Ask, “Why did we change the process?” and the release post is the better source. If the assistant can't reach a source that answers the question, it should say so. A polished guess is still a guess.
That's what I want out of Publisher's next round: give the announcement a place to land, give the instructions a place to live, and make it easy to check where an answer came from.