A scan Mula can’t read. A card the bank declines. A filing the city sends back. Something breaks on both sides of this product, often in the same afternoon, and a producer meeting it cold needs the same three answers every time rather than a different apology on every screen: what happened, whose fault it is, and what happens now and when. Whose fault is not optional. A producer who can’t tell whether she broke it or Mula broke it picks up the phone, and that call is the cost of leaving it out. Every block here is .failblock from section 4d, unchanged, with data-state="mula" on the ones that are on us. Coral sits on the state word alone, because a producer reading thirteen of these on one sheet should not feel shouted at.
The same instance already on the shared component sheet (section 4d), labelled here to the two screens that both hand a document to Mula to read: the intake and the file. A scan that will not read is nobody’s mistake, so the state word stays coral and the fix is a person, not a retry button.
Not your fault, and not really anyone’s. It’s a scan of a scan, and the text on it isn’t text.
Somebody at Mula reads it by hand within the hour. You’ll hear either way, and nothing else on your file waits on it.
The one failure in this whole product with real money attached, so the sentence says plainly that nothing moved: no coverage, no charge. A producer who thinks she might be covered on a card that was declined is the worst version of this screen.
The bank’s, or the card’s. Not something Mula did.
Nothing is placed and nothing is charged. Coverage isn’t in force until it’s placed. Try another card.
The same instance already on the shared component sheet (section 4d): the Vernon warehouse’s own correction, M6's whole guarantee made visible. This is the one failure in the product that is already built as a real screen, certificate-fix.html, so the action here routes to it rather than standing in for it.
Mula’s. The wording came from the agreement you gave us and Mula read it short.
The corrected certificate goes out within the hour, to the same people. The fee is not charged again.
A name that does not match is the one failure a producer can create by typing, so the fault line names who typed it while still telling her exactly where to fix it. The stake is physical, not abstract: the brief’s own line is that the counter does not release the gear on a name that does not match.
Whoever typed it, and it’s fixable in Settings.
The certificate can’t go out on a name that doesn’t match. The counter won’t release the gear on it either.
M5's promise is that the timeline is told straight on Monday, not discovered on Thursday, so a bounced filing gets the same treatment: real dates, worked backward from the refiling, not a vague "delayed." The scheduled-wording requirement is the city’s own, pinned in BRIEF-M3.md, so this is the honest way that requirement bounces a filing back.
The city’s own requirement, whether or not it feels reasonable.
It asked for scheduled wording instead of blanket, the way its own form requires. Refile today and the three business days restart from today, Wednesday. That puts the permit on Monday September 14, the same morning your first truck rolls.
A schedule Mula cannot read is not a dead end: the segmented picker already on delivery.html exists for exactly this, so the fix is the screen’s own second path rather than a new one.
Nobody’s. Schedules come in every format a distributor’s legal team has ever used.
Pick your distributor type instead, and Mula matches your file against the standard list for it.
The same document-reading problem as the file, on a license instead of an agreement, and the same honest answer: nobody knows what it clears until it is read, which is the real risk sitting in the cue list until then.
Nobody’s. It’s the same kind of scan problem, on a license instead of an agreement.
Nobody knows what that license actually clears until it’s read, and that’s the real risk sitting in your cue list.
D8's own point: a finding is why the report exists, not a defect in it. The example is the exact kind of finding D8 names, a phone number that turns out to be real, and the sentence says outright that catching it now is cheaper than catching it in delivery.
Nobody’s, and it’s the reason the report exists.
A character’s phone number in the script matches a real one in service. Change it before the shoot and it’s a line in the script. Catch it in delivery and it’s a reshoot.
D9's whole value is that the attorney already has everything, so the honest failure is the one place that is not yet true. The composer agreement, out for signature since September 1, is the real gap in Low Tide’s own file today, so the block names it rather than a placeholder document.
Nobody’s. The opinion can’t be finished without it.
It’s the signed composer agreement. It’s out for signature since September 1, and the opinion waits on it.
The one binder failure that is on Mula: the document exists, and something happened to it after Mula stored it. The fix is a re-upload rather than a support ticket, because the binder’s own order does not change when one line is temporarily missing.
Mula’s, if Mula stored it wrong. The file exists. Something happened to it on the way in.
Re-upload it and the binder builds around it, same order, same fourteen lines.
A bounced email is the address’s fault, never the message’s, and the fix lives one screen away in Settings rather than in a support flow.
The address, not the message.
It’s on file as dani@reyespictures.com. Update it in Settings and Mula sends this one again.
The smallest failure in the product and the only one with no stake attached to it at all: a link just does not last forever, and the fix is one press away.
Nobody’s. Links just don’t last.
Links last an hour. Here’s a new one.
The one failure block that answers for the whole product rather than one screen, and the only place "Mula’s" is said without a qualifier. It is what every screen falls back to when nothing more specific applies, which is why it names a person rather than only a retry.
Mula’s, said in those words. Not yours, and not something you did on this screen.
It’s being looked at. Try again in a few minutes, and here’s a person if you’d rather talk to one.