Knowledge Graph & Cross-Learning
Graph-based learning system enabling agents to share patterns, learn from each other, and continuously improve through experimentation.
Learning Pipeline Components
Learning Coordinator
Orchestrates entire learning pipeline, subscribes to events, triggers pattern recognition
Pattern Recognizer
Analyzes deployment outcomes, identifies explicit/implicit patterns and anti-patterns
Experiment Manager
A/B tests, canary deployments, champion/challenger, Bayesian optimization
Model Updater
Applies learned improvements: pattern addition, weight adjustment, strategy updates
What the Graph Learns From
Every agent reports the outcome of its work. The learning coordinator watches these signals and uses them to recognise patterns and update what the fleet does next:
What a Learning Observation Captures
- What was observed — a pattern worth repeating, an anti-pattern worth avoiding, or an optimisation that paid off.
- How sure the system is — a confidence level, plus the indicators that pointed to success or failure.
- What to do about it — concrete recommendations agents can apply on their next task.
- How often it holds — how many times the pattern has been seen and how often it succeeded. Observations lose weight as they age and gain weight as they keep proving right.
Cross-Learning Flow
Code Dependency Analysis
The Knowledge Graph includes comprehensive code dependency analysis at both project and file levels, enabling agents to understand impact, trace relationships, and make informed decisions.
Import Analysis
Tracks module imports across TypeScript, JavaScript, Go, Python, and Java files
Database Table Tracking
Identifies SQL table references from queries and maps file dependencies
API Route Discovery
Extracts API endpoint definitions and maps handlers to routes
Config & Environment
Tracks configuration keys and environment variables used across files
Function & Class Analysis
Maps exported functions, classes, and their relationships
Change Impact Analysis
Determines affected components when a file or table changes
What the Dependency Graph Holds
Things
Source files, external modules, database tables, API endpoints, functions and classes, across TypeScript, JavaScript, Go, Python and Java.
Relationships
Which file imports which module, which file queries which table, which file exposes which endpoint, and which function calls which.
Questions it answers
Which files break if this table changes? Who reads this configuration key? Where is this endpoint defined? Agents ask these before they change anything.