# Decisions and the charter

> In short: A decision is something the production settled that should hold for every take, written down so people, the checks and CODA all work to it. The charter is the production's goal, audience and tone in a few sentences. This page explains how to write, propose, accept, amend and withdraw a decision.

Applies to: v0.13 · Last reviewed: 2026-11-02 · Canonical: https://docs.zymcos.com/product/decisions-and-charter/

Some things get settled once and should hold for every take: "everything is delivered at 2.39:1", "hero shots use only these models", "no take costs more than $2". A **decision** writes that down, with why, so the next person (and CODA) does not have to ask again. The **charter** is the shorter, softer record of what the production is for.

Both live in **Files**, under **Decisions**, below the nine folders. They are documents, not files: there is nothing to download, and they cannot be moved into a folder.

## The charter

Five short fields: **goal**, **audience**, **tone**, **deliverables** and **brand**, two thousand characters in all. Choose **Write the charter** (or **Edit**) at the top of Decisions. CODA reads the charter before every reply, so what you write here shapes what it suggests. In a Solo production anyone who can curate may edit it; in Studio you need the *approve* right.

## Writing a decision

Choose **New decision**. A decision has:

- a **title**;
- four short sections: **context** (what led to this), **decision** (what was decided), **alternatives considered** and **consequences**;
- optionally some **rules the checks can read**: an aspect ratio, a minimum resolution, models that are allowed or never allowed, or a most a take may cost.

Saving makes a **draft**. A draft has no number and can be edited or discarded freely. CODA can write a draft for you too: tell it what the production has agreed ("write that down as a production decision") and it drafts one for you to read. It never proposes or accepts for you.

## Propose, accept, amend, withdraw

| Step | What it does | Who |
| --- | --- | --- |
| **Propose** | Gives the draft its number (PDR-0001, PDR-0002…) and puts it up for acceptance | anyone who can curate |
| **Accept** | Puts the decision **in force**. Its text is then fixed | someone who can approve |
| **Amend** | Proposes a change to a decision in force. The accepted text keeps ruling until the amendment is accepted | anyone who can curate; accepting needs approve |
| **Withdraw** | Takes a decision out of force. It stays on record | someone who can approve |

Accepted text is never edited, only amended or replaced, so the history on each decision is complete. Numbers are never reused.

## What a decision does

A decision in force with rules is read by the **Production decisions** check on every request to make a take a final (see [Finals and requests](https://docs.zymcos.com/product/finals-and-requests/)). A take that breaks a rule fails that check, with the rule named. A decision with no rules is read by people and by CODA, which follows it over a passing preference or an older memory, and says so.

A decision can apply to the whole production, or, when drafted with CODA, to one scene, shot or Bible entry.

## The history

Each decision lists its steps in order, with the date, a mark on your own, and **with CODA** where CODA wrote the text. Steps are recorded against a private reference rather than a name, so if a person is later erased the history stays complete and unchanged.
