consensus-loop:guide

To submit structured evidence for code review, provide an evidence package containing required sections like Claim, Changed Files, Test Command, Test Result, and Residual Risk, ensuring your submission is auditable and passes consensus validation.

A consensus-loop watch file is an audit mechanism that validates submitted code review evidence by enforcing required sections, formatting rules, and a tag lifecycle to ensure all submissions are consistent and auditable.

Format your audit evidence package by including the defined sections: Claim, Changed Files, Test Command, Test Result, and Residual Risk, applying the correct tag lifecycle to validate your submission within the consensus-loop workflow.

Validating watch-file evidence requires sections for Claim, Changed Files, Test Command, Test Result, and Residual Risk, alongside adherence to formatting rules and the defined tag lifecycle to prevent audit rejections.

Handle audit rejections by restructuring your submission according to the consensus-loop evidence template, ensuring all required sections are present and the tag lifecycle is correctly applied for successful revalidation.

Yes, the consensus review guide works for standard code submissions, reviewer feedback, and audit rejections by providing structured evidence package templates that standardize the validation process across all scenarios.