---
schema: wtfp.workflow/v1
action: review-section
source: wtfp.protocol
---

# Review a section

@protocol://project/README.md
@protocol://skills/wtfp-review-manuscript/SKILL.md
@protocol://skills/wtfp-review-manuscript/references/actions.md

## Record contract

Read: `project://manifest`, `project://decisions`, `project://structure/outline`, `project://sections/{section}`, `project://sections/{section}/context`, `project://sections/{section}/plans/{plan}`, `project://sections/{section}/research`, `project://sections/{section}/summary`, `project://evidence/{evidence}`, `project://paper/{artifact}`.
Produce: `project://sections/{section}/reviews/{review}` (create), `project://validations/{validation}` (create), `project://sections/{section}` (update).

Resolve every logical URI through the host adapter. Portable v1 JSON records are the source of truth: schema-validate before a write, preserve stable IDs, update revision and timestamps where required, and replace records atomically. Never pass a literal logical URI to a shell command or infer record state from a legacy Markdown control file.

Manuscript prose and supporting context, research, plan, review, summary, handoff, and deliverable artifacts retain their authored format (normally Markdown). Link them from the relevant v1 record; do not convert manuscript prose into project-state JSON.

## Procedure

1. Resolve one manuscript section, its outline claims, context, plan, research, summary, decisions, evidence, neighboring prose, and review rubric.
2. Dispatch one read-only review of claim coverage, reasoning, evidence, citations, coherence, prose, and requirements. If the structured result is malformed, allow at most one corrective retry for result-contract compliance; never retry until a reviewer says pass, and do not retry warning-only or explicitly accepted debt.
3. Write layer, confidence, location, impact, recommendation, and other rich detail in the Markdown review. Encode the read-only validation using only members allowed by the closed v1 schema; issue objects contain only severity, summary, and optional evidence, and the root never gains an `input_revisions` member. Disputed findings go through a user gate; accepted warning debt remains an `issues-found` result and does not authorize manuscript edits.
4. Update only the section record to link the review. Review does not write project state, create a pause checkpoint or handoff, invoke pause implicitly, or invent a `paused` phase; leave lifecycle transitions to their owning actions.

## Safety and completion

Do not initialize a repository or run branch, stage, commit, merge, push, or publish operations. If requested, return a clearly labeled optional handoff for a separately authorized action.

Report the logical resources read, created, updated, archived, or deleted; the gates crossed; validation results; unresolved checkpoints; and the safest next action. Never claim a mutation that was not verified.