artifact_id: glyf
rubric_version: 2.8.0
formula: baseline
judges:
- openai:gpt-5.6-terra
rows:
- criterion_id: DEL-01
  category: delivery
  checker: program
  verdict: 'yes'
  points_possible: 10
  points_earned: 10.0
  evidence: ''
  agreement: null
  votes: 0
- criterion_id: DEL-02
  category: delivery
  checker: program
  verdict: 'yes'
  points_possible: 0
  points_earned: -4.0
  evidence: 1 console errors
  agreement: null
  votes: 0
- criterion_id: DEL-03
  category: delivery
  checker: program
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: ''
  agreement: null
  votes: 0
- criterion_id: COR-01
  category: correctness
  checker: program
  verdict: na
  points_possible: 0
  points_earned: 0.0
  evidence: the brief has no reference numbers
  agreement: null
  votes: 0
- criterion_id: BRF-01
  category: answers_brief
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: 'Checked each brief question against visible elements: current metrics; backlog trend and
    weekly opened/closed; triage status/age, response rate, and oldest-first queue; area/adapter breakdowns;
    epic-completion table; and requested-issues/assignee views.'
  agreement: 1.0
  votes: 1
- criterion_id: BRF-02
  category: answers_brief
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked the visible page content for charts, tables, and metrics outside the requested issue-health
    questions.
  agreement: 1.0
  votes: 1
- criterion_id: WRK-01
  category: working
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked the full page for a crash, error state, widespread empty panels, failed-load messages,
    and spinners.
  agreement: 1.0
  votes: 1
- criterion_id: WRK-02
  category: working
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked each visible KPI card, chart, and table panel for blank, loading, error, or placeholder
    states.
  agreement: 1.0
  votes: 1
- criterion_id: HON-01
  category: honesty
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked value-axis baselines on the visible area and bar charts, including Open issues over
    time, Opened vs closed per week, triage status and age, area, adapter, and assignee charts.
  agreement: 1.0
  votes: 1
- criterion_id: HON-02
  category: honesty
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Compared rate/percentage wording with the displayed measures, including “Answered within 48h
    (28d, %)” and “New issues answered within 48 hours.”
  agreement: 1.0
  votes: 1
- criterion_id: HON-03
  category: honesty
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Compared issue-category colors across charts that reuse bug, feature, other, and task categories.
  agreement: 1.0
  votes: 1
- criterion_id: HON-04
  category: honesty
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked the visible charts for separate dual value axes and unclear series-to-axis mappings.
  agreement: 1.0
  votes: 1
- criterion_id: HON-05
  category: honesty
  checker: judge
  verdict: na
  points_possible: 0
  points_earned: 0.0
  evidence: Checked for side-by-side or small-multiple peer charts showing the same measure on differing
    unlabeled scales.
  agreement: 1.0
  votes: 1
- criterion_id: HON-06
  category: honesty
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked line charts for connections across unordered categories; the visible line chart uses
    weekly dates on the x-axis.
  agreement: 1.0
  votes: 1
- criterion_id: FRM-01
  category: form
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: All visible charts and their forms, including time-series, category comparisons, and tables.
  agreement: 1.0
  votes: 1
- criterion_id: FRM-02
  category: form
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Whether two or more charts use a form that hides their principal comparison.
  agreement: 1.0
  votes: 1
- criterion_id: FRM-03
  category: form
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: 'Multi-series/category charts: issue-category stacks in the area and bar charts; opened/closed
    series; triage age buckets.'
  agreement: 1.0
  votes: 1
- criterion_id: FRM-04
  category: form
  checker: judge
  verdict: 'yes'
  points_possible: 0
  points_earned: -3.0
  evidence: “Open issues by area” — areas are displayed in an apparent alphabetical/arbitrary order rather
    than by issue count | “Open issues by adapter” — adapters are displayed alphabetically rather than
    by issue count | “Open issues by assignee” — top assignees are not displayed in descending issue-count
    order
  agreement: 1.0
  votes: 1
- criterion_id: FRM-05
  category: form
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Whether any standalone metric is rendered as a gauge or one-bar chart.
  agreement: 1.0
  votes: 1
- criterion_id: FRM-07
  category: form
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Whether any two charts present the same data in the same chart form.
  agreement: 1.0
  votes: 1
- criterion_id: FRM-08
  category: form
  checker: judge
  verdict: 'yes'
  points_possible: 0
  points_earned: -8.0
  evidence: “Opened vs closed per week” — the approximately 450-opened outlier week forces the normal
    weekly opened/closed bars into a very compressed range, making their differences difficult to read
  agreement: 1.0
  votes: 1
- criterion_id: FRM-06
  category: form
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: First and last points of the visible time series, along with the displayed refresh/as-of date
    and any partial-period notes.
  agreement: 1.0
  votes: 1
