reviewer-protocol

A lockout-driven reviewer workflow prevents original authors from self-revising rejected artifacts. By enforcing strict per-artifact lockout rules, it blocks the original author and forces a neutral, independent revision path by a different agent.

During code review escalation when all eligible agents are locked out, the system escalates to bring in a new expert. This ensures the collaborative development artifact can still be revised independently without violating the lockout rules against the original author.

A coordinator enforces revision author identity by verifying the author of the new revision against the original artifact creator. It prevents co-authoring during the revision process and ensures the new revision is produced by a different, eligible agent.

Yes, you can reassign a rejected artifact to a different agent instead of escalating. The lockout-driven workflow supports reassign and escalate options to bring in the appropriate expertise for producing the independent revision.

A limitation of per-artifact lockout scopes is that if all eligible agents become locked out, the system must escalate to a new expert. Additionally, it strictly prevents co-authoring during revision, which may restrict collaborative fixing approaches.