Ritual Studio · How Changes Flow

How changes flow

“Can we outline the system we'll use if changes are made internally? Like website, OS, App, Automated emails, marketing, sms. how they connect and trickle to one another.”

You asked: "Can we outline the system we'll use if changes are made internally? Like website, OS, App, Automated emails, marketing, sms. how they connect and trickle to one another." This page is that system. The short version: every fact lives in exactly one place, a change is decided there first, then it is pushed out to every surface that carries it, and nothing is called done until a scan of all surfaces comes back clean. Below is where the facts live, who owns each surface, the order things move in, and your Sep 8 website updates traced through the whole chain as a worked example.

Updated September 9, 2026

Where the truth lives

Three places hold every decided fact. If a number or a line is not in one of these, it is not decided yet.
Membership Rules page

The offer and every policy behind it: the four tiers, standard and founding prices, sessions and perks per plan, founding terms and extras, the 4 week billing cycle, upgrades and downgrades, cancellation, discounts (Those Who Serve, household), session and booking rules, drop-ins and session packs, loyalty and referrals. Every rule carries a status, your open decisions are listed at the top, and your Looks good on a section is the sign-off. If a number is not on this page, it is not decided yet.

Open →
Social Playbook, approved words

The words we use and the words we never use, in your voice. Every caption, email, text, page and notification is written against this list. Phrases you have retired live here too, so the scan knows what to catch.

Open →
Content Studio

The 27 week content bank. You approve two weeks at a time and only approved posts get scheduled. When a fact changes, the whole bank is rewritten to match, not just the next two weeks, so nothing stale is waiting in the queue for month four.

Open →

The surfaces, and who owns each

Every place a fact can appear, how to request a change there, and how it propagates.
Website, ritualstudiospa.com (pages, popup, FAQ, blog)
Punit
No store build
How to request
Post in Slack and tag Punit. Link the rules page section the change comes from so the words and the numbers are already decided when he starts.
How it propagates
Punit edits and publishes. The site is live the moment he publishes, and it is the surface most people see, so it is also where a stale number does the most damage. The blog lives here as well and follows the same path.
How we verify
After Punit publishes, Autosterea scans the live site for old names, numbers, dates and retired phrases, then a second reader checks each changed page against the rules page line by line.
RitualOS web app, app.ritualstudiospa.com
Our dev team builds, Autosterea verifies
No store build
How to request
Through the Request Center once it is live. Until then, Slack or the feedback box on the hub page the change belongs to. Describe the outcome you want, not the fix.
How it propagates
Every change lands on dev.ritualstudiospa.com first, gets verified there, then moves to production. This is where the pricing catalog, discount codes, plan perks, receipts, notification templates and all member-facing copy live. The catalog is locked to the approved numbers, so a price that does not match the rules page is rejected by the system rather than quietly saved.
How we verify
Checked on dev, checked again on production, then the same scan and second-reader review as every other surface. For money changes we also run a test checkout on dev before production moves.
Mobile app, everything inside it
Vidya (app), with the web layer following RitualOS
No store build
How to request
Nothing extra. A change to the web app is a change to the mobile app.
How it propagates
The app is a window onto the web app (a WebView). Prices, perks, copy, booking flow, notifications, all of it appears in the app the next time a member opens it, with no store submission and no waiting on Apple or Google.
How we verify
Opened on a real phone after the production move to confirm the new screens render the same as the web.
Mobile app, native shell (login screen, app icon, store listing, splash)
Vidya
Needs a store build
How to request
Request Center once live, otherwise Slack tagging Vidya. These are rare.
How it propagates
Only the pieces built into the app itself need a new build: the login screen, the app icon, the name and screenshots in the store listing. A new build goes through App Store and Play Store review, which can take days, so we batch these and never let a price or policy depend on one.
How we verify
Store listing text is scanned like any page. The build is installed and checked on a phone before it is submitted.
Automated emails (RitualOS) and texts (GoHighLevel)
Autosterea maintains, Rory approves wording
No store build
How to request
Request Center once live, otherwise Slack. Any change to the wording of a sequence goes back to you for approval, because you approved the originals.
How it propagates
RitualOS holds every lead and sends the welcome email from hello@ritualstudiospa.com. GoHighLevel keeps a copy of the contact and sends the texts. An edit to either is live for the next send.
How we verify
Every sequence is scanned for the old fact, then a test send goes to an internal inbox and phone so we read exactly what a member would read.
App notifications (sent by RitualOS)
Autosterea
No store build
How to request
Request Center once live, otherwise Slack.
How it propagates
Receipts, booking confirmations, payment reminders and plan-change messages are templates inside RitualOS. They change with the app: dev first, then production.
How we verify
Preview and test send on dev, then scanned with everything else.
Social content bank (Content Studio)
Autosterea rewrites, Rory re-approves
No store build
How to request
Leave a note on the post in the Content Studio, or Slack.
How it propagates
When a fact changes, every post in the bank that mentions it is rewritten, not just the next two weeks. Anything already scheduled is pulled and comes back to you for approval. Anything already published gets a correction or comes down, depending on the fact.
How we verify
The whole bank is scanned, all 27 weeks. A post with a stale number cannot be approved.
Google Business Profile
Autosterea
No store build
How to request
Slack.
How it propagates
Services, offers, hours and the description are edited directly in the profile. Google can take a day to show the change.
How we verify
Scanned once Google shows the update.

