Every list in Mula starts at zero before it starts at something: a file with nothing in it yet, a stage nobody has touched, a queue with nothing left to do. These states are written once here rather than once per screen so a producer meets the same shape every time she meets nothing, and so this sheet is where a new screen’s empty state gets composed from, not invented fresh. Each one is .emptystate from section 4d, unchanged: one sentence that says what will fill the space, in her own words, and one action that starts it. None of them report that a list is empty, because she can already see that.
The very first screen a producer meets, before she has answered a single question. No illustration and no welcome mat: the sentence names the eleven questions she is about to answer, so the number matches the sitting she is walking into on the next screen.
The moment: signed up, no film yet.
Answer eleven questions and Mula builds the plan for the first one from them.
Start your first productionNot one dashed box but the real .stagecards grid, every card reading not started, because this is the first thing she sees the moment her plan exists and the truest empty state in the product does not hide the shape of the work ahead of her. One action for the whole page, matching the rule that a page carries one primary button: Covered comes first, so that is where it points. The four totals (12, 4, 12, 6) are the plan’s own structure from BRIEF-M2.md; only the done count changes, to zero.
The moment: a film with nothing done, the day the plan is built.
Nothing on Low Tide’s plan has started yet.
Low Tide’s own Permitted stage is genuinely at zero today, so this is not an invented scenario: nothing in it has started, and the one thing it is waiting on is her. The sentence names that thing instead of describing the stage’s condition, since "nothing has started" is what the ring already shows her.
The moment: a stage nothing has started in. Permitted, 0 of 4.
Everything else in Permitted, the filing, the city’s three days, the permit itself, waits on that one answer from you.
Confirm your 9 location daysThe register the brief was explicit about: this is not "all done." Fifteen tasks are locked and twelve are finished, so a queue with nothing in To do is a queue where everything left is waiting on someone else, not a queue that is over. The sentence says exactly who that is.
The moment: nothing owed by her, every open task moving or waiting on someone else.
The same instance already on the shared component sheet (section 4d), labelled here to the screen it belongs to. The first document that will ever land in her file is the policy itself, so the sentence names that document rather than the abstract idea of a file.
The moment: nothing in it, before the package is bound.
The policy lands here first. Everything you sign after it lands here as it’s signed, so the file is built by the time anyone asks to see it.
Add something to your filePermits and location days is genuinely at zero in Low Tide’s own file today. The small variant drops the heading, per section 4d’s own rule, since the group heading above it already said what the group is, and it drops the action too: the file screen’s own primary button, Add to the file, already covers it, so a second button on every one of four groups would be four competing invitations to press the same thing.
The moment: Permits and location days, 0 in the file.
Your permit lands here once the city issues it, after you confirm your 9 location days.
Bound but nothing issued yet is the moment right after the package places and before Mula has sent a single certificate. The sentence says when the first one shows up rather than that the list is short.
The moment: none issued, right after the package binds.
A location, your stage, or your rental house asks, and the certificate is in their inbox the same day.
Request a certificateNobody on this screen is added by hand: every row on it arrives because Mula read a signed agreement or a certificate went out. The sentence says that, so a producer never goes looking for an "add a person" button that does not exist.
The moment: nobody added, before any documents exist.
Everyone who needs paper from you, and everyone Mula reads a signed agreement for, shows up here on its own.
Add to your fileSaid in the terms D6 gives the screen: what gets checked and why it happens now instead of at delivery, since a scene can still be rewritten and a song can still be swapped in prep.
The moment: no cue list yet.
Every cue in your cut gets checked against where it’s going, media, term and territory, before you lock picture.
Add your music listThe screen exists because the timing is not obvious: script clearance is the slow one, so a producer who orders in the order she thinks of them first loses days she did not need to lose. The sentence puts the arithmetic ahead of the button.
The moment: none ordered.
Title and copyright come back in ten business days. Script clearance takes fifteen, so it’s the one to start first.
Order your reportsThe binder is close to empty even on a good day, since it cannot exist as one package until the file answers every line on the distributor’s own list. The sentence says what has to be true, not how few lines are checked.
The moment: nothing to bind.
This becomes one package the moment your file answers every line on your distributor’s list, not before.
See what’s missingThe one state in this sheet that is not a gap waiting to be filled: nothing is wrong here, there is simply nothing new. Kept to the exact line the brief gives it. The action does not start anything, since there is nothing to start; it returns her to the plan, which is where the next real thing will show up first.
The moment: caught up, nothing unread.
Before the first policy places, the billing page has nothing to show, and the sentence says exactly when that changes: once, at the first placement, never a subscription and never a percentage.
The moment: nothing charged yet.
The fee is charged once, when you place your first policy, and it shows up here as its own line.
See your number