reviewer-protocol

Independent code review is enforced by strict lockout rules that block the original author from self-revision post-rejection, requiring a different agent to handle the revision. This avoids defensive feedback loops and ensures unbiased artifact validation.

A reviewer rejection protocol triggers strict lockout semantics, locking out the original author and requiring coordinator enforcement to select a different agent for revision. Reviewer reassignment and expertise escalation are supported for complex artifacts.

Code review deadlock occurs when all eligible agents are locked out from revision. The protocol escalates the deadlock directly to the user, ensuring the coordinator cannot bypass lockout rules or force self-revision.

Yes, a coordinator systemically verifies that the selected revision author is not the original author after a code review rejection. This enforcement mechanism guarantees strict lockout semantics and maintains independent review integrity.

An independent review protocol prevents authors from fixing rejected code to avoid defensive feedback loops. Strict lockout rules ensure the original author cannot self-revise, mandating a different agent for revision to maintain objective quality standards.

A lockout protocol for code review coordination is needed after an artifact is rejected by a reviewer. It enforces strict lockout rules, preventing self-revision and requiring a different agent to handle the revision to ensure independent review.