You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decision point (from PR #151 review, docs/semantic-rules.md)
Currently severity is separate from verdicts:
"verdicts": { "vague": "A need, but too vague to act on", "solution": "..." },
"severity": { "vague": "info", "solution": "warning" }
Alternative shape — severity inline per verdict:
"verdicts": {
"vague": {
"description": "A need, but too vague to act on",
"guidance": "Say who has the need and what they are trying to do.",
"severity": "info"
}
}
Tradeoffs
Merged: one place to read a verdict's meaning; severity defaulting to ignore (omitted) feels natural in this shape.
Separate (current): the default pass/fail case stays a one-liner ("severity": "warning"); the merged shape would force a full verdicts map just to set a severity.
Decided already (do not relitigate)
Default ignore when severity is left out for a verdict.
Keep severity separate for the default case; the merged form stays available via custom verdicts.
Related
Should be settled together with the check-as-precondition question (see the fail-fast precondition issue): both reshape the semantic rule contract.
Activity