# DECISION DAY A college admissions guessing game where players analyze fictional student applications, predict college decisions, and see how well they did. ## Project status The first frontend version is committed. Players can select Admit, Waitlist, or Reject for each school. **Scoring intentionally stays disabled until the secure Supabase answer checker is configured and the private case data is added.** ## Files - `index.html` — applicant profile and prediction interface - `styles.css` — responsive visual design - `app.js` — selection, secure submission, and results display - `config.js` — public Supabase URL and anon/publishable key placeholders - `supabase/schema.sql` — database schema - `supabase/functions/submit-predictions/index.ts` — server-side scoring function ## Supabase setup 1. Create a Supabase project. 2. Open SQL Editor and run `supabase/schema.sql`. 3. Add the fictional case and its correct outcomes privately in Supabase SQL Editor. Do not put answer keys in frontend files or a public GitHub repository. 4. Deploy the Edge Function `submit-predictions`. 5. Copy the project URL and anon/publishable key into `config.js`. 6. Test predictions and verify that the browser receives no actual decisions before submission. Never place a Supabase service-role key or database password in frontend files. The service-role key is only for trusted server-side use. ## Hosting This is a static frontend. You can preview the layout by opening `index.html`, but secure scoring will not work until Supabase is configured. Upload the files to your Hostinger website directory or connect the repository using a compatible deployment workflow. ## Current game rules - Players choose Admit, Waitlist, or Reject for every school in the case. - Results show the number of correct predictions and percentage accuracy; the interface no longer presents a points or bonus system. - Players can share a short summary of their result using the browser's share menu or clipboard fallback. - The current public page is still a single fictional starter case. Daily challenges, archive/endless rotation, accounts, friend comparisons, and owner-only case administration are planned features, not yet implemented. - The production answer checker and database still require separate deployment/configuration verification; a frontend commit alone does not deploy Supabase Edge Function code. All starter applicant details should be treated as fictional. Do not present fictional outcomes as real admissions results.