Qudwah
Real-time translation of sermons and religious address.
Fidelity is the requirement — and it is the first thing speed gives up.
A congregation rarely shares one language. The address does not pause, cannot be rewound, and carries meaning that survives poorly in loose paraphrase — register, citation and cadence are part of what is being communicated, not decoration on top of it. Generic real-time translation optimises for speed and fluency. In this setting, fidelity matters more than either.
Register is not ornament in this genre. A sermon moves between address, citation and argument, and a listener reads the shift as part of the meaning: a quoted line is not the speaker's own claim, and a change of cadence marks where the argument turns. Translation that flattens all of it into one even voice returns the words and loses the shape.
The harder half is attribution. A quotation carries an origin, and a listener who cannot tell quotation from commentary has been handed something other than what was said. The failures that matter are the fluent ones — a sentence that reassigns authorship or softens a source, with no signal to the listener that anything has been lost.
How this case is written.
Every case answers the same six blocks, in the same order — the template is set out on the case-studies page. The sixth, what we would do differently, is the one a competitor will not copy.
The full case file — constraint, build, outcomes, and what we would change — is walked through in person.
The rest of this case is a conversation.
Ask what constrained it, where a person still decides, and what we would do differently if we started again. A demonstration answers none of those.