Visible jobs
Long work happens outside HTTP and comes back through status, events, and the worker.
Every teaching follows the same path: bring it in, shape the output, review it, then use it across notes, Ask, inbox, and sharing.
The product stays boring in the best way: every piece of work has a row, a status, and a visible next step.
done
done
transcribing
fetching transcript
Short answer
Across eleven teachings, suffering is framed as a place where God is present rather than absent.
Add a teaching manually or through a source. Retry only failed or waiting work, so staff do not create duplicate product paths.
A draft is generated from the transcript. Approve it, or request changes. Autosave is not training data.
Questions search this church’s teaching. Citations name the source. Nothing leaks across churches.
Invite staff. Campuses share knowledge from headquarters when you say so.
Long work happens outside HTTP and comes back through status, events, and the worker.
The church stays in the URL and database context, not a token or hidden header.
Ask and generated-note changes run through the eval package before they ship.