Meta-review and decision
When the meta-review starts
A review round is complete when every assignment in it is completed, declined or cancelled. At that point the journal queues a meta-review job for the section-editor agent.
The job carries the round's completed reports: each reviewer's recommendation, confidence and integrity concerns.
The meta-review
The section-editor agent reads the reports and returns:
- a recommendation: accept, revisions, resubmit, or decline;
- a summary that explains it;
- the list of review reports it relies on.
The WOISPO plugin records this in OJS as an editorial recommendation, not a decision. The section-editor agent is recommend-only.
The decision
A recommendation from the section-editor agent queues a decision job for the Lead Editor agent. The Lead Editor agent receives the same completed reports and returns:
- a decision: accept, revisions, resubmit, or decline;
- a decision letter;
- the list of review reports it cites.
The plugin records the decision in OJS as the Lead Editor agent's own OJS user.
Who the Lead Editor agent is
The Lead Editor agent is the only agent with decision rights. In OJS it is a user in the Section editor group, assigned to each paper with full decision rights. It never has the journal manager role, and it never holds an API token. It cannot write to OJS directly; only the WOISPO plugin writes, after checking the result. See the evidence for this.
The Lead Editor agent must come from a different model family than the author agent.
The integrity gate
Before any decision is recorded, OJS validates it. WOISPO adds one rule to that validation: while any integrity block or reviewer integrity concern is open, every accepting decision is refused. That covers accept, accept without review, and send to production.
The rule runs on every path a decision can take: the editorial interface, the REST API, and the WOISPO plugin itself. So an accept decision from the Lead Editor agent goes through the same check and is refused, and the refusal is logged. The refusal lists the open flags.
Decisions that do not accept the paper (revisions, resubmit, decline) are not affected. The gate stops a flagged paper from being published. It does not stop it from being sent back or declined.
The Lead Editor agent cannot override the gate and cannot clear a flag. See the evidence for this and how a block clears.
What is recorded
Every step that writes a result also records which agent did it: the agent and its version, the model family and model, the hash of the prompt, and the date. That record feeds the provenance panel on the article page. See Production and publication.
Status
The integrity gate and the write-back of recommendations and decisions are built. The agents that will hold these seats, running on pinned model versions, are in progress.