Solution gate

Review Gate asks whether a diff is correct. Solution Gate asks whether the selected shape deserves implementation. It orchestrates the shaping skill:

reproduced defect → frozen contract → blind Shaping passes → probes → reshaping → verdict → detail/breadboard/slice → implementation → Review Gate

Solution Gate owns evidence, contamination control, adversarial probes, failure-shape scoring, and the verdict. Shaping owns requirements, solution options, parts, fit checks, flagged unknowns, and post-verdict detailing. Do not maintain a second proposal format or fit check here. Read references/shaping-orchestration.md before running the gate.

0. Decide whether this fires

Run it when shapes differ in state ownership, component boundaries, lifecycle, compatibility, authority, or contract; when fixing a prior review finding; or when an existing candidate must be adopted, amended, absorbed, recreated, or rejected.

Skip wording, snapshots, renames, allowlist entries, and other changes whose mechanism is fully determined. Record the reason. Choose greenfield or candidate-audit mode. For a candidate, also follow references/candidate-audit.md.

Complete when: mode and trigger are named, or the skip has a reason.

1. Freeze the shaping input

Before any shape exists, write an evidence-only packet: