Internal doctrine for writer, reviewer, and reviser subagents under hydromind-research-write. The parent skill owns all phase advancement and promotion decisions; this skill governs how subagents write, review, and revise artifacts.

Shared Rules

• Start by reading hydro research write status <research_id> --json and hydro research write instructions <research_id> --phase <phase> --json.
• Treat read_paths, write_paths, forbidden_paths, completion_checks, and pre_call_prompts[] as authority.
• Record every LLM call in paper/provenance.json.llm_calls[] with SHA-256 hashes of the prompts supplied by oracle instructions.
• Read only paths authorized by the oracle. Typical sources include design/paper/paper_plan.json, the complete design/paper/*.md design group, execution/results.md, execution/evidence_review.json, and loop evidence.
• Finish by running hydro research write validate <research_id> --phase <phase> --strict --json and return the JSON findings to the parent.

outline-planner

• Phase: outline.
• Read the current write status and hydro research write instructions <research_id> --phase outline --json before reading authorized source files.
• Produce paper/outline.json from paper_plan.json; include paper_plan_sha256, sections, figures, tables, equations, and claims.
• Finish by running hydro research write validate <research_id> --phase outline --strict --json and return the JSON findings to the parent.

opening-drafter

• Phase: opening.
• Read the current write status and hydro research write instructions <research_id> --phase opening --json before reading authorized source files.
• Draft paper/opening/opening.md from the approved outline and paper contract.
• Preserve user citation markers instead of inventing citations.
• Finish by running hydro research write validate <research_id> --phase opening --strict --json and return the JSON findings to the parent.

figures-planner

• Phase: figures.
• Read the current write status and hydro research write instructions <research_id> --phase figures --json before reading authorized source files.
• Produce figure/table manifest, captions, and assets that trace to paper-plan figure/table IDs and ready evidence.
• Keep diagnostic-only evidence out of main-text support unless the paper plan marks it as diagnostic.
• Finish by running hydro research write validate <research_id> --phase figures --strict --json and return the JSON findings to the parent.

draft-writer

• Phase: draft.
• Read the current write status and hydro research write instructions <research_id> --phase draft --json before reading authorized source files and applying any pre_call_prompts[].
• Write a unified paper/drafts/paper.md; use [CLAIM:<claim_id>] and [EVIDENCE:<evidence_id>] markers where needed for validator traceability.
• Do not add unregistered empirical claims, use diagnostic-only evidence as main-text support, or describe a protocol different from execution/evidence_review.json.
• Finish by running hydro research write validate <research_id> --phase draft --strict --json and return the JSON findings to the parent.

refinement-reviewer

• Phase: refinement.
• Read the current write status and hydro research write instructions <research_id> --phase refinement --json before reviewing or revising, and apply any pre_call_prompts[].
• Run the formal reviewer quorum, aggregate required revisions, revise only when evidence remains sufficient, and preserve the best accepted draft snapshot.
• If evidence is insufficient, tell the parent to rollback to Execute or Propose instead of filling gaps with prose.
• Finish by running hydro research write validate <research_id> --phase refinement --strict --json and return the JSON findings to the parent.

No-Reference Policy

HydroMind Research does not perform citation discovery, citation pool construction, BibTeX generation, reference formatting, or citation coverage verification. Do not invent citation keys.

If the paper needs a user-supplied reference, preserve a marker such as [USER_CITATION_NEEDED: reservoir forecasting baseline]. This marker may remain in the final manuscript for user post-processing.

Reviewer Personas

Formal-paper refinement uses at least six comprehensive reviewers per round:

• narrative_quality_reviewer
• hydrology_logic_reviewer
• experimental_skeptic_reviewer
• method_reporting_reviewer
• figure_equation_reviewer
• severe_generalist_reviewer

Each persona may emphasize a different concern, but every reviewer must cover the whole manuscript: sections, mandatory claims, main-text evidence, protocol transparency, writing quality, blocking issues, required revisions, and score justification.

paper-review-v1

Each reviewer writes one JSON review with:

• schema_version: "paper-review-v1"
• reviewer_id
• round
• axis_scores with numeric scores and concrete justifications
• per_section_comments
• claim_level_objections
• evidence_checks
• blocking_issues
• required_revisions
• decision
• overall_score

Invalid reviews do not count toward review quorum. A review is invalid if it misses required sections, mandatory claims, main-text evidence, score justifications, traceable blocking issues, or actionable required revisions.

paper-refinement-v2

The reviser and parent workflow maintain paper/refinement/worklog.json with schema paper-refinement-v2:

• rounds[]
• per-round review_paths
• valid_review_count and invalid_review_count
• aggregate_path
• reviser_response_path
• decision
• overall_score
• blocking_issue_count
• accepted_snapshot
• top-level best_round, best_score, halted, and halt_reason

Acceptance rules are conservative: score drops, increased blocking issues, unsupported claims, stale paper-plan linkage, or protocol transparency regressions require revert. Halt requires minimum rounds, valid review quorum, zero blocking issues, and a best accepted draft snapshot.

Promote Boundary

Subagents do not write paper/final/paper.md. The parent calls hydro research write promote <research_id> --json, which copies the best accepted draft and records promotion provenance.

Do Not

• Do not create references, BibTeX, or citation keys.
• Do not merge reviewer and reviser roles into one transcript.
• Do not omit prompt hashes from provenance.
• Do not bypass oracle validation with manual structure checks.
• Do not write outside the current phase's write_paths.