Monthly Dispatch: August 2026

Issue No. 4August 15, 20268 min read

Welcome back to the Plexara Monthly Dispatch. In July we told you the quiet numbers in our benchmark were our roadmap, and pointed at the quietest one: a fact taught by one person reached a teammate less than half the time. That number is now 98.9%. One targeted fix, found by measurement, and the single most important thing this platform does went from coin flip to near certainty. The rest of the month kept pace: a research center where every study ships its raw runs, two new pre-registered studies (one that killed a claim we liked, but we published that too), and email notifications that finally reach people outside the portal. And down in the usage tip: stop asking your agent for reports.

What is new this month

The transfer fix is the headline. The same release wave also pulled catalog governance, the knowledge graph, and the prompt library into one place, and gave shares and comments a way to reach an inbox.

A fact taught once now reaches the whole team

New

Cross-user transfer is the moment this platform exists for. An analyst corrects the assistant once: that revenue figure should be net, not gross. Weeks later someone in another department asks a related question and gets the corrected answer, with a note naming who taught it. In July we had to report that this mostly was not happening. Measured as its own bench in the accuracy study, transfer sat at 46.7%.

The measurement also named the likely cause, and the fix followed it. Visibility now changes when a reviewer applies an insight: the capture stops being a private note and becomes something every identity can find, still attributed to its teacher. Before, a fact promoted into the catalog reached nobody but its author, unless a question happened to name the exact table it hung off.

The rerun: 94 of 95 transfer attempts succeeded. That is 98.9%, 95% CI 96.8 to 100.0, and graded so conservatively that a right answer only counts after the transcript shows the knowledge actually reaching the learner. (One caveat, which the report states up front: 46.7% was measured on spring code and 98.9% after the fix, so it is a comparison across versions, not a bigger sample.) The method and every raw run are in the accuracy study, the human version of the story is in What one person teaches, the whole team gets, and the product page behind it all is Knowledge Capture & Application.

For practitioners: teach the platform once and stop repeating yourself in DMs. For managers: what your best people know now compounds instead of leaving with them, and every promoted fact still passes review first.

One place to govern what your business knows

Tables, context documents, tags, domains, and the business glossary now sit under a single Catalog tab in the portal, and retiring anything states its blast radius before you confirm. Lesson 211 walks the whole surface. Next to it is a graph view that draws your knowledge corpus as a reference network: it opens on the idea the most connections run through, groups pages into topics, and sizes each node by how much of the picture it holds together. It is the first honest answer we have had to "what does our team actually know?", and lesson 212 covers how to read it.

The prompt library grew up in the same release. Every prompt keeps a version history, an approval is bound to the exact version it approved, and each row shows run count and time since last run, which makes a never-used prompt visible instead of immortal. The library also opened inside the conversation: ask the assistant to show your prompts and a browser appears right in the chat with search, filters, an argument form, a Run button. That browser is one of two MCP Apps the platform now delivers; the other shows platform status and your active personas.

Uploaded reference files joined search as well. A brand guide or a data dictionary is now found by what it says, not just what it is named, and replacing a file keeps every citation pointing to it working. Full release notes are on the changelog.

The Catalog tab inside the Knowledge area, with sub-tabs for Tables, Context Docs, Tags, Domains, and Glossary, a connection picker, a search box for tables by name, description, or tag, and table cards for daily sales, customers, and clickstream events, each with a description and tags such as certified, finance, and pii. — The Catalog tab: tables, context documents, tags, domains, and the glossary under one roof, with a connection picker at the right.

Shares and comments now reach inboxes

Shares, comments, and mentions send email now. Each person picks delivery per category (immediate, daily digest, or off), preferences follow the email address so they cover guests who have never signed in, and shares can issue one-time view links that expire in minutes and die after first use. Forwarded share links grant nothing; they are bound to their recipient.

