Datasets:
id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 146 256 | question stringclasses 44
values | domain stringclasses 6
values | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_ff0a156c64e53236_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the supervisor. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_74a4e0ab68d9626c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.62,
0.37
] | The checkout api shows certificate expiry in 40 minutes; additionally p99 latency jumped to 8.4s. Context: during a 3x traffic spike, during the holiday freeze. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_7a5ac4a7dc508289_n | noul | [
"false",
"true"
] | [
0.81,
0.19
] | The nightly feed passed all 47 freshness checks; additionally shows referential breaks against the dim table. Context: under SOX controls, shortly after a software update. Reported by the on-call engineer. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_b5b3f0d4f4d45135_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0,
0,
0.97,
0.03
] | A standing-privilege request was approved by their own direct report; additionally seeks write access outside department scope. Context: with an expired justification, immediately after go-live. Reported by the monitoring system. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_d6c10fc4aa16aa10_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.01,
0.04,
0.36,
0.55,
0.03
] | A hotfix build is scheduled for the Friday freeze window; additionally introduces a new database index on a 2TB table. Context: in the payments repo, at the end of the fiscal period. Reported by the monitoring system. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_49731329fcd719a9_n | noul | [
"false",
"true"
] | [
0.37,
0.63
] | An ids signature detected DNS tunneling entropy patterns; additionally caught a service account writing to a share it never touches. Context: on a build runner, during the system migration. Reported by the supervisor. | Is this scenario one where: credentials are likely compromised? | security_alerts | technical | yuri_v3 |
v3_ce1a0e13123fd534_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.04,
0.83,
0.13
] | The search cluster lost its primary replica; additionally p99 latency jumped to 8.4s. Context: with no recent change, during an external partner integration. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_1afc777bd3ffdb81_c | choice | [
"ship",
"ship_with_monitoring",
"hold",
"rollback"
] | [
0,
0.03,
0.72,
0.25
] | A hotfix build changes 40% of the billing module; additionally shows a 9% regression in the p95 benchmark. Context: after a 3-week stabilization, during an external partner integration. Reported by the review queue. | Go/no-go for this scenario. | software_delivery | technical | yuri_v3 |
v3_64cad838069bfa1b_n | noul | [
"false",
"true"
] | [
0.55,
0.45
] | The fact-sales table shows values outside physical bounds; additionally arrived 3 hours late. Context: in the sandbox only, during the holiday freeze. Reported by the monitoring system. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_1e47c0596dfb9606_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.02,
0.48,
0.28,
0.21,
0.01
] | An api-delivered dataset shows values outside physical bounds; additionally passed all 47 freshness checks. Context: feeding the quarterly report, while on-call rotation changed. Reported by the supervisor. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_cd4340f357be9574_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.65,
0.02,
0.04,
0.29
] | The auth gateway is rejecting 30% of requests; additionally failed its health check in 3 of 5 regions. Context: in us-east-1 only, during the system migration. Reported by the monitoring system. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_9895a1ba66ee4c6e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.72,
0.27
] | The auth gateway shows certificate expiry in 40 minutes; additionally error rate hit 14%. Context: with no recent change, with a new vendor onboarded. Reported by the automated check. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_01f585220f2a7512_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | The payments worker shows OOM kills every 90 seconds; additionally p99 latency jumped to 8.4s. Context: during a 3x traffic spike, under reduced staffing. Reported by the operator. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_519ee9a2da8a94b9_n | noul | [
"false",
"true"
] | [
0.71,
0.29
] | The sdk release changes 40% of the billing module; additionally ships behind a feature flag at 5% traffic. Context: ahead of the audit, during the holiday freeze. Reported by the operator. | Is this scenario one where: the flag default is wrong? | software_delivery | technical | yuri_v3 |
v3_390846ddd72e392d_n | noul | [
"false",
"true"
] | [
0.71,
0.29
] | A standing-privilege request seeks write access outside department scope; additionally requests admin on a database holding PII. Context: after offboarding was missed, with staffing at reduced levels. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_04fab3354bf40b2e_n | noul | [
"false",
"true"
] | [
0.74,
0.26
] | An ids signature fired during the sanctioned pen-test window; additionally fired on 40 failed logins from one ASN. Context: from a contractor laptop, under an active deadline. Reported by the review queue. | Is this scenario one where: credentials are likely compromised? | security_alerts | technical | yuri_v3 |
v3_e0d3c1ee95aedb6c_n | noul | [
"false",
"true"
] | [
0.96,
0.04
] | The customer table has a row count variance of -18%; additionally has 12,000 duplicate keys today. Context: under SOX controls, during the morning shift. Reported by the monitoring system. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_edbdfb05f96c3ce1_n | noul | [
"false",
"true"
] | [
0.33,
0.67
] | A canary deploy has one blocking review comment unresolved; additionally modifies the auth middleware. Context: in the payments repo, during the morning shift. Reported by the review queue. | Is this scenario one where: the change needs a second reviewer? | software_delivery | technical | yuri_v3 |
v3_b57694734e7fd94b_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | An api-delivered dataset shows referential breaks against the dim table; additionally has a row count variance of -18%. Context: upstream of the ML feature store, during the system migration. Reported by the automated check. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_7eca8ce2f39a4ac6_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | A break-glass request needs temporary access during an active SEV1; additionally is a new hire requesting team-lead permissions. Context: with MFA verified, while legacy systems are still active. Reported by the monitoring system. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_b14046f8f0cae6a9_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.1,
0.85,
0.04,
0.01
] | The etl pipeline p99 latency jumped to 8.4s; additionally error rate hit 14%. Context: under normal load, under an active deadline. Reported by the review queue. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_a7d59ab11f5a2a41_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.09,
0.27,
0.44,
0.18,
0.01
] | An api-delivered dataset arrived 3 hours late; additionally passed all 47 freshness checks. Context: under SOX controls, during the holiday freeze. Reported by the automated check. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_43a0b04e96061fdf_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | The fact-sales table exhibits schema drift in 2 columns; additionally has a row count variance of -18%. Context: under SOX controls, with staffing at reduced levels. Reported by the review queue. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_fce3179791601617_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.01,
0.01,
0.63,
0.35
] | The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_18e2129dba1ee58d_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.02,
0.06,
0.65,
0.27
] | Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the automated check. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_e8bfcdd20a7895fb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.11,
0.18,
0.63,
0.07,
0
] | A sensor telemetry stream shows values outside physical bounds; additionally shows referential breaks against the dim table. Context: in the sandbox only, during the quarterly review. Reported by the on-call engineer. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_177e5d3b394c7e06_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.88,
0.1
] | The checkout api returns 503s from one availability zone; additionally p99 latency jumped to 8.4s. Context: with no recent change, with staffing at reduced levels. Reported by the monitoring system. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_2e56f45b3ba05ac5_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.92,
0.03,
0.01,
0.04
] | Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the automated check. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_1709b8306cf82041_c | choice | [
"smoke",
"full_regression",
"targeted_suite",
"extended_soak"
] | [
0.02,
0.63,
0.31,
0.04
] | The sdk release deletes a deprecated API with 3 known consumers; additionally passed the full canary matrix. Context: in the payments repo, while on-call rotation changed. Reported by the operator. | Test depth for this scenario. | software_delivery | technical | yuri_v3 |
v3_3968b451c5473ebb_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.04,
0.28,
0.66,
0.02
] | A break-glass request requests read-only access matching current role; additionally seeks write access outside department scope. Context: during audit season, following a recent audit. Reported by the on-call engineer. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_8c8da0f236d99ddb_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | A service-account grant asks for 90-day standing access to the finance share; additionally follows the documented on-call path. Context: with an expired justification, during the quarterly review. Reported by the automated check. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_d64de024f3b83e3d_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.55,
0.44,
0,
0.01
] | The search cluster shows OOM kills every 90 seconds; additionally p99 latency jumped to 8.4s. Context: following the schema migration, under an active deadline. Reported by the monitoring system. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_c87d9647f1d41827_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.65,
0.34
] | The checkout api error rate hit 14%; additionally lost its primary replica. Context: after the 14:00 deploy, immediately after go-live. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_d28f6594fe986d6c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.31,
0.65,
0.02
] | A service-account grant follows the documented on-call path; additionally seeks write access outside department scope. Context: after offboarding was missed, during an external partner integration. Reported by the on-call engineer. | Rate privilege-escalation risk for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_eac8efc6fb236ef8_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.58,
0.41,
0.01,
0
] | An api-delivered dataset arrived 3 hours late; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, following a recent audit. Reported by the on-call engineer. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_1117b6d34cb277cd_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.01,
0.9,
0.01,
0.08
] | The etl pipeline shows OOM kills every 90 seconds; additionally returns 503s from one availability zone. Context: under normal load, while legacy systems are still active. Reported by the automated check. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_6c21c05422d23d4f_c | choice | [
"external_attacker",
"insider",
"malware",
"misconfiguration"
] | [
0.46,
0.51,
0.02,
0.01
] | A siem correlation rule fired during the sanctioned pen-test window; additionally matched threat-intel IOC set 7. Context: in the finance VLAN, during the holiday freeze. Reported by the on-call engineer. | Actor type for this scenario. | security_alerts | technical | yuri_v3 |
v3_31041d976e2fc465_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.87,
0.12,
0
] | Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the monitoring system. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_2a01fa375425398c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.41,
0.52,
0.01
] | A standing-privilege request matches the least-privilege baseline; additionally is a new hire requesting team-lead permissions. Context: with an expired justification, during the quarterly review. Reported by the monitoring system. | Rate audit exposure for this scenario on a 0-5 scale. | access_permissions | technical | yuri_v3 |
v3_48a45bc49918e8c9_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.87,
0.01,
0.04,
0.08
] | The search cluster p99 latency jumped to 8.4s; additionally returns 503s from one availability zone. Context: following the schema migration, during the system migration. Reported by the on-call engineer. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_86951e48b46712b1_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.07,
0.29,
0.33,
0.27,
0.03
] | The fact-sales table lost its partition for one region; additionally is byte-identical to yesterday. Context: under SOX controls, under reduced staffing. Reported by the on-call engineer. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_ef5a129d99ba731b_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.94,
0.04,
0,
0.02
] | Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer. | Action for this scenario. | observability | technical | yuri_v3 |
v3_d80c94e8febf63dc_n | noul | [
"false",
"true"
] | [
0.94,
0.06
] | The sdk release shows a 9% regression in the p95 benchmark; additionally passes unit tests but fails 2 integration tests. Context: ahead of the audit, during a scheduled maintenance window. Reported by the on-call engineer. | Is this scenario one where: this is safe to ship today? | software_delivery | technical | yuri_v3 |
v3_473f8fe14c4310c4_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | The etl pipeline has connections pooling at max; additionally succeeded its failover drill. Context: under normal load, during the quarterly review. Reported by the on-call engineer. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_7dd720f15105da81_n | noul | [
"false",
"true"
] | [
0.93,
0.07
] | An api-delivered dataset shows referential breaks against the dim table; additionally exhibits schema drift in 2 columns. Context: in the sandbox only, during the system migration. Reported by the monitoring system. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_58e56ce78fdef5ba_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1414,
0.8182,
0.0404
] | A hotfix build passes unit tests but fails 2 integration tests; additionally was rebased after a security patch. Context: ahead of the audit, while on-call rotation changed. Reported by the supervisor. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_7f866e17d8147c30_n | noul | [
"false",
"true"
] | [
0.9,
0.1
] | The release candidate deletes a deprecated API with 3 known consumers; additionally was rebased after a security patch. Context: ahead of the audit, during peak load. Reported by the monitoring system. | Is this scenario one where: this is safe to ship today? | software_delivery | technical | yuri_v3 |
v3_48ee605a64b55f7b_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.29,
0.53,
0.15,
0.03
] | Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the on-call engineer. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_32457f6869cf5286_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.12,
0.87,
0.01
] | The migration pr passes unit tests but fails 2 integration tests; additionally shows a 9% regression in the p95 benchmark. Context: after a 3-week stabilization, during the system migration. Reported by the on-call engineer. | Rate regression risk for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_93f4e87e68d6fef2_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.14,
0.08,
0.77,
0.01
] | A sensor telemetry stream shows values outside physical bounds; additionally arrived 3 hours late. Context: feeding the quarterly report, as part of a compliance sweep. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_49a28c17b6d89e43_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.03,
0.85,
0.12,
0
] | The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_21d02c8daf395a91_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.83,
0.15
] | The search cluster is rejecting 30% of requests; additionally lost its primary replica. Context: with no recent change, during the holiday freeze. Reported by the review queue. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_e42a2b9ed39529df_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | A sensor telemetry stream exhibits schema drift in 2 columns; additionally shows values outside physical bounds. Context: in the sandbox only, following a recent audit. Reported by the on-call engineer. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_5bebd3d7f2d6c668_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.62,
0.33,
0.03,
0.02
] | The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the automated check. | Action for this scenario. | observability | technical | yuri_v3 |
v3_e92f72ae3e889525_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | The checkout api returns 503s from one availability zone; additionally failed its health check in 3 of 5 regions. Context: following the schema migration, at the end of the fiscal period. Reported by the operator. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_3bca7e6eacff7252_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | The fact-sales table exhibits schema drift in 2 columns; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, mid-incident. Reported by the review queue. | Is this scenario one where: a backfill is required? | data_quality | technical | yuri_v3 |
v3_c122abf63bfef586_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.39,
0.23,
0.36,
0.02
] | An api-delivered dataset has 12,000 duplicate keys today; additionally exhibits schema drift in 2 columns. Context: feeding the quarterly report, during the system migration. Reported by the supervisor. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_48205101db704ad3_c | choice | [
"block_pipeline",
"quarantine",
"proceed_with_warning",
"ignore"
] | [
0.55,
0.45,
0,
0
] | The nightly feed contains unexpected unicode in key columns; additionally shows values outside physical bounds. Context: under SOX controls, mid-incident. Reported by the supervisor. | Triage for this scenario. | data_quality | technical | yuri_v3 |
v3_2280759e05fed9de_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.91,
0.04
] | The auth gateway error rate hit 14%; additionally returns 503s from one availability zone. Context: under normal load, with a new vendor onboarded. Reported by the supervisor. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_d66ee72c37e246fe_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | The auth gateway shows certificate expiry in 40 minutes; additionally is serving stale data since 02:14. Context: with no recent change, mid-incident. Reported by the supervisor. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_3f379c18396ccef7_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | The checkout api is serving stale data since 02:14; additionally shows certificate expiry in 40 minutes. Context: under normal load, under reduced staffing. Reported by the review queue. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_63e486b9fb8a1f17_n | noul | [
"false",
"true"
] | [
0.83,
0.17
] | The release candidate was rebased after a security patch; additionally modifies the auth middleware. Context: after a 3-week stabilization, while legacy systems are still active. Reported by the on-call engineer. | Is this scenario one where: this is safe to ship today? | software_delivery | technical | yuri_v3 |
v3_cad508f0b0b0e00f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.05,
0.75,
0.19,
0
] | A sensor telemetry stream has 12,000 duplicate keys today; additionally shows 0.4% null rate where none existed. Context: in the sandbox only, during the morning shift. Reported by the on-call engineer. | Rate data corruption severity for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_15ef09f8f1f56231_c | choice | [
"smoke",
"full_regression",
"targeted_suite",
"extended_soak"
] | [
0.05,
0.44,
0.49,
0.02
] | A hotfix build passes unit tests but fails 2 integration tests; additionally ships behind a feature flag at 5% traffic. Context: ahead of the audit, under reduced staffing. Reported by the review queue. | Test depth for this scenario. | software_delivery | technical | yuri_v3 |
v3_52b7f48abfbcc2c2_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.04,
0.85,
0.11
] | An ids signature detected a new admin role grant at 03:12; additionally detected DNS tunneling entropy patterns. Context: in the finance VLAN, shortly after a software update. Reported by the on-call engineer. | Rate blast radius for this scenario on a 0-5 scale. | security_alerts | technical | yuri_v3 |
v3_1e066227f5b1b8b5_c | choice | [
"smoke",
"full_regression",
"targeted_suite",
"extended_soak"
] | [
0.01,
0.84,
0.14,
0.01
] | The migration pr changes 40% of the billing module; additionally has one blocking review comment unresolved. Context: in the payments repo, while on-call rotation changed. Reported by the monitoring system. | Test depth for this scenario. | software_delivery | technical | yuri_v3 |
v3_f25b1409884691c8_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.27,
0.71,
0.02
] | Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the on-call engineer. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_27e6ea194c56bafe_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.2,
0.78,
0.02
] | The migration pr introduces a new database index on a 2TB table; additionally adds a new dependency with no pinned hash. Context: for the 4.2 release, under reduced staffing. Reported by the on-call engineer. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_413a26e7a0741956_c | choice | [
"approve",
"approve_reduced",
"deny",
"request_more_info"
] | [
0.34,
0.32,
0.04,
0.3
] | A service-account grant matches the least-privilege baseline; additionally needs temporary access during an active SEV1. Context: with MFA verified, as part of a compliance sweep. Reported by the operator. | Decision for this scenario. | access_permissions | technical | yuri_v3 |
v3_cbedd710af052acf_n | noul | [
"false",
"true"
] | [
0.68,
0.32
] | The checkout api has a queue depth of 1.2M messages; additionally is serving stale data since 02:14. Context: with no recent change, during the holiday freeze. Reported by the supervisor. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_f7064cceee68e061_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.34,
0.59,
0.03,
0.04
] | The payments worker succeeded its failover drill; additionally is rejecting 30% of requests. Context: under normal load, during the morning shift. Reported by the supervisor. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_fd46e7a559c77ff2_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.08,
0.2,
0.56,
0.14,
0.01
] | A canary deploy ships behind a feature flag at 5% traffic; additionally is scheduled for the Friday freeze window. Context: after a 3-week stabilization, during an external partner integration. Reported by the on-call engineer. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_9b578757e070cd94_n | noul | [
"false",
"true"
] | [
0.13,
0.87
] | The auth gateway has a queue depth of 1.2M messages; additionally returns 503s from one availability zone. Context: with no recent change, under reduced staffing. Reported by the on-call engineer. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_64e281f4f43d9902_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.1,
0.03,
0.09,
0.78
] | A production access request requests read-only access matching current role; additionally requests sudo on a container host. Context: after offboarding was missed, during a scheduled maintenance window. Reported by the automated check. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
v3_99b43ace4dea31d3_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.36,
0.04,
0.57,
0.03
] | An api-delivered dataset is byte-identical to yesterday; additionally has 12,000 duplicate keys today. Context: feeding the quarterly report, during the system migration. Reported by the on-call engineer. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_57b9030626dc3630_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during normal operations. Reported by the on-call engineer. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_27071fa850439ae3_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | A service-account grant matches the least-privilege baseline; additionally asks for 90-day standing access to the finance share. Context: with MFA verified, during the morning shift. Reported by the on-call engineer. | Is this scenario one where: this is appropriate for the role? | access_permissions | technical | yuri_v3 |
v3_e87bf4bbd2432aa3_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.2,
0.79,
0.01
] | The fact-sales table has a row count variance of -18%; additionally exhibits schema drift in 2 columns. Context: upstream of the ML feature store, during the morning shift. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_af912ed0d439949b_n | noul | [
"false",
"true"
] | [
0.85,
0.15
] | The nightly feed shows referential breaks against the dim table; additionally passed all 47 freshness checks. Context: upstream of the ML feature store, while on-call rotation changed. Reported by the automated check. | Is this scenario one where: this blocks the monthly close? | data_quality | technical | yuri_v3 |
v3_66b6e3eadd798d2b_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.44,
0.51,
0.04,
0.01
] | The nightly feed shows a sudden distribution shift in one field; additionally shows values outside physical bounds. Context: feeding the quarterly report, immediately after go-live. Reported by the operator. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_e251f35e18549fc4_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.79,
0.2
] | The checkout api error rate hit 14%; additionally p99 latency jumped to 8.4s. Context: after the 14:00 deploy, at the end of the fiscal period. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_ca56fdd72c1a063b_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.12,
0.4,
0.45,
0.03
] | The nightly feed is byte-identical to yesterday; additionally shows values outside physical bounds. Context: under SOX controls, as part of a compliance sweep. Reported by the monitoring system. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_6b4d2e0cb38b0a29_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.14,
0.83,
0.03
] | The release candidate adds a new dependency with no pinned hash; additionally shows a 9% regression in the p95 benchmark. Context: ahead of the audit, during peak load. Reported by the automated check. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_647017d2485abd9c_n | noul | [
"false",
"true"
] | [
0.65,
0.35
] | The log shipper returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the monitoring system. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_93660f6279b8021c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.09,
0.74,
0.13,
0
] | The nightly feed exhibits schema drift in 2 columns; additionally shows values outside physical bounds. Context: in the sandbox only, at the end of the fiscal period. Reported by the operator. | Rate downstream impact for this scenario on a 0-5 scale. | data_quality | technical | yuri_v3 |
v3_e6fcaff43b54ea0e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0,
0.01,
0.25,
0.69,
0.04
] | A hotfix build modifies the auth middleware; additionally introduces a new database index on a 2TB table. Context: for the 4.2 release, under reduced staffing. Reported by the automated check. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_bd0b1cde44040228_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.54,
0.44,
0
] | The sdk release shows a 9% regression in the p95 benchmark; additionally changes 40% of the billing module. Context: after a 3-week stabilization, while on-call rotation changed. Reported by the on-call engineer. | Rate release readiness for this scenario on a 0-5 scale. | software_delivery | technical | yuri_v3 |
v3_107f47b947ff0775_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.67,
0.33
] | A siem correlation rule detected DNS tunneling entropy patterns; additionally observed a 2.1 GB egress to a raw-IP host. Context: on a Tier-0 asset, while legacy systems are still active. Reported by the supervisor. | Rate threat severity for this scenario on a 0-5 scale. | security_alerts | technical | yuri_v3 |
v3_38d27fb32fe0d8b2_n | noul | [
"false",
"true"
] | [
0.23,
0.77
] | A break-glass request seeks write access outside department scope; additionally requests read-only access matching current role. Context: with MFA verified, immediately after go-live. Reported by the supervisor. | Is this scenario one where: an expedited path applies? | access_permissions | technical | yuri_v3 |
v3_b58c1601242e1580_n | noul | [
"false",
"true"
] | [
0.37,
0.63
] | An edr alert found a disabled EDR agent on a jump host; additionally caught a service account writing to a share it never touches. Context: in the finance VLAN, under reduced staffing. Reported by the supervisor. | Is this scenario one where: credentials are likely compromised? | security_alerts | technical | yuri_v3 |
v3_65feede711c5a39e_c | choice | [
"producer_change",
"schema_drift",
"infrastructure",
"expected_variation"
] | [
0.4,
0.57,
0.02,
0.01
] | An api-delivered dataset passed all 47 freshness checks; additionally shows referential breaks against the dim table. Context: upstream of the ML feature store, under reduced staffing. Reported by the automated check. | Root cause for this scenario. | data_quality | technical | yuri_v3 |
v3_376db311091b4a08_n | noul | [
"false",
"true"
] | [
0.95,
0.05
] | An api-delivered dataset is byte-identical to yesterday; additionally shows values outside physical bounds. Context: feeding the quarterly report, during a scheduled maintenance window. Reported by the supervisor. | Is this scenario one where: the data is fit for use? | data_quality | technical | yuri_v3 |
v3_5669f50f0831c0f7_n | noul | [
"false",
"true"
] | [
0.73,
0.27
] | The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the supervisor. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_c701c921e0fdfe27_n | noul | [
"false",
"true"
] | [
0.37,
0.63
] | The payments worker error rate hit 14%; additionally has a queue depth of 1.2M messages. Context: following the schema migration, under an active deadline. Reported by the operator. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_93358990c55a8b61_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.18,
0.78,
0.04
] | The payments worker returns 503s from one availability zone; additionally is serving stale data since 02:14. Context: under normal load, mid-incident. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_24f5f1c0b5ca5c86_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1,
0.87,
0.03
] | The etl pipeline error rate hit 14%; additionally has connections pooling at max. Context: following the schema migration, mid-incident. Reported by the review queue. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_069b055d1fda653b_n | noul | [
"false",
"true"
] | [
0.35,
0.65
] | The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the review queue. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_03791fb3cdaef214_n | noul | [
"false",
"true"
] | [
0.34,
0.66
] | Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, during normal operations. Reported by the monitoring system. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_c94ccb87b60a2083_n | noul | [
"false",
"true"
] | [
0.72,
0.28
] | Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_3bd22cda690af402_c | choice | [
"permanent",
"30d",
"7d",
"single_session"
] | [
0.02,
0.02,
0.12,
0.84
] | A production access request seeks write access outside department scope; additionally matches the least-privilege baseline. Context: with an expired justification, following a recent audit. Reported by the operator. | Access duration for this scenario. | access_permissions | technical | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - technical family
57,797 typed calibrated decision rows from the jev-distill-corpus-v3 corpus, grouped by family.
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Domains in this family
data_quality- 9,789 rowsobservability- 9,711 rowsaccess_permissions- 9,669 rowsincident_triage- 9,572 rowssoftware_delivery- 9,546 rowssecurity_alerts- 9,510 rows
Other views of the same data
- per-domain:
SargeDev/jev-corpus-<domain> - the whole corpus in one repo: SargeDev/jev-distill-corpus-v3
- Downloads last month
- -