Plexara
Knowledge Application
Capture
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 Admin Review Pipeline
Nothing writes to the catalog without human approval. Every change is tracked and reversible.
Capture
Insight recorded with source, confidence level, entity reference, and suggested changes.
Review
Administrator evaluates accuracy and relevance. Bulk or per-entity review workflows.
Synthesize
Related insights about the same entity are combined into cohesive documentation.
Apply
Approved changes written to the catalog as a tracked changeset with full provenance.
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.