vc-risk-evidence-pack

To generate an evidence pack for high-risk code changes, you must manually opt-in by risk class to automate the creation of structured artifacts that document the review process and ensure safety compliance.

You need an evidence pack for security compliance when modifying critical systems like authentication, billing, or data migration, ensuring that high-risk development tasks meet required safety and review protocols.

Risk assessment for high-risk development tasks works by using a risk gate to automatically identify and categorize sensitive code changes, then validating the completeness of the generated evidence pack.

Yes, you can validate the completeness and correctness of a generated evidence pack before finalizing changes, ensuring that all required structured artifacts for high-risk tasks are properly documented.

Yes, generating an evidence pack requires manual opt-in by risk class, allowing developers to selectively apply automated validation and artifact generation to specific high-risk critical systems.

The main limitation of automating evidence pack generation is that it requires manual opt-in by risk class and is specifically scoped to critical systems like authentication, billing, and data migration rather than general code review.