Book a call

Repository task supply

Repository tasks with runnable environments and verifiable outcomes.

Commission coding, investigation, terminal and tool-use tasks built around approved repositories and your target agent setup. Each accepted package includes a pinned starting state, reference evidence, outcome checks and reproducible handoff instructions.

Book a call

Proposed

Proposed scope
1,000+ accepted tasks, subject to representative-batch results and confirmed capacity.
First commitment
A paid representative batch with agreed acceptance criteria.
Delivery schedule
First delivery, full completion and review milestones set in the production proposal.

Purchase unit

What an accepted repository task includes

One accepted task is a uniquely identified assignment, starting state, reference and grading package that passes the agreed review. Several tasks may share a repository or runtime base. Delivery reporting separates environments, task families, accepted instances and model rollouts.

You receive versioned task briefs, runnable workspace assets, verifiers, reference evidence, reset instructions and a delivery manifest. Source revisions, permissions and known public-answer exposure are recorded. Where external facts affect correctness, the package includes the required tool state and checks its effect on the outcome.

Container or Harbor integration is validated in the representative batch. Additional adapters and data packages are scoped separately. The proposal itemizes setup, accepted-task or milestone pricing, compute, usage rights, corrections and delivery responsibilities.

Buyer task catalog

Task types

End-to-end software projects

1 task type

Commission coherent software projects with linked milestones and final integration requirements. Later work depends on earlier changes, so success requires preserving prior behavior while completing the whole assignment. Session handoffs, checkpoints and review rounds can be included where useful. The representative batch validates the requested persistence, restoration and grading behavior before you commit to a larger project collection.

Configure

  • Feature, migration or modernization
  • Milestone dependencies
  • Sustained or multi-session work
  • Checkpoints
  • Review feedback
  • Terminal/API/MCP
  • Calibrated difficulty

Illustrative tasks

  • Migrate a service and its clients
  • Deliver a database-to-UI feature
  • Modernize a subsystem across linked review rounds

Operating panel

Project: Migrate a versioned service. Milestones: Data compatibility, API changes and client updates. Success check: Final integration plus preserved earlier requirements. Handoff: Baseline, dependency map, reference and checkpoint checks where commissioned.

Showing 1 of 1 task types in this category

These are configurable task specifications. Availability and the selected setup are confirmed during scoping.

Filter task types

0 active filters

Interface
Outcome
State
Horizon
Delivery and signal

Acceptance method

Review the package in your runner

The paid representative batch lets your team inspect a successful reference, relevant incorrect-result controls, grading isolation and clean resets. Calibration names the model, harness and execution budget. RL delivery additionally validates episode behavior, rewards, export and the agreed concurrency.

  1. 01

    Define

    Agree the capability, task family, interface and acceptance criteria.

  2. 02

    Validate

    Run the representative batch and resolve package or integration defects.

  3. 03

    Produce

    Deliver the accepted scope against signed milestones and review rules.

  4. 04

    Handoff

    Supply versioned assets, validation logs and the agreed correction record.

Next step

What should your agent complete in the repository?

Tell us what your agent should complete and where it should run.

Book a call