reviewer-protocol

Code-review lockout enforcement is achieved by restricting revision rights to a non-original agent. The protocol locks out the original author and requires the Coordinator to reassign the revision to a different agent before approval.

A reviewer rejection protocol is a deterministic governance flow that prevents defensive feedback loops by ensuring rejected artifacts cannot be self-edited by the original author, requiring reassignment to a new engineer.

Yes, rejected artifacts can be escalated to new expertise. The protocol allows the reviewer to request escalation, and the Coordinator enforces this path while maintaining the original author lockout.

To prevent self-editing, apply strict lockout semantics that deterministically block the original author from contributing to the revision, forcing the Coordinator to designate a new revision owner.

Yes, the protocol is designed for team-based code-review scenarios. It applies deterministic rules where a failed artifact must be revised by another engineer to ensure objective quality improvements.

The lockout rules require a Coordinator to enforce reassignment or escalation, meaning the workflow depends on a centralized coordination agent to manage the revision owner transition and approval process.