How It Works

The Weekly Sermon, Start to Finish

Every Sunday's sermon travels from the livestream to a published video mostly on its own. The work once done by hand now comes down to a few short taps. Nothing is shared and nothing is published until a person approves it.

The whole week

One picture, Sunday to published

Read it downward. The left side is everything that happens on its own. The right side is every moment a person decides something, and there are only a few.

  1. Before Sunday · The pastor

    Enters the sermon title and the scripture passages in the church calendar

  2. Sunday

    The service streams live on YouTube, exactly as it does today

  3. Monday

    Finds that Sunday’s service video and reads the captions YouTube made for it

  4. Monday

    Marks where the sermon starts and ends, and says how confident it is

  5. sends a link
    1Approval 1 · Abraham or John

    Confirm the start and end on a phone. Nothing has been downloaded or uploaded yet

  6. After approval 1

    Trims the sermon out of the service, levels the audio, saves to Drive, and stages the video unlisted

    approves
  7. ready to check
    2Approval 2 · Abraham or John

    Approve publishing, once the staged version looks right

  8. After approval 2

    Public on YouTube, emailed to the congregation and to VietChristian, added to this site and the podcast

    approves
  9. Then

    Proposes short vertical clips taken from the same sermon

  10. offers clips
    3Approval 3 · Abraham or John

    Pick which clips are worth making, then approve each finished clip

  11. After approval 3

    The chosen clips are made in the church’s style and go public

    picks
Automatic A person decides 3 approvals in a week

Your part

Three approvals, and one thing before Sunday

This is the entire human job. Everything not listed here runs without anyone.

  1. ◆
    Before Sunday · the pastor

    The pastor sets the title and passages

    Ahead of the service the pastor enters the sermon title and the scripture passages in the planning calendar on vietgrace.org. Everything downstream uses them: the video title, the description and its Bible Gateway links, and the tags on the audio file.

  2. 1
    Approval 1 · Abraham or John

    Confirm where the sermon starts and ends

    A link arrives by Telegram, a free messaging app much like a text message. It opens the page below: the sermon, the proposed start and end, and the service video itself so the times can be checked by ear. One tap approves. A different tap corrects the times and the system tries again.

    What has not happened yet: nothing has been downloaded, trimmed, or uploaded. This approval decides two timestamps and nothing else.

    The review page: sermon title, the source video, and the proposed start and end times.
    Verifytitle, video, proposed cut
    The command surface: tap a command to open the Telegram bot with it pre-filled.
    Acttap, then send in Telegram
  3. 2
    Approval 2 · Abraham or John

    Approve publishing

    By now the sermon has been trimmed, leveled, saved, and staged on YouTube as unlisted, which means it is viewable with the link but is neither public nor searchable. That staged video is the proof. When it looks right, approving publishing sends it everywhere at once.

    What this decides: the moment the congregation and VietChristian receive it. The system never makes a sermon public on its own.

  4. 3
    Approval 3 · Abraham or John

    Pick the short clips, then approve each one

    After a sermon is public, the system offers a few short vertical clips, the tall full-screen kind people watch on a phone. They arrive in the same Telegram chat, each with the quote it is built around. Tap the ones worth making and skip the rest. The finished clips are staged unlisted like the sermon was, and each one needs its own approval before it becomes public.

    Optional. A sermon is complete without clips. Nothing is made until someone picks, and no clip goes public without a second look.

Between your taps

What the system does on its own

Six jobs, all unattended. They are the left lane of the diagram above.

Monday morning

Finds the service

Checks the church YouTube channel, identifies Sunday's livestream, and collects the captions YouTube produced for it. Captions are the timed text of what was said.

Monday morning

Marks the sermon

An AI reads the transcript and finds where the message begins and ends, separating it from worship, announcements, and the closing. It reports how confident it is, so an uncertain week gets flagged.

Only if there are no captions

Transcribes locally

When YouTube produces no captions that week, a church computer makes the transcript from the audio itself. The recording never leaves that machine, and the week rejoins the normal path.

After approval 1

Cuts and levels

Downloads only the sermon span rather than the whole service, and copies it out without re-encoding, so the picture stays exactly as it was streamed. Then it levels the sound to the same broadcast loudness every week, because live audio drifts quiet and uneven.

After approval 1

Saves and stages