- criterion_id: LEG-01
  category: legibility
  checker: judge
  verdict: 'yes'
  points_possible: 0
  points_earned: -6.0
  evidence: Overlapping weekly date tick labels in “Open issues over time” | Overlapping weekly date tick
    labels in “Opened vs closed per week” | Overlapping weekly date tick labels in “New issues answered
    within 48 hours”
  agreement: 1.0
  votes: 1
- criterion_id: LEG-02
  category: legibility
  checker: judge
  verdict: 'yes'
  points_possible: 0
  points_earned: -8.0
  evidence: “Open issues over time” | “Opened vs closed per week” | “New issues answered within 48 hours”
  agreement: 1.0
  votes: 1
- criterion_id: LEG-03
  category: legibility
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked titles, labels, legends, and visible table columns within their individual cards for
    clipping, ellipses, or overflow.
  agreement: 1.0
  votes: 1
- criterion_id: LEG-04
  category: legibility
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked the full-resolution tiles, rather than the scaled overview, for unreadably small or
    faint text.
  agreement: 1.0
  votes: 1
- criterion_id: LEG-05
  category: legibility
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked whether plotted bars, lines, stacked segments, or table cells are too compressed to
    distinguish at their rendered size.
  agreement: 1.0
  votes: 1
- criterion_id: LBL-01
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked all KPI tiles, chart axes, chart titles/subtitles, and table columns. Counts are labeled
    as issues; 11.0 is labeled “%”; and 14.2 is labeled “Median days to close (28d).”
  agreement: 1.0
  votes: 1
- criterion_id: LBL-02
  category: labeling
  checker: judge
  verdict: 'yes'
  points_possible: 0
  points_earned: -4.0
  evidence: “week → open_issues” | “issue_category” | “status_label → issue_count” | “age_bucket” | “week
    → pct_responded_48h” | “issue_number, issue, issue_category, age_days, days_idle, reactions, comments,
    is_customer_reported” | “area → issue_count” | “adapter → issue_count” | “epic_number, epic, child_closed,
    child_total, pct_complete, milestone_title” | “assignee_login → issue_count”
  agreement: 1.0
  votes: 1
- criterion_id: LBL-03
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked the page header and subtitle for scope and time coverage.
  agreement: 1.0
  votes: 1
- criterion_id: LBL-04
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked each headline tile for a period or page-level date. The page states “Refreshed 14
    Oct 2026, 20:02 UTC,” and period-specific metrics are marked “(28d).”
  agreement: 1.0
  votes: 1
- criterion_id: LBL-05
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked all visible KPI cards, charts, and tables for descriptive titles or labels.
  agreement: 1.0
  votes: 1
- criterion_id: LBL-07
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked the visible percentage metric. The 48-hour measure is labeled “Answered within 48h
    (28d, %),” and its chart clarifies “By week opened; unanswered issues count as misses.”
  agreement: 1.0
  votes: 1
- criterion_id: LBL-08
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked chart titles, axes, legends, and displayed values for mismatched measures or contradictory
    labels.
  agreement: 1.0
  votes: 1
- criterion_id: LBL-09
  category: labeling
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Compared the headline metrics with their related charts/tables and checked visible dates and
    notes for conflicts. The latest open-issues area chart is consistent with the 511 open-issues headline,
    and the page shows one refresh timestamp.
  agreement: 1.0
  votes: 1
- criterion_id: LAY-01
  category: layout
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked spacing between dashboard cards and sections across the full page.
  agreement: 1.0
  votes: 1
- criterion_id: LAY-02
  category: layout
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked card rows, chart containers, KPI cards, and tables for visibly mismatched edges or
    gaps.
  agreement: 1.0
  votes: 1
- criterion_id: LAY-04
  category: layout
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked whether tables, filters, or secondary detail appear before or outweigh the dashboard’s
    summary KPIs and primary charts.
  agreement: 1.0
  votes: 1
- criterion_id: LAY-05
  category: layout
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked borders, card treatments, chart styling, icons, and other decoration against the visual
    prominence of the data.
  agreement: 1.0
  votes: 1
- criterion_id: LAY-06
  category: layout
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked chart color usage and legends for unencoded, inconsistent, or misleading color assignments.
  agreement: 1.0
  votes: 1
- criterion_id: LAY-07
  category: layout
  checker: judge
  verdict: 'no'
  points_possible: 0
  points_earned: 0.0
  evidence: Checked visible dashboard content for placeholder, debug, test, or starter-material remnants.
  agreement: 1.0
  votes: 1
- criterion_id: EXC-01
  category: excellence
  checker: judge
  verdict: 'no'
  points_possible: 10
  points_earned: 0.0
  evidence: Looked for a declarative finding in the page title, section headings, and chart annotations,
    then checked whether a chart substantiated it.
  agreement: 1.0
  votes: 1
