Monthly Dispatch: July 2026

Issue No. 3July 16, 20267 min read

Welcome back to the Plexara Monthly Dispatch. Last month's issue was about the loop that captures what your team learns. This month the loop got a destination, canonical knowledge pages the assistant can find and cite, and we finally published the benchmark we spent the spring running. The short version: on questions that depend on business context, the same agent went from 42.7% correct on bare data tools to 98.7% on Plexara. The long version, and what the numbers tell us to build next, is further down.

What is new this month

Canonical knowledge pages are the big one. Discovery also got a single front door, answers now ground themselves in your catalog before they touch the warehouse, and the portal picked up a round of security hardening.

Canonical knowledge pages, linked like a wiki

New

Until now, knowledge in Plexara accumulated as captured notes and reviewed insights, each tied to the data it described. That works for a fact about a table. It does not work for the vocabulary, definitions, and runbooks that span a whole domain. Canonical pages are for those: formatted text with diagrams, version-tracked on every save, searchable by meaning, open to feedback in place.

The part we care most about is the linking. A page references the exact assets, prompts, collections, connections, and catalog entries it describes, and the references are live links that work in both directions. From a dataset you can see every page that documents it. From a page you can open the data it is talking about.

All of it now lives in one Knowledge area with a single lifecycle: a note is captured, promoted to an insight for review, then promoted to shared canonical knowledge, and each step is gated by who is allowed to apply knowledge. The assistant works the same loop. It searches across every kind of knowledge, reads a result back in full, and cites pages precisely in answers. And when it tries to create a page that closely matches one that already exists, the platform steers it to update the existing page, so the canonical layer consolidates over time.

For practitioners: the runbook you finally wrote down is now something the assistant can find, read, and cite. For managers: every promotion into shared knowledge passes review and permissions, so the canonical layer is curated on purpose, page by page.

One search, grounded answers, and a tighter foundation

Discovery got a single front door. The assistant no longer needs to know the shape of your platform before it can ask; one call searches everything a role can reach, across the catalog, memory, captured knowledge, saved assets, prompts, connected APIs, and connections. Results come back balanced so the largest source cannot drown out the rest, and long reference documents now index reliably, so the big spec or policy is something the assistant can actually surface.

Answers got more grounded too. Before it runs a warehouse query, the assistant checks your catalog first, so answers reflect the data you actually have instead of a guess at its shape. The business context wrapped around each answer now stays within a set budget, summary first, so it never crowds out your data. Underneath it all, a round of hardening: cross-site request protection on every change made through the portal, sign-in brought up to current standards, catalog edits that no longer risk overwriting the tags and descriptions already there, and a review queue that shows how long its oldest item has been waiting, so nothing captured ages out unreviewed.

From the Learning section

We publish to the Learning section on a regular cadence. The flagship this month is the one we have been working toward all year.

Benchmarking the context layer

July 13, 2026

We built this suite to do two jobs: prove what the platform is worth, and show us exactly where to work next. It holds the model, the prompt, and the data constant, and varies only the platform. The questions that matter most are the ones where the correct answer depends on a business fact outside the data, the kind a veteran analyst knows and a schema does not reveal. On those, an agent on raw data tools was right 42.7% of the time. The same agent on Plexara was right 98.7% of the time, a +56.0-point gain (95% CI +44 to +67), in fewer tool calls. Figures, confidence intervals, and reproduction commands are in the full benchmark report, and the harness itself is open in the platform repository.

Five kinds of memory, and how each comes back

June 18, 2026

A fact, an incident, a person, a link, and a habit are five different kinds of knowledge. Plexara stores each as its own dimension and recalls each the way that kind needs. This is the architecture underneath the knowledge lifecycle described above.

What you keep if you leave

July 2, 2026

Everything this issue describes, the pages, the definitions, the catalog, accumulates in DataHub in open formats. If you stop using Plexara, the catalog, the lineage, and the definitions your team wrote stay with you. Portability is a property of the storage, not a promise on a slide.

You may notice we do not benchmark against competitors. That is because, honestly, as of July 2026 there is not one to benchmark against. Products like Snowflake can quote impressive numbers inside their own walls, and those numbers are real, provided your entire business runs in Snowflake. Snowflake would love that dream. The real world is much messier: databases that predate the warehouse, third-party APIs, vendor services, systems nobody is migrating this decade. Harnessing that mess is the job Plexara exists to do, and it is the job the benchmark measures.

