# Original Review Request

This file MUST be written by the Coordinator at Phase 1 (Scope and Thesis)
before any other pipeline phase runs. It preserves the verbatim user prompt
that initiated the review — the upstream provenance of every artifact in the
repository (title, table of contents, cluster structure all originate here).

> **Template scaffold.** This is a placeholder. The orchestrator skill
> (`skills/comprev-orchestrator-v29.md`, Phase 1) instructs the Coordinator to
> overwrite this file with the actual user prompt at the start of every run.
> Validator check `REVIEW_REQUEST_CAPTURED` (Phase 14V) fails if this scaffold
> text is still present at assembly time.

**Operon project ID:** `[PIPELINE FILLS THIS]`
**Captured at:** `[PIPELINE FILLS THIS]`
**Pipeline:** Expert Review Pipeline v29 (`skills/comprev-orchestrator-v29.md`)

---

## Verbatim user prompt

> [PIPELINE INSERTS THE USER'S TASK DESCRIPTION HERE, VERBATIM, AS A
> BLOCKQUOTE. NO PARAPHRASING, NO SUMMARIZATION, NO REORDERING. The only
> permitted edits are mechanical re-flow of whitespace that the chat client
> stripped — split a run-together TOC back into a numbered list; convert a
> run-together skills-list into a bullet list. The Editorial note section
> below MUST document any such mechanical change.]

---

## Editorial note

[Document each mechanical reformat applied above (e.g. "the chat client
submitted the TOC as a single paragraph; it has been split into N numbered
entries; no titles or ordering were changed"). If no edits were applied,
write "No edits applied; the prompt above is byte-for-byte identical to the
user's submission."]

The unaltered single-line original is preserved at
[`provenance/review_request.txt`](review_request.txt) for byte-for-byte
audit.