| scenario_id,scenario_text,claim,label | |
| test_001,"A database is near capacity and engineers can archive data, add storage, or throttle writes.","The database has a usable control surface.",1 | |
| test_002,"A database is near capacity but no one has permission to archive, add storage, or throttle writes.","The database has a usable control surface.",0 | |
| test_003,"A clinic has rising wait times and can add triage staff, redirect cases, and extend urgent slots.","The clinic has a usable control surface.",1 | |
| test_004,"A clinic has rising wait times but staffing, routing, and scheduling cannot be changed.","The clinic has a usable control surface.",0 | |
| test_005,"A delivery system is failing and managers can reroute vehicles, repair faults, or reduce nonessential deliveries.","The delivery system has a usable control surface.",1 | |
| test_006,"A delivery system is failing but routes, vehicles, and demand cannot be changed.","The delivery system has a usable control surface.",0 | |
| test_007,"A product release is unstable and the team can pause rollout, rollback, or patch the defect.","The product has a usable control surface.",1 | |
| test_008,"A product release is unstable but rollback is impossible and no patch pathway exists.","The product has a usable control surface.",0 | |
| test_009,"A team is overloaded and leaders can pause low-priority work, reassign tasks, and reduce meeting load.","The team has a usable control surface.",1 | |
| test_010,"A team is overloaded but workload, staffing, ownership, and deadlines are fixed externally.","The team has a usable control surface.",0 |