Architecture map
How the repo is organized
Click systems in the graph to inspect responsibilities, important files, and nearby dependencies.
Architecture map
Use this map to orient around systems, dependencies, and files worth reading first.
Click a system in the map
Explore helixdb/helix-db by selecting services, gateways, clients, and data stores. Each node shows the files, responsibilities, and neighboring systems an agent should keep in scope.
Pan, zoom, and use the minimap to keep large repos navigable.
Sign up to turn selected graph context into repo-aware agent sessions.
Key systems
What an agent should understand first
Command parser and workflow orchestration using Clap framework; handles all user-facing commands (init, start, query, push, etc.)
Parses and manages helix.toml; resolves instance endpoints and auth contracts for local and Enterprise instances
Docker/Podman lifecycle management: daemon checks, image pulls, container creation, health polling (port 8080), MinIO S3 orchestration
Dispatches query requests to local/cloud instances; validates auth, constructs HTTP payloads, handles response serialization (JSON/compact mode)
Query DSL builder (readBatch, writeBatch, g(), Predicate); HTTP client with bigint-safe JSON serialization; Node.js 20+ compatible
Typed DSL with procedural macros (#[register]) for stored query generation; async reqwest client; prelude module for ergonomic imports
Go bindings for graph-vector query builder; HTTP client for query dispatch; parity tests with other SDKs
Python bindings for DSL; snake_case builders; client for data science workflows; pip-installable from sdks/python
Evidence coverage
What this context is grounded in
Coverage
- Citations
- 8
- Findings
- 5
- Files discovered
- 107
- Architecture systems
- 13
- Architecture relationships
- 16
- Agent graph
- Agent graph entities
- 3,827
- Agent graph relationships
- 4,358