Not every suite produced a headline, and the quiet ones did not surprise us. Cross-user knowledge transfer, measured as its own isolated bench, sits near 45% today. Treating recall as a separate bench somewhat undersells it, since the primary surface for recall is the semantic layer, exactly where the 98.7% lives. But we want every Plexara tool to prove its value on its own, and this is where the benchmark earns its keep: the quiet numbers are our roadmap. Expect them to move with every release. We are not slowing down, because AI knowledge integration is the future and we intend to lead it. Full figures in the benchmark report.

Usage tip: promote what you know into a page

The tips in the first two issues were about saving a finished workflow as a prompt, then resolving feedback into captured knowledge. With canonical pages live, the next step is consolidation.

Say your team has spent months capturing insights about the receiving pipeline: the column stored in cents, the join that double-counts on Mondays, the vendor code that means "return" in one region and "damaged" in another. Ask Plexara to pull it together:

Search our captured knowledge about the receiving pipeline, then create a canonical knowledge page called 'Receiving data: definitions and gotchas' that consolidates what we know and links the datasets and prompts it describes.

Plexara drafts the page, links it to the catalog entries and assets it covers, and routes it through the same review gate as any other promotion. From then on the assistant can cite it in answers, and anyone who lands on one of those datasets can click through to the page that explains it.

For practitioners. The knowledge you carry in your head becomes a page with your name on the version history, and the next person finds it instead of re-learning it.
For managers. Consolidation is the step most knowledge bases never take. Duplicate prevention plus review gating means one good page per topic, not five conflicting ones.

Worth reading from others

Four pieces this month. Two of them are benchmarks; apparently everyone was measuring the context layer this spring.

Semantic Layer vs. Text-to-SQL: 2026 Benchmark Update

Jason Ganz and Benoit Perigaud, dbt Labs, April 7, 2026

dbt sells the semantic layer they are benchmarking, so keep that in mind, but they published the half that cuts against them too: raw text-to-SQL accuracy has nearly doubled since their 2023 run. Even so, Claude Sonnet 4.6 goes from 90.0% on text-to-SQL to 98.2% through the semantic layer, and GPT-5.3 Codex from 84.1% to 100%. The finding that matches our experience is about failure modes. The semantic layer fails loudly with an error. Text-to-SQL fails silently, with a plausible wrong answer. Our knowledge-trap questions exist to measure that silent failure.

Semantic Layers for Reliable LLM-Powered Data Analytics

Michael Rumiantsau and Ivan Fokeev, April 28, 2026

The academic version of the same result, across three frontier models. A 4KB semantic documentation file lifted accuracy 17 to 23 points on every model tested, and with context in place the three models landed within a point of each other. Their statistical conclusion is our benchmark's thesis from the other direction: model choice accounted for almost none of the variance, semantic documentation for essentially all of it.

AI Model Context Protocol Adds Centralised Auth for Enterprise

InfoQ, July 6, 2026

The Enterprise-Managed Authorization extension is now stable. Anthropic, Microsoft, and Okta have implemented it, with Asana, Atlassian, Canva, Figma, Linear, and Supabase supporting it server-side. One login through your identity provider replaces the wall of per-server consent prompts. The caveat InfoQ flags is the important part: EMA governs which servers a user can connect to, not what an agent does once connected. Runtime control over agent actions is still your job, and it is the layer Plexara's persona model and execution-time enforcement occupy.

The 2026-07-28 MCP Specification Release Candidate

Model Context Protocol blog, May 21, 2026

The final spec lands July 28, twelve days after this issue reaches your inbox. The headline change is a stateless protocol core that runs on ordinary HTTP infrastructure with no sticky sessions. Long-running work moves to a Tasks extension, servers can ship sandboxed UI through MCP Apps, authorization aligns with OAuth 2.0 and OpenID Connect, and a formal deprecation policy guarantees at least twelve months of notice before anything is removed. If you run MCP servers behind a load balancer, the stateless core alone is worth the read.

We read every reply. If something here was useful, or wasn't, tell us. The API Gateway now has a full product page, and we are still onboarding design partners, so if your team has an internal service or a third-party API the agent should be able to call, send it our way and we will get you set up.

One ask this month. The benchmark harness is open, with arm configs, graders, and reproduction commands in the platform repository. If you run it, or find a hole in the method, reply and tell us. We would rather hear it from you now than find it ourselves in version two.

The Plexara team