How They Get Here

Two paths into onboarding:

Both paths end at thumos.academy/onboarding. The page checks auth and onboarded status — if already onboarded, redirects to portal.

Step 1: The Commitment

What they see: A commitment statement (not terms and conditions). Sam's video will play here explaining what they're stepping into — currently a placeholder until Sam records it.

The commitment text:

• "I am here to become the man I am capable of being. Not to observe. Not to consume. To become."
• "I will post my daily action and gratitude every weekday without exception."
• "I will set three honest milestones — one for each realm."
• "I will show up to the calls."
• "I will hold my brothers to the same standard I hold myself."
• "I understand that my failure belongs to the men beside me."

What they do: Type their full name and today's date. This replaces a checkbox — writing it makes it real.

What's saved: Nothing yet — the commitment is a ritual, not data. Future: store the signed commitment in D1.

Design intent: Abundance energy, not compliance. Alan's feedback: "put them in a state of abundance, not obligation." Sam's video will set the tone. The dark aesthetic may change to something more expansive.

Step 2: Your Milestones

What they see: An AI prompt they copy-paste into Claude or ChatGPT. The AI walks them through a guided conversation to discover what they actually want to work on.

How the prompt works:

1. Asks which domain feels most alive — Women, Money, or Body
2. Goes deep on ONE domain at a time (one question at a time, never a list)
3. If they're stuck, flips to anti-vision: "What do you NOT want?"
4. Sharpens into a concrete 30-day milestone (binary, specific, uncomfortable)
5. Repeats for each domain
6. Outputs 3 clean lines: WOMEN: / MONEY: / BODY:

Key principles in the prompt:

• Never hand them a milestone — guide them to their own conclusion
• If they list 6 goals, stop them: "Pick one."
• If they're already strong in a domain (like Body), respect it — don't manufacture struggle
• Match their energy. Call out deflection gently.
• 10-20 minutes if done right

What they do: Paste their 3 milestones into the input fields (Women, Money, Body).

What's saved: 3 milestones saved to D1 milestones table with current cycle ID.

Prompt location: Embedded in onboarding.html inside a copy-paste box.

Step 3: First Post

What they see: A mock post card showing the daily format. The "Action" is pre-filled: "I joined the Forge. My milestones are set. I am beginning." They type one thing they're grateful for.

What they do: Write their gratitude → click "Post it — Enter the Forge"

What happens:

1. Milestones saved to D1 (POST /onboarding/milestones)
2. User marked as onboarded = 1 in D1
3. "You're in" screen appears with 4 links

"You're In" Screen

After completing step 3, they see 4 action items:

Below these: "Don't have Telegram? Download it here" link + "Need help? Message Q directly" link to Q's Telegram DM.

After Onboarding

Once onboarded, visiting /onboarding redirects to /portal. They're in the system:

• Portal shows their real data (streak, squad, milestones, leaderboard)
• Telegram bot tracks their daily posts
• Courses are accessible with progress tracking
• 8pm reminder kicks in if they don't post

What's Not Built Yet

• Sam's commitment video — placeholder in step 1
• Photo signature — currently text name+date, future: upload photo of handwritten signature
• Anti-vision pairing — each milestone paired with "what happens if I don't" (fuel)
• Sovereign Declaration — deeper values exercise for month 2-3 members who plateau
• Auto-squad assignment — paid members currently get no squad, need manual assignment
• Portal aesthetic — currently dark, planned redesign to clean white

What It Is

@ThumosAI is a Cloudflare Worker-powered bot. It has no separate server — it runs on the same thumos-api Worker as everything else. Telegram sends messages to /telegram endpoint via webhook.

How Post Detection Works

