Mythoscope Development Lifecycle
How methodology refinement flows from private workshop to public product
← FEEDBACK LOOP →
The Temple
Private Workshop (Slack #the-temple)
Hourly / Daily
5 activities — click to expand
💬Discuss what's working and what isn't
✏️Revise methodology language & structure
💾SAVE_DRAFT — store revised prompt
🧪RUN_DRAFT — test on real people's actual inputs
🔁Compare, iterate, repeat
⏱ Minutes to hours per cycle
▼
Staging Gate
Founders Review
When it sings
4 activities — click to expand
👀All founders review draft readings
⚖️Compare draft vs. current live version
✅Unanimous agreement to deploy
🚀DEPLOY_DRAFT vX.Y.Z — promote to live
⏱ Decision point (hours to days)
▼
Live Methodology
Active Production Prompt
Weekly / Biweekly deploys
4 activities — click to expand
🔮All RUN_MYTHOSCOPE readings use this
📊Collect feedback from beta users
📝Log observations in #the-temple
🔄Feedback flows back into next Temple cycle
⏱ Stable for days to weeks
▼
Public Release
mythoscope.app / Beta Users
Monthly milestones
4 activities — click to expand
📱Methodology locked for app version
👥40-100 beta users generating readings
✦Lumen economy active
📈Usage data informs next Temple cycle
⏱ Stable for weeks to months
Shared Data Layer
The Temple and the public Mythoscope both read from the same user inputs — real users and test users alike.
The difference is what happens to the outputs.
User Inputs
Shared across all environments
LovesCultural preferences (D1 polarities)
HatesCultural aversions (D1 polarities)
DreamsAspirational signals (D1 polarities)
Both Temple drafts and live readings pull from the same D1 database — same real users, same test users. No separate test data needed.
Reading Outputs
Visibility depends on origin
Temple Readings (Draft & Test)
Visible only to Temple members in Slack. Never saved to user profiles. Never shown to the subject. Purely for calibration.
Live Readings (Production)
Saved to Notion Outputs DB. Shown on user's private profile page. Costs Lumens. This is the real thing.
Version Flow
v1.2.0
live
Current production methodology
v1.3.0-draft
draft
Being shaped in The Temple now
v1.3.0
future
Deployed when draft is approved
v2.0.0
future
Major overhaul after beta feedback
How it works: Temple sessions produce drafts (purple).
When founders approve, the draft deploys as the new live version (green).
Live versions serve all readings until the next deploy.
Major user-facing app releases lock a version for stability (blue milestones).
Feedback from each layer feeds back up into the next Temple cycle.
Cadence Summary
Temple Iteration
30min – 2hrs
Draft → Test → Revise
Staging Review
Same day
Compare & approve
Live Deploy
1–2x / week
New methodology goes active
App Release
Monthly
Locked version for users