- criterion_id: EXC-03
  category: excellence
  checker: judge
  verdict: 'yes'
  points_possible: 3
  points_earned: 3.0
  evidence: 'Open issues: “511” with “▲ +52 (+11.3%) vs previous 459”'
  agreement: 1.0
  votes: 1
- criterion_id: EXC-04
  category: excellence
  checker: judge
  verdict: 'no'
  points_possible: 6
  points_earned: 0.0
  evidence: Checked charts for an annotation at a spike/dip, target/reference line, or a specifically
    highlighted data mark.
  agreement: 1.0
  votes: 1
- criterion_id: EXC-06
  category: excellence
  checker: judge
  verdict: 'no'
  points_possible: 5
  points_earned: 0.0
  evidence: Checked whether neutral gray is used for most data with a single accent reserved for the focal
    subject.
  agreement: 1.0
  votes: 1
- criterion_id: EXC-07
  category: excellence
  checker: judge
  verdict: 'no'
  points_possible: 4
  points_earned: 0.0
  evidence: Checked multi-series charts for direct series labels at line ends or on marks rather than
    reliance on legends.
  agreement: 1.0
  votes: 1
- criterion_id: EXC-08
  category: excellence
  checker: judge
  verdict: 'yes'
  points_possible: 5
  points_earned: 5.0
  evidence: “Open at the end of each week, by type” — Open issues over time | “Complete weeks; when closed
    > opened the backlog shrank” — Opened vs closed per week | “By week opened; unanswered issues count
    as misses” — New issues answered within 48 hours | “Issues with several areas count in each” — Open
    issues by area | “(none) = adapter-agnostic” — Open issues by adapter | “Top 15, excluding unassigned”
    — Open issues by assignee
  agreement: 1.0
  votes: 1
score: 0.367
category_scores:
  delivery: 0.6
  excellence: 0.242
agreement: 1.0
judge_errors: []
votes:
- criterion_id: BRF-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: 'Checked each brief question against visible elements: current metrics; backlog trend and
    weekly opened/closed; triage status/age, response rate, and oldest-first queue; area/adapter breakdowns;
    epic-completion table; and requested-issues/assignee views.'
  round: 1
- criterion_id: BRF-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked the visible page content for charts, tables, and metrics outside the requested issue-health
    questions.
  round: 1
- criterion_id: WRK-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked the full page for a crash, error state, widespread empty panels, failed-load messages,
    and spinners.
  round: 1
- criterion_id: WRK-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked each visible KPI card, chart, and table panel for blank, loading, error, or placeholder
    states.
  round: 1
- criterion_id: HON-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked value-axis baselines on the visible area and bar charts, including Open issues over
    time, Opened vs closed per week, triage status and age, area, adapter, and assignee charts.
  round: 1
- criterion_id: HON-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Compared rate/percentage wording with the displayed measures, including “Answered within 48h
    (28d, %)” and “New issues answered within 48 hours.”
  round: 1
- criterion_id: HON-03
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Compared issue-category colors across charts that reuse bug, feature, other, and task categories.
  round: 1
- criterion_id: HON-04
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked the visible charts for separate dual value axes and unclear series-to-axis mappings.
  round: 1
- criterion_id: HON-05
  judge: gpt-5.6-terra
  sample: 0
  verdict: na
  evidence: Checked for side-by-side or small-multiple peer charts showing the same measure on differing
    unlabeled scales.
  round: 1
- criterion_id: HON-06
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked line charts for connections across unordered categories; the visible line chart uses
    weekly dates on the x-axis.
  round: 1
- criterion_id: FRM-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: All visible charts and their forms, including time-series, category comparisons, and tables.
  round: 1
- criterion_id: FRM-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Whether two or more charts use a form that hides their principal comparison.
  round: 1
- criterion_id: FRM-03
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: 'Multi-series/category charts: issue-category stacks in the area and bar charts; opened/closed
    series; triage age buckets.'
  round: 1
- criterion_id: FRM-04
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: “Open issues by area” — areas are displayed in an apparent alphabetical/arbitrary order rather
    than by issue count | “Open issues by adapter” — adapters are displayed alphabetically rather than
    by issue count | “Open issues by assignee” — top assignees are not displayed in descending issue-count
    order
  round: 1
- criterion_id: FRM-05
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Whether any standalone metric is rendered as a gauge or one-bar chart.
  round: 1
- criterion_id: FRM-07
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Whether any two charts present the same data in the same chart form.
  round: 1
- criterion_id: FRM-08
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: “Opened vs closed per week” — the approximately 450-opened outlier week forces the normal
    weekly opened/closed bars into a very compressed range, making their differences difficult to read
  round: 1
