Models and versions

A model is a lineage: a name you chose, and every version you have entered under it. A version is one submission: two files and their two hashes.

Versions of one model replace one another. A new one that passes its trial supersedes the previous one, inherits its rating, and takes its place on the ladder. Different models never replace each other: they are separate entries with separate ratings, they can sit on the same ladder at the same time, and one of yours beating another of yours is an ordinary result.

A season may limit how many of your models enter it.

The name is the key, and it is yours

Your model’s name identifies it, and must be unique among your own entries for a game. The site addresses its page by id:

/models/{id}          the model, and its whole version history
/models/{id}/v3       one version of it

• Two competitors may hold the same name. The platform decides nothing on a name. Your account is your identity: signing in with any of the site’s sign-in providers establishes it, and that is the only thing a provider does here.
• You can edit the name at any time. The name is a label and the id is the address, so a rename breaks no link and moves no rating.
• No repository is involved. A model is tied to no GitHub repository: every ceiling on a competitor is a season rule, none of them mentions one, and creating a model never waits on GitHub.

Creating one

await fetch('/v1/games/ants/models', {
  method: 'POST',
  credentials: 'same-origin',
  headers: {'Content-Type': 'application/json'},
  body: JSON.stringify({ name: 'Nano probe' })
});

The platform refuses a name you already hold in this game with model_name_taken, whatever its case; a name another competitor holds does not matter.

Nothing on this path reaches GitHub, so creating a model works even while GitHub is down.

Creating a model enters nothing. It starts no clock, costs no attempt, and puts nothing on a ladder; submitting a version does that.

Version numbers restart per model

Your second model’s first version is v1. Numbering across models would start a new lineage at v4 because of an unrelated earlier model, and no page could explain that number.

The platform assigns the number, one past this model’s highest; you do not choose it.

Retiring one

A retired model takes no new versions and frees its slot against a season’s limit on how many models one competitor may enter. Retiring withdraws nothing: every version keeps its rating, its rank and its place in every match it played, since a standing records what happened. You can reverse a retirement, and it does not restart the version series.

What is per model, and what is per competitor

The five rows the season sets are season rules, and all are absent by default. A season’s own page shows the ones it sets. GET /v1/games/{game}/submission reports your standing against the model limit, the admission limit, the version caps and the submission interval before you make a request. The submission itself answers the duplicate-weights rule, since it needs your weights’ hash. A season may also declare how many of your models may sit in one weight class, and the platform does not enforce that one yet.

More

• Submitting a version: putting a version under a model
• The life of a version: what happens to it after that
• Seasons: the rules a season may declare