Contracts

How a game's contract is drafted, submitted, signed and locked, and what changes are still allowed at each step.

Studio

Every project has one contract. It records who made the game, each developer's part and the pool of shares (see How a game is split). It moves through three steps, Draft, Submitted and Approved, and once approved it never changes. Contracts belong to weeks, not cycles: a contract carries the studio week of its date, and nobody opens a week.

The three steps

Draft

Generated at registration with the default split. The project's developers and owners correct names and parts freely. Nobody can sign yet.

Submitted

Submitting freezes the terms and their SHA-256 hash and makes the version's PDF. Every signer is told. Developers (and any leaver) sign this version.

Approved

Every signer has signed the same version. The last signature approves the game for launch, locks the contract and makes the sealed signed contract.

A contract's three steps. Registering a project creates the contract as a Draft, which developers and owners edit freely. Submitting it makes version 1 with its PDF. While Submitted, any change to names or parts makes a new version and clears every signature. When the last signer signs the current version, it is Approved and locked for good.

Before submitting, the split must stand: 1 to 10 developers, each once, each at least 10%, and the parts adding up to exactly what the pool leaves. Otherwise Submit is refused with the reason, for example "The developers' parts add up to 60%; with 2 developers they must add up to 70%". The Edit names and parts sheet checks the same as you type and keeps Save names and parts disabled until the split makes 100%.

Blockout Games is a group of developers, not a company, so the contract names no company details: the studio is the group working under that name, acting through its owners in the panel, and the contract is governed by the laws of Quebec and Canada. Nothing has to be filled in before a contract is submitted.

What locks when

  • After submission, names and parts can still change, but any change makes a new version with a new PDF and deletes every signature. Everyone is told. The tab's Version history lists every version with what changed from the one before.

  • After approval, nothing changes the contract, not even an owner. The API answers every change with a refusal.

Saving the same names and parts again changes nothing: no new version, no notifications.

A developer removed by someone else becomes a leaver. They are told at once, even in a draft. The PDF names them as leaving at 0% with their own signature block, and the contract cannot be approved until they sign: their signature is their consent to leave. They stay a signer of every later version until approval. Naming them a developer again removes them from the leavers.

Who may do what

Any member

Read every project, contract and its shares; register a project.

A developer on the project

Correct the draft, submit, sign, download its PDFs, give a game-less project its game.

A leaver

Sign and download its PDFs.

An owner

Correct and submit any contract, download its PDFs, give a project its game. An owner who is not on the project does not sign it.

New developers must be studio members who have signed in at least once; anyone else is refused with "Choose studio members who have signed in".

Notifications

Everyone the contract names is told when it moves, except the person who made the change:

New project

Each developer, when someone registers the project with them on it.

Contract edited

Everyone named before or after, when the draft's names or parts change.

Contract to sign

Every signer, when the contract is submitted.

Contract changed

Everyone named, when a submitted contract changes and becomes a new version.

Signature cleared

Instead of "Contract changed", to whoever had already signed the old version.

Removed from the project

The developer removed, who becomes a leaver.

Someone signed

Every signer, with how many of how many have signed.

Contract approved

Every signer, when the last signature locks it.

They are in the Contracts group of Notifications.

How signing works: Signing a contract. Where it appears: the game's Contract tab.

API routes for panel developers

The tab calls these routes with the member's session. Every change also needs the x-requested-with header the panel sends.

PUT/v1/studio/projects/:id/contract

Saves the names and parts: shares, each a userId with its basisPoints (at least 1,000).

POST/v1/studio/projects/:id/contract/submit

POST/v1/studio/projects/:id/contract/sign

GET/v1/studio/projects/:id/contract/pdf

The last takes version and kind (draft or final).

What each status code means
  • 400: the split does not stand; the answer names the field, such as "At least 10%".

  • 403: the asker may not do this.

  • 404: no such project or document.

  • 409: the current state forbids it, such as a change after approval, submitting twice, or signing twice.

Updated