The flow, start to finish

From someone wanting a change to that change being verified everywhere.
1
Whoever wants the change (you, staff, or us)

Say it once, in one place. Website: Slack, tag Punit. App and system: the Request Center once live, otherwise Slack or the feedback box on the hub page it belongs to. Describe the outcome, not the fix, and do not go edit a surface directly.

2
Autosterea

Sort it. If it touches a fact (a price, a perk, a policy, a date, a name, a phrase), it goes to step 3. If it is layout, a bug, or a design ask, it goes straight to the owner of that one surface and skips to step 6.

3
Rory

Decide the fact on the source page first. A price or policy goes onto the Membership Rules page as a decision and you hit Looks good. A word goes into the approved words list. Until the source says it, no surface moves.

4
Autosterea

Map what it touches. We list every surface that carries the fact, the owner of each, and what changes there, and post the map back on the request. The Sep 8 example below is what that map looks like.

5
Autosterea

Update the sources. The rules page, the approved words, and the content bank are changed first so everything downstream is copying from the right place.

6
Each surface owner

Change the surfaces, in this order: automated emails and texts first (sent messages cannot be unsent), then the RitualOS catalog and codes on dev (money), then the website (Punit), then the mobile app picks the web changes up on its own, then social and Google. Same day wherever possible.

7
Our dev team builds, Autosterea verifies

App changes are verified on dev.ritualstudiospa.com before they move to production. Nothing goes to production unverified.

8
Autosterea

Run the sweep. A scan across every surface for the old number, the old name, the old date and any retired phrase. Every hit becomes a to-do with an owner. This is what stops a fact from being fixed on the website and still wrong in a text.

9
A second reader at Autosterea, never the one who made the change

Read each changed surface against the rules page, line by line. If the maker and the checker are the same person the check is worth nothing, so they are always different.

10
Autosterea

Close it. The request is marked done with the list of surfaces touched and the scan result. You see one line: what changed, where, verified everywhere.

A live example

Your September 8 website updates, traced across every surface they touch.

Your Sep 8 website updates. On the surface they were a memberships page rewrite, but they changed policy facts: Those Who Serve moves from 15% to 10% and applies to standard pricing only, never with founding pricing; the founding offer gains four named extras (protected rate while continuously active, a $200 curated welcome kit, a preview session for two, 48-hour opening-week priority booking); session packs are priced at $275 for 5 and $500 for 10; and the retail discount is now Essential 5%, Complete 10%, Unlimited 10%. Each of those facts lives on more than one surface, so here is everything they touch.

SurfaceWhat changesOwner
Membership Rules page (the source)Today the page still says Those Who Serve is 15% with a SERVE15 code, and lists retail at Essential 10%, Complete 15%, Unlimited 10%. It needs: Those Who Serve 10% on standard pricing only, not combinable with founding; retail Essential 5%, Complete 10%, Unlimited 10%; the four founding extras written in as rules; session packs at $275/5 and $500/10; and 'valid service ID at signup' recorded as the verification path. This also closes open Decision 8 and answers half of Decision 4.Autosterea writes, Rory signs off
Website copyMembership cards with the founding extras block on all four, Essential 5% and Complete and Unlimited 10% retail, the Those Who Serve section at 10%, the new Single Sessions and Session Packs cards, the FAQ, and the pricing line on the Contrast Therapy page.Punit
RitualOS pricing catalogRetail discount perk on Essential (5%), Complete (10%) and Unlimited (10%); 5 pack at $275 and 10 pack at $500 as sellable items; the catalog lock updated so these become the approved numbers and the old ones are rejected.Our dev team builds, Autosterea verifies, dev then production
RitualOS discount codeThe Those Who Serve discount drops to 10% and is restricted to the standard rate so it can never combine with founding pricing. The SERVE15 code is retired or renamed, and the automatic tag for first responder, military and EMS follows the same rule.Our dev team builds, Autosterea verifies
Mobile appNothing to do. The new catalog, packs and copy show in the app on next open through the WebView. No store build.Vidya (no action)
GHL waitlist emails and SMSAny sequence step that mentions Those Who Serve 15%, a retail discount number, or describes founding benefits. Founding steps gain the four extras in your words. Because these are sent automatically, they change before the website does.Autosterea edits, Rory approves the wording
App notificationsReceipt and plan-change templates that list plan perks pick up the new retail percentages. Pack purchase receipts show $275 and $500.Autosterea
Social content bank35 references to Those Who Serve at 15% become 10% on standard pricing. Posts that list retail discounts are corrected. Founding posts gain the extras. Every rewritten post comes back to you for approval, including any already scheduled.Autosterea rewrites, Rory re-approves
Google Business ProfileThe offers and description are checked for any pricing or Those Who Serve mention and corrected if found.Autosterea
Staff scriptThe Those Who Serve line staff say at signup: 10% off standard pricing, valid service ID required, not combinable with founding.Autosterea drafts, Rory approves

The rules we hold to

Short, so they get followed.
Feedbackon this page