Writes the video and the audio to the church Google Drive and uploads the video to YouTube as unlisted. No email goes out and nothing is public.

After approval 2

Publishes and writes it up

Makes the video public, adds it to the Sermons playlist, sends the emails, and writes a short summary in Vietnamese and English for the sermon's page here and for the podcast feed.

Reach

One sermon becomes several Shorts

Most people now meet a message mid-scroll rather than by sitting down to an hour. So the same pipeline that trims the sermon takes one more step: it looks for moments that carry a whole thought on their own, and shapes them into short vertical clips that link back to the full sermon.

That reach is also what makes a clip risky. Lifted out of the sermon, a true sentence loses the context that held it steady, and it can land as something the pastor never meant. So no clip is published on its own judgement. Every candidate is graded, then put through a gate that can reject it outright, and a person still approves what goes out.

Full sermon · 2026-09-13
Điều Giúp Biết Tình Yêu Thương Là Gì · Mục Sư Trịnh Văn Khánh

Tội tôi hay xưng nhất với Chúa.

The sin I confess to God most often.

Hook
82
Weight
90
Alone
88
Council
83

Humble confession of failing to love; convicting and faithful.

Tình yêu thật là gì? Hãy nhìn thập tự giá.

What is real love? Look at the cross.

Hook
80
Weight
95
Alone
95
Council
82

Cross-defined love, doctrinally sound and self-contained.

Thù ghét là dấu của thế gian.

Hatred marks the world. Love marks the church.

Hook
75
Weight
88
Alone
92
Council
80

World=hatred/Cain vs church=love/Christ; matches text well.

The gate

What vets a clip before you see it

An AI agent here is an AI given one small job and nothing else. Not a chatbot you hold a conversation with: one question, one answer, and it is done. “Would this clip stop a scroll?” is that kind of job. Nobody asks a single AI “is this good enough to publish?” and takes its word for it, because a model asked a question that broad tends to agree with whoever asked it.

So the judgement is split into six narrow questions across two stages. A clip has to clear all of them before it reaches you.

1 Three marks, out of 100

The proposer scores every candidate it finds. These decide which moments are worth considering at all.

Hook

Would the opening seconds stop a scroll?

this clip: 82

Weight

Does it leave something lasting?

this clip: 90

Stands alone

Does it hold up with the sermon around it removed?

this clip: 88

2 Three lenses, each with a veto

A separate review reads each surviving clip against the sermon it came from. Any one lens below its floor cuts the clip, and the clip's overall mark is its weakest lens, so two strong answers can never outvote one bad one. If the review cannot run at all, the clip is cut rather than passed: it fails closed.

Doctrine

Is the teaching sound?

Checks the clip against Scripture and flags anything off.

floor 75 · this clip 90

Context

Does it survive being lifted out?

Reads the clip against the sermon around it, watching for a true sentence that turns into something the pastor never meant.

floor 70 · this clip 88

Power

Is it worth someone’s time?

Weighs whether it carries real force, or is only a tidy line.

floor 65 · this clip 83

Whatever survives is usually two or three clips out of a whole sermon, and a rejection is recorded with its reason so you can read why. Then it is still yours to pick, and yours to approve one by one. Nothing reaches the Page or the channel without that.

Where it lands

Everything at the same moment

Approving publishing sends the sermon to all of these at once: the video goes public on the church channel and joins the Sermons playlist, the audio goes to VietChristian with a direct download link so it can publish its own copy, the congregation is emailed, and the sermon appears here with its own page, a bilingual summary, an outline, and scripture links, as well as on the podcast feed.

YouTube YouTube
Public video, Sermons playlist, short clips
VietChristian VietChristian
MP3 sent to the publisher

Two promises

What is guaranteed

The system never publishes on its own. A person approves the trim, approves publishing, and approves each short clip. Nothing reaches the congregation before that.

The audio and video of every sermon are kept in the church Google Drive. A separate job makes each file shareable and records its real address, and it now runs every day, so a download link cannot quietly sit broken. The sermons page shows no download button at all until the file has a verified address, because no link is better than a link that fails.

If a sermon's files ever need to be rebuilt, they can be, without disturbing anything the congregation already has: the sermon stays published, the YouTube video is left alone, and no email is sent a second time. The audio email to VietChristian is held back entirely unless a working public download link exists, so the publisher never receives a message it cannot use.