Plexara
Knowledge Capture & Application
Reach
What one person teaches, the whole team gets
The finance lead explains that a column is gross margin, not revenue. Normally that stays inside one conversation, and the next analyst re-derives it from the data and gets it wrong.
Promotion is what changes that. The moment a reviewer applies an insight, it stops being the capturer’s private note and becomes something every identity can find through the same search they already use, still attributed to the person who taught it. Nobody needs to know it exists, or who to ask.
Until then it stays private. An insight still waiting on review is visible only to whoever captured it, because a capture under review is not yet something the organization asserts.
A teammate who never saw the original conversation, answering correctly
46.7%→98.9%
Our lifecycle benchmark teaches a fact with one identity and then asks a different one. Moving the visibility boundary to the act of applying an insight took that from under half the time to near-total.
30 protocols, 95 transfer attempts on claude-sonnet-5; 95% CI 96.8 to 100.0. Measured on v1.102.0 and again on v1.118.0, so the comparison is across code rather than across samples.
Read the accuracy studyCapture
Three Sources of Knowledge
01
User-Provided Knowledge
"That column is gross margin, not revenue"
When a user corrects an agent during a conversation, the correction is captured as a structured insight with the specific entity, the type of correction, and the suggested catalog change. No separate tool needed.
02
Agent-Discovered Insights
"Column amt appears to be in cents based on value ranges"
When an agent queries data and observes patterns, these observations are captured as lower-confidence insights flagged for human review. The agent does the analytical work. Humans validate the conclusion.
03
Enrichment Gap Flags
"This table has no description and 12 undocumented columns"
When the semantic enrichment middleware finds missing metadata, the gap is recorded automatically. Over time, the gap log becomes a prioritized list of documentation debt ranked by access frequency.
Pipeline
The Review Pipeline
Nothing becomes shared knowledge without human approval. Review and promotion belong to whoever holds that capability, which your team assigns and which need not be an administrator.
Capture
Insight recorded with source, confidence level, entity reference, and suggested changes.
Review
A reviewer evaluates accuracy and relevance. Bulk or per-entity review workflows, with the whole queue enumerable rather than only searchable.
Synthesize
Related insights about the same subject are combined, and each proposed change is shown beside the value it would replace.
Apply
Approved knowledge is written to whichever of the two homes fits it, as a tracked changeset with full provenance.
A pending insight is not judged in the abstract. The panel looks up the table the claim is about and reports what it finds right now, so the reviewer decides against the data as it stands rather than as the capturer remembered it.
Two Homes
Where a Promoted Fact Lands
Not every fact belongs on a table. Promotion routes each one to the place it can be found from: business and domain knowledge becomes a page, technical and entity knowledge goes to the catalog. The reviewer picks the destination at promotion time, and one search covers both.
Canonical knowledge pages
Business and domain facts
Durable, human-readable pages written in formatted text with diagrams, version-tracked on every save, searchable by meaning, and open to feedback in place. They hold the vocabulary, definitions, runbooks, and context that do not fit inside the metadata on a single table.
- How the fiscal calendar differs from the calendar year
- What counts toward net revenue and what does not
- The runbook for a month-end close that spans six systems
The data catalog
Technical and entity facts
A fact that belongs to one table, column, dashboard, or glossary term is written where that entity already lives, so it arrives with the metadata every time anyone touches the entity. Descriptions, tags, glossary terms, quality flags, curated queries, and incidents are all reachable this way.
- The amt column is in cents, not dollars
- This extract is deprecated in favor of the modeled table
- Rows before the March migration are in UTC
Repeated promotions about the same subject consolidate into one living page rather than piling up beside each other, and when an agent tries to write a page that closely matches one that already exists, the platform steers it into updating that page instead. Canonical knowledge gets deeper over time instead of splintering into near-copies.
Structure
Knowledge Is Linked, Not Filed
A wiki asks you to remember where you put something. Knowledge in Plexara hangs off the things it describes, so it arrives when you are looking at them.
The result is a corpus with a shape you can inspect: the portal draws it as a reference network, sizes each node by how much of the graph it holds together, and traces the chain of references between any two things.
Pages cite what they are about
A page states the assets, prompts, collections, connections, catalog entries, glossary terms, tags, and domains it concerns. Each one renders as a live chip carrying the current name, not the identifier some system generated, and deep-links to where that thing is managed.
The link runs both ways
Standing on a glossary term, a tag, a domain, or a table, you see the knowledge written about it. A steward reading a definition finds the runbook that depends on it without knowing the runbook exists.
Access decides what you see
A reference to something you cannot reach is omitted from both directions, so you see the part of the corpus you are cleared for and nothing hinting at the rest.
Reversible
Every Promotion Can Be Undone
The objection to letting an agent contribute to your catalog is the obvious one: what happens when it is wrong. A person approves every promotion, every promotion records what it wrote over, and a bad one comes back out.
Every promotion is a changeset
Each run records exactly what it wrote and the values it wrote over, on both destinations. The changeset list sits with the promoted knowledge, showing what was applied, to what, by whom.
A changeset can be rolled back
Rolling one back restores what was there before and returns the source insights to the queue. A promotion that created a page removes it; one that revised a page restores the prior version. Reversibility is stated up front, before you apply, so you never learn at rollback time that a change could not be undone.
Nothing ages silently
The review queue reports how old its oldest pending item is and how much has aged past thirty days, and says so in the assistant, in the portal, and on the admin screens. When the backlog crosses the threshold your team sets, it emails a digest with a link straight into the queue.
Flywheel
Usage Improves the Platform
Usage generates insights
Insights improve documentation
Better documentation improves agent accuracy
Better accuracy drives more usage
This flywheel distinguishes knowledge application from one-time documentation initiatives. A documentation sprint produces a snapshot that begins decaying immediately. Knowledge application produces documentation that improves continuously because it is connected to ongoing data usage.
The rate of improvement is proportional to usage. Datasets queried frequently accumulate documentation faster. Columns discussed in conversations get descriptions sooner. Business terms explained to agents get linked to glossary entries. The documentation naturally prioritizes what matters most.
Over 15 change types are supported: update descriptions at entity and column level, add tags, add glossary terms, flag quality issues, add curated queries, raise incidents, add context documents, and create prompts. Works across datasets, dashboards, charts, data flows, containers, data products, domains, and glossary terms.
Next
Catalog Governance
Where promoted knowledge lands, and how your team curates the catalog around it.