Orlando Grace Church
Orlando, FL
Prepared by Ministry of Order for The Church Executive AI Workshop · June 4, 2026 · Orlando
In the room: Jim Davis (Teaching Pastor), Robert Jackson (Executive Pastor), and your newly hired Worship Pastor.
Where you're starting from
Orlando Grace is the most technically ready church at the workshop. Robert is already building with Claude Code and Codex — an airgapped prayer-request automation and a three-way room-reservation sync. And Jim co-authored The Great Dechurching, the research the entire Rechurching framework is built on. So this packet isn't "get started with AI." It's "validate, document, and extend what you're already doing — and become the reference implementation the other four churches learn from."
Your recommended builds
1. Prayer Request System · Airgapped — you're already building this
Robert's instinct here is exactly right, and the research backs it. For the church's most sensitive data, the best practice is to reduce connectivity and refuse AI entirely — a logical air-gap inside the Workspace you already own. This packet's full brief documents why that design is correct so you can defend it to elders and hand the pattern to other churches. Treat this as your reference build. → Full brief: ideas/05-prayer-request-airgapped.md
2. Calendar & Room Conflict Sync — formalize the 3-way sync you're attempting
You're already wiring Google Calendar, Monday.com, and Planning Center. The brief's key upgrade: make Planning Center the single source of truth and mirror one-way, then add the nightly scan that catches not just room collisions but the same person double-booked across teams and over-loaded evening weeks. That turns a sync into an early-warning system. → Full brief: ideas/07-calendar-room-conflict-sync.md
3. Rechurching Diagnostic Suite — the flagship; you own the framework
With Jim's authorship, Orlando Grace is the natural home for the live version of the 20-point audit. It exists today only as a static PDF — no live-dashboard product exists. The flagship prototype in this repo shows what a green/yellow/red, data-scored version looks like. Of all five churches, you're best positioned to make this real. → Full brief: ideas/11-rechurching-diagnostic-suite.md · prototype on the hub at /prototype
4. Sermon Prep RAG Assistant — for the preaching team
A retrieval assistant grounded only on your own doctrine and approved commentary, with cite-or-refuse. Given how much hallucinated-citation risk there is in open chatbots, this gives the preaching team speed without fabricated quotes. Start no-code in NotebookLM this month. → Full brief: ideas/10-sermon-prep-rag-assistant.md
Your 90-day path
| Quarter | Move |
|---|---|
| Q1 (0–90 days) | Document the airgapped prayer system as the reference pattern. Make Planning Center the calendar source of truth. Pilot the Sermon RAG in NotebookLM. |
| Q2 | Add cross-team conflict detection to the calendar sync. Begin encoding the 20-point audit. |
| Q3 | Build out the Rechurching Diagnostic with data-backed signals; share the airgap + diagnostic patterns with the cohort. |
The one rule that governs all of it
From the workshop's security model: know what must never leave your trusted systems. Prayer requests and pastoral care notes never touch a third-party AI. Giving data is aggregated before analysis. Everything member-facing gets human review before it sends. You're already living this — keep it the non-negotiable.
Full idea library and the other churches' packets are on the Ministry of Order briefs hub.