THE
ENGINEERING
" Built by a Engineer
who doesn't believe in motivation. "
Most people use apps to track habits.

I built the app.

A single-person accountability OS — engineered from scratch to be stronger than willpower, excuses, or any weak moment at 3 AM.

42
DATABASE
TABLES
130+
DAILY
CHECKPOINTS
5
CLOUD SYNCS
PER DAY
<1s
CROSS-DEVICE
SYNC
↓ SCROLL TO EXPLORE ↓
SECTION 01

A DAY IN THE SYSTEM

From wake to midnight lock — every minute is accounted for.

03:15 AM
WAKE
The alarm rings. The watch is already recording — heart rate, movement, sleep quality captured before my feet touch the floor. The system knows I'm awake before I do.
04:00 AM
RUN
Every step GPS-verified. Heart rate recorded every second. Pace, cadence, elevation — all sealed by satellite. No human can fake a Strava GPS trace. The road doesn't lie.
05:15 AM
PHOTO + POST
Live photo. That morning. That moment. Carousel generated on firstlight.live. Posted to Instagram. Not scheduled. Not pre-made. If this doesn't happen before 6 AM — ₹15,000 is up for grabs.
05:55 AM
CLOUD SYNC #1
Zero human intervention. A Google Cloud Function wakes up, pulls data from Strava and Instagram APIs, cross-references GPS trace with photo timestamp, and stores everything permanently in 42 database tables. The machine doesn't need sleep.
06:00 AM
THE LINE
Post must be live. Run must be logged. If not — the system is already recording the miss. There is no undo button. There is no "I'll fix it later." The deadline is final.
ALL DAY
130+ CHECKPOINTS
50 morning rituals. 14 midday. 35 evening. 25 mastery items. 10 deep work blocks with focus timer. Fortress discipline. Japa. Reading. Every single item tracked, timestamped, and synced across all devices in real-time via WebSocket.
11:59 PM
MIDNIGHT LOCK
The day seals. Every data point locks permanently. Tomorrow starts fresh. Yesterday can never be changed — not even by the admin. The database physically rejects the request. The code says no.
SECTION 02

THE DATA FLOW

How data moves from your wrist to the world.

⌚ WATCH
GPS + HR + PACE
STRAVA
API v3
GOOGLE CLOUD
FUNCTIONS
DATABASE
42 TABLES
📸 PHONE
PHOTO + POST
INSTAGRAM
GRAPH API v21
GOOGLE CLOUD
STORAGE (GCS)
PERMANENT
ARCHIVE
💻 ANY DEVICE
LAPTOP · TABLET · PHONE
WEBSOCKET
REAL-TIME SYNC
ALL DEVICES
< 1 SECOND
SECTION 03

THE UNBREAKABLE LAYERS

Five layers of protection. Each one makes cheating harder. Together — impossible.

5
PUBLIC EYES
Anyone on the internet can verify and claim ₹15,000 if the 6 AM deadline is missed. The accountability is not private — it's global.
4
IMMUTABLE DATABASE
PostgreSQL triggers physically reject DELETE and UPDATE on sealed records. Even with admin access, the data won't change.
3
MIDNIGHT LOCK
At 12:00 AM, all data for the day becomes read-only. The application code refuses to write to any past date. No grace period.
2
CLOUD AUTOMATION
5 daily cloud syncs run on Google's servers — not my laptop. Even if every device I own dies, the cloud still pulls, verifies, and stores.
1
GPS PROOF
Strava GPS traces are satellite-verified. Heart rate is biometric. You cannot fake a 10km run — the physics won't allow it.
"To cheat, you'd need to hack Strava's satellite GPS, bypass PostgreSQL database triggers, override Google Cloud Functions, fake Instagram's API timestamps, and do it all before midnight — while the entire internet watches."
SECTION 04

THE JUDGE

The system doesn't just track. It punishes. Automatically. Publicly. Permanently.

