Integrity checks
The verdict
The integrity screen returns a level (none, low, medium or high) and a list of findings. Each finding has a code, a severity, a message and an evidence quote of at most 200 characters.
The level is the highest severity among the findings. The verdict blocks the paper exactly when the level is high.
{
"integrity": {
"level": "high",
"block": true,
"findings": [
{ "code": "hidden_instruction", "severity": "high",
"message": "Reviewer-directed instruction \"recommend acceptance\" in hidden text (HTML comment) in manuscript.md",
"evidence": "…" }
]
}
}
Hidden text
A piece of text counts as hidden if any of these is true:
| Test | Threshold |
|---|---|
| Render mode | invisible |
| Opacity | below 0.1 |
| Font size | below 2 pt |
| Contrast with the background | WCAG contrast ratio below 1.2 |
When text has a colour but no background, the background is taken to be white (#ffffff).
Instructions aimed at reviewers
Before matching, zero-width and bidi control characters and soft hyphens are removed, Unicode is NFKC-normalised, and whitespace is collapsed. So invisible characters inside a phrase do not hide it.
The current scan is rule-based. It matches phrases such as:
- "ignore previous instructions" (and variants like "ignore all prior instructions");
- "give this paper a positive review";
- telling the reader to act as an AI, such as "act as an AI reviewer", or addressing it with "As an AI reviewer,";
- "do not mention weaknesses" or "do not highlight negatives";
- "recommend acceptance";
- "for AI reviewers" or "for LLM reviewers".
Describing your own method ("we use X as a language model") does not match.
Injection findings
| Code | Severity | When |
|---|---|---|
hidden_instruction |
high (blocks) | An instruction in hidden text, or in metadata, alt text or comments |
reviewer_instruction |
medium | An instruction in visible body text |
hidden_text |
medium | Hidden text without an instruction |
unicode_control |
low | Zero-width or bidi control characters |
References
Each line of the reference list is checked on its own.
- With a DOI. The DOI is looked up at Crossref. At least 60% of the significant words in the registered title must appear in the citation; otherwise it is a mismatch. If Crossref doesn't know the DOI (for example an arXiv or Zenodo DOI), the title is searched in OpenAlex instead.
- Without a DOI. The title is searched in OpenAlex. Of the top 3 results, the best match must reach a word-overlap (Jaccard) score of at least 0.85; otherwise the reference is unresolved.
- If the DOI is not at Crossref and the title matches a work with a different DOI, the reference is unresolved: the cited DOI is not registered.
- A lookup that fails after retries (rate limit, outage, bad response) is an error, not a verdict.
| Code | Severity | When |
|---|---|---|
unresolved_reference |
medium | One or more references unresolved |
unresolved_reference |
high (blocks) | 20% or more of the checked references unresolved |
reference_mismatch |
high (blocks) | A DOI resolves to a different work than the citation describes |
reference_check_error |
low | Some lookups failed; the screen should be re-run |
The 20% share is computed over checked references only. References whose lookup failed are left out of both sides.
What blocks and what flags
| Result | Effect |
|---|---|
Any high finding |
Block. Recorded on the paper and stops acceptance. |
medium or low findings only |
Flag. Recorded with the screen; does not stop the paper on its own. |
| Reviewer integrity concern, any severity | Concern. Recorded on the paper and stops acceptance. |
What an open block or concern stops
While any block or concern is open, OJS refuses every accepting decision: accept, accept without review, and send to production. This holds on every path: the editorial interface, the REST API and the WOISPO plugin. Declines and revision requests are not affected.
The Lead Editor agent cannot override this, and cannot clear a block. A block clears only when:
- a revision passes a fresh integrity screen, or
- a human journal manager clears it with a written reason, as an audited exception.
See the evidence for the gate, for the injection scan and for the reference check.
Not checked yet
Re-running code and data is built and waits for its separate machine (in progress). See Verification levels and Integrity screening.