id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 166 234 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_487ecbb24843a821_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | A status report exceeds the 200-word brief target; additionally omits the customer-facing impact. Context: for the board packet, while legacy systems are still active. Reported by the operator. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_941f17141aeb7e1d_n | noul | [
"false",
"true"
] | [
0.83,
0.17
] | A status report exceeds the 200-word brief target; additionally summarizes a resolved SEV2. Context: in the public status page, during a scheduled maintenance window. Reported by the automated check. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_8e2b4901d04a0dbe_n | noul | [
"false",
"true"
] | [
0.65,
0.35
] | An executive summary goes to the full distribution list; additionally uses plain language for a technical audience. Context: in the public status page, during the quarterly review. Reported by the on-call engineer. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_997aeb3bd80b9539_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.33,
0.66,
0,
0.01
] | An executive summary contains unreleased financial figures; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, during a scheduled maintenance window. Reported by the monitoring system. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_8c5f8c45225fbec7_n | noul | [
"false",
"true"
] | [
0.77,
0.23
] | The changelog entry buried the deadline in paragraph six; additionally contains unreleased financial figures. Context: at hour 2 of the incident, following a recent audit. Reported by the automated check. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_66a979d00857843d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.09,
0.23,
0.57,
0.1,
0
] | A status report omits the customer-facing impact; additionally needs translation for 3 locales. Context: in the internal postmortem, during the holiday freeze. Reported by the automated check. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_a8652b401981ca81_n | noul | [
"false",
"true"
] | [
0.19,
0.81
] | The incident update omits the customer-facing impact; additionally names an individual in a security failure. Context: at hour 2 of the incident, at the end of the fiscal period. Reported by the supervisor. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_f068056cca45f061_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.36,
0.27,
0,
0.37
] | The changelog entry goes to the full distribution list; additionally uses plain language for a technical audience. Context: for the board packet, while on-call rotation changed. Reported by the on-call engineer. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_4b6526418ebc343b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.07,
0.11,
0.23,
0.52,
0.06,
0.01
] | The incident update buried the deadline in paragraph six; additionally exceeds the 200-word brief target. Context: in the internal postmortem, while legacy systems are still active. Reported by the review queue. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_8da6f1a89115242e_n | noul | [
"false",
"true"
] | [
0.73,
0.27
] | The incident update exceeds the 200-word brief target; additionally needs translation for 3 locales. Context: in the public status page, following a recent audit. Reported by the automated check. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_bfd129cf5ff1d780_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.06,
0.26,
0.44,
0.2,
0.02
] | An executive summary uses plain language for a technical audience; additionally buried the deadline in paragraph six. Context: at hour 2 of the incident, during the quarterly review. Reported by the automated check. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_db7c85efada16d10_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.06,
0.06,
0.65,
0.23
] | The incident update needs translation for 3 locales; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, under reduced staffing. Reported by the monitoring system. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_4a96c2a6a95d7d53_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.22,
0.33,
0.43,
0.01,
0
] | The changelog entry exceeds the 200-word brief target; additionally buried the deadline in paragraph six. Context: in the public status page, with a new vendor onboarded. Reported by the on-call engineer. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_4b4d2202f6796046_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.38,
0.54,
0.02
] | A status report buried the deadline in paragraph six; additionally contains unreleased financial figures. Context: in the public status page, while on-call rotation changed. Reported by the operator. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_f2ff5d248befaf1d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.18,
0.75,
0.06
] | The changelog entry names an individual in a security failure; additionally contains unreleased financial figures. Context: for the board packet, during the holiday freeze. Reported by the supervisor. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_ffaad0a1d8661ca2_n | noul | [
"false",
"true"
] | [
0.88,
0.12
] | An executive summary buried the deadline in paragraph six; additionally includes the required compliance disclaimer. Context: for the board packet, during the system migration. Reported by the operator. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_8cf35e5b5409cdb1_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.13,
0.81,
0.05
] | An executive summary uses plain language for a technical audience; additionally includes the required compliance disclaimer. Context: at hour 2 of the incident, while on-call rotation changed. Reported by the operator. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_86e829b9463b7abe_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.02,
0,
0.54,
0.44
] | The incident update goes to the full distribution list; additionally exceeds the 200-word brief target. Context: in the public status page, mid-incident. Reported by the review queue. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_ae951b15be6ecad0_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.07,
0.11,
0.36,
0.36,
0.09,
0.01
] | The incident update includes the required compliance disclaimer; additionally uses plain language for a technical audience. Context: at hour 2 of the incident, during an external partner integration. Reported by the supervisor. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_506b1bcb88987cc9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.02,
0.13,
0.45,
0.36,
0.03
] | The changelog entry summarizes a resolved SEV2; additionally names an individual in a security failure. Context: in the public status page, during the system migration. Reported by the operator. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_2eaa815657ccfd0c_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.01,
0.97,
0.02,
0
] | The changelog entry omits the customer-facing impact; additionally exceeds the 200-word brief target. Context: for the board packet, during the holiday freeze. Reported by the supervisor. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_cccfc8701b8a386a_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.11,
0.14,
0.55,
0.2
] | A status report contains unreleased financial figures; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, during peak load. Reported by the operator. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_c40064a71ae4995f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.21,
0.44,
0.15,
0.15,
0.03,
0.02
] | The incident update goes to the full distribution list; additionally uses plain language for a technical audience. Context: in the internal postmortem, during a scheduled maintenance window. Reported by the automated check. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_8349a962eb275559_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.01,
0.04,
0.27,
0.6,
0.07
] | An executive summary contains unreleased financial figures; additionally needs translation for 3 locales. Context: at hour 2 of the incident, at the end of the fiscal period. Reported by the review queue. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_af162e88d310dda6_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.18,
0.43,
0.35,
0.02,
0
] | A status report uses plain language for a technical audience; additionally buried the deadline in paragraph six. Context: in the internal postmortem, shortly after a software update. Reported by the operator. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_844a7dda63d47e78_n | noul | [
"false",
"true"
] | [
0.89,
0.11
] | The changelog entry summarizes a resolved SEV2; additionally contains unreleased financial figures. Context: at hour 2 of the incident, while on-call rotation changed. Reported by the automated check. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_b7ac646f8a2dd428_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.04,
0.1,
0.54,
0.32
] | The incident update goes to the full distribution list; additionally exceeds the 200-word brief target. Context: in the public status page, during peak load. Reported by the automated check. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_f80f3f57bf946942_n | noul | [
"false",
"true"
] | [
0.3,
0.7
] | The changelog entry uses plain language for a technical audience; additionally buried the deadline in paragraph six. Context: for the board packet, during a scheduled maintenance window. Reported by the supervisor. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_32c99795a61a5983_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.4,
0,
0,
0.6
] | The incident update goes to the full distribution list; additionally uses plain language for a technical audience. Context: in the internal postmortem, while on-call rotation changed. Reported by the supervisor. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_f67cf1db5093fbbd_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.01,
0.05,
0.21,
0.62,
0.1
] | A status report names an individual in a security failure; additionally buried the deadline in paragraph six. Context: at hour 2 of the incident, under an active deadline. Reported by the monitoring system. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_2f54345dde2bf748_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.01,
0.99,
0,
0
] | The incident update buried the deadline in paragraph six; additionally exceeds the 200-word brief target. Context: for the board packet, shortly after a software update. Reported by the automated check. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_1183838d2350b40e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.07,
0.19,
0.57,
0.16,
0
] | The incident update exceeds the 200-word brief target; additionally needs translation for 3 locales. Context: at hour 2 of the incident, with a new vendor onboarded. Reported by the on-call engineer. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_aff2b3583a80717f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.03,
0.13,
0.51,
0.31,
0.01
] | The changelog entry names an individual in a security failure; additionally needs translation for 3 locales. Context: for the board packet, as part of a compliance sweep. Reported by the supervisor. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_3472006ec72acd06_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | The changelog entry summarizes a resolved SEV2; additionally goes to the full distribution list. Context: in the internal postmortem, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_e58ade7c7c9943b1_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.6,
0.34,
0.05
] | The changelog entry needs translation for 3 locales; additionally uses plain language for a technical audience. Context: for the board packet, during peak load. Reported by the operator. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_6f2e0429caa2d3c4_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.5,
0.23,
0,
0.27
] | An executive summary uses plain language for a technical audience; additionally goes to the full distribution list. Context: at hour 2 of the incident, mid-incident. Reported by the on-call engineer. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_ff5b7cfa2524375a_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.08,
0.48,
0.33,
0.11
] | The changelog entry contains unreleased financial figures; additionally includes the required compliance disclaimer. Context: in the internal postmortem, shortly after a software update. Reported by the on-call engineer. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_d284ed25723bca04_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.04,
0.21,
0.41,
0.31,
0.02
] | A status report uses plain language for a technical audience; additionally names an individual in a security failure. Context: in the internal postmortem, while on-call rotation changed. Reported by the monitoring system. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_75997cd1501b008e_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.07,
0.14,
0.54,
0.25
] | A status report names an individual in a security failure; additionally needs translation for 3 locales. Context: in the public status page, during a scheduled maintenance window. Reported by the review queue. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_941804de5a802a25_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | A status report uses plain language for a technical audience; additionally contains unreleased financial figures. Context: in the public status page, following a recent audit. Reported by the operator. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_d4369fc7703521a2_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.02,
0.74,
0.2,
0.04
] | The changelog entry uses plain language for a technical audience; additionally names an individual in a security failure. Context: for the board packet, at the end of the fiscal period. Reported by the monitoring system. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_33a83eb46f5d086d_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | The incident update names an individual in a security failure; additionally summarizes a resolved SEV2. Context: in the public status page, immediately after go-live. Reported by the monitoring system. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_0ae0065c9b2e364d_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.06,
0.06,
0.67,
0.21
] | The incident update exceeds the 200-word brief target; additionally contains unreleased financial figures. Context: in the public status page, during the system migration. Reported by the on-call engineer. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_3758d93d914697f6_n | noul | [
"false",
"true"
] | [
0.41,
0.59
] | The changelog entry contains unreleased financial figures; additionally includes the required compliance disclaimer. Context: at hour 2 of the incident, under reduced staffing. Reported by the review queue. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_1b0d845472c2f53d_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | An executive summary contains unreleased financial figures; additionally includes the required compliance disclaimer. Context: in the public status page, at the end of the fiscal period. Reported by the supervisor. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_c1614da480a09756_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.07,
0.19,
0.5,
0.22,
0.01
] | The changelog entry contains unreleased financial figures; additionally summarizes a resolved SEV2. Context: for the board packet, during the holiday freeze. Reported by the operator. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_087c9678ba746986_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.07,
0.27,
0.26,
0.3,
0.09,
0.01
] | The changelog entry needs translation for 3 locales; additionally goes to the full distribution list. Context: in the public status page, during normal operations. Reported by the automated check. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_36a2a8b552b149c8_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0,
0.77,
0,
0.23
] | A status report needs translation for 3 locales; additionally goes to the full distribution list. Context: for the board packet, during the quarterly review. Reported by the operator. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_c7f29d3565da230d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.09,
0.3,
0.37,
0.2,
0.02
] | An executive summary names an individual in a security failure; additionally includes the required compliance disclaimer. Context: for the board packet, at the end of the fiscal period. Reported by the operator. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_a1848333054ffd0a_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.03,
0.93,
0.03,
0.01
] | The changelog entry includes the required compliance disclaimer; additionally buried the deadline in paragraph six. Context: for the board packet, during a scheduled maintenance window. Reported by the review queue. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_9cae67617fb66129_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.08,
0.33,
0.44,
0.12,
0.01
] | An executive summary buried the deadline in paragraph six; additionally includes the required compliance disclaimer. Context: for the board packet, during an external partner integration. Reported by the on-call engineer. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_4e35f8bc2fce5e87_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The changelog entry buried the deadline in paragraph six; additionally includes the required compliance disclaimer. Context: in the internal postmortem, during the morning shift. Reported by the automated check. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_fada5599cba07f39_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.73,
0.25,
0.01
] | The incident update uses plain language for a technical audience; additionally needs translation for 3 locales. Context: for the board packet, during the system migration. Reported by the automated check. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_7b807dce2c1b5baf_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.02,
0.56,
0.4,
0.02
] | A status report names an individual in a security failure; additionally uses plain language for a technical audience. Context: for the board packet, immediately after go-live. Reported by the automated check. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_c42aaf413326e51a_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.13,
0.17,
0.54,
0.16
] | The changelog entry contains unreleased financial figures; additionally needs translation for 3 locales. Context: in the internal postmortem, under an active deadline. Reported by the supervisor. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_30294886fe7f2d2c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.03,
0.12,
0.29,
0.43,
0.12,
0.01
] | An executive summary includes the required compliance disclaimer; additionally buried the deadline in paragraph six. Context: for the board packet, following a recent audit. Reported by the operator. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_c06fc386bc54bd07_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.05,
0.18,
0.63,
0.14
] | A status report needs translation for 3 locales; additionally names an individual in a security failure. Context: in the public status page, during the quarterly review. Reported by the operator. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_16382ac6f9cce65a_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.02,
0.98,
0,
0
] | An executive summary omits the customer-facing impact; additionally needs translation for 3 locales. Context: for the board packet, while on-call rotation changed. Reported by the automated check. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_cfb2f02473126b5f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.03,
0.16,
0.2,
0.37,
0.21,
0.03
] | An executive summary goes to the full distribution list; additionally needs translation for 3 locales. Context: in the public status page, during the system migration. Reported by the automated check. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_7e5c943b58aab915_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.06,
0.21,
0.4,
0.3,
0.02
] | The incident update names an individual in a security failure; additionally uses plain language for a technical audience. Context: in the public status page, while on-call rotation changed. Reported by the supervisor. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_581c521e87817064_n | noul | [
"false",
"true"
] | [
0.24,
0.76
] | A status report names an individual in a security failure; additionally omits the customer-facing impact. Context: in the public status page, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_4da7215dc223e667_n | noul | [
"false",
"true"
] | [
0.45,
0.55
] | The incident update buried the deadline in paragraph six; additionally includes the required compliance disclaimer. Context: at hour 2 of the incident, with a new vendor onboarded. Reported by the monitoring system. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_14eee273b96d2da0_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.06,
0.14,
0.8,
0
] | The changelog entry contains unreleased financial figures; additionally omits the customer-facing impact. Context: in the public status page, during the quarterly review. Reported by the monitoring system. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_a3b26519758e0d55_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A status report uses plain language for a technical audience; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, while legacy systems are still active. Reported by the supervisor. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_6bd6a8e86d1491fa_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.55,
0.41,
0.03
] | An executive summary buried the deadline in paragraph six; additionally uses plain language for a technical audience. Context: in the internal postmortem, while legacy systems are still active. Reported by the automated check. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_6b53b10310e6e0e9_n | noul | [
"false",
"true"
] | [
0.61,
0.39
] | A status report buried the deadline in paragraph six; additionally uses plain language for a technical audience. Context: in the internal postmortem, following a recent audit. Reported by the supervisor. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_f1c9e65f750512f7_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.79,
0.18,
0.02
] | The incident update uses plain language for a technical audience; additionally exceeds the 200-word brief target. Context: in the public status page, shortly after a software update. Reported by the operator. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_d0d7b116ad2f8ec5_n | noul | [
"false",
"true"
] | [
0.92,
0.08
] | The changelog entry buried the deadline in paragraph six; additionally names an individual in a security failure. Context: in the public status page, during the system migration. Reported by the supervisor. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_bd356b7f851d9ed1_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.03,
0.97,
0,
0
] | The incident update summarizes a resolved SEV2; additionally names an individual in a security failure. Context: for the board packet, during the morning shift. Reported by the automated check. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_e040fe21f20b67f9_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.06,
0.11,
0.64,
0.19
] | An executive summary omits the customer-facing impact; additionally buried the deadline in paragraph six. Context: in the public status page, while legacy systems are still active. Reported by the review queue. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_14ca7062ef362b54_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.02,
0.09,
0.49,
0.38,
0.01
] | The incident update goes to the full distribution list; additionally omits the customer-facing impact. Context: at hour 2 of the incident, shortly after a software update. Reported by the monitoring system. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_2a91dff4416d26cc_n | noul | [
"false",
"true"
] | [
0.25,
0.75
] | The changelog entry exceeds the 200-word brief target; additionally contains unreleased financial figures. Context: for the board packet, during an external partner integration. Reported by the review queue. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_7e0043e51add5543_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | An executive summary omits the customer-facing impact; additionally buried the deadline in paragraph six. Context: in the internal postmortem, during normal operations. Reported by the automated check. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_b7265b2a26f4ba77_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.02,
0.11,
0.16,
0.33,
0.33,
0.05
] | An executive summary omits the customer-facing impact; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, immediately after go-live. Reported by the operator. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_b160dcd9772a673b_n | noul | [
"false",
"true"
] | [
0.38,
0.62
] | The incident update summarizes a resolved SEV2; additionally names an individual in a security failure. Context: at hour 2 of the incident, during a scheduled maintenance window. Reported by the review queue. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_da5450831769a939_n | noul | [
"false",
"true"
] | [
0.79,
0.21
] | A status report buried the deadline in paragraph six; additionally omits the customer-facing impact. Context: in the internal postmortem, during the holiday freeze. Reported by the operator. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_cd724e6c284d2fea_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0.39,
0.57,
0.01,
0.03
] | The incident update contains unreleased financial figures; additionally buried the deadline in paragraph six. Context: at hour 2 of the incident, during the holiday freeze. Reported by the monitoring system. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_16f5e23e508e53ab_n | noul | [
"false",
"true"
] | [
0.9,
0.1
] | The changelog entry contains unreleased financial figures; additionally includes the required compliance disclaimer. Context: at hour 2 of the incident, during the quarterly review. Reported by the operator. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_aff2b3583a80717f_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | The changelog entry names an individual in a security failure; additionally needs translation for 3 locales. Context: for the board packet, as part of a compliance sweep. Reported by the supervisor. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
v3_333506f414f8772b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.12,
0.25,
0.21,
0.37,
0.04,
0.01
] | The incident update includes the required compliance disclaimer; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, under reduced staffing. Reported by the monitoring system. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_a7cd81e29fdb2328_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.02,
0.41,
0.53,
0.04
] | A status report includes the required compliance disclaimer; additionally exceeds the 200-word brief target. Context: in the internal postmortem, at the end of the fiscal period. Reported by the monitoring system. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_177d9da8c9ab6be3_n | noul | [
"false",
"true"
] | [
0.25,
0.75
] | An executive summary includes the required compliance disclaimer; additionally summarizes a resolved SEV2. Context: in the public status page, as part of a compliance sweep. Reported by the monitoring system. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_fb3960a84fcaa7e7_n | noul | [
"false",
"true"
] | [
0.1,
0.9
] | The changelog entry names an individual in a security failure; additionally contains unreleased financial figures. Context: for the board packet, immediately after go-live. Reported by the review queue. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_d9a4749e0270102c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.25,
0.3,
0.23,
0.14,
0.07,
0.01
] | An executive summary summarizes a resolved SEV2; additionally uses plain language for a technical audience. Context: in the internal postmortem, shortly after a software update. Reported by the automated check. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_019b27b9a4c6f911_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.1111,
0.202,
0.3333,
0.2828,
0.0707,
0
] | The incident update summarizes a resolved SEV2; additionally goes to the full distribution list. Context: in the internal postmortem, with a new vendor onboarded. Reported by the monitoring system. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_a3434e85fa1cc3bc_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.31,
0.59,
0.04
] | The incident update names an individual in a security failure; additionally needs translation for 3 locales. Context: at hour 2 of the incident, following a recent audit. Reported by the supervisor. | Rate urgency for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_b9ac1b37b31101c0_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | The incident update needs translation for 3 locales; additionally uses plain language for a technical audience. Context: in the internal postmortem, during the system migration. Reported by the review queue. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_04109d55482f7f22_c | choice | [
"engineering",
"executives",
"customers",
"all_staff"
] | [
0,
0.99,
0.01,
0
] | The changelog entry omits the customer-facing impact; additionally exceeds the 200-word brief target. Context: for the board packet, immediately after go-live. Reported by the supervisor. | Audience for this scenario. | communication_routing | agent | yuri_v3 |
v3_91476abbf7b79ff2_n | noul | [
"false",
"true"
] | [
0.37,
0.63
] | The incident update needs translation for 3 locales; additionally goes to the full distribution list. Context: for the board packet, mid-incident. Reported by the automated check. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_ec2fab116d785fa5_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0,
0.72,
0.27,
0.01
] | The incident update uses plain language for a technical audience; additionally includes the required compliance disclaimer. Context: for the board packet, during the quarterly review. Reported by the automated check. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_b9d4e8b59199df87_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.11,
0.15,
0.53,
0.21
] | The changelog entry buried the deadline in paragraph six; additionally goes to the full distribution list. Context: for the board packet, at the end of the fiscal period. Reported by the on-call engineer. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_cf8de4a34fe6af51_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.24,
0.59,
0.16
] | An executive summary omits the customer-facing impact; additionally uses plain language for a technical audience. Context: in the public status page, with staffing at reduced levels. Reported by the supervisor. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_471e8de1b1d37927_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.01,
0.76,
0.19,
0.04
] | The incident update buried the deadline in paragraph six; additionally uses plain language for a technical audience. Context: in the public status page, during the holiday freeze. Reported by the operator. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_1099ecfbfa6b2e0c_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.09,
0.21,
0.54,
0.16
] | A status report buried the deadline in paragraph six; additionally needs translation for 3 locales. Context: in the public status page, during the holiday freeze. Reported by the on-call engineer. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_3e08ee806ee8d0f8_n | noul | [
"false",
"true"
] | [
0.82,
0.18
] | An executive summary contains unreleased financial figures; additionally goes to the full distribution list. Context: in the public status page, immediately after go-live. Reported by the operator. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_5f52ebb2b798ca9b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.05,
0.38,
0.48,
0.07,
0.01
] | The changelog entry uses plain language for a technical audience; additionally contains unreleased financial figures. Context: in the internal postmortem, with a new vendor onboarded. Reported by the automated check. | Rate clarity for this scenario on a 0-5 scale. | communication_routing | agent | yuri_v3 |
v3_5c7e2ba50ef45777_c | choice | [
"raw",
"technical",
"summary",
"minimal"
] | [
0.04,
0.08,
0.52,
0.36
] | The changelog entry exceeds the 200-word brief target; additionally names an individual in a security failure. Context: in the public status page, while on-call rotation changed. Reported by the review queue. | Detail level for this scenario. | communication_routing | agent | yuri_v3 |
v3_f1e8a3d3fd7146b8_n | noul | [
"false",
"true"
] | [
0.82,
0.18
] | A status report uses plain language for a technical audience; additionally exceeds the 200-word brief target. Context: at hour 2 of the incident, while legacy systems are still active. Reported by the monitoring system. | Is this scenario one where: this needs legal review? | communication_routing | agent | yuri_v3 |
v3_08fa8dbcc2a71772_n | noul | [
"false",
"true"
] | [
0.3,
0.7
] | The incident update summarizes a resolved SEV2; additionally uses plain language for a technical audience. Context: for the board packet, during normal operations. Reported by the supervisor. | Is this scenario one where: the tone is appropriate? | communication_routing | agent | yuri_v3 |
v3_c6d90877484ace97_n | noul | [
"false",
"true"
] | [
0.94,
0.06
] | The changelog entry exceeds the 200-word brief target; additionally contains unreleased financial figures. Context: at hour 2 of the incident, while on-call rotation changed. Reported by the monitoring system. | Is this scenario one where: this is safe to publish externally? | communication_routing | agent | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - communication_routing
9,478 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: communication_routing).
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Part of the per-domain split of SargeDev/jev-distill-corpus-v3 - the full corpus in one repo.
Domains:
- Downloads last month
- 34