Set an Eighty-Point Gate Before an OSS Model Review

Before an OSS model review, a contribution must meet a gate set at eighty points. The gate freezes reproduction, patch scope, tests, and rollback before any model comment. The scorecard resides in a single directory next to the clone. Five notes carry fixed weights totaling one hundred. A missing note scores zero for that weight.

The repro note holds the failing command and observed result. The patch note contains the candidate change. Tests note lists the failing and passing commands. Scope note holds git diff stat output and an allowlist of paths. Rollback note records the branch name and drop command. Weights are twenty, forty, twenty, ten, and ten. Forty points focus on the diff for scope creep.

Twenty points cover reproduction due to hearsay. The remaining forty points encompass tests, scope, and rollback. To freeze reproduction, create a clean directory, shallow clone, and branch named with the issue ID and "repro." Replace the placeholder clone URL with the target repository. Run the smallest command showing the bug, storing the command, exit code, and key lines.

Commit any needed fixtures on the throwaway branch. The patch should stay within the paths listed in scope.txt. Extra refactors go to a separate pull request. The contributor writes scope.txt from git diff stat, appending an allowlist of paths. The full diff is saved as patch.diff. The test evidence includes failing and passing commands, both using the same script name.

Rollback note explains how to abandon the branch, including the branch name and any added files. The local checker examines presence, weight, and length of the notes, but does not execute project tests. A passing score allows a later request for model feedback.