scoring-and-release-gatelisted

# Scoring and Release Gate Two separate judgments that must never be collapsed: how good the package is, and whether it may be released. ## Iron Law **THE GATE IS BINARY AND CONJUNCTIVE — 18 of 18 or NOT-RELEASABLE. A high score never substitutes for a failed condition.** The score is a quality signal for the people improving the package. The gate is a release decision. A 98 with one unapproved public claim is `not ready`, and the 98 is irrelevant to that fact. ## Scoring Ten weighted dimensions summing to 100. Full tests and 0/3/5/8/10 anchors: `references/scorecard-rubric.md`. | # | Dimension | Weight | |---:|---|---:| | 1 | Evidence grounding and freshness | 18 | | 2 | Coverage and completeness | 12 | | 3 | Technical correctness | 15 | | 4 | Cross-document consistency | 10 | | 5 | Due-diligence decision value | 10 | | 6 | Onboarding and operability | 10 | | 7 | Security, privacy, and disclosure safety | 10 | | 8 | Reliability and verification depth | 5 | | 9 | Public usefulness and claim integrity | 5 | | 10 | Clarity and maintainability | 5 | Two rules: - **Every deduction cites at least one finding ID.** A deduction with no finding is a mood. If the deduction is real, write the finding. - **Every dimension must reach `gate.minDimensionPercent` of its available points** (default 80%). This is a gate condition, not a scoring rule — it exists so a package cannot average well while failing one dimension outright. ## Who scores what Each verification pass scores in