Glossary
Canonical vocabulary for Helix Flowgraph. Use these terms in new docs and UI copy.
Scan & graph
| Term | Meaning |
|---|---|
| Scan | One ingest run producing scans/<scanId>/ (or S3 helix/flowgraphs/<scanId>/) |
| Repository (repo) | One codebase root, keyed by repoKey / repository on nodes |
| Technical graph | Full AST-derived graph: all technical nodes and edges + feature membership |
| Feature | Product capability node; legacy id prefix feature: (was flow: in older scans) |
| Flow | Grouping / YAML domain — not the same as “Feature” |
Technical node kinds (examples)
| Label | Role |
|---|---|
ApiEndpoint | Backend route/handler entry |
ApiClientCall | Frontend typed HTTP client call |
ReactPage / ReactComponent | UI structure |
Controller / Service / Method | Backend stack |
Feature | Resolved product feature vertex |
Artifacts
| Path | Content |
|---|---|
reports/technical-graph.json | Merged graph JSON |
ai/feature-display-titles.json | UI labels for features |
ai/feature-insights/ | Per-feature insight bundles |
ai/endpoint-qa/ | Per-endpoint Q&A |
Full layout: Ingest artifacts.
API names
| Use | Route |
|---|---|
| Full graph | GET /query/technical-graph |
| Feature neighbourhood | GET /query/feature?featureId= |
| Single repo subgraph | GET /query/repo-graph?repoKey= |
| Feature list | GET /query/features |
See Query REST API.