Working timelineJuly 31 is an internal preparation checkpoint; public competition deadlines remain TBA.
Competition schedule

Timeline

A staged launch separates interface stabilization, development resources, public validation, hidden evaluation, and the ICSE 2027 competition session.

Current phase
Data and protocol preparation
Internal checkpoint
July 31, 2026
Final session
ICSE 2027

The accepted proposal specifies milestone months rather than final deadlines. Dates below should be used for planning, not as binding submission cutoffs.

Planned competition sequence

  1. In progress

    Complete the first data, validator, and protocol pass

    Finish the first audit of the original cases, package the first validated new cases, run the Docker validator proof of concept, and publish working input/output and evaluation drafts.

    • Original 268-case audit status
    • First validated expansion cases
    • case.zip and result.zip draft
    • Docker validator end-to-end record
    • Website and Dataset Card draft
  2. Planned

    Development set and baselines released

    Release public development cases, conformance examples, evaluator documentation, and reproducible baseline Agents.

  3. Planned

    Public validation leaderboard opens

    Accept versioned Agent entries, run public validation cases, and return bounded diagnostic feedback.

  4. Planned

    Final submission freeze

    Freeze each team's selected Agent artifact, the interface version, evaluator, case manifests, and resource policy for hidden evaluation.

  5. Planned

    Final results and participant reports

    Complete hidden evaluation, audit finalist repairs, publish aggregate results, and collect eligible participant reports.

  6. Conference

    Competition session and results presentation

    Present the benchmark, leading systems, common failure modes, and final competition outcomes to the ICSE community.

What must be ready before public validation

Gate AAgent contract frozen

Entrypoint, input/output schemas, packaging, conformance tests, and failure semantics are versioned.

Gate BEvaluation policy frozen

Metrics, budgets, allowed APIs, network policy, tie-breakers, and submission limits are published.

Gate CDataset release audited

Splits, licensing, checksums, immutable paths, and near-duplicate grouping are verified.

Gate DEnd-to-end path tested

Example Agent submission, case execution, containerized build validation, structured result, and leaderboard update all succeed.

Freeze first, then run hidden cases

1Select final entry
2Freeze versions
3Run hidden set
4Audit results
5Publish ranking

The final hidden evaluation is expected to finish within one day under the initial proposal target. The exact queue, rerun window, and result publication time will be announced with final deadlines.

Where authoritative changes will appear

Any change to a milestone, interface, evaluator, dataset, or rule will be versioned and announced through the official competition website and the support channel selected by the organizers.