merv

Independently review a Merv reflection-wave code consolidation after the reflection is approved. Verify the immutable proposal, its tests, and its decision for every experiment, then submit pass or return it only to code consolidation. Use for the consolidation_reviewer gate.

Perform a read-only adversarial review of a completed Merv experiment attempt. Verify execution, submitted results, metrics, and conclusions against the approved plan, then submit the verdict and correct return path.

Perform a read-only adversarial review of a Merv experiment design before execution. Check whether the submitted plan can test its claim, then submit the verdict through the review capability.

Post to the project feed as work happens — results, kills, hunches, ideas, papers, questions, live checkpoints — in one voice, short, with what you looked at attached. Load at the start of a session and post throughout.

Run a Merv project-reflection wave across completed experiments: create the five-lens roster, fan out independent lens agents, reconcile their findings into the reflection document and change spec, coordinate independent review, and hand approved research to code consolidation. Use when the user requests reflection or workflow.status_and_next reports stale project knowledge or a reflection gate.

Perform a read-only adversarial review of a Merv project-reflection wave. Check the reflection document and change spec against the snapshotted corpus and five lens reflections, then submit the verdict and correct return path.

Operate the Merv research workflow: select a project, follow workflow.status_and_next, create and run experiments and tasks, submit evidence, and coordinate required design, attempt, or task reviews. Use for experiment- and task-level work and for resuming work already in progress.

Operate Merv cloud sandboxes through merv-sandboxes: select hardware, use certificate SSH or durable jobs, retain outputs, extend leases, and release machines for remote or expensive experiment work.

Perform a read-only review of a completed Merv task delivery. Verify each Done-when check in the brief against the delivery's evidence — by checking, not by reading — judge whether the checks met mean the goal is achieved, then submit pass, needs_changes (back to in_progress), or fail (the task ends).