A.2.6:16.2 - Architect’s design rubric for scopes

• Prefer predicates over prose. Name the parameters, ranges, and standard editions that affect membership; name gammaTime only when time affects membership.
• Factor common conditions. Use Refit to normalize units and factor shared predicates; do not widen by stealth.
• Partition support lines. If you plan a SpanUnion, document independence up front.
• Publish supported scope. Add slices as support appears (ΔG+).
• Design translations early. Test the direct F.9 Bridge first, then state each proposed translation use separately with its direction, mapping rule, tolerated loss, and evidence plan; do not turn an expected loss score into permission to use the mapping.