01 / Prepare
Gather the work.
Bring the service order, programs and media into a version people can review. Incoming material keeps its source and its approval state.
The Creative Origin / ChurchOSProduct experience / continuing development
ChurchOS by TCOˢ
The church
comes first.
The service. The people. The work around Sunday. A connected place for a church to carry its own responsibilities.
Enter the synthetic church ↗Public interactive walkthrough · Invented church and service · Browser-local changes · No church account required
The purpose
People should be able to continue without the maker supplying every missing connection.
TCO Basic makes the responsibilities understandable. TCO Lab makes the simulated boundaries visible. Forge supplies the continuing pattern: prepare, revise, keep and return to the same Work.
Follow the service journey ↓01 / The work surrounding Sunday
Before. During.
After.
A service is a sequence of decisions, contributions and outcomes. ChurchOS brings that journey into view. This overview describes the product’s purpose; the demo identifies its own supported workflows.
02 / Approve
Know the version.
The responsible person reviews an exact revision. Preparation and approval remain distinguishable.
03 / Participate
Find what matters.
People approach the same church through their own responsibilities: reading, preparing, approving or operating.
04 / Return
Keep the record.
Preserve the published work and what happened, so someone can understand the service after Sunday ends.
02 / The next experience
Quiet until
it is useful.
Woulo / Founder design direction, October 9
Implementation and human testing continue.
The church owns the surrounding environment. Woulo is the proposed continuous surface for finding information, asking questions and performing permitted work.
The direction begins with a recognizable origin and reveals what matters in context. Information and operation have distinct orientations; moving a control does not grant permission or execute a consequential action.
What is being tested?
Origin-led navigation, persistent church context, role-shaped information, reversible transitions, and keyboard or tap alternatives to gestures. These are design candidates; they do not establish a live release or device acceptance.
A synthetic churchA quiet, church-owned environment
Example service · Revision 02 · DraftInformation
From Phil’s sketches
Original sketch / historical
● Church context
TodayChurch identityFor You
The early composition established context, identity and relevance. Its blue drawing field was not an approved palette.
Direction after the corrections
● Persistent church context
One Woulo surface
Read · Ask · Permitted work
Read · Ask · Permitted work
The Scroll became the reveal; Soul of the Scroll names the information inside it. Modern glass replaces literal parchment. One origin and one surface; top receives information, bottom presents information to control.
Concept and original sketches: Phil Baptiste. This compact diagram and interactive visual interpretation: Codex, for review. It summarizes selected source direction; the original sketches and private handoff documents remain unchanged.
03 / Start with the experience
Enter the
Synthetic Lab.
Open an invented church week and do the work. As Secretary, prepare the service and send an exact revision to Pastor. Approve it, publish the team packet and public program, then rehearse loading the approved revision as Media operator. Leave and return in the same browser to continue.
Open the interactive ChurchOS walkthrough ↗The walkthrough is browser-local. It demonstrates the sequence and its limits; it does not sign you into a church, publish to a congregation, or control equipment.
Already part of FSBFMC?
Continue through your church’s existing ChurchOS account and assigned permissions. This entrance accesses a real church environment.
Open FSBFMC’s ChurchOS ↗