Book a conversation
Menu
TAKL · Architecture walkthrough/Architecture deep dive

Architecture deep dive

How an AI agent's questions are routed through a governed knowledge layer, and how that resolves into three components: Access Intel, AI Economics Routing Prioritization, and Certified Knowledge Blocks.

01

End-to-end footprint

Three verticals: unstructured data on the left, structured data on the right, and the Trusted AI Knowledge Layer in the center, with AI consumer agents on top. Grey chips show example technologies for each component. Select a route to trace it, or a component to read about it.

UNSTRUCTURED DATA U-1 Enterprise Business Documents MS SharePoint U-2 RAG Pipelines embed · retrieve · augment U-3 Vector DBs PostgreSQL AI CONSUMER AGENTS token economics Context window where cost accrues TRUSTED AI KNOWLEDGE LAYER AI SERVICE LAYER Neo4j Knowledge Graph DB T-1 Access Intel T-2 AI Economics Prioritization Router T-3 Certified Knowledge Blocks INTELLIGENCE COLLECTION & GOVERNANCE LAYER I-1 Business Document Intake Document Slices Doc Chunks Document Metadata Deasy Labs I-2 AI and Data Governance 1 Ontology 2 Taxonomy 3 Classifications CollibraBigID I-3 Data Assets Intake Collibra Edge Docs metadata, inventory of Doc Slices assets metadata governed metadata stewards → personas STRUCTURED DATA S-3 BI & Analytics PowerBI Tableau Looker S-2 Certified Data Products Starburst S-1 Source Data & Datalakes Enterprise Datalake Source DBs Google Cloud Platform (GCP) Document Scans(Stored as Chunks - enabling Slices,core component of Context Packages) collections + contextual metadata report scanning product metadata tech metadata scan - data profiling vendor technology footprint (examples) 2a brute force $$$$$ 2b semanticsearch · $$ 2c precise KPI · $ 1 ask first, get the prioritized route governed recommendation
ALL ROUTES select a route

Three routes, one decision

Route 1 always runs first. The knowledge layer then recommends 2a, 2b, or 2c for the question at hand, and the agent follows that recommendation.

02

Architecture components

Each component maps to a part of the footprint. Together they make the routing recommendation possible.

  1. UNSTRUCTURED DATA

    • U-1Enterprise Business Documents

      The enterprise's unstructured corpus: policies, contracts, procedures and reports held in document repositories. It is the source for brute-force retrieval (route 2a) when a known set of documents answers a critical question, and Business Document Intake scans and chunks it.

      Technology: MS SharePoint
    • U-2RAG Pipelines

      Pipelines that embed documents, retrieve relevant passages and augment the prompt for AI consumers. Every step carries cost, so the knowledge layer decides when RAG is the right route for a question.

    • U-3Vector DBs

      Stores document embeddings for semantic search (route 2b), the economic middle path for very large corpora. Collection metadata such as embedding coverage is shared with the knowledge layer, and contextual metadata from Business Document Intake improves retrieval.

      Technology: PostgreSQL
  2. AI SERVICE LAYER

    • T-1Access Intel

      Before any route is taken, the graph resolves who is asking, what the data is, and what they inherit, so the agent only sees what that persona is entitled to.

      Enabled by: Collibra + Neo4j; Automated Persona Permissions Framework
    • T-2AI Economics Routing Prioritization

      The knowledge layer recommends 2a, 2b, or 2c at runtime by weighing criticality, document count, token economics, and certified-metric matches.

      Enabled by: Knowledge-Layer Metadata + Token-Economics Model
    • T-3Certified Knowledge Blocks

      Business logic harvested from BI reports and document slices from enterprise content are certified through the stewardship framework. They become reusable blocks: Certified Context Packages and Certified Data Products, ready to plug into any AI consumer. Each block is built once and reused everywhere, which raises the speed and accuracy of AI responses.

      Enabled by: Starburst, Deasy Labs + Collibra; Governance Certification Framework
  3. INTELLIGENCE COLLECTION & GOVERNANCE LAYER

    • I-1Business Document Intake

      Scans enterprise documents for metadata and chunks large documents into smaller slices. It produces Document Slices and Document Metadata, and passes docs metadata and an inventory of doc slices to AI and Data Governance.

      Technology: Deasy Labs
    • I-2AI and Data Governance

      The governance system of record and the human-facing interface where stewards define, approve and certify. It holds the ontology, taxonomy and classifications that give AI consumers business meaning, and feeds governed metadata to the AI Service Layer.

      Technology: Collibra, BigID
    • I-3Data Assets Intake

      Harvests metadata from structured sources: source systems and datalakes, certified data products, and BI reports with their KPIs, metrics, dimensions and business logic. It passes assets metadata to AI and Data Governance.

      Technology: Collibra Edge
  4. STRUCTURED DATA

    • S-1Source Data & Datalakes

      Operational source databases and the enterprise datalake where structured data lands. Source DBs feed the datalake, and Data Assets Intake scans both for metadata.

      Technology: Google Cloud Platform (GCP)
    • S-2Certified Data Products

      Reusable data products that calculate KPIs and metrics once, using business rules approved through stewardship. They answer KPI questions precisely through route 2c, without documents or extra context.

      Technology: Starburst
    • S-3BI & Analytics

      Reports and dashboards that consume certified data products. Report scanning harvests the KPIs, metrics and business logic buried in reports so they can be certified and reused.

      Technology: PowerBI, Tableau, Looker

Technology-neutral: Neo4j or similar (Graph DB) · Starburst or similar ("query-anything-where-it-lives") · Collibra or similar (Data Governance & Metadata Catalog) · Deasy Labs or similar (Docs chunking, cross-file slices) · BigID or similar (auto data classification).

TADA gets you ready; TAKL keeps you trusted.

Book a conversation