القائمة
Review exactly one unit and one declared role in one named Vocal2Midi Linux model manifest without writing production code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Prepare dependency, asset, tensor-interface, seam, and rollback evidence for one named Vocal2Midi Linux model unit under the py2rs control plane.
Coordinate one named Vocal2Midi Linux model shard under the py2rs model control plane. Use when selecting, re-cutting, routing, implementing, reviewing, or promoting Qwen3-ASR, Romaji ASR, HubertFA, GAME, or RMVPE work.
Implement exactly one confirmed unit from one named Vocal2Midi model manifest as the writer role after dependency/bootstrap acceptance.
| name | vocal2midi-rs-review-gate |
| description | Review exactly one unit and one declared role in one named Vocal2Midi Linux model manifest without writing production code. |
Review one role for one unit in one selected model shard. The reviewer does not patch production code, change Cargo state, or mark a manifest promoted.
Read the model control plane, selected manifest, unit sources/tests/assets, writer verification, dependency/bootstrap evidence, relevant historical reports, and rollback route. Do not read the closed backend manifest or other model manifests.
The review batch must contain only writer-verified reimplemented units. A
review report must name the batch and record a verdict for every in-scope unit;
one unit failing does not erase evidence for unrelated units.
behavior_reviewer: required first for legacy_seam units; compare the
named legacy public seam exactly across inputs, outputs, errors, side effects,
lifecycle, and caller handoff.dependency_bootstrap_reviewer: verify crate-recon mode/report, features,
dependency paths, asset provenance, canonical shared dependency ownership,
and inventory impact.error_tracing_reviewer: verify structured errors, stage/path context,
cancellation, redaction, and rollback diagnostics.data_algorithm_reviewer: verify model IO data structures, deterministic
adapters, complexity evidence, and no unsupported algorithm changes.rust_style_reviewer: verify ownership, visibility, module shape, lints,
generated-code boundary, and maintainability.architecture_reviewer: verify seam depth, ownership, shared capability
storage, routing, and rollback.product_ergonomics_reviewer: verify repeated use, batching, cancellation,
cleanup, recovery, and operator-facing errors.For model_evidence execution units, do not demand output-value parity. Demand
asset/load provenance, tensor names/ranks/shapes/dtypes, structured failures,
repeated-call and cleanup behavior, production routing, and rollback.
reimplemented.legacy_seam.pass, pass_with_followups, fail, or not_required per unit.Do not convert a failed parity review into a Rust-only oracle. Do not treat compilation, generated code, or a Rust-to-Rust contract as promotion evidence.
Write one report under rewrite-in-rust/reviews/ using the project naming
convention. Include model, manifest, unit, batch, role, evidence commands,
findings ordered by severity, per-unit verdict, residual risk, and rollback
readiness. Reports are new evidence; existing reports remain historical and
must not be edited by this gate.
Name the selected model/unit/batch/role, verdict, report path, highest-severity findings, checks, and coordinator readiness. Reviewers never update unit state.