verification-reference

Code artifact verification uses four levels—exists, substantive, wired, and functional checks—to validate real implementations. It scans your software project to detect universal placeholder patterns like TODO and empty implementations across components and APIs.

Detecting placeholder code requires scanning for universal stub patterns including TODO, FIXME, and empty implementations. This verification process identifies incomplete artifacts by checking if they contain substantive logic rather than placeholders across your repository.

Wiring checks validate that API routes, schemas, hooks, and environment variables are properly connected within your project. The verification framework applies artifact-type checklists to ensure each component meets its specific wiring requirements.

Automated verification scripting provides pattern-driven checks across your repository and generates a VERIFICATION.md report as output. This enables continuous auditing of build quality by systematically validating artifacts against the four-level framework.

Artifact verification supports software projects containing components, API routes, schemas, hooks, and environment variables. It applies existence and substantive checks tailored to each artifact type, ensuring comprehensive coverage regardless of project structure.

Multi-level verification is necessary when simple build checks cannot distinguish between functional features and placeholders. Use this approach to enforce substantive, wired, and functional checks that prevent confusing stub implementations with complete artifacts.