hiivmind-corpus-bridge

Cross-corpus search routing links related concepts by defining query aliases in a registry-graph.yaml file, maintaining a registry-graph to ensure searches span and discover datasets across multiple corpora. This validates cross-corpus relationships across projects.

Validating registry-graph integrity involves checking the consistency of cross-corpus mappings stored in registry-graph.yaml to maintain accurate relationship tracking and query routing across multiple corpora within a project.

Yes, cross-corpus concept bridges require an existing registry.yaml containing at least two corpora, and a graph.yaml file present on at least two corpora to define aliases and route queries properly.

Defining aliases in graph.yaml creates concept bridges that route queries between corpora, improving multi-corpus discovery by linking related terms and ensuring cross-corpus relationships are consistently tracked across datasets.

Yes, registry-graph maintenance supports projects with multiple corpora by validating cross-corpus relationships and storing concept bridges in a central registry-graph.yaml file to ensure consistent mappings across different project environments.

Cross-corpus relationship validation integrates with Read, Glob, Grep, Write, Edit, AskUserQuestion, Bash, and WebFetch to manage registry-graph.yaml files, query aliases, and maintain multi-corpus concept bridges.