Build the Domain-Specific Ontology Auto-Binning Engine

[squid-protocol]

Epic: #75
Target: gitgalaxy_config.py, detector.py, & Output Recorders

Context & Strategic Value

Generic static analysis classifies a file as "C++". GitGalaxy must be smarter. By cross-referencing extracted dependencies (#include, import) against predefined industry ontologies, we can instantly tell a Director of Engineering: "This C++ file is handling High-Frequency Trading Logic," or "This file is managing Aerospace Flight Dynamics." This provides zero-trust architectural mapping instantly.

Implementation Tasks

• In gitgalaxy_config.py, create the CUSTOM_ONTOLOGY dictionary.
  • Populate it with the Aerospace & Robotics, FinTech & HFT, and MedTech & BioInformatics domains (as outlined in Epic [EPIC] Aerospace Compliance & Enterprise Integration #75).
• In detector.py (StructuralExtractor._dependency_capture), implement the interception logic.
  • After raw dependencies are parsed, perform an O(1) set-intersection against the CUSTOM_ONTOLOGY matrix.
• If a match is found, append the specific Domain Signature (e.g., Avionics & Middleware) to the file's telemetry dictionary.
• Update llm_recorder.py and audit_recorder.py to surface these ontology tags prominently at the top of their generated reports.

Validation

Scan a repository utilizing px4 or mavlink (like ArduPilot). The final Markdown and JSON reports must explicitly label those specific files with the Avionics & Middleware Domain Signature.