orchestrata_ultimate.knowledge_graph

Reference › orchestrata_ultimate › knowledge_graph

Knowledge Graph module for Orchestrata.

The knowledge_graph package makes the codebase and its surrounding work a queryable graph: files contain classes, classes define methods, functions call each other, specs trace to code, and runtime events mention the code they touched. Everything it writes goes to the operational knowledge graph, the orchkg database on the orchgraph engine (a Memgraph fork), reached over Bolt. The neo4j driver names that remain are Bolt-client naming only, since Neo4j is retired. The separate shared semantic/RAG graph, the memgraph database, belongs to the semantic_graph package; only semantic_bridge reads from both. The conversation capture path writes to a third, dedicated conversation graph.

The parts, by role:

• Identity and schema: canonical_schema (merge keys, DDL, conformance), schema, ontology_mapping, plus the types in types, types_enums and types_nodes.
• Access: graph_client, config, nodes, relationships and the interfaces protocols.
• Ingestion: sync for bulk AST JSON, synchronizer with file_watcher for incremental updates, and ast_analyzer with code_parser and the extractors for live analysis.
• Read side: query_engine, search, kg_context, and context injection in context_injector with the context_pack subpackage and graph_context_validator.
• Writers and records: runtime_writer, architecture_writer, kg_design, cxp_auditor, conversation_consumer and test_results_store.
• Governance and history: pam_integration, prolog_bridge, temporal, history, versioning, anomaly_detector and portfolio.

Source files enter through sync or synchronizer, land in orchkg under canonical ids, and are read back by query_engine, kg_context and the context injector when a volk starts a task. The one server entry point is the gRPC service in server. Start with canonical_schema, then sync, then context_injector; the story is on the knowledge_graph module page.

Curated narrative

The hand-written story of this package: orchestrata_ultimate.knowledge_graph.

55 modules, 21,436 lines of code.

Subpackages

Modules

Dependency diagram

Truncated: showing 40 of 48 modules/subpackages (most connected first) and 5 of 5 outside packages.