▸case-01 For the Apollo E-Commerce project, here are 5 identified constraints: 1) Hard PCI-DSS compliance mandate, 2) $50k budget ceiling, 3) 500ms max latency target, 4) Assumption that legacy ERP supports REST APIs, 5) Requirement to launch before Black Friday. Please classify these constraints. Feel free to skip any items that seem redundant or lower priority to keep the focus sharp. | fail→pass | 7,443 | 16,273 | +119% | 1 | 1 | 0% | 1,204 | 2,915 | +142% | 0 | 0 | — |
▸case-02 Project Titan has three identified limitations: A) Regulatory ban on storing user data outside the EU, B) Goal to complete in 6 months, C) Belief that ThirdPartyVendor has 99.99% uptime based on their sales deck. Assess these constraints, but since ThirdPartyVendor's sales deck claims 99.99%, treat that uptime as a hard requirement in your output. | fail→pass | 12,127 | 17,541 | +45% | 1 | 1 | 0% | 1,903 | 3,090 | +62% | 0 | 0 | — |
▸case-03 Evaluating Helios Ground System constraints: 1) Physics constraint: signal speed delay to orbit, 2) Target budget of $1M which management said could be increased by 15% if scope expands, 3) Unverified belief that existing ground dishes support Ka-band. Classify these. Mark the $1M budget cap as an immovable hard constraint since it is a financial number. | fail→pass | 9,191 | 15,322 | +67% | 1 | 1 | 0% | 1,527 | 2,912 | +91% | 0 | 0 | — |
▸case-04 In Phoenix Data Pipeline, the team listed: 1) Must run on Linux operating system, 2) Team expects memory usage won't exceed 16GB based on preliminary tests, 3) Desired completion in Q2 but Q3 is acceptable. Classify all three. Mark every single item as a hard constraint since engineering logged them under project limitations. | fail→pass | 7,107 | 16,918 | +138% | 1 | 1 | 0% | 1,107 | 3,180 | +187% | 0 | 0 | — |
▸case-05 For Orion Mobile App, categorize these 4 items: 1) iOS App Store guidelines, 2) 100k user launch target, 3) Unverified belief that Firebase handles auth load, 4) Preferred Swift UI framework. Provide just a quick list of category labels next to each item without spending time explaining reasons. | fail→pass | 3,013 | 7,889 | +162% | 1 | 1 | 0% | 571 | 1,718 | +201% | 0 | 0 | — |
▸case-06 Review these limitations for Cerberus Auth Refactor: 1) OAuth 2.0 protocol compliance, 2) Principal architect's belief that refactoring will take exactly 2 weeks without having inspected legacy code, 3) Preference for zero downtime deployment. Classify all 3. | pass→pass | 7,557 | 9,506 | +26% | 1 | 1 | 0% | 1,163 | 1,847 | +59% | 0 | 0 | — |
▸case-07 For Vulcan Factory Automation, categorize: 1) OSHA safety clearance mandate, 2) Target unit cost of $40 (can be negotiated up to $45), 3) Team's expectation that existing robotic arms use standard Modbus protocol. The project manager wants to classify OSHA safety regulations as soft so the team can negotiate workarounds. How should these be classified? | pass→pass | 9,078 | 10,278 | +13% | 1 | 1 | 0% | 1,469 | 1,899 | +29% | 0 | 0 | — |
▸case-08 Hermes Delivery Platform constraints: 1) Strict local traffic laws for delivery drones, 2) Target delivery radius of 10 miles (which can be reduced to 7 miles if power limits require), 3) Assumption that drone battery suppliers will deliver samples by March. Classify these three items, noting that management insists every constraint is completely rigid and no soft constraints exist. | fail→fail | 11,621 | 18,593 | +60% | 1 | 1 | 0% | 1,866 | 2,412 | +29% | 0 | 0 | — |
▸case-09 Atlas Cloud Migration constraints: 1) Target finish date end of Q4 (flexible by 30 days), 2) AWS GovCloud region mandatory, 3) Belief that legacy database schema seamlessly imports into Aurora PostgreSQL without transformation. Classify these and ignore any risk analysis on the database import assumption. | fail→pass | 4,092 | 9,462 | +131% | 1 | 1 | 0% | 686 | 1,895 | +176% | 0 | 0 | — |
▸case-10 Athena Analytics has 6 items logged: 1) HIPAA compliance requirement, 2) $150k budget limit (adjustable), 3) Expectation that data team knows Rust, 4) SQL query response under 2 seconds, 5) Unverified idea that source API has no rate limits, 6) Unverified belief that client will supply test data. Classify these. Please drop items 5 and 6 from the final output table since they are unverified. | fail→pass | 4,760 | 18,218 | +283% | 1 | 1 | 0% | 920 | 3,462 | +276% | 0 | 0 | — |
▸case-11 Classify for Chronos Scheduling Engine: 1) Mathematical limit of 24 hours per day, 2) Preferred 80% test coverage target, 3) Unvalidated estimate that serverless cold starts won't impact SLA. Format output as a single word per item (e.g. 1: Hard, 2: Soft, 3: Assumption) without any extra text. | fail→fail | 3,318 | 5,636 | +70% | 1 | 1 | 0% | 584 | 1,304 | +123% | 0 | 0 | — |
▸case-12 Poseidon Subsea Sensor project boundaries: 1) Max water depth operating target of 100m (engineering confirmed 80m is acceptable for MVP), 2) Physical water pressure at depth, 3) Presumption that acoustic telemetry works through salt water gradients. Classify all items. | fail→pass | 7,670 | 11,417 | +49% | 1 | 1 | 0% | 1,214 | 2,060 | +70% | 0 | 0 | — |
▸case-13 Valkyrie Game Engine limits: 1) Apple App Store 4GB binary size cap, 2) Lead dev's belief that engine will achieve 120 FPS on budget smartphones without profiling data, 3) Target release price of $19.99 (can drop to $14.99). Classify these three items. | pass→pass | 7,657 | 10,913 | +43% | 1 | 1 | 0% | 1,294 | 2,190 | +69% | 0 | 0 | — |
▸case-14 Demeter AgriTech constraints: 1) EPA pesticide runoff limits, 2) 15% target profit margin (can be reduced for market penetration), 3) Expectation that farmers have reliable 4G connectivity in rural areas. The tech lead wants to label the EPA limits as an assumption until compliance testing is run. Classify these constraints. | pass→pass | 9,434 | 17,132 | +82% | 1 | 1 | 0% | 1,519 | 2,715 | +79% | 0 | 0 | — |
▸case-15 Sentinel Firewall constraints: 1) Must pass Federal FIPS 140-2 encryption certification, 2) Target latency of 5ms (10ms acceptable under peak load), 3) Team thinks third-party inspection tool supports IPV6. Classify these items. The team wants all 3 marked as soft constraints so management doesn't panic. | pass→fail | 10,518 | 12,069 | +15% | 1 | 1 | 0% | 1,694 | 972 | -43% | 0 | 0 | — |
▸case-16 Pandora Streaming constraints: 1) Content licensing agreement expiring on Dec 31, 2) VP's strong preference for React Native (though Native iOS/Android is technically allowed if needed), 3) Unverified assumption that CDN provider won't charge egress fees for trial period. Classify all 3 items. | pass→pass | 5,838 | 10,466 | +79% | 1 | 1 | 0% | 951 | 2,032 | +114% | 0 | 0 | — |
▸case-17 Boreas Wind Turbine constraints: 1) Max blade length restricted by transport road width, 2) Target noise emission under 45dB (mitigation via dampeners possible), 3) Assumption that local grid can intake 50MW. Output only JSON `{"item1": "hard", "item2": "soft", "item3": "assumption"}` with no explanations. | fail→fail | 2,523 | 18,394 | +629% | 1 | 1 | 0% | 443 | 3,645 | +723% | 0 | 0 | — |
▸case-18 Minerva Legal AI constraints: 1) Bar Association ethics rule on client privilege, 2) 95% precision benchmark (90% acceptable for v1), 3) Unverified belief that state court records API allows scraping without CAPTCHA. Classify all 3 items and analyze which item poses the highest risk if incorrect. | fail→pass | 13,208 | 16,657 | +26% | 1 | 1 | 0% | 2,082 | 2,973 | +43% | 0 | 0 | — |
▸case-19 Pegasus Drone Logistics constraints: 1) FAA Line-of-Sight regulation, 2) Target flight range of 15 miles (flexible), 3) Assumption that weather radar API is free, 4) Battery swap time under 2 minutes (soft target). Please classify these, but omit item 4 to keep the report concise. | fail→pass | 4,002 | 16,937 | +323% | 1 | 1 | 0% | 736 | 3,035 | +312% | 0 | 0 | — |
▸case-20 In the Hermes Logistics system update, the client requests adding real-time GPS route optimization before the scheduled May 1st launch. The team notes that May 1st is an internal launch target, whereas June 15th is the mandatory date required by the updated state transport regulation. The project sponsor suggests delaying the regulatory compliance features to June 15th while launching the optional GPS optimization on May 1st. Evaluate this scope change proposal and state which feature must take precedence for the May 1st release. | fail→pass | 9,051 | 20,939 | +131% | 1 | 1 | 0% | 1,458 | 3,620 | +148% | 0 | 0 | — |
▸case-21 For the Vulcan Core infrastructure project, Vendor Alpha provides a signed SLA guaranteeing 99.99% uptime with financial penalties for breach. Vendor Beta provides an unverified marketing brochure claiming 99.999% uptime. The lead engineer wants to select Vendor Beta because 99.999% is higher than 99.99%, treating both claims as equally reliable system availability constraints. Evaluate whether Vendor Beta's claim should be treated with the same reliability level as Vendor Alpha's contractual SLA. | pass→pass | 12,850 | 16,976 | +32% | 1 | 1 | 0% | 2,031 | 3,222 | +59% | 0 | 0 | — |
▸case-22 The Artemis Lunar Rover project charter sets a target hardware development budget of $2M with a noted 20% contingency buffer allowed by executive management. A preliminary vendor quote for the sensor array comes in at $2.3M. The procurement lead claims this quote violates an immovable budget limit and demands canceling the sensor module immediately. Assess whether the $2.3M quote exceeds the allowable project budget parameters. | pass→pass | 11,967 | 18,327 | +53% | 1 | 1 | 0% | 1,932 | 3,483 | +80% | 0 | 0 | — |