The Creative Origin / Edition 004October 2026 · Published October 7

A continuing creative practice.

Keep
moving
forward.

Take what survived. Make it clearer.
Make it real. Carry it forward.

Follow the work
Carried into this editionStudio / 01
Motion study / 00:12 / Silent
An existing TCO study, still moving.

Origin / After Hours

Explore the study
Field work. Creative work. Work carried forward.A note on Edition 004

Edition 4.5 / The AI-assisted addendum

What carries
the work?

A week of working pieces, unfinished handoffs, and a clearer definition of continuity. The October 3 account returns here with its dates, sources, and limits intact.

Recovered October 3 writing · AI-assisted synthesis · Original reading copy retained

Read Edition 4.5 Original October 3 PDF

01 / The work in front of us

Take what survived.

A useful piece of work gives the next person
something to return to.

01In the field

ChurchOS by TCO

The service. The people. The work around Sunday. Follow the product and the published program that started this record.

Published work + continuing developmentExplore ChurchOS
02In the Studio

Give it form.

Identity, images, motion, and software. Start with an existing study. Change the palette. Make something of your own.

Origin / After Hours · Creative studiesEnter the Studio
03On the bench

Leave a trail.

Experiments with something to show for them. Open a question, inspect the work, and follow what it taught us.

Studies, prototypes, and recorded learningExplore TCO Lab
September 27, 2026 / Field noteAfter MoissonRead the Sunday field note

02 / A note on Edition 004

What we learned
should be visible
in what we make.

Keep moving forward.
The Creative Origin · October 3, 2026

Take what survived.

A useful experiment leaves something behind: a working object, a clearer question, a way for the next person to continue.

Moving forward asks for more than another beginning. It asks us to return to what exists, see it clearly, and make it usable beyond the person who made it.

Carry its history with it. Who made it. What changed. What worked. What still needs to be proven. Those details make a handoff possible; they let the next person continue with judgment.

Read the earlier Lab note
  1. 01 / ConvergenceBring the pieces together.
  2. 02 / EmbodimentPut the work in someone’s hands.
  3. 03 / ContinuityKeep what made it possible.
  4. 04 / ExecutionFinish something worth carrying.

Edition 004 / From the field

After Moisson

A Sunday field note about the distance between working software and a church experience people can depend on.

Based on Phil Baptiste’s firsthand account. These are observations from September 27, 2026.

The service exposed the gaps

Moisson brought months of work into a real church day. The program carried the pastor’s written message, but the planned remote video appearance did not happen. The stream suffered interruptions. Camera direction, projection, graphics, troubleshooting, and coordination competed for the same operator’s attention.

An experience that depends on one person holding every connection together is not yet a dependable system. Better software has to reduce that burden, and clear responsibilities and human support have to accompany it.

There was tangible progress

A twelve-page program review edition brought together the service order, the pastoral message, and selected hymn texts, with an editable source for corrections. The published program and the ChurchOS access-request page were reachable. Requesting access, however, is not the same as completing onboarding.

A local promotional display cycled through church information, the program, and an invitation to request access every 36 seconds. It demonstrated a useful presentation path; it was not yet commissioned as an always-on public channel.

Isolated corrections for Finance, invitation activation, and songbook integration also received testing. At the September 27 closeout, they had not been deployed. Those distinctions belong in the story.

What moving forward means

The next milestone is a repeatable Sunday: a dependable viewing destination, a usable program, a complete onboarding journey, and an operating handoff that someone else can follow.

Each part needs to work with the others, under real conditions, with a practiced fallback. Today produced useful work and a clearer account of what remains. The commitment now is to turn those pieces into an experience that asks less of the people serving.

Open the September 27 public program

03 / The continuing record

Earlier pages.
Still part of the story.

Each edition keeps its place.

003 / September 2026

It takes shape.

Open Edition 003 002 / September 2026

Work, kept.

Open Edition 002 001 / August 2026

A Sunday, issued.

Open FSBFMC’s issued program

The person behind the work

Phil Baptiste.
A practice of his own.

Photography, film, identities, and the ideas that become something else. Phil Baptiste’s personal body of work remains distinct from company work.

See Phil’s work

The end of this edition / A beginning

The work itself
can teach.

What is it? Where did it come from? What changed? What can we do with it now?

These ordinary questions are the beginning of TCO Basic: making the work understandable enough for someone else to use, repeat, and carry forward.

An opening inquiry, with human capability as the outcome. This example is an illustration; it does not establish that learning has transferred into real work.

Try one small decision / Fictional example

Community supperSaturday.
Seven o’clock.Poster / Revision 02 / Awaiting approval

The designer changed the time from six to seven and saved a new poster. The host has not approved that revision.

What happens before this goes to print?

Choose a next step to see what the available information supports.

Now imagine an edited photograph or a corrected program. The same question travels: which version, whose decision, and what is the next permitted step?