write_review
Record review decisions for artefacts (tasks, reports, code changes) using structured review files. Supports approval, rejection, requests for changes, or escalation to human review.
Instructions
Write a REVIEW file (governance-layer decision, per ADR-0017/0025).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reviewer_role | Yes | Role code of the reviewer (must have ``review_decision`` capability; typically ``layer: governance`` or ``layer: admin``). | |
| subject_type | Yes | What is being reviewed. One of ``task`` / ``report`` / ``role_switch`` / ``code_change``. | |
| subject_ref | Yes | Reference to the artefact under review — file path for task/report/code_change; fcop.json diff range for role_switch. | |
| decision | Yes | Review decision. One of: ``approved`` — artefact is accepted; ``rejected`` — artefact is rejected (cannot proceed); ``needs_changes`` — must be revised (requires ``required_changes``); ``abstained`` — reviewer recuses; ``needs_human`` — reviewer escalates to human (ADR-0025, v1.1). The review stays pending until ``mark_human_approved`` is called to close the loop. | |
| rationale | No | Free-text rationale for the decision. Recommended for all non-``approved`` decisions. | |
| required_changes | No | Newline- or comma-separated list of required changes. Mandatory when ``decision=needs_changes``. | |
| reviewer_agent | No | Optional agent/session identifier on top of the role code. | |
| body | No | Additional Markdown body after the frontmatter. | |
| subject_short | No | Override the ``-on-{slug}`` segment of the filename. Auto-derived from ``subject_ref`` when omitted. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |