Skip to main content

ISO Tracker - Interstellar Tracking Application - Progress 23 Nov 2025

Published: November 23, 20252 min read
#ISO Tracker#ISO#Interstellar Object#Build-in-public

Progress Report - November 23, 2025

Project: ISO Tracker

✅ Completed

Sprint 11: Community Arguments & Debate System

  • Built arguments and argument_votes database tables with RLS policies
  • Created API endpoints for argument CRUD and voting
  • Implemented ArgumentCard, ArgumentSubmissionForm, and ArgumentList components
  • Added "Community Debate" tab to ISO detail pages with stance filtering (Artificial/Natural/Uncertain)
  • Tier-gated voting: Event Pass+ users can vote, free users submit only

Sprint 12: Evidence Tab & Threaded Comments

  • Integrated Evidence tab into ISO detail pages with EvidenceList component
  • Built EvidenceSubmissionForm (Event Pass+ tier) with validation
  • Built EvidenceAssessmentForm (Evidence Analyst tier) with quality score sliders
  • Implemented threaded EvidenceComments component with max 3 nesting levels
  • Created API endpoints: /api/evidence/[id]/comments, /api/evidence/[id]/assess

Sprint 13: ISO Following & Notifications

  • Created ISODetailHeader.tsx client component with Follow button integration
  • Built Follow API endpoints: POST/DELETE/GET with follow counts
  • Discovered pre-existing notification infrastructure (settings page, Resend emails, cron job)
  • Verified complete notification system: preferences, unsubscribe, rate limiting, templates

Sprint 14a: Landing Page Alignment

  • Fixed pricing tiers: Removed "Professional", renamed to "Event Pass" ($4.99) & "Evidence Analyst" ($19/mo)
  • Added "Evidence Framework" section explaining core value proposition
  • Created multi-domain routing middleware for 3i-atlas.live
  • Built standalone 3i-atlas.live landing page with email capture form
  • Created email_signups database table and /api/email-signup endpoint

🐛 Issues & Learnings

Issue: Email signup API returning 500 error

  • Root Cause: Using @supabase/ssr createClient in API route context without proper cookie handling
  • Fix: Switched to direct @supabase/supabase-js client with service role key for server-side operations
  • Prevention: Use direct Supabase client for non-auth API routes; SSR client for auth flows only
  • Time Impact: ~30 minutes debugging

Impact Summary

Massive progress day - completed 4 sprints (11, 12, 13, 14a) bringing ISO Tracker to monetization-ready state. The core engagement loop is now complete: users can follow ISOs, submit arguments, assess evidence, and participate in community debates. Landing pages now accurately reflect the product strategy with correct pricing and clear value proposition.

Next Steps

  • Sprint 14: Stripe Payments integration (CRITICAL - monetization)
  • Deploy migration 018 (email_signups table) to production
  • Configure 3i-atlas.live domain in Vercel dashboard

Generated from progress.md on 2025-11-23 at 4:45 PM

Share this post