reviewer-protocol

Strict code review workflows are enforced by applying lockout semantics that prevent original authors from self-revising rejected artifacts, ensuring objective peer evaluation. The coordinator verifies agent eligibility and reassigns tasks to new agents.

Agent lockout semantics prevent the original author from modifying a rejected artifact during the code review cycle. This forces the coordinator to assign revision tasks to a different agent, eliminating defensive feedback loops and maintaining independent quality assurance.

Self-revision cycles are prevented by automatically locking out the original author from rejected artifacts. The protocol requires the coordinator to reassign the rejected work to a new agent who implements the necessary changes based on reviewer feedback.

Yes, this protocol applies directly to multi-agent orchestration by managing independent revision and task reassignment. It ensures that when a lead developer rejects a module due to flaws, the coordinator verifies eligibility and assigns a different agent.

Coordinator agent eligibility verification is required to prevent self-revision cycles and ensure independent code quality. It guarantees that the agent assigned to revise a rejected artifact is not the original author, enforcing objective peer review.

Automated lockout enforcement requires a multi-agent environment with a coordinator capable of verifying agent identity and managing task reassignment. It is limited to scenarios where independent peer review and strict artifact rejection workflows are mandatory.