1. Member posts a message in their squad Telegram group
2. Telegram sends the message to our Worker webhook
3. Worker checks: does the message have Action: AND Grateful: at the start of a line?
4. If yes → look up the user by their Telegram ID in D1
5. Check if they already posted today (UTC date) → if yes, silently ignore
6. Record the post in daily_posts table (who, when, which squad, weekday/weekend)
7. Calculate their new streak (consecutive weekdays with posts)
8. Bot responds in the group: 🔥 username — Day X

Important: The bot NEVER stores message content. Only records that a post happened and when.

Post Format Rules

Streak Rules

Streak = consecutive weekdays with a recorded post. Counted backwards from today.

• Post Mon-Fri → streak goes up
• Miss a weekday → streak resets to 0
• Saturday/Sunday → ignored (don't help, don't hurt)
• Post on weekend → recorded but streak doesn't increase

8pm Reminder

A cron job runs every hour. For each active member, it checks: "Is it 8pm in their timezone?" If yes and they haven't posted today, the bot messages their squad group: [name] hasn't posted today.

Timezone is stored per user in D1 (detected from browser on signup). Default: America/New_York.

Known issue: If the Worker is redeployed while messages are in-flight, Telegram may mark them as delivered but the Worker didn't process them. Posts are lost — Telegram won't retry.

Account Linking

Members need their Telegram account linked to their THUMOS account for posts to be tracked.

Automatic (onboarding): "Join Squad" button on the onboarding completion screen is a deep link: https://t.me/ThumosAI?start=LINK_{userId}. When they tap it, the bot auto-links their Telegram ID.

Manual: In a DM or group, send /link [email protected]. Bot looks up the email in D1 and links the Telegram ID.

Admin: Directly update D1: UPDATE users SET telegram_user_id='...' WHERE email='...'

Bot Commands

Group Welcome

When a new member joins a registered squad group, the bot automatically sends a welcome message with their name and the daily post format.

Groups

To add a new squad: create Telegram group → add @ThumosAI as admin → use /chatid to get the ID → add squad in Admin panel or D1.

Troubleshooting

Personal Score (per cycle)

(posts ÷ weekdays × 50) + (milestones_hit ÷ 3 × 50) = max 100

Example: 18 posts out of 22 weekdays = 40.9 pts. Hit 2 of 3 milestones = 33.3 pts. Total = 74.2 pts.

Squad Score (per cycle)

Same formula but aggregated across all squad members. Percentage-based so squad size doesn't matter.

Stored in squads.cycle_total_score. Recalculated nightly at midnight UTC.

Cumulative Score

Personal score carries over between cycles. Stored in users.cumulative_score. Determines rank.

Ranks

Rank persists forever. Leaderboard resets each cycle.

Cycles

• ~30 days per cycle
• Start: squad scores reset, new cycle record created
• End: pick winning squad → private debrief with Sam
• New members mid-cycle: excluded from squad score

Milestones

• 3 per user per cycle: Body, Women, Money
• Set during onboarding or cycle start
• Visible to squad. Cannot be changed.
• Declare hit/miss at cycle end

Architecture

Everything runs on Cloudflare. One Worker (thumos-api) handles all API requests. One D1 database (thumos-db) stores all data. Three Pages projects serve the websites.

Services

D1 Tables

Deploy Commands

# API (Worker)
cd selene/markets/thumos/deploy_api && npx wrangler deploy

# Main site
npx wrangler pages deploy "selene/markets/thumos/deploy_main" --project-name=thumos-academy --commit-dirty=true

# Editor
npx wrangler pages deploy "selene/markets/thumos/deploy_editor" --project-name=thumos-editor --commit-dirty=true

# Admin
npx wrangler pages deploy "selene/markets/thumos/deploy_admin" --project-name=thumos-admin --commit-dirty=true

# Or: git push (auto-deploys main site)

Worker Secrets

Set via npx wrangler secret put NAME from deploy_api/:

• STRIPE_SECRET_KEY
• STRIPE_WEBHOOK_SECRET
• RESEND_API_KEY
• TELEGRAM_BOT_TOKEN