From d244261aa78bfabbf96ebd84f6d37c3ba83f0738 Mon Sep 17 00:00:00 2001 From: Luca Martial <48870843+luca-martial@users.noreply.github.com> Date: Thu, 14 May 2026 17:57:16 -0400 Subject: [PATCH] docs: add context layer diagram (#102) --- .../docs/concepts/the-context-layer.mdx | 155 ++++++++++++++++++ 1 file changed, 155 insertions(+) diff --git a/docs-site/content/docs/concepts/the-context-layer.mdx b/docs-site/content/docs/concepts/the-context-layer.mdx index 3baf30f6..cb03b7c0 100644 --- a/docs-site/content/docs/concepts/the-context-layer.mdx +++ b/docs-site/content/docs/concepts/the-context-layer.mdx @@ -27,6 +27,161 @@ The industry has moved through three distinct approaches to getting AI and data A context layer is the infrastructure that gives agents the business knowledge they need to produce correct analytics artifacts. It includes a semantic layer - that's a critical component - but it's not the whole thing. +
+ {"How KTX works"} +
++ {"KTX pulls structured metadata and human knowledge from your analytics stack, reconciles it into reviewable files, then gives agents a trusted surface for search, SQL generation, validation, and edits."} +
++ {"Source systems"} +
++ {"Warehouses"} +
++ {"schemas, types, row counts, constraints, query history"} +
++ {"Modeling tools"} +
++ {"dbt, MetricFlow, LookML"} +
++ {"BI systems"} +
++ {"Looker explores, Metabase questions, dashboards"} +
++ {"Notion and team knowledge"} +
++ {"runbooks, definitions, policies, analyst notes"} +
++ {"KTX ingest"} +
+{"Extract"}
++ {"adapters read metadata, files, APIs, and warehouse evidence"} +
+{"Reconcile"}
++ {"the ingest agent merges new facts with existing context"} +
+{"Verify"}
++ {"validation and provenance make each write auditable"} +
++ {"KTX project"} +
++ {"Agent workflows"} +
+