Task relevance
Keep real tasks visible. Let evidence decide what belongs in the engineering queue.
investigated cases passing all checks
Small synthetic set, not measured real-world accuracy.
The question is whether it becomes another forgotten note or the right work.
A customer call just ended. One sentence could change what the team ships next.
Useful AI needs more than a convincing answer. We evaluate task relevance, engineering readiness, and code implementation separately—and publish the limits alongside the results.
Latest Nebius results and live workflow checks. The dated results below remain available for comparison.
Keep real tasks visible. Let evidence decide what belongs in the engineering queue.
investigated cases passing all checks
Small synthetic set, not measured real-world accuracy.
Recognize when a request has enough context to become engineering work—and when it does not.
correct readiness decisions
Readiness is not plan correctness. Independent plan-quality review is still pending.
Test code changes against a separate, externally defined coding benchmark.
64/113 · full-cohort tasks passed
A separate Compress Cloud run, not a meeting-to-code success rate.
Separate measurements of task relevance, plan preparation and coding. Development fixtures are not independently labeled real-world accuracy. These scores must not be combined into an end-to-end success rate.
Meeting extraction: independently labeled capture precision and recall are not yet available. Transcript-upload acceptance is a user-journey check, not an accuracy estimate.
This archived report does not measure independently reviewed plan quality, human correction time, or a representative meeting-to-code success rate. Historical results do not establish current-model performance or competitor superiority.
The DeepSWE mark identifies Datacurve’s benchmark. Our result is a Light Reach evaluation, not a Datacurve endorsement or an official leaderboard entry.