README: the movement bottom line leads — multiply the prayer surface

A global prayer movement cannot run on one website: coverage stalls when there
is one place to see the task and one place to sign up. The opening now leads
with that insight and the fix (the same living map on every partner team's own
site — ownership breeds stewardship), trains three roles in the T4T spirit
(map maker / map multiplier / prayer mobilizer, t4tonline.org), and adds THE
PLAYBOOK: list partner teams -> keep the list in a secure collaborative CRM
(Disciple.Tools; the list is an attack surface) -> commission mobilizers ->
embed everywhere (Share button + utm attribution) -> train the trainer. The
craft story, glossary and quickstart remain for the map-maker persona.

README.md

@@ -1,11 +1,28 @@
 # doxa-maps — a JAMstack map bundler for vibe coders
 
-> **Built by a vibe coder, for vibe coders** — and for map‑maker multipliers who want to multiply
-> maps everywhere, to reach every people, in every place, for Jesus.
+> **Built by a vibe coder, for vibe coders** — and for map multipliers and prayer mobilizers who
+> want every people, in every place, prayed for by name.
 
-**The seemingly impossible part, first: one build composes all your maps, tables, and dashboards
-into a single‑page application — and that one SPA runs as a website, installs as a mobile app,
-and embeds on partner sites piece by piece (iframe or shadow DOM). Same code, every screen.**
+**A global prayer movement cannot run on one website.** With a single site carrying the map,
+coverage stalls in the hundreds of people groups — because there is exactly one place to see the
+task and one place to sign up. The way past the plateau is to **multiply the prayer surface**:
+the same living map embedded on every partner team's own website — each team seeing it on *their*
+site, owning it, stewarding it — all feeding one signup flow, all lighting up the moment someone
+commits to pray.
+
+**That is what this bundler builds.** One build turns every map into a self‑contained web
+component that embeds anywhere an embed script or URL works — team websites, WordPress,
+Squarespace, Wix, even internal boards and dashboards — and every map carries a **Share button**
+so any team can pass its map to the next team. In the spirit of **T4T — Training for Trainers**
+([t4tonline.org](https://t4tonline.org)), this README trains you three ways:
+
+1. **A map maker** — build every map you can imagine from one repo (glossary + quickstart below).
+2. **A map multiplier** — put the maps on every partner site (the Share button is the tool).
+3. **A prayer mobilizer** — run the campaign that multiplies the surface (**[the Playbook](#the-playbook--start-a-prayer-movement-with-this-map)**).
+
+**And the seemingly impossible part:** the same build also composes all your maps, tables, and
+dashboards into a single‑page application that runs as a website, installs as a mobile app, and
+embeds on partner sites piece by piece. *Same code, every screen.*
 
 <p align="center">
   <img src="docs/assets/spa-desktop.png" alt="The composed SPA on desktop — many maps, tables and dashboards in one app" width="680">
@@ -108,6 +125,29 @@ New to this? Read this table first. You do **not** need to memorize it — just
 
 ---
 
+## The Playbook — start a prayer movement with this map
+
+The learn‑by‑doing use case this bundler was built for. Five steps, trainable to any team:
+
+1. **List your partner teams.** Build a spreadsheet of every team you know that is working to
+   multiply disciples among the unreached — their websites, and the contact who can edit each site.
+2. **Keep the list in a secure, collaborative CRM — not a loose file.** That list of teams,
+   contacts, and sites is an **attack surface** in the wrong hands; protect the people on it.
+   [Disciple.Tools](https://disciple.tools) is an open‑source, multiplayer CRM built exactly for
+   tracking teams, contacts, and mobilization campaigns — privately.
+3. **Commission prayer mobilizers.** Assign real people to work the list — call, network, and ask
+   each team to put the prayer map on their site and present it to their spiritual family.
+4. **Embed everywhere.** The embed works anywhere a script or URL can go: team websites, WordPress,
+   Squarespace, Wix, link dashboards, internal boards and tools. Copy the snippet from the map's
+   **Share button** or from the staging page — it carries the full URL of whatever host serves
+   your maps, plus a `utm_source` tag so every site's traffic is measurable.
+5. **Train the trainer.** Teach each team to use the Share button to embed the map — then teach
+   them to train the *next* team the same way. The movement doesn't hang on one mobilization
+   team: every team that carries the map can multiply it.
+
+The result: one signup flow, a thousand doorways into it — and a map that visibly changes as
+people commit, so every team watches the task shrink on *their own* site.
+
 ## A word before you decide
 
 This architecture is probably different from what you're used to. **Different doesn't mean worse** — it