Use after editing multiple chapters of Rupture and Return, before manuscript assembly, or when checking cross-chapter coherence. Triggers on: "check consistency", "cross-chapter scan", "manuscript assembly", "final check", "prepare submission", "consistency report".
REQUIRED: Load rr-editorial first for VOCABULARY, CHAPTER-MAP, NO-NOS.
Run both scripts on the chapter files ONLY (exclude backup directories):
mkdir -p /tmp/rr-scan && cp chapter_0*.tex /tmp/rr-scan/
python scripts/scan_consistency.py /tmp/rr-scan/
python scripts/check_redundancy.py /tmp/rr-scan/
These check: signposting, throat-clearing, vocabulary violations, concept re-explanations, key line survival, forward references naming chapter numbers.
For each pair of adjacent chapters, read the last paragraph of N and first paragraph of N+1. Verify:
Expected handoffs:
These MUST be present (regex-searchable):
Verify each chapter carries its political weight (see rr-editorial for per-chapter requirements).
Search for orphaned specifics — model names, tool names, API names, hardware specs that aren't doing argumentative work. The test: would the argument break if you replaced the specific name with a generic description? If not, flag for generalisation.
Grep targets: GPT-4o, Mistral, LoRA, Qdrant, OpenRouter, A100, text-embedding, cosine similarity, silhouette, Betti.
For each hit: is it contextualised for the Meson reader? Is it necessary? Or is it an implementation detail?
Write a timestamped report to feedback/consistency-YYYYMMDD-HHMMSS.md:
# Cross-Chapter Consistency Report
**Date:** YYYY-MM-DD HH:MM:SS
## Automated Scan
- [results from scan_consistency.py and check_redundancy.py]
## Key Lines: [present/missing for each]
## Handoff Chain: [assessment of each transition]
## Specificity Audit: [orphaned specifics found, with recommendation]
## Political Dimension: [chapter-by-chapter assessment]
## Must Fix: [violations with file, line, quoted text, suggested fix]
## Needs Iman's Judgement: [issues requiring human decision]