detector-workflow

Adding a new detector to the AICA scanner involves a complete 8-step workflow that guides you through planning, scaffolding, implementing detection logic, integrating with scanner/core.py, writing tests, and final documentation.

The AICA detector development workflow is an 8-step process that standardizes detector outputs, enforces logger conventions, validates relative paths, and ensures testable integration into the scanner pipeline to eliminate error-prone manual coding.

Testing and validating detector integration for AICA's scanner requires applying specific workflow guidance for creating tests and running validations, ensuring your detection logic integrates testably into scanner/core.py with correct structured outputs.

Yes, AICA detector development requires specific logger conventions and relative paths to satisfy the requirements for structured detector outputs and ensure testable integration into the scanner core pipeline.

The best way to standardize detector outputs for AICA's repository intelligence system is to use a complete detector workflow that provides templates, reference detectors, and conventions integrating directly with the scanner pipeline.

Your AICA detector integration into scanner/core.py may fail validation if it does not satisfy the required structured detector outputs, logger conventions, relative paths, and testable integration outlined in the detector workflow.