- criterion_id: FRM-06
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: First and last points of the visible time series, along with the displayed refresh/as-of date
    and any partial-period notes.
  round: 1
- criterion_id: LEG-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: Overlapping weekly date tick labels in “Open issues over time” | Overlapping weekly date tick
    labels in “Opened vs closed per week” | Overlapping weekly date tick labels in “New issues answered
    within 48 hours”
  round: 1
- criterion_id: LEG-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: “Open issues over time” | “Opened vs closed per week” | “New issues answered within 48 hours”
  round: 1
- criterion_id: LEG-03
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked titles, labels, legends, and visible table columns within their individual cards for
    clipping, ellipses, or overflow.
  round: 1
- criterion_id: LEG-04
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked the full-resolution tiles, rather than the scaled overview, for unreadably small or
    faint text.
  round: 1
- criterion_id: LEG-05
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked whether plotted bars, lines, stacked segments, or table cells are too compressed to
    distinguish at their rendered size.
  round: 1
- criterion_id: LBL-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked all KPI tiles, chart axes, chart titles/subtitles, and table columns. Counts are labeled
    as issues; 11.0 is labeled “%”; and 14.2 is labeled “Median days to close (28d).”
  round: 1
- criterion_id: LBL-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: “week → open_issues” | “issue_category” | “status_label → issue_count” | “age_bucket” | “week
    → pct_responded_48h” | “issue_number, issue, issue_category, age_days, days_idle, reactions, comments,
    is_customer_reported” | “area → issue_count” | “adapter → issue_count” | “epic_number, epic, child_closed,
    child_total, pct_complete, milestone_title” | “assignee_login → issue_count”
  round: 1
- criterion_id: LBL-03
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked the page header and subtitle for scope and time coverage.
  round: 1
- criterion_id: LBL-04
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked each headline tile for a period or page-level date. The page states “Refreshed 14
    Oct 2026, 20:02 UTC,” and period-specific metrics are marked “(28d).”
  round: 1
- criterion_id: LBL-05
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked all visible KPI cards, charts, and tables for descriptive titles or labels.
  round: 1
- criterion_id: LBL-07
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked the visible percentage metric. The 48-hour measure is labeled “Answered within 48h
    (28d, %),” and its chart clarifies “By week opened; unanswered issues count as misses.”
  round: 1
- criterion_id: LBL-08
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked chart titles, axes, legends, and displayed values for mismatched measures or contradictory
    labels.
  round: 1
- criterion_id: LBL-09
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Compared the headline metrics with their related charts/tables and checked visible dates and
    notes for conflicts. The latest open-issues area chart is consistent with the 511 open-issues headline,
    and the page shows one refresh timestamp.
  round: 1
- criterion_id: LAY-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked spacing between dashboard cards and sections across the full page.
  round: 1
- criterion_id: LAY-02
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked card rows, chart containers, KPI cards, and tables for visibly mismatched edges or
    gaps.
  round: 1
- criterion_id: LAY-04
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked whether tables, filters, or secondary detail appear before or outweigh the dashboard’s
    summary KPIs and primary charts.
  round: 1
- criterion_id: LAY-05
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked borders, card treatments, chart styling, icons, and other decoration against the visual
    prominence of the data.
  round: 1
- criterion_id: LAY-06
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked chart color usage and legends for unencoded, inconsistent, or misleading color assignments.
  round: 1
- criterion_id: LAY-07
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked visible dashboard content for placeholder, debug, test, or starter-material remnants.
  round: 1
- criterion_id: EXC-01
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Looked for a declarative finding in the page title, section headings, and chart annotations,
    then checked whether a chart substantiated it.
  round: 1
- criterion_id: EXC-03
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: 'Open issues: “511” with “▲ +52 (+11.3%) vs previous 459”'
  round: 1
- criterion_id: EXC-04
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked charts for an annotation at a spike/dip, target/reference line, or a specifically
    highlighted data mark.
  round: 1
- criterion_id: EXC-06
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked whether neutral gray is used for most data with a single accent reserved for the focal
    subject.
  round: 1
- criterion_id: EXC-07
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'no'
  evidence: Checked multi-series charts for direct series labels at line ends or on marks rather than
    reliance on legends.
  round: 1
- criterion_id: EXC-08
  judge: gpt-5.6-terra
  sample: 0
  verdict: 'yes'
  evidence: “Open at the end of each week, by type” — Open issues over time | “Complete weeks; when closed
    > opened the backlog shrank” — Opened vs closed per week | “By week opened; unanswered issues count
    as misses” — New issues answered within 48 hours | “Issues with several areas count in each” — Open
    issues by area | “(none) = adapter-agnostic” — Open issues by adapter | “Top 15, excluding unassigned”
    — Open issues by assignee
  round: 1