Trigger: After Stage 2 (WRITE) completion, before Stage 3 (REVIEW) Purpose: Ensure all references and data are not fabricated or erroneous before submission for review
Execution steps:
1. integrity_verification_agent executes Mode 1 (initial verification) on the paper
2. Verification scope:
- Phase A: 100% reference existence + bibliographic accuracy + ghost citations
- Phase B: >= 30% citation context spot-check
- Phase C: 100% statistical data verification
- Phase D: >= 30% originality spot-check + self-plagiarism check
- Phase E: 30% claim verification spot-check (minimum 10 claims)
3. Result handling:
- PASS -> checkpoint -> Stage 3
- FAIL -> produce correction list -> fix item by item -> re-verify corrected items
- PASS after corrections -> checkpoint -> Stage 3
- Still FAIL after 3 rounds -> notify user, list unverifiable items
Trigger: After Stage 4' (RE-REVISE) or Stage 3' (RE-REVIEW, Accept) completion, before Stage 5 (FINALIZE) Purpose: Confirm the revised paper is 100% correct and ready for publication
Execution steps:
1. integrity_verification_agent executes Mode 2 (final verification) on the revised draft
2. Verification scope:
- Phase A: 100% reference verification (including those added during revision)
- Phase B: 100% citation context verification (not spot-check, full check)
- Phase C: 100% statistical data verification
- Phase D: >= 50% originality spot-check (100% for newly added/modified paragraphs)
- Phase E: 100% claim verification (zero MAJOR_DISTORTION + zero UNVERIFIABLE required)
3. Special check: Compare with Stage 2.5 results to confirm all previous issues are resolved
4. Result handling:
- PASS (zero issues) -> checkpoint -> Stage 5
- FAIL -> fix -> re-verify -> PASS -> Stage 5
5. ⚠️ **IRON RULE**: Must PASS with zero issues to proceed to Stage 5
Reference: academic-pipeline/references/score_trajectory_protocol.md
At Stage 3' (RE-REVIEW), the pipeline_orchestrator_agent tracks per-dimension score deltas and triggers a MANDATORY checkpoint on regressions. Results stored in Integrity Report score_trajectory field (Schema 5).