Service plan
Approved and blocked service items are visible without exposing real member data.
Sunday operations
First Sunday demo service.
SNAPSHOTSanitized snapshotA sample Sunday plan: service items, demo people, songbook references, packet handoff.
Intake, review, approval, role access, service planning, packet publishing, and the archive boundary. Real church identity and member records remain sealed.
Draft ready
One sermon approval remains open.
3 items
All items are synthetic fixtures.
Published sample
Demo users see role-safe details only.
Demo trail
No live sending in this cut.
Review lane
Sample approvals show the governed handoff from planning to Sunday-facing output.
Bulletin preview
Program copy contains service-facing fields only and synthetic fixture names.
Intake → review → approval → access
Governed Sunday loop.
ChurchOS keeps the real operational loop explicit: new people enter a review lane, approved roles unlock the right surfaces, and Sunday output is derived from approved service and worship state.
Workspace cuts
Three surfaces, one canon.
local_program runs the real Flask runtime for controlled pilot use.
demo_showcase is this static Vercel-safe presentation with synthetic content only.
builder_developer orients builders around fixtures, docs, and canon boundaries.
Intake
New person or team
Sample contacts use example.org and 555-0100 numbers.
Review
Human approval lane
Review records intent; agents do not promote truth.
Publish
Worship and program
Service items drive packets and public program details.
Archive
Reference boundary
Archive examples stay reference-only unless reviewed.