Admins get a delivery log (every message, its status, attempts, and the mail server's error when one fails), alert thresholds for a review queue going stale, and a choice of mail server: ours by default, or point the Admin mail settings at your own provider and confirm with a test send. The product's subprocessor count stays at zero either way. Details are on the notifications page.

The Notifications tab of the admin dashboard: counters for failed, pending, sending, and sent messages, a note that resolved notifications are removed after thirty days, filters by recipient, status, and category, and a delivery table listing when each message was queued, its recipient, subject, category such as share, mention, or comment digest, status, attempt count, and send time. — The admin delivery log. A failed share notification shows five attempts, a mention went out on the first, and a daily digest is still pending. The notifications page covers the per-person delivery choices behind it.

From the Learning section

The Learning section grew a sibling this month: a research center where every study ships four things: the report, the raw runs, the code, and the protocol. Our standard there is blunt: any benchmark you cannot rerun is an ad. Two new pre-registered studies landed in August, and the July knowledge-use results got a plain-language companion, When do agents use what you teach them?

The knowledge-pollution study

August 7, 2026

What does a wrong fact cost once it has cleared review? The frontier-class models we run in production took a planted wrong answer zero times in 96 runs; a small model took it in 16 of 24 on the one kind of claim that traveled. The mechanism surprised us: the wrong fact never out-argued the correct source, but suppressed the query that would have refuted it. And our pre-registration was wrong. We expected the dangerous claim to be the one nobody can check; the data said the claims that spread are exactly the ones the platform could have verified before approving. That is now where the review tooling is aimed.

The graph-completion study

August 10, 2026

What do references between knowledge pages buy an agent that must be complete, writing an operational document with every governing constraint grounded in a page it actually read? On a connected corpus the agent grounded 100% of constraints at every size we tested, 50 to 5,000 pages, while reading 0.2% of the largest corpus. Strip the references from the same pages, and search effort per constraint climbs 2.3x and keeps climbing with scale. This study is also what publishing a dead idea looks like in practice: a pre-registered kill condition fired, retired the headline claim we hoped to make, and the report leads with that instead of burying it.

The knowledge-use study

July 26, 2026

Why does an agent use delivered knowledge at all? With the company definition delivered, confident fabrication of institutional facts fell from 75% to zero, and capable models re-verified every delivered claim they could check against live data, 48 of 48. The finding that changed how we write knowledge: anything a strong model can re-derive from actual data, it will. The payoff is in the facts it cannot re-derive and your conventions and definitions, which is exactly where the fabrication lived.

What one person teaches, the whole team gets

August 5, 2026

The story behind this issue's lead item, told properly: the measurement that said transfer was failing, the cause it pointed to, and the rerun that says the gap is closed.

The other thing steering us is production. We rebuilt use cases around two case studies whose counts read live from client platforms: a retailer where ad-hoc analysis that used to consume a specialist for a day now takes about 20 minutes of agent work plus a human review pass, and a public broadcaster whose agent works through more than 1,400 governed API operations and nine reviewed knowledge pages instead of tribal memory. The benchmarks tell us what the platform can do. These pages show what teams actually do with it.

Usage tip: ask for the strategy, not the report

The first thing most people do with an AI agent is speed up their daily routine, and reporting is the first thing most teams point it at. That works, but it aims low, and it quietly turns the agent into a replacement for automation you already had. You never needed a frontier model to pull numbers out of a warehouse; scheduled jobs have done that for decades. The agent's genuine contribution to a report is crafting the query, and Plexara's contribution is making the result dependable, because the platform knows what each number means. If you stop there, you have rebuilt an automated report with more expensive parts.

The goal this industry has chased for decades is not faster reporting. It is data-driven decisions. So change what you ask for. Do not ask for an informative summary; ask where you should direct your effort. Ask how an experienced operator would react to these numbers. Argue with the assistant about what the data means, shape the strategy together, and write the result down as a decision memo. Then make it repeatable:

Here are this month's numbers. Do not summarize them, advise me. Write a decision memo: what changed, what an experienced operator would do about it, where we should direct effort next week, and what we should stop doing. Then save the procedure as a reusable prompt called 'Weekly direction memo'.

Plexara resolves the definitions behind every number the memo cites, and the saved prompt lands in your library with a version history and an approval trail. Letting the agent write the prompt shows the save step in detail. The last step is scheduling: Claude's scheduled tasks can run the prompt weekly through your Plexara connection (lesson 404 walks through running prompts by hand and on a schedule), so a memo is waiting Monday morning and the meeting starts at the decision instead of the data pull.

For practitioners. You stop being the person who compiles the numbers and become the person who decides what to do about them. The compiling still happens. It just is not your morning anymore.
For managers. The strategy conversation stops living in one person's chat history. It becomes a versioned, approved prompt the whole team runs, and the memos it produces are consistent enough to compare month over month.

Worth reading from others

Three pieces this month: the MCP spec grew up, a warning for everyone building agents, and the scheduling feature the tip above ends on.

Model Context Protocol prepares to break with its stateful past

Joab Jackson, The Register, July 23, 2026

Last issue previewed the release candidate; the final 2026-07-28 spec shipped on schedule, and this is the practical read on it. Protocol-level sessions are gone: state travels with each request, so a remote server that needed sticky sessions and a shared session store can now run behind a plain load balancer. The caution matters as much as the headline. The revision is not backward compatible, the clock on deprecated features is twelve months, and sampling, roots, and logging are deprecated. If you maintain an MCP server, treat this as your migration notice.

Your agent will be your undoing

Benn Stancil, June 5, 2026

Stancil argues that startups building standalone agents are renting a temporary advantage, because the frontier labs will subsume them with general-purpose agents co-developed with the models themselves. His advice: build the things agents need instead, the tools, sandboxes, and infrastructure. We obviously have an interest in agreeing, since Plexara is that layer; the general-purpose agent your team already uses plugs in over MCP, and the platform's whole job is to be worth plugging into. Read it for the argument, not for our agreement with it.

Claude's scheduled tasks finally fixed what ChatGPT, Gemini, and every other AI tool got wrong

Mahnoor Faisal, XDA Developers, March 29, 2026

A practical tour of the feature this issue's usage tip ends on. Tasks are defined in plain language, run on a schedule on Anthropic's infrastructure or in the desktop app, and reach the connectors on your Claude account, which is what makes the weekly decision memo work: the scheduled run reaches Plexara the same way your live conversations do.

We read every reply. One more thing worth saying plainly: Plexara is now a signatory of the Cloud Security Alliance AI Trustworthy Pledge. It is a public commitment rather than an audit, and it sits alongside a refreshed trust page and a security page that spell out, control by control, what the platform enforces on every request. If your security team wants the vendor memo and DPA, reach out and ask.

And if you are the type who reruns things, every table in both new studies regenerates with one command from the published raw runs. Find a hole in the method and tell us. We would rather hear it from you now than find it ourselves in version two.

The Plexara team