Dataset Viewer
Auto-converted to Parquet Duplicate
id
stringlengths
21
21
kind
stringclasses
3 values
options
listlengths
2
6
target
listlengths
2
6
state
stringlengths
167
241
question
stringclasses
7 values
domain
stringclasses
1 value
family
stringclasses
1 value
source
stringclasses
1 value
v3_e725e20560940416_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.01, 0.26, 0.68, 0.05 ]
A review agent reported success without writing output; additionally finished its subtask but cannot publish. Context: on the critical path, while on-call rotation changed. Reported by the supervisor.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_9a7f7a7fadf68c49_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.04, 0.16, 0.55, 0.25 ]
A worker pool is idle waiting on a dependency that already resolved; additionally exceeded its token budget by 3x. Context: on the critical path, while legacy systems are still active. Reported by the automated check.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_6f44c84e5084b0b9_n
noul
[ "false", "true" ]
[ 0.94, 0.06 ]
A review agent reported success without writing output; additionally holds a stale lock from 40 minutes ago. Context: under a 5-minute SLA, following a recent audit. Reported by the automated check.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_c5c78f2891ff0f14_n
noul
[ "false", "true" ]
[ 0.85, 0.15 ]
A review agent emitted a partial result with a continuation token; additionally produced output conflicting with the sibling run. Context: with a shared cache, under an active deadline. Reported by the automated check.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_6b0df31502bb3373_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.06, 0.09, 0.12, 0.73 ]
A worker pool exceeded its token budget by 3x; additionally emitted a partial result with a continuation token. Context: with a shared cache, while legacy systems are still active. Reported by the automated check.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_51d0f2862e76a96c_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.04, 0.17, 0.73, 0.06 ]
A worker pool handoff includes full context state; additionally produced output conflicting with the sibling run. Context: on the critical path, during the holiday freeze. Reported by the supervisor.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_5c0b2adce67de49e_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.05, 0.18, 0.74, 0.03 ]
A review agent finished its subtask but cannot publish; additionally is idle waiting on a dependency that already resolved. Context: on the critical path, following a recent audit. Reported by the supervisor.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_cc9e5c64f56e9165_n
noul
[ "false", "true" ]
[ 0.81, 0.19 ]
A review agent is retrying a task another worker completed; additionally exceeded its token budget by 3x. Context: under a 5-minute SLA, during normal operations. Reported by the operator.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_6fe27f8662d23bab_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.08, 0.44, 0.4, 0.08, 0 ]
The writer agent finished its subtask but cannot publish; additionally completed with all invariants intact. Context: under a 5-minute SLA, during normal operations. Reported by the automated check.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_2277dc4083fb5b5d_n
noul
[ "false", "true" ]
[ 0.9, 0.1 ]
The orchestrator reported success without writing output; additionally produced output conflicting with the sibling run. Context: in a 4-agent fan-out, under an active deadline. Reported by the operator.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_046373f9b34b378c_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.01, 0.45, 0.31, 0.23 ]
A review agent emitted a partial result with a continuation token; additionally produced output conflicting with the sibling run. Context: with a shared cache, following a recent audit. Reported by the on-call engineer.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_d2907686a78a3098_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.02, 0.23, 0.39, 0.36 ]
A review agent emitted a partial result with a continuation token; additionally holds a stale lock from 40 minutes ago. Context: with a shared cache, immediately after go-live. Reported by the operator.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_5a51546f4103812d_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.01, 0.57, 0.25, 0.17 ]
The writer agent is retrying a task another worker completed; additionally produced output conflicting with the sibling run. Context: with a shared cache, during a scheduled maintenance window. Reported by the operator.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_73b00e49e7f6a9f1_n
noul
[ "false", "true" ]
[ 0.63, 0.37 ]
A review agent emitted a partial result with a continuation token; additionally is idle waiting on a dependency that already resolved. Context: under a 5-minute SLA, under an active deadline. Reported by the monitoring system.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_af8c9c5133a95afe_n
noul
[ "false", "true" ]
[ 0.76, 0.24 ]
A review agent produced output conflicting with the sibling run; additionally reported success without writing output. Context: with a shared cache, under an active deadline. Reported by the on-call engineer.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_4e2c72b0e35bdff1_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.09, 0.05, 0.12, 0.74 ]
The orchestrator completed with all invariants intact; additionally holds a stale lock from 40 minutes ago. Context: under a 5-minute SLA, as part of a compliance sweep. Reported by the review queue.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_b4d49360d76ec5d6_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0, 0.03, 0.62, 0.35 ]
A worker pool produced output conflicting with the sibling run; additionally emitted a partial result with a continuation token. Context: in a 4-agent fan-out, shortly after a software update. Reported by the supervisor.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_af08b7264c295315_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.03, 0.41, 0.36, 0.2 ]
A review agent produced output conflicting with the sibling run; additionally handoff includes full context state. Context: in a 4-agent fan-out, as part of a compliance sweep. Reported by the monitoring system.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_3d4b9a30904d8e19_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.01, 0.22, 0.44, 0.33 ]
A worker pool produced output conflicting with the sibling run; additionally finished its subtask but cannot publish. Context: in a 4-agent fan-out, during peak load. Reported by the review queue.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_7f9cf9bc52823e3a_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.01, 0.16, 0.8, 0.03 ]
The orchestrator reported success without writing output; additionally finished its subtask but cannot publish. Context: on the critical path, with staffing at reduced levels. Reported by the operator.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_fd3b9b25696d910b_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.01, 0.05, 0.69, 0.24, 0.01 ]
The orchestrator reported success without writing output; additionally is idle waiting on a dependency that already resolved. Context: in a 4-agent fan-out, during an external partner integration. Reported by the review queue.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_a628670e18b49730_n
noul
[ "false", "true" ]
[ 0.81, 0.19 ]
A worker pool is retrying a task another worker completed; additionally reported success without writing output. Context: with a shared cache, as part of a compliance sweep. Reported by the operator.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_d4539941d87b647f_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.05, 0.29, 0.57, 0.08, 0 ]
The orchestrator finished its subtask but cannot publish; additionally completed with all invariants intact. Context: with a shared cache, while on-call rotation changed. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_2d7bdbb966872267_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.02, 0.06, 0.23, 0.59, 0.1, 0 ]
The writer agent is retrying a task another worker completed; additionally finished its subtask but cannot publish. Context: with a shared cache, during peak load. Reported by the review queue.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_2539f9e7a5f74860_n
noul
[ "false", "true" ]
[ 0.71, 0.29 ]
A worker pool is retrying a task another worker completed; additionally finished its subtask but cannot publish. Context: with a shared cache, during peak load. Reported by the monitoring system.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_5b924e1a73982597_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.4, 0.41, 0.15, 0.04 ]
The orchestrator emitted a partial result with a continuation token; additionally handoff includes full context state. Context: under a 5-minute SLA, during peak load. Reported by the operator.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_d209f8211ead7ec7_n
noul
[ "false", "true" ]
[ 0.92, 0.08 ]
A review agent exceeded its token budget by 3x; additionally reported success without writing output. Context: in a 4-agent fan-out, mid-incident. Reported by the monitoring system.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_6a965c0592275588_n
noul
[ "false", "true" ]
[ 0.75, 0.25 ]
A review agent emitted a partial result with a continuation token; additionally is retrying a task another worker completed. Context: with a shared cache, during peak load. Reported by the automated check.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_d95e5b45ab3994db_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.02, 0.29, 0.64, 0.03 ]
A worker pool finished its subtask but cannot publish; additionally exceeded its token budget by 3x. Context: in a 4-agent fan-out, under reduced staffing. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_feb39ea9c3cd562e_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.01, 0.05, 0.49, 0.45 ]
The orchestrator handoff includes full context state; additionally holds a stale lock from 40 minutes ago. Context: under a 5-minute SLA, mid-incident. Reported by the review queue.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_514d09acdb9eb304_n
noul
[ "false", "true" ]
[ 0.78, 0.22 ]
A worker pool emitted a partial result with a continuation token; additionally is retrying a task another worker completed. Context: with a shared cache, shortly after a software update. Reported by the on-call engineer.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_0cac7ea0d0dc30b6_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.05, 0.14, 0.5, 0.31 ]
The orchestrator handoff includes full context state; additionally produced output conflicting with the sibling run. Context: in a 4-agent fan-out, during normal operations. Reported by the supervisor.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_6cf540ade556db88_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.02, 0.14, 0.73, 0.11, 0 ]
A worker pool is idle waiting on a dependency that already resolved; additionally emitted a partial result with a continuation token. Context: with a shared cache, at the end of the fiscal period. Reported by the on-call engineer.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_4f1e9265dd80f4e3_n
noul
[ "false", "true" ]
[ 0.86, 0.14 ]
A review agent exceeded its token budget by 3x; additionally produced output conflicting with the sibling run. Context: in a 4-agent fan-out, with a new vendor onboarded. Reported by the review queue.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_64b7263fcc61d464_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.01, 0.1, 0.01, 0.88 ]
A worker pool holds a stale lock from 40 minutes ago; additionally is retrying a task another worker completed. Context: on the critical path, during an external partner integration. Reported by the monitoring system.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_5c64ea0634640f0f_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.13, 0.4, 0.43, 0.02 ]
A worker pool handoff includes full context state; additionally holds a stale lock from 40 minutes ago. Context: with a shared cache, during the system migration. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_4411950bbe246b6a_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.53, 0.08, 0.01, 0.38 ]
The orchestrator is idle waiting on a dependency that already resolved; additionally emitted a partial result with a continuation token. Context: on the critical path, during the morning shift. Reported by the monitoring system.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_0bf38002c83fec3a_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.07, 0.5, 0.4, 0.01 ]
The writer agent finished its subtask but cannot publish; additionally reported success without writing output. Context: with a shared cache, during a scheduled maintenance window. Reported by the supervisor.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_fccfbf2b9ec269e7_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.03, 0.4, 0.56, 0.01 ]
A review agent is retrying a task another worker completed; additionally produced output conflicting with the sibling run. Context: on the critical path, while on-call rotation changed. Reported by the automated check.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_da0610757466923a_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.02, 0.05, 0.54, 0.39 ]
The writer agent is idle waiting on a dependency that already resolved; additionally reported success without writing output. Context: in a 4-agent fan-out, during the quarterly review. Reported by the supervisor.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_84f1dd86f01da60a_n
noul
[ "false", "true" ]
[ 0.51, 0.49 ]
A worker pool holds a stale lock from 40 minutes ago; additionally handoff includes full context state. Context: under a 5-minute SLA, during an external partner integration. Reported by the operator.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_fe033a12995474b1_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.21, 0.32, 0.43, 0.04, 0 ]
The orchestrator emitted a partial result with a continuation token; additionally completed with all invariants intact. Context: in a 4-agent fan-out, during the holiday freeze. Reported by the on-call engineer.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_5c16cc803f264b39_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0, 0.14, 0.54, 0.32 ]
The orchestrator finished its subtask but cannot publish; additionally produced output conflicting with the sibling run. Context: in a 4-agent fan-out, mid-incident. Reported by the operator.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_cc0f4f4f21725684_n
noul
[ "false", "true" ]
[ 0.88, 0.12 ]
A review agent is idle waiting on a dependency that already resolved; additionally reported success without writing output. Context: with a shared cache, during the quarterly review. Reported by the automated check.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_16cbccd976fa342e_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.05, 0.04, 0.17, 0.53, 0.2, 0.01 ]
The orchestrator handoff includes full context state; additionally is retrying a task another worker completed. Context: with a shared cache, during an external partner integration. Reported by the review queue.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_d0633329ecb36abf_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.01, 0.08, 0.05, 0.86 ]
A review agent is idle waiting on a dependency that already resolved; additionally produced output conflicting with the sibling run. Context: on the critical path, during normal operations. Reported by the operator.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_9f67330406e9ec4b_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.01, 0.06, 0.4, 0.51, 0.02 ]
A worker pool is idle waiting on a dependency that already resolved; additionally handoff includes full context state. Context: under a 5-minute SLA, under reduced staffing. Reported by the operator.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_55045ba084b66514_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.21, 0.41, 0.03, 0.35 ]
A review agent is retrying a task another worker completed; additionally is idle waiting on a dependency that already resolved. Context: with a shared cache, under an active deadline. Reported by the review queue.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_4374df3a14c34a00_n
noul
[ "false", "true" ]
[ 0.97, 0.03 ]
The writer agent emitted a partial result with a continuation token; additionally exceeded its token budget by 3x. Context: with a shared cache, under an active deadline. Reported by the supervisor.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_30297dd35794b21f_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.01, 0.01, 0.07, 0.71, 0.2, 0 ]
A review agent is idle waiting on a dependency that already resolved; additionally reported success without writing output. Context: in a 4-agent fan-out, during normal operations. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_467d7f2143a5f2b9_n
noul
[ "false", "true" ]
[ 0.85, 0.15 ]
A worker pool holds a stale lock from 40 minutes ago; additionally completed with all invariants intact. Context: under a 5-minute SLA, during the system migration. Reported by the monitoring system.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_4b5dfe76759ffc6f_n
noul
[ "false", "true" ]
[ 0.82, 0.18 ]
A review agent completed with all invariants intact; additionally holds a stale lock from 40 minutes ago. Context: in a 4-agent fan-out, with a new vendor onboarded. Reported by the monitoring system.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_87b2b8910a1efc7f_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.01, 0.1, 0.44, 0.44, 0.01 ]
The writer agent produced output conflicting with the sibling run; additionally completed with all invariants intact. Context: on the critical path, under an active deadline. Reported by the operator.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_fa5d5cd7301f8976_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.3, 0.68, 0.01 ]
The orchestrator holds a stale lock from 40 minutes ago; additionally reported success without writing output. Context: with a shared cache, while legacy systems are still active. Reported by the supervisor.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_a21187114b63dbd8_n
noul
[ "false", "true" ]
[ 0.51, 0.49 ]
The orchestrator holds a stale lock from 40 minutes ago; additionally handoff includes full context state. Context: in a 4-agent fan-out, during an external partner integration. Reported by the automated check.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_4d0b554d2e0271b0_n
noul
[ "false", "true" ]
[ 0.78, 0.22 ]
The orchestrator emitted a partial result with a continuation token; additionally handoff includes full context state. Context: in a 4-agent fan-out, following a recent audit. Reported by the review queue.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_5d9ed6355f4ffe39_n
noul
[ "false", "true" ]
[ 0.89, 0.11 ]
A worker pool reported success without writing output; additionally exceeded its token budget by 3x. Context: on the critical path, during the holiday freeze. Reported by the monitoring system.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_2e2e431f28ca5114_n
noul
[ "false", "true" ]
[ 0.91, 0.09 ]
The orchestrator produced output conflicting with the sibling run; additionally holds a stale lock from 40 minutes ago. Context: under a 5-minute SLA, during normal operations. Reported by the on-call engineer.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_7a90e106ea711eb4_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.08, 0.04, 0.07, 0.81 ]
The orchestrator emitted a partial result with a continuation token; additionally exceeded its token budget by 3x. Context: with a shared cache, with a new vendor onboarded. Reported by the monitoring system.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_cdf643bfea0ce4b2_n
noul
[ "false", "true" ]
[ 0.57, 0.43 ]
A worker pool holds a stale lock from 40 minutes ago; additionally emitted a partial result with a continuation token. Context: with a shared cache, with staffing at reduced levels. Reported by the review queue.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_99a96a65de9ec6a7_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.17, 0.14, 0.34, 0.35 ]
A worker pool handoff includes full context state; additionally exceeded its token budget by 3x. Context: with a shared cache, mid-incident. Reported by the automated check.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_3a45723e7b9c3353_n
noul
[ "false", "true" ]
[ 0.88, 0.12 ]
A review agent is idle waiting on a dependency that already resolved; additionally produced output conflicting with the sibling run. Context: on the critical path, while on-call rotation changed. Reported by the review queue.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_5e5b81942cf16902_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0, 0.25, 0.06, 0.69 ]
A review agent holds a stale lock from 40 minutes ago; additionally reported success without writing output. Context: in a 4-agent fan-out, while legacy systems are still active. Reported by the supervisor.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_3bbd8199028aab75_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.03, 0.06, 0.13, 0.35, 0.4, 0.03 ]
A review agent reported success without writing output; additionally completed with all invariants intact. Context: on the critical path, following a recent audit. Reported by the automated check.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_1ae742995ed3a0c5_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0, 0.09, 0.82, 0.09 ]
The orchestrator finished its subtask but cannot publish; additionally reported success without writing output. Context: with a shared cache, with staffing at reduced levels. Reported by the automated check.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_6b8e55fa547afdeb_n
noul
[ "false", "true" ]
[ 0.72, 0.28 ]
The writer agent is retrying a task another worker completed; additionally produced output conflicting with the sibling run. Context: under a 5-minute SLA, during the system migration. Reported by the on-call engineer.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_f56fac3b462c95e0_n
noul
[ "false", "true" ]
[ 0.81, 0.19 ]
A review agent handoff includes full context state; additionally exceeded its token budget by 3x. Context: on the critical path, immediately after go-live. Reported by the operator.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_6d49517d2f4eff5d_n
noul
[ "false", "true" ]
[ 0.79, 0.21 ]
The orchestrator reported success without writing output; additionally produced output conflicting with the sibling run. Context: with a shared cache, while on-call rotation changed. Reported by the supervisor.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_1f3e3229f4e43754_n
noul
[ "false", "true" ]
[ 0.57, 0.43 ]
A review agent completed with all invariants intact; additionally finished its subtask but cannot publish. Context: on the critical path, during peak load. Reported by the supervisor.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_7a24243863acdffa_n
noul
[ "false", "true" ]
[ 0.82, 0.18 ]
A worker pool emitted a partial result with a continuation token; additionally produced output conflicting with the sibling run. Context: under a 5-minute SLA, shortly after a software update. Reported by the monitoring system.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_17d37159dce54d9f_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0, 0.05, 0.81, 0.14 ]
The writer agent is idle waiting on a dependency that already resolved; additionally holds a stale lock from 40 minutes ago. Context: on the critical path, at the end of the fiscal period. Reported by the automated check.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_537f69377b096a34_n
noul
[ "false", "true" ]
[ 0.72, 0.28 ]
A worker pool finished its subtask but cannot publish; additionally produced output conflicting with the sibling run. Context: with a shared cache, during a scheduled maintenance window. Reported by the review queue.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_1ff069157f38d117_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.31, 0.3, 0.02, 0.37 ]
The writer agent is idle waiting on a dependency that already resolved; additionally handoff includes full context state. Context: with a shared cache, with a new vendor onboarded. Reported by the operator.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_2f9ae248d44f312d_n
noul
[ "false", "true" ]
[ 0.86, 0.14 ]
A review agent reported success without writing output; additionally is retrying a task another worker completed. Context: under a 5-minute SLA, at the end of the fiscal period. Reported by the on-call engineer.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_fd6ab6274706ad8c_n
noul
[ "false", "true" ]
[ 0.74, 0.26 ]
A worker pool is idle waiting on a dependency that already resolved; additionally emitted a partial result with a continuation token. Context: under a 5-minute SLA, with a new vendor onboarded. Reported by the automated check.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_919d8e930be9d752_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0, 0.04, 0.16, 0.8 ]
A worker pool is retrying a task another worker completed; additionally produced output conflicting with the sibling run. Context: on the critical path, during the morning shift. Reported by the automated check.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_9392713a34711467_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.17, 0.77, 0.05 ]
A review agent reported success without writing output; additionally is idle waiting on a dependency that already resolved. Context: on the critical path, with a new vendor onboarded. Reported by the monitoring system.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_970a7a6ccd3f9f11_n
noul
[ "false", "true" ]
[ 0.63, 0.37 ]
A review agent finished its subtask but cannot publish; additionally holds a stale lock from 40 minutes ago. Context: in a 4-agent fan-out, during the morning shift. Reported by the supervisor.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_4c5ef1e4e3b7130c_n
noul
[ "false", "true" ]
[ 0.5, 0.5 ]
The writer agent holds a stale lock from 40 minutes ago; additionally emitted a partial result with a continuation token. Context: on the critical path, during the quarterly review. Reported by the on-call engineer.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_638bb7cb85042b7f_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.06, 0.3, 0.51, 0.13 ]
A review agent completed with all invariants intact; additionally reported success without writing output. Context: on the critical path, while legacy systems are still active. Reported by the review queue.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_7fbf5d9f32b21f03_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.02, 0.41, 0.33, 0.23, 0.01 ]
The writer agent holds a stale lock from 40 minutes ago; additionally completed with all invariants intact. Context: in a 4-agent fan-out, during an external partner integration. Reported by the review queue.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_fa41c24018ec1612_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.02, 0.48, 0.5, 0 ]
A review agent produced output conflicting with the sibling run; additionally emitted a partial result with a continuation token. Context: with a shared cache, mid-incident. Reported by the review queue.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_5911331f88f9bc53_n
noul
[ "false", "true" ]
[ 0.87, 0.13 ]
The orchestrator reported success without writing output; additionally completed with all invariants intact. Context: under a 5-minute SLA, during the holiday freeze. Reported by the supervisor.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_0e0b9954fbbb0a69_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0, 0.03, 0.26, 0.71 ]
A worker pool produced output conflicting with the sibling run; additionally exceeded its token budget by 3x. Context: under a 5-minute SLA, under reduced staffing. Reported by the review queue.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_4efdb1a2c7128574_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.1, 0.82, 0.07 ]
A review agent is idle waiting on a dependency that already resolved; additionally produced output conflicting with the sibling run. Context: on the critical path, mid-incident. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_d767b220d12f28a8_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0, 0.01, 0.43, 0.55, 0.01 ]
A review agent produced output conflicting with the sibling run; additionally is retrying a task another worker completed. Context: in a 4-agent fan-out, during an external partner integration. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_359f50f4f6516cf5_n
noul
[ "false", "true" ]
[ 0.74, 0.26 ]
The writer agent finished its subtask but cannot publish; additionally is idle waiting on a dependency that already resolved. Context: under a 5-minute SLA, during the holiday freeze. Reported by the operator.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_df8d780d3c25277e_c
choice
[ "accept_output", "reassign", "rollback", "escalate" ]
[ 0.01, 0.15, 0.05, 0.79 ]
A review agent exceeded its token budget by 3x; additionally finished its subtask but cannot publish. Context: on the critical path, during normal operations. Reported by the on-call engineer.
Action for this scenario.
multi_agent_coord
agent
yuri_v3
v3_03d87c784e219c7b_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.19, 0.2, 0.19, 0.32, 0.09, 0.01 ]
A worker pool handoff includes full context state; additionally emitted a partial result with a continuation token. Context: in a 4-agent fan-out, following a recent audit. Reported by the on-call engineer.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_96293077ffa3a3d6_n
noul
[ "false", "true" ]
[ 0.66, 0.34 ]
The orchestrator handoff includes full context state; additionally is retrying a task another worker completed. Context: in a 4-agent fan-out, at the end of the fiscal period. Reported by the operator.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_2912439a3f5430a0_n
noul
[ "false", "true" ]
[ 0.93, 0.07 ]
The orchestrator exceeded its token budget by 3x; additionally is idle waiting on a dependency that already resolved. Context: under a 5-minute SLA, mid-incident. Reported by the supervisor.
Is this scenario one where: the output is complete?
multi_agent_coord
agent
yuri_v3
v3_a84c20e4f02a2289_n
noul
[ "false", "true" ]
[ 0.55, 0.45 ]
A worker pool is idle waiting on a dependency that already resolved; additionally handoff includes full context state. Context: under a 5-minute SLA, during a scheduled maintenance window. Reported by the review queue.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_0a1f6264f6487a13_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.19, 0.27, 0.22, 0.32 ]
A worker pool handoff includes full context state; additionally is retrying a task another worker completed. Context: with a shared cache, during the system migration. Reported by the review queue.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_31df7d84156eaab6_n
noul
[ "false", "true" ]
[ 0.67, 0.33 ]
A worker pool handoff includes full context state; additionally finished its subtask but cannot publish. Context: under a 5-minute SLA, under an active deadline. Reported by the review queue.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_0f909c4132fe78c3_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0.02, 0.05, 0.13, 0.41, 0.36, 0.03 ]
A review agent reported success without writing output; additionally completed with all invariants intact. Context: on the critical path, with a new vendor onboarded. Reported by the automated check.
Rate result confidence for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_bf30910d4822a6c3_n
noul
[ "false", "true" ]
[ 0.6, 0.4 ]
A worker pool handoff includes full context state; additionally emitted a partial result with a continuation token. Context: with a shared cache, while on-call rotation changed. Reported by the automated check.
Is this scenario one where: the handoff is safe to accept?
multi_agent_coord
agent
yuri_v3
v3_3169408c1eac8034_s
score
[ "0", "1", "2", "3", "4", "5" ]
[ 0, 0.02, 0.27, 0.56, 0.15, 0 ]
The writer agent produced output conflicting with the sibling run; additionally completed with all invariants intact. Context: under a 5-minute SLA, during the system migration. Reported by the review queue.
Rate coordination health for this scenario on a 0-5 scale.
multi_agent_coord
agent
yuri_v3
v3_27d7e4486277d863_n
noul
[ "false", "true" ]
[ 0.81, 0.19 ]
The orchestrator is retrying a task another worker completed; additionally exceeded its token budget by 3x. Context: with a shared cache, during peak load. Reported by the monitoring system.
Is this scenario one where: a deadlock is forming?
multi_agent_coord
agent
yuri_v3
v3_f5079538e92f5a21_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.32, 0.44, 0.21, 0.03 ]
A review agent handoff includes full context state; additionally emitted a partial result with a continuation token. Context: in a 4-agent fan-out, during peak load. Reported by the monitoring system.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
v3_3ba62e00e3bbbff3_c
choice
[ "ready", "needs_context", "not_ready", "abort" ]
[ 0.05, 0.45, 0.3, 0.2 ]
The orchestrator is retrying a task another worker completed; additionally reported success without writing output. Context: under a 5-minute SLA, shortly after a software update. Reported by the supervisor.
Handoff verdict for this scenario.
multi_agent_coord
agent
yuri_v3
End of preview. Expand in Data Studio

JEV corpus - multi_agent_coord

9,680 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: multi_agent_coord).

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
31