Reference — Nexus Meta KG Vocabulary

Principle

Nexus Meta KG uses a stable technical vocabulary in English.

The technical identifiers are the canonical contract for the API, storage, tests, context packs and future MCP tools. UI labels may help human reading, but they must not replace the canonical identifiers.

Recommended display:

Human label · TECHNICAL_ID
Human label · TECHNICAL_ID (count)

Examples:

Importe · IMPORTS
Définit · DEFINES
Fichier avec anomalie · HAS_ANOMALY

Node Types

Node types are stored in meta_nodes.node_type.

They describe what a node represents in the application graph. They are technical developer-facing identifiers and should stay in English.

Core node types currently include:

Node type	Meaning
`repository`	Scanned repository root.
`directory`	Directory in the scanned repository.
`file`	Source or configuration file.
`python_module`	Python module parsed from a `.py` file.
`typescript_module`	TypeScript or TSX module.
`react_page`	Next.js page entry point.
`react_component`	React component.
`hook`	React hook or hook-like symbol.
`api_endpoint`	API route or endpoint detected from code.
`class`	Class symbol.
`function`	Function symbol.
`method`	Method symbol.
`import`	Import reference extracted from code.
`external_reference`	Dependency or target outside the scanned repository.
`test_file`	Test file.
`test_case`	Test case or test function.
`code_anomaly`	Backward-compatible finding node for code diagnostics.
`finding`	Canonical finding node for diagnostics.

Relation Types

Relation types are stored in meta_edges.edge_type.

They describe how two nodes are connected. They are Nexus canonical identifiers, not raw strings copied from the source code.

Core relation types currently include:

Relation type	Meaning
`CONTAINS`	Source node contains target node.
`DEFINES`	File or module defines a symbol.
`IMPORTS`	Source file or module imports target file, module or external reference.
`USES_COMPONENT`	Source uses a React component.
`USES_HOOK`	Source uses a hook.
`EXPOSES_ENDPOINT`	Code exposes an API endpoint.
`HANDLES_ENDPOINT`	File or symbol handles an API endpoint.
`CALLS_API`	Source calls an API endpoint.
`TESTED_BY`	Source is covered by a test node.
`HAS_ANOMALY`	File has a diagnostic/finding node.
`BLOCKS_EXTRACTION`	Finding blocks full extraction of a source file.
`FINDING_AFFECTS_FILE`	Canonical finding affects a file.
`FINDING_AFFECTS_SYMBOL`	Canonical finding affects a symbol.
`FINDING_HAS_EVIDENCE`	Finding is linked to evidence.
`FINDING_REPORTED_BY_TOOL`	Finding was reported by a tool.
`TOOL_RESULT_NORMALIZED_AS`	Raw tool result was normalized as a finding.

Data and vector relation types include:

Relation type	Meaning
`SCHEMA_CONTAINS_TABLE`	Postgres schema contains table.
`TABLE_HAS_COLUMN`	Table has column.
`TABLE_HAS_PRIMARY_KEY`	Table has primary key.
`TABLE_HAS_FOREIGN_KEY`	Table has foreign key.
`TABLE_REFERENCES_TABLE`	Table references another table.
`TABLE_INDEXED_BY`	Table is indexed by an index.
`MIGRATION_CREATES_TABLE`	Migration creates table.
`MIGRATION_ALTERS_TABLE`	Migration alters table.
`CODE_READS_TABLE`	Code reads table.
`CODE_WRITES_TABLE`	Code writes table.
`CODE_UPDATES_TABLE`	Code updates table.
`CODE_DELETES_FROM_TABLE`	Code deletes from table.
`CODE_READS_COLUMN`	Code reads column.
`QDRANT_CONTAINS_COLLECTION`	Qdrant instance contains collection.
`COLLECTION_HAS_PAYLOAD_FIELD`	Collection has payload field.
`COLLECTION_USES_EMBEDDING_MODEL`	Collection uses embedding model.
`CODE_QUERIES_COLLECTION`	Code queries vector collection.
`CODE_WRITES_COLLECTION`	Code writes vector collection.
`CODE_DELETES_POINTS`	Code deletes vector points.
`CODE_USES_FILTER_FIELD`	Code uses vector payload filter field.
`PAYLOAD_FIELD_MAPS_TO_COLUMN`	Payload field maps to relational column.
`DOCUMENT_INDEXED_IN_COLLECTION`	Document is indexed in a vector collection.
`RETRIEVER_USES_COLLECTION`	Retriever uses vector collection.

Source of the Vocabulary

The vocabulary is generated by Nexus parsers and graph builder rules:

repository scanner;
Python parser;
TypeScript/TSX parser;
SQL parser;
Qdrant/static usage parser;
Meta KG graph builder.

The source code provides facts. Nexus normalizes these facts into canonical node_type and edge_type identifiers.

UI Rule

Node types stay technical: python_module, react_page, api_endpoint.
Relation types show both human help and canonical ID: Importe · IMPORTS.
Counts may be appended when the graph provides facets: Importe · IMPORTS (1015).
Future translations may translate only the human label, never the technical identifier.