EigenLab Yukon participation

1. Participation and reference results

EigenLab Yukon is a collaborative partner category for the 2026 Virtual Embryo Challenge. It appears as a single reference entry when public results are enabled. Its results do not take an official prize position or displace an eligible team. The partner team and its members are not eligible for the Challenge’s official prizes through their Yukon participation.

Eigen Labs administers its own contest and additional awards. Any reference comparison used to determine its prize pool is separate from official VE prize eligibility. Eigen Labs is responsible for publishing its award criteria, contribution-points formula and distribution terms.

2. Registration and team membership

Every participant must register directly with VE using a verified sign-in, provide the required registration information, and personally accept the current Challenge Rules and Terms of Use. One person may have only one account and one active team. Applying to Yukon does not itself join or transfer a VE team.

The EigenLab Yukon partner team has no member-count limit. It may include Eigen Labs employees, contractors and independent participants. These are partner-specific exceptions to the ordinary team-size and mixed-capacity restrictions; they do not change the requirements for ordinary teams. Operating the partner contest does not itself exclude Eigen Labs personnel from this non-prize partner category. Restrictions on access to held-out data, conflicts of interest, lawful participation and conduct still apply.

3. One-way transfer for this edition

A member of an ordinary team may join Yukon through a valid invitation and the transfer confirmation. Once a participant joins the partner category, they cannot join or create an ordinary team for the remainder of the 2026 edition, even if they later leave Yukon. This restriction does not automatically extend to future editions.

Previous submissions and scores remain with the original team; they do not transfer to Yukon. A departing captain must hand over captaincy if other members remain. If the transfer leaves the original team empty, that team is archived and excluded from subsequent rankings and awards, while its historical results are retained.

4. Collaboration and submission allowances

During the collaborative phase, active, authorized Yukon participants may share and build on executable code, fitted models and weights, methods, and submission feedback within the team, subject to the rights and licences governing those materials. Sharing methods is permitted; transferring or pooling personal submission allowances is not.

During P2, each member has eight submissions per subtask per UTC day. Each T2 subtask has its own allowance: submitting once to each of the three T2 subtasks uses one attempt in each of three separate allowances. Website and API submissions use the same allowances. Another member’s unused allowance cannot be used to obtain extra attempts for your own entry.

Submissions must use the submitting member’s personal API key or signed-in account. A member may authorize Yukon to submit using their personal key; attribution and quota remain with that member. A partner service credential is read-only and does not authorize submissions. VE checks current membership and required agreements when a submission is requested.

5. Final phase

The Yukon collaborative phase must end before the P3 transition on 27 October 2026. Participants may use the history shared during the collaborative phase to develop their final P3 methods independently. P3 methods, prediction files and detailed evaluation feedback must remain private from other participants until the final score announcement on 11 December 2026. Authorized contest operators may process them for scoring and verification; this does not make them available for participant collaboration.

P3 starts on 27 October 2026 at 09:00 America/Los_Angeles (16:00 UTC). Members may continue P2 validation submissions until they explicitly obtain the official validation answers or have a first P3 submission accepted. Either action permanently stops that member’s P2 submissions across all tasks. Accessing validation data uses no P3 attempt. Frozen P2 preserves only results scored before the P3 opening cutoff; later results appear only on live Validation.

For P3 final records, VE’s team-scoped service and captain export expose only stable member and submission identifiers, board information, submission status, headline scores when scores are visible, and basic scoring-validity information. They do not expose model or architecture descriptions, method summaries, prediction files, file hashes, rejection diagnostics, evidence, or detailed evaluation metrics. A member retains access to their own private submission details. Captain status does not grant access to another member’s P3 details or evidence.

The API does not automatically release private P3 information when a deadline passes. Any subsequent sharing with Eigen Labs operators requires a separate reviewed release after the P3 submission deadline; disclosure to other participants remains subject to the 11 December final-announcement restriction above.

During P3, each member has two final submissions per available test board for the entire phase, rather than a daily allowance. Final submissions are due through 2 December 2026 (UTC). The VE timeline governs phase dates. Public leaderboard scores remain subject to VE’s published score-display rules; privacy of methods and files does not imply a hidden public leaderboard.

6. Data, identity and access

VE’s data-use, held-out-data, publication and attribution requirements continue to apply. Showing an authorized VE download link within Yukon does not grant permission to redistribute the dataset publicly or authorize additional uses of data or model weights outside the applicable terms.

The team-scoped partner service can receive member identifiers, verified identity information, membership and required-agreement status, material-access eligibility, and submission records needed for onboarding and verification. Ordinary Yukon members cannot see other members’ names or email addresses in VE’s team interface; captains and authorized service operators retain the access needed to administer the team.

Access to hosted shared materials and future updates requires active membership and the required agreements. Yukon checks membership daily and removes access within 24 hours of confirmed departure, removal or explicit VE notice. During a VE API outage, no new participants are admitted; existing access follows the last verified status unless an explicit removal notice is received. This cannot remotely erase copies already downloaded.

Leaving the team blocks new submissions attributed to it. Submissions accepted and cleared for scoring before an ordinary departure may finish and remain available for team verification. Submissions still awaiting required evidence are cancelled on departure. Withdrawing a required agreement or disqualification cancels unfinished submissions. Historical records are retained.