Skip to content
← Back to research index

abstract indexed · arXiv 2609.39325 · updated 2026-10-18

WorkGenesis: Building the Worlds That Teach Agents to Work

First page of WorkGenesis: Building the Worlds That Teach Agents to Work
From the original paper · arXiv 2609.39325Page 1. Select the image to read the PDF.

WorkGenesis replaces expert-authored occupational training tasks with an automated pipeline that retrieves real public files guided by O*NET knowledge, synthesizes the surrounding task context and itemwise rubric, and iteratively repairs defects via execution-guided consistency checks. The cost is substantial API inference for retrieval, synthesis, rendering reference deliverables, and multi-round auditing, plus engineering effort to build the pipeline; the reader cannot replicate the 35B SFT run on a 24 GB GPU and would need API fine-tuning or a smaller model. Failures include residual rubric or task defects passing the automated audit, distribution mismatch between synthesized tasks and the reader's actual workload, and benchmark gains that may not transfer to domain-specific production tasks.

For solo builders

A possible application for this research area. Paper-specific feasibility still needs a full-paper review.

You already need task-specific training and want to reduce its memory or compute cost.

What you would change

Change only the training technique on a small controlled run after checking prerequisites.

Try the idea on your product

A proposed first test. Set your budget and success criteria before running it.

Change only the training technique on a small controlled run after checking prerequisites.

Compare against

Your current training recipe with the same model, data split, and evaluation.

  1. Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
  2. Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
  3. Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
  4. Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.

What to measure

Held-out quality, peak memory, training time, and full compute cost to the target quality.

When to keep it

Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.

Download test plan ↓

abstract indexedPaperraft next step

Do not allocate compute yet.

This page uses the abstract and public adoption signal only. Request the deep report before relying on its recommendation.

Abstract-level screening only. Risks and infrastructure may not have been evaluated. This recommendation is not a reproduced result.
minimum test setup
not reported
published evidence setup
not reported
source-linked claims
0 of 2
exposure checks
0 of 8

Why it was shortlisted

The technical change, research area, and reason it entered the archive.

recommendation
test
research area
efficient training
technical change
Evidence-grounded synthetic work-task generation with execution-based verification
published
2026-09-30

The data-generation pipeline is reproducible with third-party APIs at modest cost, but its value for the reader's specific agent workload is unproven and the reported training setup exceeds local hardware, so a small-scale pilot is warranted before adoption.

About the technical core

Equations have not been fetched yet.

When reading the methods, identify the rule, algorithm, or evaluation protocol that produces the claimed change. An equation is useful here only if it explains that mechanism.

Inspect the original paper

Claims and evidence

A claim is source-linked only when the PDF page and matching excerpt are available.

  1. claim 01Paperraft inference
    Read the brief interpretation

    WorkGenesis replaces expert-authored occupational training tasks with an automated pipeline that retrieves real public files guided by O*NET knowledge, synthesizes the surrounding task context and itemwise rubric, and iteratively repairs defects via execution-guided consistency checks. The cost is substantial API inference for retrieval, synthesis, rendering reference deliverables, and multi-round auditing, plus engineering effort to build the pipeline; the reader cannot replicate the 35B SFT run on a 24 GB GPU and would need API fine-tuning or a smaller model. Failures include residual rubric or task defects passing the automated audit, distribution mismatch between synthesized tasks and the reader's actual workload, and benchmark gains that may not transfer to domain-specific production tasks.

    This is a Paperraft inference. It is not pinned to a verified PDF passage.

    Inspect the source
  2. claim 02Paperraft inference

    A 35B model SFT-trained on 20K WorkGenesis-synthesized tasks scores 31.00 versus 24.79 average for comparable baselines across GDPvalAA-v2, APEX-Agents-AA, and JobBench, and reportedly surpasses DeepSeek-V4-Pro-Preview on these benchmarks.

    This is a Paperraft inference. It is not pinned to a verified PDF passage.

    Inspect the source

Exposure map

Author findings, Paperraft interpretations, and the next check. Missing analysis never counts as evidence of safety.

quality

Still unknown

Which tasks improve, and which regress against the baseline?

compute and memory

Still unknown

What memory, hardware, and total compute does the complete method require?

latency

Still unknown

Are startup time, typical response time, and slow requests measured separately?

operations

Still unknown

What must be monitored, maintained, and rolled back?

software compatibility

Still unknown

Does the implementation support your model, runtime, and hardware?

security

Still unknown

What new data access, permissions, or trust boundaries does it introduce?

data and training

Still unknown

What data preparation or training is required, and is it included in the cost?

reproducibility

Still unknown

Are code, versions, inputs, and evaluation scripts available?

Continue the investigation

A reading guide for efficient training.

Editorial prompts, not findings from this paper or a validated test plan. Detailed analysis is still pending for the topics below.

What to inspect

Which assumptions does the proposed method need, and where might your workload violate them?

Plan a fair comparison

Identify the baseline, metric, dataset, and experimental settings in the paper. Which can you match?

Questions for adoption

What implementation and evaluation artifacts are available, and what would you need to supply?

Read the paper with these questions

Inside the paper

Preview the first 3 pages of the original PDF. Click the stack to turn the page.

The downloadable skill includes SKILL.md and evidence.json, with recorded findings and unanswered checks. TRY-IT.md adds a product test plan and a blank results sheet.

A reading aid for your agent. Findings still need validation.

Page 1 of 3
Open this page in the PDF ↗

Provisional research brief updated 2026-10-18. Paperraft has not reproduced this experiment.

Discuss this paper

Question a claim, compare interpretations, or share what happened when you tried the method.

Join the conversation on GitHub. Use this paper's arXiv ID in the title when starting a discussion.

arXiv 2609.39325

Comments are public and separate from Paperraft's research brief. When sharing a result, include the model, hardware, baseline and a link to your work.