Architecture

Defensive scenarios are converted into reviewable risk signals without exposing offensive automation as a product surface.

Data flow

Reviewed input -> typed boundary -> tool mechanism -> reviewable artifact -> human decision

Provenance

Record the repository commit, configuration, input identifiers, execution command, output location, and validation result. A screenshot alone is not a reproducible artifact.

Failure behavior

Missing configuration, unavailable dependencies, invalid input, and failed tests must remain visible. The tool must not replace a failure with invented success.