STEP 1 — RULE BROKEN
The system detects the violation.
When a rule is broken, the admin logs a slip. The moment it's submitted — the system takes over. The admin has no more control.
STEP 2 — PUNISHMENT AUTO-ASSIGNED
The system decides the penalty. Not the admin.
Standard violation: 20km walk with GPS proof. Fortress breach: 50km walk + 5km run OR 100km cycling. The code assigns it. No negotiation. No appeal.
STEP 3 — PUBLISHED INSTANTLY
The slip goes live on the public accountability ledger — instantly.
Date. Rule broken. Penalty status: RED — PENDING. Anyone on the internet can see it. The admin cannot hide it, delete it, or make it private. The database trigger rejects the attempt.
STEP 4 — WALK THE PENALTY
The only way to clear: walk. Upload. Prove.
Upload a Strava GPS screenshot. Enter km walked (system validates minimum). Provide Strava activity URL. Only then — the status changes to GREEN — CLEARED. But the slip itself? Still visible. Forever.
PERMANENT RECORD
Cleared ≠ Erased. The scar remains.
Every slip — the date, the rule, the penalty, the proof screenshot — lives permanently on the public ledger. 10 years from now, you'll still see it. That's the point. Consequences should leave marks.
The admin built the system.
The system now controls the admin.
He can't delete slips. He can't modify history. He can't hide failures.
He can only do one thing — walk the punishment and upload the proof.
IN DEVELOPMENT PHASE 2 — AUTO-PAY
The final evolution: the system pays the penalty itself.
When the streak breaks, ₹15,000 is automatically deducted from a dedicated Axis Bank account and sent directly to the first person who claims it. No manual transfer. No delay. No human in the loop. The system pays the penalty on its own — the moment a miss is verified.
DONE
Penalty system
built & live
IN PROGRESS
Dedicated Axis Bank
account setup
NEXT
Payment API
integration
The machine doesn't just track discipline. It will enforce consequences with real money — automatically. No human approval. No second chances. Every comment timestamped to the millisecond — first claim wins. The code decides. The bank pays.
SECTION 05

THE SAFETY NET

Every feature exists because a failure scenario was imagined — and eliminated.

ANY WATCH. ONE SYSTEM.
Apple Watch, Garmin, COROS, Polar — doesn't matter. The watch records every run, every heartbeat. GPS verified. No phone needed. Change watches 10 times — nothing breaks.
📱
ZERO DEVICE DEPENDENCY
Phone dies? iPad breaks? Laptop stolen? The streak still syncs. The cloud doesn't sleep. The watch records offline and uploads whenever it finds internet. The system is stronger than any single device.
REAL-TIME SYNC
Update on laptop — tablet sees it in under 1 second. WebSocket connection. Not polling. Not refreshing. Instant. Works offline too — queues changes, syncs when back online. Zero data lost. Ever.
🔒
DATA IS IMMUTABLE
Once recorded, even I cannot delete or modify it. The database permanently rejects all attempts. Every run, every miss, every metric — sealed forever. View the ledger →
🔄
SELF-HEALING TOKENS
Strava tokens expire every 6 hours. Instagram tokens expire every 60 days. The system auto-refreshes them via Google Cloud. No human touches a token. The machine maintains itself.
💰
₹15,000 EVERY DAY
Not a one-time bet. Not a monthly thing. Every. Single. Day. Miss once = someone gets paid within 24 hours. The money is real. The stakes are permanent.
🌍
ANYONE CAN CLAIM
This isn't private accountability. Anyone on the internet can check, verify, and claim ₹15,000 if the 6 AM deadline is missed. Comment on Instagram, DM, or message here — first claim wins.
⚖️
PUBLIC ACCOUNTABILITY
Every slip is published automatically. Every penalty requires a verified 20km+ walk with GPS proof. No backdoor. No override. The internet is the witness. View the ledger →
🏗️
BUILT FOR 10 YEARS
42 database tables. 5 daily cloud syncs. Auto-archival to cold storage. Self-renewing API tokens. Cross-device WebSocket sync. This system will outlive the devices that built it.
SECTION 06

THE TECH STACK

For those who want to look under the hood.

FRONTEND
Vanilla JavaScript · Zero frameworks · 29 modules · 13 pages
DATABASE
Supabase PostgreSQL · 42 tables · Row Level Security · Immutable triggers
STORAGE
Google Cloud Storage · Auto-archive to Coldline · Lifecycle policies
HOSTING
Firebase Hosting · Custom domain · Global CDN · SSL
SYNC
Supabase Realtime WebSocket · Offline queue · Pull-on-focus · <1s latency
APIs
Strava API v3 · Instagram Graph API v21 · Auto-refreshing OAuth tokens
AUTOMATION
Google Cloud Functions · Cloud Scheduler · 5 daily cron jobs · Zero human intervention
SECURITY
Supabase Auth · RLS policies · Secret Manager · Obfuscated credentials · No API keys in code
DESIGN
IBM Plex Mono + Inter · Dark-first · Mobile-first · 44px touch targets · Safe area insets
"No React. No Next.js. No npm install. No build step.
29 JavaScript files. 13 pages. Runs forever."
SECTION 07
This entire system costs
₹4
PER MONTH
42 database tables. 5 daily cloud syncs.
Real-time WebSocket. Auto-archival.
Self-healing tokens. GPS verification.
Less than a cup of chai.
"The only thing that can break this streak
is choosing to stay in bed.
Everything else has been engineered out."
VIEW STREAK SEE EVIDENCE CHECK LEDGER