Hypo-Workflow

Route project work through the manifest-based Hypo-Workflow protocol. Use for /hw:* commands, repository initialization, Goal or Cycle delivery, structured experiments, focused maintenance records, final acceptance, and restart-safe Resume.

Define and run a multi-stage Hypo-Workflow delivery with ordered Milestones and one final manual acceptance. Use for /hw:cycle or work whose stages have real dependency order.

Maintain a non-linear, reproducible experiment lane with project knowledge, run identity, parameter scans, long-run supervision, scientific review, immutable Git records, and instant materialized status. Use for /hw:experiment, experiment setup or reruns, NeRF/AceSim-style comparisons, baseline changes, parameter sweeps, result triage, and questions such as "现在实验怎么样".

Define and run one bounded Hypo-Workflow delivery outcome without fake Milestones. Use for /hw:goal or when the user wants one explicit acceptance target that a capable model can execute after approval.

Inspect the repository and recommend one available Hypo-Workflow path. Use for /hw:guide or when the user is unsure whether to initialize, use Goal, use Cycle, manage experiments, maintain, resume, accept, or reject.

Build an evidence-driven Goal Design or Cycle Plan. Use for /hw:plan and planning requests that need questions, architecture choices, ordered decomposition, or durable research before execution.

Resume the active manifest-based Hypo-Workflow Delivery from Runtime, Continuation, and the latest valid Recovery Pack. Use for /hw:resume or when tracked Goal/Cycle work must continue after restart or compaction.

Accept the active Goal or Cycle at its final pending acceptance gate. Use for /hw:accept or an explicit user acceptance statement.

Initialize or inspect a Hypo-Workflow workspace using the manifest-based format. Use for /hw:init when starting a repository, adopting an existing codebase, or checking whether legacy state can be adopted safely.

Persist focused day-to-day project facts without opening a Goal or Cycle. Use for /hw:maintain and for ambient capture of requirements, preferences, decisions, or feedback in a current workspace.

Reject the active Goal or Cycle at final manual acceptance with structured feedback. Use for /hw:reject or an explicit rejection of pending results.