AI Monk Index MCP server

→ Daisuke134/life-manager へ移行済み

Anicca — Behavior Change Agent + Wake-up SaaS

Proactive agent that helps people break harmful patterns and build better habits. Two surfaces share one codebase:

The wake-up SaaS uses a real voice agent ("Anicca") who talks back over PSTN, not a recorded ringtone. She knows your calendar, your home location, and your day-job start time — and if you're falling behind schedule she'll keep calling plus optionally email a 報連相 (heads-up) to your manager.

Repo layout

How the Wake-up SaaS works

User signs up at aniccaai.com/alarm
        ↓ Stripe webhook
Supabase `subscriber_profiles` row created (phone, wake_time, tz, name)
        ↓
scheduler/alarm_scheduler.py  (every 60s, multi-tenant)
        ↓  it's wake_time in user's tz, and not fired today
scheduler/wake_loop.py        →  POST /dialout on bridge
        ↓
bridge/server.js              →  Twilio Calls API
        ↓
Twilio → user's phone → bridge WebSocket → Gemini Live (Charon voice)
        ↓
Real two-way conversation until user is verifiably awake.

Then, every 15min from 6:00-23:00 local:
scheduler/saas_lateness.py    →  reads gcal + OwnTracks location
        ↓  ETA - now < buffer
Calls again with lateness persona, optionally emails stakeholders.

OwnTracks setup (required for lateness detection)

The lateness loop needs to know where the user is right now. We use OwnTracks — open-source location publisher — because it's privacy-respecting (you own the data) and battery-aware.

One-time setup on the user's phone

1. Install OwnTracks

• iOS:
• Android:

1. Configure HTTP publishing (Settings → Preferences → Connection)

• Mode: HTTP
• URL: https://.up.railway.app/ingest/owntracks?token=
• The token comes from aniccaai.com/alarm/setup after signup.
• Identification → DeviceID: anything (e.g. iphone)
• Identification → TrackerID: 2 chars (e.g. DA)

1. CRITICAL: Set mode to Move, NOT Significant_**

Significant mode publishes nothing while the device is stationary. If the user is asleep in bed, no location update is sent for hours — and Anicca then sees a stale fix and can't tell whether they left home. Move publishes every 5 min OR 100 m of movement (whichever is sooner), which is what the lateness loop needs. Battery cost is roughly that of a navigation app, so we recommend the user enables Low Power Mode override.

• Open OwnTracks → ⓘ icon → Mode selector
• Choose Move
• Why: per OwnTracks docs,

1. Grant always-on location permission (iOS: "Always Allow")

• Otherwise iOS will silently throttle background publishes.

1. Verify it's working

within 5 minutes of you walking around with the phone.

• Go to aniccaai.com/alarm/setup → "Last seen" timestamp should refresh

Why HTTP and not MQTT

Shortened. The full README is on GitHub.