Personal AI Operating System for @induwarauthsara Β· Running on Azure B2ms Β· Managed by Hexa (Hermes v0.14)
All 9 n8n workflows have 0 nodes β they're empty shells. Hermes cronjobs with LLM skills
were tested and work reliably (email-triage, crypto-alert, calendar-sync all ran successfully).
Decision: Move all automation to Hermes cronjobs. n8n stays only as a WhatsApp webhook receiver.
All 17 of Induwara's needs mapped to ApexOS phases
Never miss a deadline. Know what to study daily.
Track all projects. Auto-convert learning to notes.
β Chatbot currently DOWN β returns 504 HTML error
| # | Name | Schedule | Type | Delivers To | Status |
|---|---|---|---|---|---|
| 1 | βοΈ morning-briefing | 07:00 daily | LLM | Telegram | β Active |
| 2 | π study-deadline-check | 07:30 daily | LLM | Telegram | New |
| 3 | π security-news | 08:00 daily | LLM | Telegram (critical) | New |
| 4 | π° payment-check | 08:00 Monday | LLM | Telegram | β Active |
| 5 | π project-check-in | 10:00 Monday | LLM | Telegram | New |
| 6 | π‘ ctf-event-scanner | 12:00 Sunday | LLM | Telegram | New |
| 7 | π calendar-sync | Every 2 hours | LLM | Local | β Active |
| 8 | π§ email-triage | Every 2 hours | Script+LLM | Local (urgentβTG) | β Active |
| 9 | π crypto-alert | Every 4 hours | LLM | Telegram | β Active |
| 10 | π€ chatbot-health | Every 6 hours | Script | TG (if broken) | β Active |
| 11 | π©Ί system-health | Every 6 hours | Script | TG (if down) | New |
| 12 | π¬ tech-digest | 18:00 Friday | LLM | Telegram | β Active |
| 13 | π weekly-review | 09:00 Sunday | LLM | Telegram | β Active |
| 14 | π cert-progress-check | 20:00 Sunday | LLM | Telegram | New |
| 15 | π₯ vlog-reminder | 10:00 1st Sun | LLM | Telegram | β Active |
| 16 | π evening-wrap-up | 21:00 daily | LLM | Telegram | New |
| 17 | π hermes-git-backup | 00:00 daily | Script | Telegram | β Active |
| 18 | πΎ disk-space-check | Every 12 hours | Script | TG (if >80%) | New |
Trackademic is Induwara's academic OS β a Next.js + Supabase web app for study management.
profiles, semesters, subjects (with credits, weights, targets), sessions (lecture/practical log), assignments, exams, past_papers, study_sessions, documents + document_chunks (RAG), ai_insights, calendar_tokens, reschedule_log, chat_history, monthly_attendance view
Trackademic handles the data layer for academics. ApexOS provides the intelligence and notification layer. Here's how they work together:
ApexOS morning briefing queries Trackademic's Supabase directly: assignments due today, attendance alerts, grade predictions. Merges with Notion data for a unified view.
When Induwara tells Hexa "Attended DSA lecture today on Stacks", Hexa creates a session entry in Trackademic Supabase. Zero manual data entry.
Trackademic AI Coach = structured academic content (questions from slides, grade predictions). ApexOS learn-deep = hobby/project learning (teach me Docker from ground level). Two AIs, two domains.
New cron: trackademic-sync β every 2 hours: fetch assignment deadlines, attendance risks, exam dates from Trackademic Supabase β inject into ApexOS context for morning briefing and alerts.
Both use the same Google OAuth identity. Induwara logs into Trackademic via Google. ApexOS's Google token can query Trackademic Supabase.