Simple Hack feature audit

168 features and settings checked against the live code at origin/main 4d20ac5b. Orange means it looks like it does something but does not.

168
Checked
114
Complete
44
Half-baked
10
Unclear to a first-time user
OrganiserOrganiser: 66 complete66Organiser: 25 half-baked25Organiser: 4 unclear495ParticipantParticipant: 19 complete19Participant: 10 half-baked10Participant: 1 unclear30JudgeJudge: 7 complete7Judge: 1 half-bakedJudge: 1 unclear9Public pagesPublic pages: 11 complete11Public pages: 3 half-bakedPublic pages: 3 unclear17AI appsAI apps: 5 complete5AI apps: 5 half-baked510EveryoneEveryone: 6 complete6Everyone: 1 unclear7
CompleteHalf-bakedUnclear

A remote judge, per team

20 sRead the summary card
→
2 minWatch the video
→
LiveOpen the site
→
RubricScore on the same screen
→
NextOne tap to the next team

Today the judge gets free text, then three buttons that open new tabs. Fixes 4 and 5 close that gap.

Fix these first

Ranked by impact over effort.

  1. 1
    Show the rubric to teams participantimpact higheffort S

    Teams build blind today, and the rubric already exists, so one read-only card on Entry and Home fixes it.

  2. 2
    Warn before panels drop untracked teams organiserimpact higheffort S

    Switching to panels silently drops every team with no track from judging, so name those teams and ask for a track before judging opens.

  3. 3
    Record guardian consent for under-18s participantimpact higheffort S

    The form says a parent must agree but records nothing, so add a consent tick and a guardian contact.

  4. 4
    Entry summary card with judges' one screen judgeimpact higheffort M

    Fixed short fields replace the summary slide, and judges get card, video, live site and rubric on one screen with a fast Save and next.

  5. 5
    Entry presets with required fields that count organiserimpact higheffort M

    Presets for no-code, coding and ideas events set what is required, including video or working link, and teams see what is missing.

  6. 6
    Participant Home as a checklist with a countdown participantimpact higheffort M

    Team, summary, video or site, and in before the deadline, ticked from real data with a live clock on the team's own deadline.

  7. 7
    Notify people when something waits on them participantimpact higheffort M

    Join requests, invites, application decisions, take-downs and extensions reach nobody today, so add an email and a badge using the mail path announcements already use.

  8. 8
    Results show what each team built publicimpact higheffort M

    Put the summary card, site and video on each result row, following the existing winners-only or all-entries setting, so the video finally reaches the public.

  9. 9
    Guided team-site publishing participantimpact higheffort M

    Inline steps per AI app plus Connected and Published states turn a bare connector address into the participant's main moment.

  10. 10
    Schedule that acts organiserimpact higheffort L

    Real milestones (deadline, voting, stages) live in the schedule so they cannot drift, and any row can carry an action or a reminder on Overview.

Every item

RoleFeatureExpectedActualGapRecommendationEffortImpact
OrganiserSchedule
Half-bakedschedule
Each schedule time should prompt an action, done by the organiser or by the system.A schedule row is only a title, note and time, driving the Now and Next labels. The real deadline and voting window sit on separate screens, and nothing happens automatically at a schedule time.
Evidence
internal/handler/hack_content.go:31-41,150-168 (schedule is just title/description/start/end, no deadline linkage), internal/handler/static/hack/screens/organiser-event-page.js:415-458 (renderSchedule, purely editorial, Now/Next labels only), internal/handler/static/hack/screens/participant-schedule.js:1-44 (same, display only), internal/handler/hack_public_json.go:50 (submission_deadline is a separate real field), internal/handler/hack.go:1438-1455 (submission_deadline is set/cleared automatically by stage changes, with no reference to schedule at all), internal/handler/hack_voting.go:13-29,102 (a third, separately-gated opens_at/closes_at voting window, also disconnected from Schedule), internal/handler/hack_eventpage.go:846-898, no calendar or .ics code anywhere
A row saying submissions close at 5pm can say one time while the real deadline says another, and nobody gets prompted.Pick: Combine both. Put real milestones in the schedule so they cannot drift, and let any row hold an action or reminder that shows on Overview.
Options
  1. Pull the entry deadline and voting window, plus every stage move, into milestone rows the organiser can edit. Free rows stay for talks and meals.
  2. Let a row hold an action, such as closing entries or opening voting, so a due manual row shows as a to-do on Overview.
  3. Add only a calendar link and a warning when a row's time does not match the real deadline.
Lhigh
OrganiserReview, approve or reject application
Half-bakedsignup
When an organiser decides an application, the applicant should find out quickly, ideally by email too.The decision is saved, and the applicant sees their new status next time they open the event, though the system never emails anyone about it.
Evidence
internal/handler/hack_registration.go:128-177 (decideApplication, no mail call), grep of hack_apply.go/hack_registration.go for mail/notify (no hits), internal/handler/static/hack/screens/public-apply.js:150-159 (status only shown on next visit)
An applicant who is not checking the site has no way to learn they were approved or rejected.Pick: Send a decision email. A missed approval costs more than one extra templated email.
Options
  1. Send a short email on decision, reusing the sender already wired for event removal warnings.
  2. Keep it in-app only and say so plainly in the applicant-facing copy, so nobody expects a notification.
Mhigh
OrganiserRequired entry fields
Half-bakedentries
Marking a field required should block submission until it is filled in.The setting only changes the missing label organisers and teams see. Saving an entry never checks required fields, so entries can lack every one and still save.
Evidence
internal/handler/hack_entries.go:61-141 (putEntry has no required-field check), internal/handler/hack_entries.go:439-451 (entryCompleteness only computes a missing[] list for display), internal/handler/hack_content.go:280-287 (queueReceipt is the only functional consumer of completeness), internal/db/hack_gallery.go:34-53 (ListGalleryCards has no completeness filter), internal/mcp/hack_member_tools.go:61 (hack_update_entry has the same no-enforcement write path)
Required fields never block anything. An organiser expecting a gate on submission or the gallery gets none.Pick: Enforce it through presets without blocking saves. Teams see what is missing and get a reminder. Organisers and judges see which entries are incomplete.
Options
  1. Show what is missing on Home and Entry, and warn before the deadline. Flag incomplete entries for judges too.
  2. Rename it to show what counts as complete, without blocking anything.
  3. Block saving when a required field is missing.
Mhigh
OrganiserTake down or restore team site
Half-bakedentries
Taking a team's site down should tell the team, since the action already asks for a reason.The reason is stored and shown only if the team opens their Website or Entry screen. No email, push or Home banner goes out at the moment of takedown.
Evidence
internal/handler/static/hack/screens/organiser-entry-detail.js:99-115 (onTakeDown, no notify call), internal/handler/static/hack/screens/participant-entry.js:13-18 (CLOSED_TEXT shown only if they visit Entry), internal/handler/static/hack/screens/participant-website.js:55-59 (shown only if they visit Website), internal/handler/static/hack/screens/participant-home.js:142-222 (hero branches cover event_taken_down and team removal, not site takedown) -- grep for 'taken_down' across participant-home.js/participant-team.js confirms no such branch
A destructive action with a reason meant for the team has no active notice. The team only sees it by opening the right screen.Pick: Add a Home banner at minimum. The reason text already exists server side and only needs showing on the one screen every role sees first.
Options
  1. Send a notice email on takedown, reusing the same path as announcements and receipts.
  2. Show a Home banner so the next visit cannot miss it.
  3. Leave it as is, relying on the team to open the right screen.
Smedium
OrganiserTrack panel assignment grid
Half-bakedjudging
Picking judges for each track's panel should get every team judged.The panel grid and eligibility both depend on a team's track. A team with no track matches no panel, so it doesn't get any judges and stays unscored.
Evidence
internal/db/hack_judging_options.go:81-83 (panel branch requires p.track_id=t.track_id), internal/db/hack_registration.go:231 (track_id is a separate, optional PATCH, not required at team creation), judging dashboard only shows a generic 'flagged' with no reason (internal/handler/hack_judging.go:867-882)
Switching to panel mode with an untracked team drops that team from judging. Nothing names the real cause, only a generic low coverage flag.Pick: Name the teams with no track when panel mode is picked, and ask the organiser to give them a track before judging opens.
Options
  1. Block the switch to panel mode, or warn plainly, while any team has no track.
  2. Add a specific dashboard note for a missing track, separate from the generic coverage flag.
Shigh
OrganiserEntry presets and per-field required or optional
Half-bakedentries
Picking the kind of event should ask teams for the right things, like a code link for coding events.One list of required fields exists, and it only drives a missing label. There are no presets, and no rule such as video or working link.
Evidence
internal/handler/hack_entries.go:436-450 entryCompleteness, hack_entries.go:61-141 putEntry saves regardless
The organiser cannot express the rule they have, and the rule they can express goes unenforced.Pick: Combine presets with per-field switches. Add an either-or rule for video or working link, and show it to teams on Entry.
Options
  1. Add a preset for coding, one for no-code or AI build, and one for ideas or design, plus a per-field switch.
  2. Offer per-field switches only, with no presets.
  3. Offer presets only, with no per-field switches.
Mhigh
OrganiserEvent dates (start/end)
Half-bakedsetup
Setting start and end dates should trigger something automatically, like opening sign-up or closing entries.Start and end dates are only shown on the public page. No code reads them to change stage, open sign-up, close entries or alert the organiser.
Evidence
internal/handler/hack_eventpage.go:360-365 (display only), internal/handler/hack.go:1166-1192 (re-anchor on time zone change, no stage effect), internal/handler/hack_cleanup.go:1-60 (ticker is for post-archive cleanup only), internal/handler/hack.go:1371-1480 (setStage has no date trigger)
The dates look important, since they are asked for up front and shown clearly. They have no automatic effect.Pick: Add the heads-up. Overview already warns about similar situations, so this is a small, consistent addition.
Options
  1. Keep the dates informational, and say so in the UI, noting stages still move by hand.
  2. Add a heads-up on Overview once the end date passes and the event is still open.
Smedium
OrganiserPrizes text versus results
Half-bakedwebsite
The Prizes field should connect to the Results screen when winners are announced.The event-level Prizes field is free text with no link to results or winners. A separate per-track prize field is the one written into the results file and shown to winning teams.
Evidence
internal/handler/hack.go:1047,1124-1129 (event-level Prizes, free text, no results link), internal/handler/hack_public_json.go:46, internal/db/hack_registration.go:26,212 (per-track Prize), internal/handler/hack_judging.go:1855,1895,1922,1932,1951 (track_prize/track_winner in results CSV), internal/handler/static/hack/screens/participant-results.js:78 ("winner: " + track.prize), internal/handler/static/hack/screens/organiser-teams.js:96,358,391 (where the real per-track Prize is actually set)
Two same-named fields exist on two screens, and only one of them does anything mechanical. Writing a Prizes paragraph attaches no prize to any winner.Pick: Add structured prizes, since results already know the ranks and winners. Keep the free text as an intro.
Options
  1. Add structured prizes covering ranks and tracks, so results show every winner with their prize.
  2. Rename the field to a prizes description and point to the per-track prize field.
Mmedium
OrganiserCode of conduct acceptance visibility
Half-bakedwebsite
An organiser should see who accepted the code of conduct, the same way they see who joined.Acceptance is enforced and recorded per member, and it appears in the CSV export. It never shows on the People screen, Entries or Overview.
Evidence
internal/handler/hack_apply.go:282 (coc_required enforced), internal/handler/hack_administration.go:96,115 (coc_required, coc_default), internal/handler/hack_administration.go:285-290 (coc_accepted_at only in CSV export), internal/db/hack.go:103 (CocAcceptedAt stored per member), internal/handler/static/hack/screens/organiser-people.js (no coc_accepted_at reference anywhere in the file)
Acceptance is enforced and recorded, but invisible in daily use. Checking it means exporting a CSV instead of looking at a person's row.Pick: Add the indicator. People already shows when someone joined, so adding when they accepted fits the same row.
Options
  1. Add an accepted-CoC indicator or timestamp to the People row or detail view.
  2. Leave it CSV-only, but mention the column in the People screen's export hint.
Smedium
OrganiserStorage usage
Half-bakedsetup
An organiser uploading files should see how much of their storage allowance is used.A real usage endpoint exists, but the current screen only shows one combined byte total next to the CSV button. The older screen showed a full breakdown, and neither compares the number to any cap.
Evidence
internal/handler/hack_administration.go:34,388-409 (the usage endpoint), internal/handler/static/hack/screens/organiser-entries.js:17-28,79 (new UI: one combined total, in Entries, not Settings or Overview), internal/handler/static/hack-app.html:5340-5346 (classic UI: full breakdown, now secondary), internal/handler/hack_ui.go:36-57 (new app is default since 2026-10-30, classic kept behind a cookie)
An old detailed breakdown is gone from the new app, and the number left is hard to find and doesn't show closeness to the limit.Pick: Move the figure to the Website tab. It already shows the per-upload size rule, so the running total answers how much is used in one place.
Options
  1. Move the combined figure, or the full breakdown, onto the Website tab next to the upload limit text.
  2. Add a percent-of-cap figure once the account's limit is known, reusing the existing limit lookup.
Smedium
OrganiserSign-up question answers after a decision
Half-bakedsignup
An organiser should be able to look up any participant's sign-up answers at any time.Answers are collected and returned by the API for every status, but the People screen only shows them while an application is pending. Once decided, nobody can see that person's answers again on the website.
Evidence
internal/handler/static/hack/screens/organiser-people.js:89 (answers rendered only in applicationCard), organiser-people.js:128 (pending = applications.filter(status==pending)), internal/handler/hack_teams.go:30-46 (listPeople explicitly omits answers/profile fields), internal/db/hack_registration.go:98-120 (ListRegistrationApplications returns answers for every status, proving the data survives), internal/handler/hack_administration.go:285 (participants.csv columns have no answers column)
Sign-up answers become invisible on the website once someone is decided, even though the data still exists and the API still returns it.Pick: Show answers on the person's row in People even after a decision, since the data already exists and the change is small.
Options
  1. Keep answers visible on the person's row in People, behind a details toggle, after a decision.
  2. Add the answers as extra CSV columns, the same way the demographic fields were added.
Smedium
OrganiserParticipants CSV columns
Half-bakedpeople
An export should include anything the organiser asked participants during sign-up.The export lists name, email, team, join date and demographic fields. It never includes the organiser's own sign-up question answers, even though those are event-specific.
Evidence
internal/handler/hack_administration.go:285 (participants.csv header), internal/db/hack_registration.go:11-20 (SignupAnswer type never touches this export)
The one export meant for taking data outside the product leaves out the thing most likely to be organiser-specific.Pick: Add the answers as trailing columns, the same way the demographic fields were appended, so existing imports keep working.
Options
  1. Add one column per sign-up question, or one joined answers column.
  2. Leave it as is, and say in the UI that answers must be read before a decision.
Smedium
OrganiserDeadline reminder before it passes
Half-bakedentries
With a working mail pipeline, an organiser would expect a reminder as a deadline approaches.No such reminder exists. The mail system only sends announcement deliveries and a one-time entry-received receipt, with no scheduled sweep before a deadline.
Evidence
internal/db/hack_content.go:104-125 (NextEventMail only knows 'announcement' and 'receipt' kinds), internal/handler/hack_content.go:310-364 (deliverContentMail switches only on those two kinds)
The organiser has to remember to post their own announcement. The platform does nothing automatic at the deadline besides freezing writes.Pick: Add the automatic reminder. It is cheap on the existing sweep and meets the standard of doing something at the deadline.
Options
  1. Add an automatic closing-soon reminder, reusing the existing per-minute mail sweep.
  2. Leave it to the organiser's own announcement, and document that clearly.
Mmedium
OrganiserView entries progress
Half-bakedentries
The Entries screen should show a count of complete entries and published sites.The Entries screen lists each team as complete or missing, and site live or not. It has no total count of complete entries or published sites.
Evidence
internal/handler/static/hack/screens/organiser-entries.js:35-65 (entryRow + paint -- no aggregate counts computed or rendered), docs/ux-atlas/features.json view-entries-progress description promises the N-of-M/sites-published summary that is absent from the code
An organiser scanning many teams has no at-a-glance readiness number and must count rows by hand.Pick: Add the header counts. The data is already on the page, so this is a few lines of arithmetic that gives organisers a number at a glance.
Options
  1. Add the two counts as a header line above the list, computed from the entries already loaded.
  2. Update the feature's own description to match reality, and leave the screen as is.
Smedium
OrganiserChoose score mode (raw vs normalised)
Half-bakedjudging
Locking judging should freeze every input that feeds the ranking, matching what the lock claims.The lock guards assignments and judges-per-team, but the score mode and two visibility flags save with no lock check at all. The screen only disables that control once the event is archived.
Evidence
internal/handler/hack_judging.go:401,428-450 (no lock check before the score_mode/public_scores/public_ranks UPDATE), internal/handler/static/hack/screens/organiser-results.js:87 ('${archived ? " disabled" : ""}' only)
After locking judging, an organiser can still flip which score decides rank, with nothing in the product flagging that this setting escaped the lock.Pick: Add the guard to score mode. It decides who wins, which is what locking is meant to stop.
Options
  1. Add the same lock guard to score mode, and leave the two visibility flags open since they are cosmetic.
  2. Change the lock's own description to say score mode stays changeable.
Smedium
OrganiserLock judging
Half-bakedjudging
Locking should freeze the rubric, assignments, conflicts and every judge's score, as its own text says.The rubric, conflicts, assignments, panels and scores are all blocked once judging is locked. Score mode and the two visibility flags are not blocked, which is the separate score-mode gap above.
Evidence
internal/handler/hack_judging.go:60-66 (writeIfJudgingLocked), used at lines 116-119 (rubric), 676,720,768,801 (conflicts), 1264/1330 (scores), organiser-judging.js:122 ('Locking stops every rubric, assignment or score change')
The lock's own claim is slightly wider than what it enforces, since score mode keeps changing after the lock is set.Pick: Fix the gap instead of the text. The current wording already matches what an organiser reasonably expects.
Options
  1. Fix the score mode gap, rather than rewriting the lock's text.
  2. Narrow the lock's text to say which fields freeze.
Smedium
OrganiserEvent purpose field
Half-bakedsetup
A purpose field the organiser fills in should shape something, like matching or guidance.Purpose is stored and editable in Settings, and shown only to the platform admin. It never appears on the public page, in matching, search or any listing.
Evidence
internal/handler/hack.go:551,601,719,882-883,1234-1239, internal/handler/static/hack/screens/organiser-settings.js:125, internal/handler/hack_admin.go:25-37, internal/handler/static/admin.html:1528
Purpose is collected and displayed, but nothing reads it except the admin's own abuse-monitoring list, which is not obvious from the organiser's side.Pick: Keep it admin-only, but tighten the help text to name the real reason instead of leaving the field looking unused.
Options
  1. Leave it as admin-only, but say so next to the field, such as helping watch for abuse.
  2. Give it a second use, showing it on the public page as an optional subtitle under About.
Slow
OrganiserExpected participants field
Half-bakedsetup
A number the organiser commits to should size something, like a capacity warning or a progress bar.The field is required at creation and editable later, but never compared against the live participant count anywhere, including the Overview snapshot.
Evidence
internal/handler/hack.go:552,605-606,876,1241-1246, internal/handler/static/hack/screens/organiser-settings.js:126, internal/handler/static/hack/screens/organiser-overview.js:119-123 (grid4 has no expected comparison), internal/handler/static/admin.html:1644
The number is collected as if it matters, but nothing in the product checks reality against it.Pick: Add it to Overview. It is cheap to add, and it matches the admin's own interest in whether events track their stated size.
Options
  1. Add it to the Overview snapshot once there is a count to compare against it.
  2. Drop the requirement at creation, since nothing consumes it yet.
Slow
OrganiserTeams CSV columns
Half-bakedteams
An export should match what the Teams screen shows, including track and lock state.The export lists only name, members, site and creation date. Track, admins and locked state all show in the Teams screen but none reach the CSV.
Evidence
internal/handler/hack_administration.go:315-318 (teams.csv header), internal/handler/hack_keys.go:358-365 (organiser team view includes track/locked/kept that the export omits)
An organiser exporting teams to plan judging panels by track has to go back to the website for that one column.Pick: Add the track and locked columns, plus the admin column. They are already loaded for the screen's own view, so the export only needs to read the same fields.
Options
  1. Add the track and locked columns, plus admin, to the teams CSV.
  2. Leave the CSV minimal, and point organisers at the Teams screen for the rest.
Slow
OrganiserCo-organiser invite link not viewable again
Half-bakedpeople
After creating an invite, an organiser should be able to see or confirm that link later.The link only exists for that page load. There is no way to fetch a pending invite again, so refreshing or leaving the page loses the URL.
Evidence
internal/handler/hack_administration.go:20-24 (only POST/DELETE routes for organiser-invite, no GET), internal/handler/static/hack/screens/organiser-people.js:63 (comment: 'the API has no GET for a pending invite'), internal/mcp/hack_organiser_tools.go:137-139 (same gap in the MCP tool set)
An organiser who copies the link wrong, or needs to resend it, has no way to retrieve it short of revoking the still-valid invite.Pick: Add the lightweight check saying an invite is pending and when it expires, so the organiser knows whether to revoke or recreate it.
Options
  1. Add a check that reports whether an invite is pending and when it expires, without showing the secret again.
  2. Document clearly that the link must be copied right away, or the invite must be recreated.
Slow
OrganiserCode of conduct re-acceptance after changes
Half-bakedsignup
A substantial change to the code of conduct should flag old acceptances as stale, or ask again.The conduct text can be edited any time with no restriction. Acceptance is a one-time timestamp written at join and never revisited when the text changes.
Evidence
internal/handler/hack.go:1131-1136 (PATCH accepts coc_text unconditionally), internal/db/hack_registration.go:79-96 (coc_accepted_at set once, at join, never updated on event changes)
A person's recorded acceptance can silently stop matching the text they would see if they read it again.Pick: Leave this as is for now. It is a real but small gap here, and the added complexity of versioning can wait.
Options
  1. Version the conduct text and show an updated-since-joining note on the next visit.
  2. Accept this as out of scope, since the conduct text works as guidance on this platform.
Mlow
OrganiserPer-team deadline extension, visible to the team
Half-bakedentries
A team with a longer deadline should be told about it, instead of discovering the later time by chance.The team's own screens correctly show their extended deadline wherever they look, but granting the extension doesn't send any email or notice.
Evidence
internal/handler/static/hack/screens/participant-entry.js:92, internal/handler/static/hack/screens/participant-home.js:148-149, internal/handler/static/hack/screens/organiser-entries.js:33,39,44-48 (organiser's own extension list)
Granting an extension doesn't send any email or notice, so the team only learns of it by opening the app and noticing the later time.Pick: Email the team and show a Home banner, using the mail path that already exists.
Options
  1. Email the team and show a Home banner when an extension is granted or cleared.
Slow
OrganiserEntries CSV export
Half-bakedentries
A CSV an organiser uses to check readiness should match what the web screen calls complete.The export lists team, title and links, but not the complete or missing columns the web screen computes from the same data.
Evidence
internal/handler/hack_administration.go:334-337 (CSV header/row has no complete/missing column), internal/handler/hack_entries.go:439-451 (entryCompleteness exists but is not plumbed into the CSV path)
The CSV and the web list show different views of the same completeness fact.Pick: Add the column. It reuses the same completeness function already in scope, one extra field per row.
Options
  1. Add a complete or missing column to the CSV, computed the same way the API does.
  2. Leave it as a raw export, and document that completeness is a web-only view.
Slow
OrganiserJudging dashboard
Half-bakedjudging
Everything the dashboard returns should be useful and shown somewhere.The dashboard always returns an empty tied-groups list, with a code comment admitting it is unfinished. No screen or tool reads or shows it.
Evidence
internal/handler/hack_judging.go:915-921, grep of internal/handler/static/hack/screens/*.js and internal/mcp/*.go for 'tied_groups' returns nothing
An always-empty field sits in the public API response, with a comment admitting it is unfinished.Pick: Remove it for now. A placeholder field with a stray comment is worse than no field, and tie information already exists on the Results screen.
Options
  1. Remove the field until it does something real.
  2. Finish it, computing and showing tied groups that need an organiser decision.
Slow
OrganiserLook tab (event colour and icon)
Half-bakedwebsite
Picking a colour and icon should give the event its own look everywhere the event appears.The colour only adds a thin line and the event mark. This is a known, filed issue.
Evidence
Linear SIM-353, internal/handler/static/hack/screens/organiser-event-page.js (Look tab), internal/handler/hack_colors.go
The Look tab barely changes how the event looks.Pick: Apply the colour across the public page, gallery and vote page with a live preview, as already planned.
Options
  1. Apply the colour to the public page, the gallery and the vote page, with a live preview.
  2. Rename the tab to colour and icon.
Mlow
OrganiserSponsor tiers
Unclearwebsite
Labelling a sponsor Gold versus Bronze should group or order them by tier on the page.Tier is a free-text label shown under the sponsor's name. Sponsors render in whatever order the organiser dragged them into, with no grouping by tier.
Evidence
internal/handler/static/hack-event.html:407-421 (no tier-based ordering, just .range over the stored order), internal/handler/static/hack/screens/organiser-event-page.js:565-566,641-642 (manual drag/arrow reorder is the only ordering mechanism)
An organiser setting tiers may expect Gold sponsors to lead visually, but today that needs manual dragging like any other order.Pick: Add one line of help text. It removes the confusion without changing behaviour.
Options
  1. Leave it as is, since manual order already lets an organiser put Gold first.
  2. Add a note in the Sponsors tab saying that dragging sets the order, and tier is only a label.
Slow
OrganiserList event in directory
Unclearsetup
An organiser looking for a public listing switch would check Settings first, where other visibility controls sit.The real on or off switch sits on the Results screen, tied to voting settings but kept as a separate save to avoid overwriting. Settings only shows a read-only line pointing to Results.
Evidence
internal/handler/static/hack/screens/organiser-results.js:11,75-76,306-310,383-427, internal/handler/hack_voting.go:161-180,356, internal/handler/static/hack/screens/organiser-settings.js:28-37,129-132
Placing the switch on Results avoids drift between two places, but it sits where intuition does not point.Pick: Leave it as is. The existing link already solves the real discoverability problem, and a third place to look would recreate the drift risk this design avoided.
Options
  1. Leave it as is, since Settings already links to Results and one source of truth holds up.
  2. Also show it, as a read-only link, on the Event page's Website tab.
Slow
OrganiserDownload all team sites archive
Unclearentries
This feature should sit on the Entries tab, as the product's own documentation says.The button works, and it sits on the Results screen, while the documentation names the Entries screen.
Evidence
internal/handler/static/hack/screens/organiser-results.js:9,438 (button lives here), internal/handler/hack_administration.go:30 (GET /export/projects.tar.gz), docs/ux-atlas/features.json download-all-team-sites-archive today_location says 'Manage > Entries tab'
This is a documentation drift. The feature works, only in a different place than the guide and a reasonable organiser would look.Pick: Add a second entry point on Entries, next to the CSV button, since organisers look there for bulk actions. Keep the Results one too.
Options
  1. Move the button, or add a second entry point, onto the Entries tab.
  2. Update the documentation to name the Results tab instead.
Slow
OrganiserChoose results visibility mode
Unclearresults
The organiser's chosen visibility should apply from the first time results go public.The full-ranking setting only exists after the first publish, and starts as winners-only. The selector stays disabled, with a hint to publish first, until then.
Evidence
internal/db/hack_judging.go:563-570 (UpsertEventResults inserts full_ranking FALSE), internal/handler/static/hack/screens/organiser-results.js:281-283
Wanting full ranking from the start still means publishing once as winners-only before switching and publishing again.Pick: Seed the setting from a pre-publish preference. It is a small change that removes a real, brief surprise for organisers who want full ranking from the start.
Options
  1. Let the organiser set visibility before any publish, and apply it to the first snapshot.
  2. Leave it as is, since the screen already explains the sequence with a hint.
Slow
OrganiserCreate event
Completesetup
Filling a short form should produce a draft event with a reserved address.Posting the create form makes a draft event with live address checking and a validated time zone and dates, then goes straight to Manage.
Evidence
internal/handler/static/hack/screens/organiser-create-event.js:1-91, internal/handler/hack.go:545-620,719-723, internal/handler/hack.go:2029-2037 (checkTimeZone)
NoneNone needed
OrganiserCheck event address availability
Completesetup
Typing an address should show whether it is free before the organiser submits.A live check updates the help text as the organiser types, showing available, taken or reserved, including for the auto-generated address from the title.
Evidence
internal/handler/static/hack/screens/organiser-create-event.js:29-45
NoneNone needed
OrganiserEdit organiser details
Completesetup
Name, organisation, contact email, purpose and expected participants should be editable after creation.Saving Settings updates all five fields with the same checks used at creation, at any stage, even after the event ends.
Evidence
internal/handler/hack.go:1058-1059,1234-1246, internal/handler/static/hack/screens/organiser-settings.js:121-127,178-198
NoneNone needed
OrganiserTime zone
Completesetup
Every deadline and schedule time should show in one time zone the organiser picks.The time zone is checked against the real list of zones and used for every deadline and schedule time. Changing it keeps each date's local clock time.
Evidence
internal/handler/hack.go:2029-2037, 1138-1158, internal/handler/static/hack/screens/organiser-event-page.js:291 ("Every deadline and schedule time shows in this zone")
NoneNone needed
OrganiserEvent page text fields
Completewebsite
Free text fields should show up on the public page.Text is edited on the Event page and shown on the public page and the judge's brief card. Sections hide or show depending on the event's stage.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:355-399, internal/handler/hack_eventpage.go:291-301, internal/handler/static/hack/screens/judge-rubric.js:34-36
NoneNone needed
OrganiserEvent colour
Completewebsite
Picking an accent colour, or leaving it automatic, should show on the public page.A colour picker saves right away and updates the preview, sidebar mark and public page together, falling back to an automatic colour drawn from the event address. A related open issue on the Look screen was not reproduced from the code and needs checking live.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:870-964, internal/handler/hack.go:792,850,1089-1094
NoneNone needed
OrganiserUpload or remove event icon
Completewebsite
Uploading a round icon should show it on the page, directory and join links.Uploading or removing the icon checks file type and size on both the browser and the server. It falls back to an initial, and the row is locked once the event is archived.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:873-924
NoneNone needed
OrganiserSwitch between built-in and custom website
Completewebsite
Toggling between the built-in page and an uploaded site should keep both without loss.Switching modes keeps the uploaded files for later use, and the server blocks custom mode unless a site already exists.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:994-1009, internal/handler/hack_websites.go:98-142
NoneNone needed
OrganiserUpload a custom event website (zip)
Completewebsite
Uploading a zip with an index page should make it live at the event address.Drag and drop or file picker upload works, with a confirm step the first time since it replaces a live page, and clear error text for a missing index page or a bad archive.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:1017-1056, internal/handler/hack_websites.go:144-189
NoneNone needed
OrganiserView website upload history (versions)
Completewebsite
An organiser should see earlier versions of their custom site.The version list shows each one's number, upload date and whether it is live. There is no way to revert to an older version, a choice confirmed in the code comments.
Evidence
internal/handler/hack_websites.go:61-83, internal/handler/static/hack/screens/organiser-event-page.js:987-993,1008 (R20 comment: switching to an older version isn't offered by the API)
NoneNone needed
OrganiserEvent website's own saved data
Completewebsite
A custom event website should save data the same way any Simple Host site can.The full key-value, SQLite and file backend is reachable at the website's own storage address. Reads stay open, writes block once archived, and there is no manage panel since the feature serves an AI app or API instead.
Evidence
internal/handler/hack_websites.go:37-59
NoneNone needed
OrganiserEvent website notifications
Completewebsite
An organiser should be notified when visitors save data or upload files on the custom website.Creating, editing, pausing, testing and rotating the notification secret all work end to end in Settings, with a delivery history. The product guide names the wrong screen for this card.
Evidence
internal/handler/notify_routes.go:28-34, internal/handler/static/hack/screens/organiser-settings.js:135-297
NoneNone needed
OrganiserSponsors (name, tier, link, logo)
Completewebsite
Adding sponsors with a logo and link should show them on the public page.Adding, editing and removing sponsors checks the logo file and the link address on both ends. Each sponsor renders with its logo, name, tier label and a website button.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:560-690, internal/handler/static/hack-event.html:407-421
NoneNone needed
OrganiserFAQ
Completewebsite
Adding question and answer pairs should show as a folded list on the public page.Adding, editing, removing and reordering all work. Answers show a short preview in the editor and start folded on the public page.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:753-820 (renderFaq)
NoneNone needed
OrganiserReorder or remove list rows
Completewebsite
Rows should be movable by drag or keyboard, and removable with a way to undo.Each list supports drag and drop, keyboard reordering, a row menu to move items, and removal with an undo option. Changes save right away.
Evidence
internal/handler/static/hack/screens/organiser-event-page.js:613-699 (sponsors, representative of the shared pattern), internal/handler/hack_content.go:111,150-191
NoneNone needed
OrganiserChange stage (moving back)
Completesetup
Moving the event between stages should have real effects, like setting deadlines and locking judging.Moving stage sets the deadline to now when entries close, and clears a passed deadline and extensions when reopening. It also locks judging on the move to Results, with its own confirm text for each move.
Evidence
internal/handler/hack.go:1371-1480, internal/handler/static/hack/screens/_orgA-util.js:60-110 (stagePicker)
NoneNone needed
OrganiserMove the event forward
Completesetup
One clear button should do the sensible next thing, matching what the API and AI apps say is next.The server works out the next step, and Overview turns it into one button with a tailored confirm and heads-up text. This replaced several competing buttons after an owner decision.
Evidence
internal/handler/static/hack/screens/organiser-overview.js:14-56,163-205, INTENT.md:1274-1280 (2026-10-31 decision)
NoneNone needed
OrganiserEnd the event (archive)
Completesetup
Ending an event should be a clear, final action that locks it for good.Archiving needs at least one participant, and an empty event is told to delete instead. A danger dialog explains the effect, and the action cannot be undone or reopened.
Evidence
internal/handler/hack.go:1395-1407, internal/handler/static/hack/screens/organiser-overview.js:51-56,139-158
NoneNone needed
OrganiserDelete event
Completesetup
Deleting an event should need extra confirmation once it has real people or has ended.Deleting requires typing the event address once it is archived or has any participants or judges, and cascades to sites, results, entries, scores and votes. The address stays reserved afterward unless nobody ever joined.
Evidence
internal/handler/hack.go:1576-1653, internal/db/hack.go:452-483 (DeleteEventAndAccount, name-reservation insert), internal/handler/static/hack/screens/organiser-settings.js:148-151,302-321, INTENT.md:627-636 (2026-10-05 decision)
NoneNone needed
OrganiserEvent stats (Overview snapshot)
Completesetup
An organiser should see participants, teams, judges and people without a team at a glance.Tiles for participants, teams, judges and people without a team appear on Overview. The judges tile is corrected on screen to count only judge-role people, since the server's count also includes judge-eligible organisers by design.
Evidence
internal/handler/static/hack/screens/organiser-overview.js:79-98,119-124
NoneNone needed
OrganiserOverview shows what to do next
Completesetup
Looking at Overview should make it obvious what the organiser should do right now.A next-step card names the one move in plain language with a one-line effect, and the snapshot, share and danger sections sit below it as secondary.
Evidence
internal/handler/static/hack/screens/organiser-overview.js:24-56,119-124
NoneNone needed
OrganiserOrganiser settings screen (full inventory)
Completesetup
One place should hold organiser details, applications, notifications and the destructive actions.Settings covers organiser details, an applications toggle with a pointer to where listing is controlled, notifications, and a danger zone for leaving or deleting, each gated by confirmation or event stage.
Evidence
internal/handler/static/hack/screens/organiser-settings.js:119-152
NoneNone needed
OrganiserReplay organiser walkthrough
Completesetup
An organiser should be able to reopen the first-time guided tour from Help.The Help menu links to Overview with a flag that forces the tour open again, even if dismissed before. A separate guard stops it reopening itself after an unrelated refresh.
Evidence
internal/handler/static/hack/screens/organiser-overview.js:6-10,118,123-124
NoneNone needed
OrganiserView as platform admin
Completesetup
A platform admin should be able to view any event without changing it, and that should be clear.A shared lock disables every control except a few explicitly marked live, such as copy buttons and filters. One consistent banner says the view is read-only, across every organiser screen.
Evidence
internal/handler/static/hack/screens/_orgA-util.js:34-56, internal/handler/static/hack/screens/organiser-announcements.js:56, internal/handler/hack.go:386,817
NoneNone needed
OrganiserRequire approval for join-link signups
Completesignup
A switch should make join-link sign-ups wait for an organiser's decision.The switch does that, and it is labelled correctly. Applications from the directory or event page always wait, regardless of this switch.
Evidence
internal/handler/hack_registration.go:65-115 (putRegistration), internal/handler/static/hack/screens/organiser-people.js:171
NoneNone needed
OrganiserAdmit everyone waiting when approval turns off
Completesignup
Turning approval off should offer to approve everyone waiting from the join link at once.Turning the switch off offers a three-way choice, approve all, leave pending or cancel. It never touches applications, which always need their own decision.
Evidence
internal/handler/hack_registration.go:101-109, internal/handler/static/hack/screens/organiser-people.js:339-378
NoneNone needed
OrganiserApplications on/off
Completesignup
A switch should turn the public apply flow on or off without touching the join link.Turning applications off hides the apply button on the directory and event page and blocks new applications. People already waiting stay, and the setting is worded clearly in Settings.
Evidence
internal/handler/static/hack/screens/organiser-settings.js:129-130,168-170, internal/handler/hack_apply.go (hackApplicationsOpenNow)
NoneNone needed
OrganiserFilter and sort waiting applications
Completesignup
Filter and sort the Applications list by source, age range, country, or date.Filtering and sorting happen in the browser over one data fetch. An AI app could filter the same list on its own.
Evidence
internal/handler/static/hack/screens/organiser-people.js:79,139-151
NoneNone needed
OrganiserJoin link and judge link controls
Completesignup
Copy a link to share. If it leaks, revoke it and get a new one.Each link can be previewed without changing anything, and copied in the browser. Regenerating a link kills the old one right away. The Overview screen shows both links.
Evidence
internal/handler/hack_administration.go (codes routes elsewhere), organiser Overview screen, features.json preview-join-link/regenerate-join-link entries
NoneNone needed
OrganiserRemove co-organiser
Completepeople
Revoke a co-organiser's access. The event's original creator is protected.Removes access, with the primary organiser protected and the check enforced on the server.
Evidence
internal/handler/hack_administration.go:204-236
NoneNone needed
OrganiserLast organiser leaving or handing over
Completepeople
A creator leaving must hand off to another organiser. An organiser leaving alone must end or delete the event.Covers six cases, with the same locking order throughout. A creator must pick a successor, and the last organiser must end or delete the event. Judged scores stay kept either way.
Evidence
internal/handler/hack_leave.go:28-55 (leaveCaseFor), hack_leave.go:202-226 (successors/close_options preview), hack_leave.go:343-394 (write-time enforcement)
NoneNone needed
OrganiserList and filter people
Completepeople
See everyone in the event, filterable by role.Works as described. Filtering by role happens in the browser over one data fetch.
Evidence
internal/handler/static/hack/screens/organiser-people.js:62,129,158,182
NoneNone needed
OrganiserRemove person from event
Completepeople
Removes someone, including their team membership, from the event. The team's code rotates so they can't rejoin on the old link.Removes the person and rotates the team code, with deadlock-safe locking and clear in-dialog text about rejoining.
Evidence
internal/handler/hack_teams.go:58-123, internal/handler/static/hack/screens/organiser-people.js:216-232
NoneNone needed
OrganiserTurn off someone's publishing key
Completepeople
Revoke another member's personal API key for publishing.Revoking the key happens right away. The person must separately request a new one, the same way as other actions in this area.
Evidence
internal/handler/static/hack/screens/organiser-people.js:111,233-246
NoneNone needed
OrganiserMax team size
Completeteams
One cap, from 1 to 50, applies everywhere a team is built or joined.Enforced at create, join, move and fill-teams time. Editable under Teams and Settings.
Evidence
internal/handler/static/hack/screens/organiser-teams.js:149-164, internal/handler/hack_teams.go (TeamSizeMax checks throughout)
NoneNone needed
OrganiserRename, move, remove, or delete a team
Completeteams
An organiser can rename a team or move a member onto it. They can also remove a member or delete the team outright.All four work as described, with the team link rotating on membership change and clear confirm text before delete.
Evidence
internal/handler/static/hack/screens/organiser-team-detail.js:62-263, internal/handler/hack_teams.go:471-692
NoneNone needed
OrganiserAdd, remove, and choose a track
Completeteams
An organiser sets up tracks, each with a challenge and prize, and a team's pick shows wherever it appears.Tracks show in the Teams list, the team-finding board, the link preview, the judging feed, and per-track winners. Removing a track warns how many teams would be left without one.
Evidence
internal/handler/hack_registration.go:178-264 (CRUD), internal/handler/static/hack/screens/organiser-teams.js:127-143 (Tracks tab), internal/handler/hack_finding.go:79-106 (track shown on open-teams board), internal/handler/hack_team_links.go:74-77 (track shown on team-link preview)
NoneNone needed
OrganiserTeam finding on or off
Completeteam-finding
One switch turns off Ask to join and Find people, including the looking list. Links and codes keep working either way.Works as described, and the Settings screen text says so plainly.
Evidence
internal/handler/hack_finding.go:40-54 (findingAccess), internal/handler/static/hack/screens/organiser-teams.js:148
NoneNone needed
OrganiserFill teams preview and apply
Completeteam-finding
Preview a plan for placing unteamed people, adjust the team size, then commit it.Works as described. Changing the size re-previews under a guard token, and a note flags any membership shift between preview and apply.
Evidence
internal/handler/hack_finding.go:412-507 (fillTeams), internal/handler/static/hack/screens/organiser-teams.js:185-299 (fillTeamsDialog)
NoneNone needed
OrganiserAccept co-organiser invite
Completepeople
A one-time link adds a co-organiser once. It blocks double use and use after the event closes.It re-checks the invite under lock, and rejects an existing member or a taken-down or archived event. The invite is deleted on use, so it can't be reused.
Evidence
internal/handler/hack_administration.go:99-202
NoneNone needed
OrganiserSet or clear the submission deadline
Completeentries
After the deadline, entries and sites lock automatically.Once the deadline passes or judging starts, the server locks entries and sites and pins the site version. The organiser can set or clear the deadline, and participants see the close time on their screens.
Evidence
internal/db/hack_sites.go:225-245 (Frozen/WriteRefusal), internal/db/hack_sites.go:304-312 (PinDueTeams), internal/handler/static/hack/screens/organiser-entries.js:57-63, internal/handler/static/hack/screens/participant-entry.js:92-94
NoneNone needed
OrganiserGallery open toggle
Completeentries
Controls whether published team sites appear in the public gallery, and gates voting.The gallery shows a site once it's published, not taken down, and ready, past the draft stage. Voting setup refuses to turn on while the gallery is closed, so both toggles are enforced on the server.
Evidence
internal/handler/hack_wire.go:61-63, internal/handler/hack_voting.go:14,125
NoneNone needed
OrganiserEntry edit conflict resolution
Completeentries
Teammates editing together keep each other's changes safe.A stale save is rejected and shown the newer entry instead. A side-by-side dialog lets the teammate keep their version or take the other, comparing only the fields that differ.
Evidence
internal/handler/hack_entries.go:120-141,320-332 (errEntryChanged -> 409 entry_changed), internal/handler/static/hack/screens/participant-entry.js:251-310 (showConflict)
NoneNone needed
OrganiserPost announcement
Completeannouncements
Post a message that shows on the public page and in the app.Posting shows the message right away on the public page and in the app. The public feed always includes announcements regardless of gallery or stage, and every signed-in role sees the same feed.
Evidence
internal/handler/hack_content.go:200-227 (postAnnouncement), internal/handler/hack_public_json.go:91-99 (always-public announcements), internal/handler/static/hack/screens/organiser-announcements.js:54
NoneNone needed
OrganiserEmail participants toggle
Completeannouncements
Checking the box triggers a real email send to participants.Email goes out through Resend's API, not the blocked port 25, with one queued delivery per participant with an email. A background sweep sends the queued mail, and the checkbox disables itself when no participant has an email.
Evidence
internal/email/resend.go:17,120-129,147-200 (HTTPS POST to api.resend.com, not local SMTP), internal/handler/hack_content.go:227-241 (CanSendNotice guard, email_unavailable if not configured), internal/db/hack_content.go:67-96 (CreateEventAnnouncement delivery queueing), internal/handler/hack_content.go:310-364 (deliverContentMail actually sends), internal/handler/static/hack/screens/organiser-announcements.js:62,89-99
NoneNone needed
OrganiserEdit announcement
Completeannouncements
Editing changes the text without sending new email, and the screen says so.Editing only updates the title and body, and never queues new mail. The edit dialog tells the organiser saving won't email anyone again, and that is accurate.
Evidence
internal/handler/hack_content.go:366,392-411 (UPDATE path, no delivery insert), internal/handler/static/hack/screens/organiser-announcements.js:110 (copy stating no re-send)
NoneNone needed
OrganiserDelete announcement
Completeannouncements
Removing an announcement takes it off the page and the app. Email already sent stays sent.Deleting also cancels any mail still queued for that announcement. The confirm dialog correctly warns that emails already sent can't be recalled.
Evidence
db/schema.sql:1169-1176 (ON DELETE CASCADE), internal/handler/hack_content.go:407-409 (DELETE FROM event_announcements), internal/handler/static/hack/screens/organiser-announcements.js:136
NoneNone needed
OrganiserEntry first-submission receipt email
Completeentries
A participant should get some acknowledgement that their entry counted.A receipt queues once per team, the first time their entry is complete. It sends through the same email pipeline as announcements, with its own entry received subject and text.
Evidence
internal/handler/hack_content.go:280-291 (queueReceipt), internal/db/hack_content.go:98-103 (QueueEntryReceipt, ON CONFLICT DO NOTHING so only once), internal/handler/hack_content.go:337-340 (receipt subject/body), internal/handler/hack_content.go:310-364 (actual send path)
NoneNone needed
OrganiserDefine rubric criteria and weights
Completejudging
Each criterion has a name and a description. It also has a weight and a point scale, which decide the score.Saving a rubric checks the criteria count and that weights sum to 100, with points running 1 to 10. Those saved rows feed the scoring math.
Evidence
internal/handler/hack_judging.go:95-220 (putRubric, validateRubric), internal/handler/hack_judging_math.go:78-106 (weights/maxes used in computeResultsWithOptions)
NoneNone needed
OrganiserConfirm score deletion on rubric change
Completejudging
Removing a criterion or cutting its points asks for confirmation if scores would be lost, naming the count.Saving a rubric change counts the scores it would delete per criterion, and blocks the save without confirmation. The confirm dialog shows that count to the organiser.
Evidence
internal/handler/hack_judging.go:184-202, internal/handler/static/hack/screens/organiser-judging.js:558-563
NoneNone needed
OrganiserReorder rubric criteria
Completejudging
Criteria can move up or down, and the order sticks for judges.Up and down buttons reorder criteria, and saving the rubric keeps that order for judges.
Evidence
internal/handler/static/hack/screens/organiser-judging.js:213-218, internal/db/hack_judging.go:56-60
NoneNone needed
OrganiserOpen, automatic, manual, and panel assignment
Completejudging
Each mode controls who can score which team.All four modes control the judge queue and score-write checks, and are enforced again when results are computed.
Evidence
internal/db/hack_judging_options.go:71-113 (EligibleJudgeTeams), internal/db/hack_judging.go:335-345 (scoreEligiblePredicate), internal/handler/hack_judging.go:1096-1110 (judgeQueue filtering)
NoneNone needed
OrganiserGenerate automatic judge assignments
Completejudging
Automatic mode spreads judges fairly and reports any team that came up short.Automatic assignment balances load, giving judges to the least-loaded teams first, and skips conflicted pairs. It reports any team left under target, and the screen names them.
Evidence
internal/handler/hack_judging.go:558-616, internal/handler/static/hack/screens/organiser-judging.js:313-332
NoneNone needed
OrganiserManual assignment grid
Completejudging
Pick which judge scores which team. Conflicted pairs can't be ticked.The grid greys out conflicted judge-team pairs in the browser, and the server also rejects them on save.
Evidence
internal/handler/static/hack/screens/organiser-judging-assignments.js:88-96, internal/handler/hack_judging_options.go:129-139
NoneNone needed
OrganiserDeclare or remove a judge conflict
Completejudging
Marking a conflict excludes that judge's scores and keeps them off future assignments for that team.A conflict excludes that judge's scores from coverage and totals, and both automatic and manual assignment skip the pair. Panel mode keeps a conflicted judge on the track panel by design, dropping only the conflicted team from their list.
Evidence
internal/db/hack_judging.go:335-345, internal/handler/hack_judging.go:530-539 (generateAssignments), internal/handler/hack_judging_options.go:129-139 (putManualAssignments), internal/handler/static/hack/screens/organiser-judging-assignments.js:52-54 (panel conflict note)
NoneNone needed
OrganiserChoose tie-break criterion
Completejudging
Picking a criterion breaks ties in the standings.Tied teams are sorted first by the chosen criterion's average, then by judge-majority wins between pairs. Only a true remaining tie is left for the organiser to break at publish.
Evidence
internal/handler/hack_judging_math.go:162-224
NoneNone needed
OrganiserShow scores or ranks publicly
Completejudging
Separate toggles control whether the public page shows scores and whether it shows rank order. Neither clashes with the ranking choice.Which teams appear, and whether scores or ranks show on each, are controlled by separate settings. When ranks are off, every view falls back to alphabetical order so no rank leaks.
Evidence
internal/handler/hack_judging.go:1690-1738, internal/handler/static/hack/screens/organiser-results.js:88
NoneNone needed
OrganiserUnlock judging requires a reason
Completejudging
Unlocking needs a reason, and it's logged.Unlocking needs a short reason, up to 300 characters, and logs who did it on the server.
Evidence
internal/handler/hack_judging.go:1033-1056
NoneNone needed
OrganiserDelete a departed judge's scores
Completejudging
Removing a former judge's scores stops them counting, with a clear warning about when published results change.Deleting needs the event name typed to confirm, the same pattern as deleting an event, and is blocked while locked. It re-checks the caller is still an organiser, and the dialog says published results only change when published again.
Evidence
internal/handler/hack_judging.go:928-1005, internal/handler/static/hack/screens/organiser-judging.js:515-521
NoneNone needed
OrganiserPublish results and preview standings
Completeresults
Publishing takes a snapshot, and publishing again replaces it cleanly. The organiser is told when live standings have changed since.Publishing takes a snapshot, and the public page never recomputes it live. The organiser screen compares live totals to that snapshot and flags a note when scores have changed since publishing.
Evidence
internal/handler/hack_judging.go:1512-1576, internal/handler/static/hack/screens/organiser-results.js:122-142
NoneNone needed
OrganiserOverride a tied rank on publish
Completeresults
An organiser can reorder only the teams still tied after the tie-break. The rest of the ranking stays untouched.Overriding only accepts teams still in an unresolved tie, and every team in that group must get its own rank. Ranks are rebuilt around the chosen order, and untouched groups stay tied.
Evidence
internal/handler/hack_judging.go:1441-1510
NoneNone needed
OrganiserScores and results CSV exports
Completeresults
Scores CSV has every judge's raw per-criterion scores and comments. Results CSV matches what is published.The scores export includes every judge's raw score, criterion, and comment. The results export matches the published snapshot, falling back to a live calculation only if nothing has published yet.
Evidence
internal/handler/hack_judging.go:1804-1954
NoneNone needed
OrganiserPer-track winners and standings
Completeresults
Teams competing within a track get their own rank and winner flag, separate from the overall ranking.Each track gets its own rank and winner flag, separate from the overall rank. Both appear in the published snapshot, the CSV exports, the public results page, and the participant's own results.
Evidence
internal/handler/hack_judging_math.go:229-249, internal/handler/hack_judging.go:1578-1605,1931-1952
NoneNone needed
OrganiserEnable people's choice voting
Completevoting
Turning on voting requires the gallery to already be open.Turning voting on is blocked if the gallery isn't open yet. The Results screen shows this as a note linking to the Event page's Look section.
Evidence
internal/handler/hack_voting.go:125-128, internal/handler/static/hack/screens/organiser-results.js:333-353
NoneNone needed
OrganiserVoting open and close window
Completevoting
The window is enforced on the server and shown to voters in the event's own time zone.Voting status comes from comparing the open and close times to now, shown in the event's own time zone. The server refuses a vote once closed no matter what the screen shows.
Evidence
internal/handler/hack_voting.go:13-30, internal/handler/static/hack-voting.html:258-261
NoneNone needed
OrganiserVoting eligibility settings
Completevoting
Narrowing eligibility removes votes that no longer qualify, and tells the organiser the count first.Tightening eligibility needs confirmation once any votes would no longer qualify. That count shows in the confirm dialog on both the app screen and a separate settings page for voting.
Evidence
internal/handler/hack_voting.go:129-145, internal/handler/static/hack-voting.html:358-365
NoneNone needed
ParticipantNotify on team request or invite
Half-bakedteam-finding
Some signal should tell a person when a team wants them or answers their request.There's no email and no in-app signal, such as a push or badge, for this. A person only finds out by opening Home or Team. Home flags a pending invite as the top next step, but nothing nudges someone who hasn't opened it.
Evidence
grep of hack_finding.go/hack_teams.go for mail/notify (no hits, only internal/handler/hack_cleanup.go:14,29 uses the mailer, for event-removal warnings), internal/handler/static/hack/screens/participant-home.js:14-24,47-70 (comment explaining this is pure client-side polling with no server signal), internal/handler/static/hack/screens/participant-team.js (invites/requests rendered only from a fresh GET on page load)
A team admin could miss a join request for days unless they open Team. The same gap hits someone who was invited.Pick: Add a nav badge first, from data already fetched. Then email the person, using the mail path announcements already use.
Options
  1. Send a short email for a new request or invite, and when either is accepted or declined.
  2. Add an unread badge on the Team nav item, using data the Home screen already fetches.
Mhigh
ParticipantParent agreement for under-18 applicants
Half-bakedsignup
Picking under 18 should collect a parent or guardian's agreement. At least it should record that the applicant was told to get one.Selecting under 18 shows a sentence pointing to the terms page. There's no consent checkbox and no field for a parent or guardian's name or email. Nothing is recorded beyond the age range, and an AI app sees the same sentence and records nothing too.
Evidence
internal/handler/static/hack/screens/public-apply.js:233-238,257-261 (the note, no consent input), internal/db/hack_registration.go:43-48 (ApplicantProfile has only City/Country/AgeRange/Gender -- no consent field), internal/mcp/hack_member_tools.go:46 (advisory text only)
Nothing records that a parent or guardian ever agreed to anything. The only safeguard is a sentence the applicant can click past.Pick: Add the checkbox. It is a small form change, and it turns an unenforceable claim into an auditable record, which matters most here in sign-up.
Options
  1. Add a checkbox for a parent or guardian's agreement, recorded alongside the age range.
  2. Keep it informational, and word it as a plain reminder to find a parent or guardian.
Shigh
ParticipantVideo link
Half-bakedentries
A link the organiser, judges, voters and public can click to watch the project demo.The link is saved and checked as a real web address, and shown to judges and the organiser. It never appears on the public gallery, the voting page, or the team's own read-only view.
Evidence
internal/handler/hack_entries.go:78,106-112 (field+validation), internal/handler/static/hack/screens/judge-scoring.js:129 (judge view), internal/handler/static/hack/screens/organiser-entry-detail.js:68 (organiser view), internal/handler/hack_eventpage.go:91-95 (hackGalleryCard struct has no video/code field), internal/handler/static/hack-event.html:440-451 (sec-sites template renders only Title/Tagline/Team/Shot), internal/handler/static/hack-voting.html:292-298 (voting card renders only o.title/o.tagline/o.url)
Teams supply a video, but only judges and organisers see it. Voters and the public never see it.Pick: Put it in the entry summary card shown in the gallery, voting, and results, and let organisers accept video or a working link as one rule.
Options
  1. Show it on the gallery card, the vote page, and the results row.
  2. Keep it visible to judges only.
Mhigh
ParticipantRubric visible before submitting an entry
Half-bakedjudging
A team should be able to see the rubric before or while writing their entry.Only organisers and judges can read the rubric today. No participant screen fetches it, and trying to read it fails.
Evidence
internal/handler/hack_judging.go:96 (loadMember(..., "organiser", "judge")), grep of internal/handler/static/hack/screens/participant-*.js shows no "rubric" reference
Teams write their entry blind to the judging criteria, though the rubric already exists and is harmless to read.Pick: Let participants read the rubric, the same data judges already see, since the only blocker is the role check.
Options
  1. Let participants read the rubric once it exists, with no stage gate.
  2. Show a short rubric summary on the entry-edit screen, pulled from the same data.
Shigh
ParticipantHome as a step-by-step path
Half-bakedhome
Home should walk a participant from joining a team through finishing the entry. It should show a live countdown to the deadline.Home shows one next-step card that says Keep building, with a fixed closing date. It never fetches the entry, so it can't say what's missing. There's no checklist and no live countdown.
Evidence
internal/handler/static/hack/screens/participant-home.js:143-148, 216-221, 232 (no /entry fetch, no setInterval anywhere in participant screens)
The participant gets a generic nudge, missing a clear list of what's done and left.Pick: Build the four-step checklist with live ticks and a countdown using the team's extended deadline when it has one.
Options
  1. A four-step checklist on Home, team, summary, video or site, and submitted, with ticks from real data and a live countdown.
  2. Keep one card, but make its text depend on what's missing.
Mhigh
ParticipantGuided publishing of team website
Half-bakedteam site
Clear steps should connect an AI app or upload a zip file, then show connected and published states.The Website screen shows a connector address to copy, saying you don't need a key, plus a zip upload. There are no per-app steps and no Connected state, and a Live pill appears only after publishing.
Evidence
internal/handler/static/hack/screens/participant-website.js:52-84
A non-technical participant gets an address and must guess what to do with it.Pick: Add inline per-app steps with Connected and Published states on the same card, since publishing is the participant's main moment.
Options
  1. Add inline steps per AI app, taken from the Get started page, plus Connected and Published states with the live link.
  2. Link out to the Get started page.
Mhigh
ParticipantOptional demographic fields in Apply
Half-bakedsignup
Fields an organiser could use to understand attendee mix, or to help place teams more fairly.Fields are collected, shown per applicant while pending with an under-18 pill, and filterable in Applications. They export to the participants CSV but are never shown as stats or used by Fill teams, and disappear from the site once the applicant is decided.
Evidence
internal/db/hack_finding.go:211-224 (PlanFillTeams ignores every demographic column), internal/handler/hack_teams.go:42-45 (comment: profile fields 'only in the Applications list and the participants CSV'), grep of organiser-overview.js/organiser-results.js for age_range/gender/city/country (no hits)
These fields only appear on the Applications screen and in the CSV export. Fill teams never uses them to balance a team.Pick: Add the small counts summary. It's cheap since the data is already loaded, and it's the one thing an organiser can't get today without exporting.
Options
  1. Add a small counts summary for age range and other demographics, on the Applications or Overview screen.
  2. Leave it CSV-only, and say so plainly in the help text.
Smedium
ParticipantCode link
Half-bakedentries
A link to the project's source code visible to anyone judging or browsing the project.Like the video link, it's saved and checked, and shown only to judges and the organiser. It's missing from the public gallery, the voting page, and CSV exports outside the organiser's own.
Evidence
internal/handler/hack_entries.go:113-118, internal/handler/static/hack/screens/judge-scoring.js:130, internal/handler/static/hack/screens/organiser-entry-detail.js:69, internal/handler/hack_eventpage.go:91-95, internal/handler/static/hack-event.html:440-451
Teams are asked for it, but only judges and organisers see it. Most no-code and idea events have no use for it.Pick: Tie it to the coding preset. Hide it for no-code and idea events, and show it on the public card when it is filled.
Options
  1. Make it required only under the coding preset and hidden otherwise.
  2. Show it publicly on every card.
Smedium
ParticipantIn-app announcements display
Half-bakedannouncements
Participants notice when a new announcement is posted.Announcements show on their own screen, and the latest two also show on Home. There's no unread indicator anywhere, and no push or browser notification. A participant notices only if they check one of these screens or opted into organiser email.
Evidence
internal/handler/static/hack/nav.js:17-23,83-88 (announcements nav entries, no badge rule, vs. people's badge rule at nav.js:27-29), internal/handler/static/hack/screens/participant-home.js:72-83 (shows latest 2, no unread state tracked), internal/handler/static/hack/screens/participant-announcements.js:1-20 (plain list, no read/unread tracking)
Showing it in the app doesn't mean a participant notices it, unless they check or get the organiser's email.Pick: Add the unread badge. It's a client-only comparison against data already fetched, with no server change, and it adds a nudge where none exists today.
Options
  1. Add a simple unread badge on the Announcements nav item, based on the last time a participant looked.
  2. Leave as is, and rely on the organiser's optional email for anything urgent.
Smedium
ParticipantRemoval notice after leaving a team
Half-bakedteam-finding
Someone taken off a team by an admin or an organiser understands why, wherever they next look.Removal sets a notice, but it's only shown on Home's hero card. The Team screen, where someone removed needs to look next, never shows it.
Evidence
internal/handler/hack_teams.go:627 and :678 (notice set on admin-removal and team delete), internal/db/hack.go:1320 (notice set on organiser removePerson), internal/handler/hack.go:969-970 (me.team_removal_notice in the event view), internal/handler/static/hack/screens/participant-home.js:167-168 (only consumer), absence confirmed by grep of participant-team.js for team_removal_notice (no hits)
A participant landing on Team after removal sees a generic no-team screen. No explanation shows, though one already exists on the server.Pick: Show it on both screens. Team is the page someone acts on next, and the notice is already fetched with the same event data.
Options
  1. Also show the notice at the top of the Team screen's no-team state.
  2. Leave it Home-only since Home is the default landing screen.
Slow
ParticipantEntry submitted state
Unclearentries
A clear moment when a participant submits their entry, through an action or a confirmation.There's no submit action, the entry autosaves on every edit and upload. It only moves from editable to read-only once frozen, taken down, or ended. The screen never uses the words submit or draft.
Evidence
internal/handler/static/hack/screens/participant-entry.js:164-194 (Save button just PUTs changed fields, no distinct submit endpoint), internal/handler/hack_entries.go:357-397 (ownEntryJSON has only editable/refusal, no draft/submitted status)
A first-time participant can't confirm judges will see this until they reopen the entry. The only hint is the deadline countdown.Pick: Keep the always-live draft, since it matches the keep-building-until-deadline model, and a submit step would need its own confirmation screen.
Options
  1. Leave it as always-live autosave, matching the fast-build intent, and make the deadline countdown more prominent.
  2. Add a Mark as ready checkbox, for the team's own peace of mind, that blocks nothing.
Slow
ParticipantList self as looking for a team
Completeteam-finding
A no-team participant can list themselves with a short intro, visible to teams browsing.Works as named. Visible in Find people and in the organiser's Solo tab.
Evidence
internal/handler/hack_finding.go:276-321 (setLooking), internal/handler/static/hack/screens/participant-team.js:157-159
NoneNone needed
ParticipantLooking for note on teams
Completeteam-finding
A team can post a short note about who they want, shown to people browsing.Works. Editable by any admin, shown on the open-teams board and the team link preview.
Evidence
internal/handler/hack_teams_admin.go:127-224 (patchTeam), internal/handler/static/hack/screens/participant-team.js:148
NoneNone needed
ParticipantBrowse the open-teams board
Completeteam-finding
See which teams are taking people, and which people are looking for one, as a participant or an organiser.One data source serves both views. Participants see it as the Ask-to-join list, and organisers see it in the Teams and Solo tabs.
Evidence
internal/handler/hack_finding.go:56-209 (listOpenTeams), internal/handler/static/hack/screens/organiser-teams.js:56-66,82-91 (lookingByUser cross-reference)
NoneNone needed
ParticipantAsk, invite, accept, decline, withdraw, or cancel
Completeteam-finding
A full lifecycle covers asking, inviting, accepting, declining, withdrawing a request, and cancelling an invite. Accepting one clears every other pending offer for that person.Works as described, with accepting one offer clearing every other pending one on the server.
Evidence
internal/handler/hack_finding.go:322-410 (createTeamRequest/resolveTeamRequest), internal/handler/static/hack/screens/participant-team.js:140-176 (ask panel), db.NewTeamRequest/ResolveTeamRequest
NoneNone needed
ParticipantTeam admin roles and last-admin protection
Completeteams
Any admin can promote or demote another member. A team is never left with zero admins.Works as described, including a step-down option for acting on yourself, and a last-admin refusal.
Evidence
internal/handler/hack_teams_admin.go:287-356, internal/handler/static/hack/screens/participant-team.js:239-247,353-368
NoneNone needed
ParticipantLock team
Completeteams
Stops new joiners through any route, link, code, request, or invite, and clears outstanding ones.Works the same from both the admin's toggle and the organiser's equivalent. Organiser placement still works on a locked team, and the screen explains that correctly.
Evidence
internal/handler/hack_teams_admin.go:226-285,419-460, internal/handler/static/hack/screens/participant-team.js:218-222,378-386
NoneNone needed
ParticipantTeam link and new team link
Completeteams
A shareable link or code that joins the team right away. A way to end the old one and make a new one.Works as named for the participant and the organiser, and rotating the link kills the old one right away. The preview page handles each status cleanly, covering locked, full, closed, and already on another team.
Evidence
internal/handler/hack_teams_admin.go:358-413,509-548, internal/handler/static/hack/screens/public-team-link.js
NoneNone needed
ParticipantJoin by code or start a team
Completeteams
Paste a code or link to join right away. Otherwise start a new team and become its admin.Both options work as named, with sensible handling for slug and name collisions. A deadline check also means a new team never starts out already frozen.
Evidence
internal/handler/hack_teams.go:201-337,339-427
NoneNone needed
ParticipantLeave team, leave event, or withdraw
Completeteams
Leaving a team or event should do what it says, with clear warnings about loss. This matters most for the last member of a team.Every leave case gets its own handling, covering the participant, applicant, judge, co-organiser, creator, and last organiser. A preview endpoint keeps the confirm dialog accurate, and withdrawing an application reuses the leave code with different copy.
Evidence
internal/handler/hack_leave.go:12-253 (previewLeaveEvent, six cases), internal/handler/static/hack/screens/participant-team.js:292-306,394-404 (leave team), participant-home.js:97-120 (leave event danger zone)
NoneNone needed
ParticipantCode of conduct acceptance at join
Completesignup
A checkbox gates joining, and acceptance is recorded with a time stamp.Every join path asks for acceptance, including the join link, applying, the organiser invite, and the judge invite. The team link skips it since it never leaves the event, and the acceptance time appears in the CSV.
Evidence
internal/handler/static/hack/screens/public-join.js:93,97, public-apply.js:244-246, public-organiser-invite.js:33,44, internal/db/hack_registration.go:88-96
NoneNone needed
ParticipantEntry screenshot
Completeentries
An image of the project should show up wherever the entry or team site appears.The screenshot uploads with type and size limits, up to 2MB and 8000 pixels. It reaches the participant, the judges, the organiser's entry view, and the public gallery card.
Evidence
internal/handler/hack_entries.go:505-539 (validation), internal/handler/static/hack-event.html:446 (public gallery img), internal/handler/static/hack/screens/judge-scoring.js:156-158,211-213, internal/db/hack_gallery.go:34-53 (galleryHasShot)
NoneNone needed
ParticipantTitle, tagline, and description fields
Completeentries
Core text should reach judges and the public.The title and tagline reach the public gallery and the voting card. Judges also see the description, and the gallery card is kept small by design.
Evidence
internal/handler/static/hack-event.html:447, internal/handler/static/hack/screens/judge-scoring.js:127-128,164-165, internal/handler/hack_eventpage.go:91-95
NoneNone needed
ParticipantRequired field labels on entry form
Completeentries
A participant should see which fields the organiser marked as required while filling in the entry.Each required field's label gets the word required added, pulled straight from the server's list. A pill at the top shows what is missing, or says complete.
Evidence
internal/handler/static/hack/screens/participant-entry.js:96-115 (fieldHTML req labels), participant-entry.js:88-90 (pillHTML)
NoneNone needed
ParticipantGet, replace, and disable publishing key
Completeteam-site
A participant should get a key and replace it, or turn it off.The key is revealed once when first created. Replacing and turning it off both need a confirm step, matching the danger-zone pattern used elsewhere.
Evidence
internal/handler/static/hack/screens/participant-website.js:86-98,151-180
NoneNone needed
ParticipantTeam site status
Completeteam-site
The team site should show a clear state. That means being set up, live, frozen, or taken down with a reason.Being set up, live, frozen, and taken down all render distinctly, each with its own actions.
Evidence
internal/handler/static/hack/screens/participant-website.js:52-71
NoneNone needed
ParticipantTeam site notifications
Completeteam-site
A team should get notified when visitors save data or upload files on their own site.Notifications can be added, paused, resumed, tested, and have their secret rotated. Each event also shows its own delivery history with real result codes, covering DNS, TLS, timeout, and refused.
Evidence
internal/handler/static/hack/screens/participant-website.js:10-14,241-300,305-403
NoneNone needed
ParticipantDownload own team site archive
Completeteam-site
A team should be able to download its own published files and saved data.A plain button does this, and it stays disabled until a site exists.
Evidence
internal/handler/static/hack/screens/participant-website.js:113,184-185
NoneNone needed
ParticipantView own team result
Completeresults
A team should see its rank, score, any track prize, and judges' feedback once results publish. This holds regardless of the public page.The team's own results always include the total, raw and normalised scores, rank, track, and track win. This shows no matter the public score or rank toggles, and the screen shows prize text and anonymised comments.
Evidence
internal/handler/hack_judging.go:1741-1802, internal/handler/static/hack/screens/participant-results.js:60,77-78,99
NoneNone needed
ParticipantView own current vote
Completevoting
A participant should see who they currently voted for while voting stays open.The vote page shows your pick while voting is open, and shows who you voted for once it closes.
Evidence
internal/handler/hack_voting.go:248-294, internal/handler/static/hack-voting.html:328-329
NoneNone needed
JudgeEntry summary card for judges
Half-bakedentries and judging
A judge should read one short fixed card per team. It should cover the problem, solution, audience, track, tools and AI, and what works today.The entry form has a title, tagline, and free text up to 5000 characters. It also has a video link, a code link, and a screenshot. The judge screen shows that text, then buttons for video, code, and the site, which all leave the page.
Evidence
internal/handler/static/hack/screens/participant-entry.js:99-110, judge-scoring.js:129-150, internal/db/hack_entries.go
Nothing makes teams describe their project the same way, so judges end up comparing essays of different shapes.Pick: Add the fixed fields as a card judges see first, before the video and site. Keep it all on one screen with the rubric and a fast save.
Options
  1. Add fixed short fields to the entry, covering problem, solution, audience, track, tools and AI, and current state.
  2. Keep the free text box, but add a template hint inside it.
Mhigh
JudgeRubric weight visible while scoring
Unclearjudging
A judge scoring a weighted rubric should see which criteria count for more.The rubric and scoring screens show each criterion's max points but never its weight. The weighting that drives the final ranking stays invisible to the person scoring.
Evidence
internal/handler/static/hack/screens/judge-rubric.js:30 (no c.weight reference), internal/handler/static/hack/screens/judge-scoring.js:174-187 (critRow never reads crit.weight)
A judge scoring two criteria cannot see that one counts for 40 percent and the other for 10 percent.Pick: Show the weight next to each criterion, reusing the weight field the rubric endpoint already returns.
Options
  1. Add the weight percentage next to each criterion's point pill on both screens.
  2. Leave it organiser-only, since scoring is the judge's job.
Smedium
JudgeRubric criterion description while scoring
Completejudging
A judge should see what each criterion means while scoring.Both scoring screens show the criterion's description under its name.
Evidence
internal/handler/static/hack/screens/judge-rubric.js:30, internal/handler/static/hack/screens/judge-scoring.js:178,186
NoneNone needed
JudgeDeclare or remove a conflict
Completejudging
A judge should flag a team they know, through the web app. They should also be able to undo it later.The scoring screen has an I know someone on this team button. The queue screen has a Teams I know tab with an undo button that calls the conflicts endpoint directly.
Evidence
internal/handler/static/hack/screens/judge-scoring.js:326-357, internal/handler/static/hack/screens/judge-queue.js:116-118,152-164
NoneNone needed
JudgeJudges told when scoring locks
Completejudging
A judge who can no longer score should be told why in plain words.The home, queue, and scoring screens show a clear Scoring is locked banner. The scoring screen then switches to a read-only view of saved scores instead of showing an error.
Evidence
internal/handler/static/hack/screens/judge-home.js:97-103, internal/handler/static/hack/screens/judge-queue.js:78-80, internal/handler/static/hack/screens/judge-scoring.js:104,160-161,178
NoneNone needed
JudgeEntry comments and who sees them
Completejudging
A judge's written feedback should reach the team. The judge should know beforehand whether their name goes with it.The comment box is labelled Not shown with your name. The team sees one anonymised comment per judge, while the organiser sees the name in the scores export.
Evidence
internal/handler/static/hack/screens/judge-scoring.js:201-202, internal/db/hack_judging.go:585-612 (TeamComments), internal/handler/static/hack/screens/participant-results.js:99 ('Judges' anonymous comments'), internal/handler/hack_judging.go:1829 (CSV 'comment' column with judge name)
NoneNone needed
JudgeSave and next while scoring
Completejudging
Moving to the next team should save the current one first and never lose a change.Score writes are chained in order so quick clicks apply correctly. Save and next, and also Previous, wait for the pending comment and the full score write before moving on.
Evidence
internal/handler/static/hack/screens/judge-scoring.js:242-256,359-376
NoneNone needed
JudgeOpen the entry site while scoring
Completejudging
Opening the team's site should show the version judges should review, the one frozen at submission.The link prefers a pinned snapshot of the site over the always-live version, matching the intended design.
Evidence
internal/handler/static/hack/screens/_judge-util.js:32-39
NoneNone needed
JudgeJudge walkthroughs across every screen
Completejudging
A first-time judge should get a guided tour that can be replayed later.The home and scoring screens start the tour on a judge's first real visit. A Help-menu link can also force a replay anytime.
Evidence
internal/handler/static/hack/screens/judge-home.js:112-124, internal/handler/static/hack/screens/judge-scoring.js:378-385
NoneNone needed
Public pagesPublic results missing site and video
Half-bakedresults
Once results are out, visitors should see what each winner built, along with its site and video.The results list shows rank, team name, track, prize, and a site link only. The gallery shows the title and tagline with a screenshot. The video and code links never reach the public.
Evidence
internal/handler/hack_eventpage.go:66-82 hackResultsRow, hack_eventpage.go:91-95 hackGalleryCard, hack-event.html:131-160
Results name the winners, and visitors still cannot see what those winners made, the part people share.Pick: Show the full card with site and video on each result row. Filter it by the existing winners-only or full-ranking setting.
Options
  1. Show the entry card with its site and video under each result row, following the current visibility setting.
  2. Link each result row to the gallery card only.
Mhigh
Public pagesCode of conduct on event page
Half-bakedevent-page
A visitor checking legitimacy should be able to read the code of conduct from the event page itself.The code of conduct shows on the join and apply pages. It also shows on the judge-invite page, after sign-in. It is never part of the public event page's own data or sections.
Evidence
internal/handler/hack_eventpage.go (no CodeOfConduct field in hackEventView or assembleHackEventPage), internal/handler/static/hack-event.html (no 'conduct' string in the whole template), docs/ux-atlas/spec.json public-event-page feature_ideas item 5 ('The code of conduct on the public page. It is shown on the join page but not in the event page data')
A visitor deciding whether an event is safe cannot read its code of conduct without starting to join first.Pick: Add the section, since it is a small change that serves the parent and sponsor audience the atlas names.
Options
  1. Add a code of conduct section to the event page, reusing text shown on the join and apply pages.
  2. Leave it as is, since the organiser's own About or Rules text often covers similar ground.
Slow
Public pagesPast events sorted the wrong way
Half-bakeddirectory
A Past section should show the most recently finished events first, the way any past list reads.Every group, including Past, sorts by start date ascending, with nulls last and then slug. As more past events run, the oldest event ever held stays at the top while the newest sinks lower.
Evidence
internal/db/hack_voting.go:208-212 (ORDER BY starts_at NULLS LAST, slug), internal/handler/hack_voting.go:356-382 (no re-sort before grouping), internal/handler/static/hack-directory.html:198-206 (client appends rows in server order, no re-sort)
Past is sorted in the wrong direction for how anyone browses past events.Pick: Reverse the Past group's sort order, since it is a small change, and the problem grows over time.
Options
  1. Sort the Past group by start date descending, and keep Now and Upcoming ascending.
  2. Leave it as is, since too few events exist yet for this to matter.
Slow
Public pagesHow people's choice relates to judges
Unclearvoting
A visitor should understand how the people's choice result relates to the judges' result.People's choice and the judges' result sit in separate sections on the public event page. They are built independently, with no cross reference between them. Nothing flags when the people's choice winner differs from the judges' top pick.
Evidence
internal/handler/hack_eventpage.go:126-187,430-432,645-670
A visitor seeing both sections may read them as competing answers to who won, especially when they disagree.Pick: Add a short line near each section naming judges or voters, since it fixes confusion with no logic change.
Options
  1. Add one line near each section naming who chose it, judges or voters.
  2. Leave it as is, since the section headings already imply the difference.
Slow
Public pagesTeam counts shown during Open stage
Unclearevent-page
A visible count should read as healthy information for every visitor.The header shows the team and participant count once either exists, even during Open. One live event showed 1 team and 1 participant while still accepting applications.
Evidence
internal/handler/hack_eventpage.go:108-123 (CountLine), live curl https://simple-hack.app/e/hackherthon-2026 on 2026-11-01, docs/ux-atlas/spec.json public-event-page open_questions item 4 ('Should the team and participant counts show during Open? ... reassuring for a big event and off-putting for a new one with 3 sign-ups')
The atlas already flags this as unresolved, and a brand-new event with one signup advertises its small size.Pick: Hide the count below a small threshold, since it is cheap and removes the downside without hurting bigger events.
Options
  1. Hide the count line until a small threshold is crossed, such as 10 participants.
  2. Keep it as is, since hiding a true number could read as evasive.
Slow
Public pagesDirectory search or filtering
Uncleardirectory
A grown directory with many events should normally offer search or a filter.No search or filter exists yet, and the atlas marks this as a future scale concern.
Evidence
docs/ux-atlas/spec.json public-directory decisions: 'Add search or filtering to the directory? Not in this pass.'
This is deferred on purpose, and it will become a real gap once the directory holds many more events.Pick: Leave it as is, since this is correctly triaged as a future scale problem.
Options
  1. Leave it as is until the directory grows past a few dozen events.
  2. Add a simple title or tagline text filter now, as cheap insurance.
Slow
Public pagesPublic judge invite link
Completejudging
A public invite link should preview the event and show the code of conduct. It should also join cleanly either way.The page handles invalid or expired codes and stages that cannot be joined, plus an already-a-member shortcut. Signed-out visitors get a sign-in-first path, and the code of conduct shows before accepting.
Evidence
internal/handler/static/hack/screens/public-judge.js:1-113
NoneNone needed
Public pagesPublic results page visibility rules
Completeresults
The page should show only what's enabled. That means winners-only or full, with or without scores and ranks, before and after publish.Results stay unpublished until a snapshot exists. After that, the settings apply as set, and ranks fall back to alphabetical order whenever they are hidden.
Evidence
internal/handler/hack_judging.go:1638-1738
NoneNone needed
Public pagesCast or change a vote
Completevoting
One vote per person should be allowed, changeable, with ineligibility shown upfront, and self-votes blocked.Voting replaces any earlier vote, so there is one row per voter. Organiser, admin, and self-votes all get rejected, and the vote page shows the reason before anyone tries.
Evidence
internal/handler/hack_voting.go:296-353,248-294
NoneNone needed
Public pagesView final vote ranking
Completevoting
Once voting closes, anyone should see which teams got the most votes.The ranking, team name and vote count, appears once voting closes, and the page shows it under Final votes.
Evidence
internal/handler/hack_voting.go:216-244, internal/handler/static/hack-voting.html:330-339
NoneNone needed
Public pagesOne action per event stage
Completeevent-page
The event page should show one clear next action matching the event's current stage.Draft shows a quiet not-open-yet card, and Open shows Apply or the join-link card. Building, Closed and Judging all show See team sites, while Results and Ended show the results list.
Evidence
internal/handler/static/hack-event.html:159-174, internal/handler/hack_eventpage.go:523-645 (buildHackStageCard), live curl https://simple-hack.app/e/hackherthon-2026 on 2026-11-01
NoneNone needed
Public pagesStatic content sections render correctly
Completeevent-page
Organiser-written text and fields should render as written and reorder by stage. They should also collapse once results are in.Checked in code and live, About, Prizes, Schedule, Rules, and Sponsors all rendered correctly on a real event. Sections with no content, such as FAQ, Tracks, and Announcements, were omitted along with their nav chip.
Evidence
internal/handler/static/hack-event.html:337-452 (sec-about through sec-sites templates), live curl https://simple-hack.app/e/hackherthon-2026
NoneNone needed
Public pagesTaken-down and not-found event pages
Completeevent-page
A deleted or taken-down event should say so plainly, with no leftover branding and a way out.Both states render a plain page with no event colour or icon, and show the admin's reason when given. A Find another hackathon link appears too, with correct noindex and 410 handling.
Evidence
internal/handler/static/hack-event.html:34-95, internal/handler/hack_eventpage.go:261 (writeHackEventNotFound)
NoneNone needed
Public pagesApply to an event without a link
Completeevent-page
Someone without a join link should apply from the event page. They should see the questions and code of conduct, then the decision later.The apply flow shows a summary before sign-in, then the full form, including the under-18 guardian note. Every outcome, pending, accepted, not accepted, applications off, or signup over, gets its own screen.
Evidence
internal/handler/static/hack/screens/public-apply.js:150-166, docs/ux-atlas/spec.json public-apply section
NoneNone needed
Public pagesDirectory grouped listing with Apply
Completedirectory
Anyone should browse public events grouped by timing, with an Apply button shown only when applications are open.A live check confirmed two running events both returned an apply link from the directory API. The directory page shows Apply only when applications are open and a link exists, matching the spec.
Evidence
internal/handler/hack_voting.go:356-382 (getDirectory), internal/handler/static/hack-directory.html:60-100, live curl https://simple-hack.app/v1/hack/directory on 2026-11-01
NoneNone needed
Public pagesPublic voting page for people's choice
Completevoting
Anyone with the link should see the teams and vote once. They can change their vote and see their current pick while voting stays open.The vote panel shows team cards and a sign-in prompt for signed-out visitors. It also shows the voter's own current vote, and a message when voting is closed or empty.
Evidence
internal/handler/static/hack-voting.html:14-39, docs/ux-atlas/spec.json public-vote section
NoneNone needed
Public pagesReport a page footer link
Completeevent-page
A visible Report a page link should go somewhere and do something real.The report form and its handler both work, sharing Simple Host's own moderation pipeline.
Evidence
internal/handler/ui.go:202-203
NoneNone needed
AI appsMCP App screens exist for two roles
Half-bakedai-app tools
An AI client with MCP Apps should show a rich screen for every role, the way the website does.Only two MCP App screens exist, one for judges and one for organisers. The organiser one still skips teams, entries, results, and the event page, and no participant app exists at all. The code's own comments call the rest a later phase.
Evidence
internal/mcp/hack_apps.go:28-36 ('The participant resource and the rest of the organiser surface (teams, entries, results, event page) are later phases'), internal/mcp/hack_apps_organiser.go:11-16, PARITY.md line 49
Plain tool replies are all a participant gets, with no rich screen. An organiser does get one, but only for half the job.Pick: Keep the current plan in PARITY.md as is, since this is tracked, phased work.
Options
  1. Build the remaining organiser phases, then a participant app, in the order PARITY.md already tracks.
  2. Leave participant and the rest of organiser as plain-tool only, since the parity decision is about function alone.
Llow
AI appsDashboard rows for unselected teams
Half-bakedai-app tools
Every row in a connected app's sites dashboard should work the same way the selected team's row does.A team site other than the one selected doesn't show a working dashboard action. The same is true for an event website with no custom page. Those rows say Select in chat for dashboard, or show nothing. Switching teams still means going back to chat.
Evidence
internal/mcp/apps/hack-sites.js:8-18 (list, label text), hack-sites.js:40-42 (canDashboard)
A screen shows a row with nothing to click, and selecting a team only happens back in the chat.Pick: Leave it as is for now. Keeping team switching out of the frame looks like a security choice, worth the owner confirming.
Options
  1. Add a Select this team button inside the frame that calls the select-team tool directly.
  2. Leave it as is, since the code notes this keeps team switching out of the frame on purpose.
Mlow
AI appsTheme setting has no web control
Half-bakedaccount
A setting an AI app can change should also be visible on the website, or not exist at all.An AI app can set theme to system, light, or dark, and the server saves it. The website's Account page has no theme control, and the product stays light-only by design. So the setting changes nothing a person can see.
Evidence
internal/mcp/hack_web_tools.go:186-210 (hack_set_preferences), internal/handler/static/hack/screens/account.js (full file read, no theme control), docs/ux-atlas/features.json id 'set-theme-preference' ('not surfaced as a visible control in this UI today')
The setting only works from an AI app. It has no match on the website and no visible effect.Pick: Remove the dead fields rather than build a web control for a setting the product does not use yet.
Options
  1. Remove the theme fields from the preference tools until the product offers a dark mode.
  2. Add a matching toggle to the Account page, so the setting behaves the same on every screen.
Slow
AI appsAccount edits missing from AI app
Half-bakedaccount
An account action on the website should also work from an AI app, per the 2026-10-27 decision.Display name is only settable through the join-time tools. Nothing lets an AI app change it, change the sign-in email, or link or unlink Google. Deleting the account is also website-only.
Evidence
internal/mcp/hack_member_tools.go:44-70 (display_name only at join), grep '"/v1/me"' internal/mcp/*.go (GET only, no PATCH/DELETE), internal/handler/static/hack/screens/account.js:14,151-166 (name form, PATCH /v1/me)
A participant renaming themselves, or an organiser doing account housekeeping, must use the website instead.Pick: Add display-name editing only, and leave the rest website-only since those are identity-sensitive.
Options
  1. Add a small set-my-profile tool for the low-risk edits, such as display name.
  2. Leave identity-sensitive actions, email change, Google linking, and account deletion, website-only by design.
Slow
AI appsWebhook setup missing from AI app
Half-bakedai-app tools
Subscribing a webhook to a site should work the same from the website and from an AI app.The AI app can only list and remove notifications, while create, pause, test, and rotate stay website only.
Evidence
internal/mcp/notification_tools.go:45,98,119-135 (only list_notifications and remove_notification)
An organiser or team working only from an AI app cannot set up a notification.Pick: Add the missing tools, since the 2026-10-27 decision says every step should work from an AI app.
Options
  1. Add create, pause, and rotate tools to match the website.
  2. Note in the tool description that setup stays on the website.
Slow
AI appsPlain tool parity across every role
Completeai-app tools
Every organiser, participant, and judge step should work fully from an AI app too.Each organiser action the MCP App views front also has its own plain tool that works the same everywhere. The organiser, member, web, and results tool files cover roughly 90 hack tools across create, read, update, and delete.
Evidence
internal/mcp/hack_apps_organiser.go:19-24 and 48, internal/mcp/hack_organiser_tools.go and hack_member_tools.go tool name lists (grepped, ~90 tools total)
NoneNone needed
AI appsPrivacy-shielded twins for app calls
Completeai-app tools
Data an MCP App screen loads for itself should not leak into the model's own context.Every read the judge or organiser app makes for itself has a shielded twin tool. That twin sends a short sentence and small counts to the model, keeping the real payload inside the app.
Evidence
internal/mcp/hack_app_only_tools.go:1-56
NoneNone needed
AI appsCSV and archive exports from AI apps
Completeai-app tools
An export request from an AI app should return something the person can use right away.Participant, team, and entry exports return CSV text directly in the tool result. Archive exports instead return a short-lived download link, since the files are too large to inline.
Evidence
internal/mcp/hack_organiser_tools.go:160-168 and 217-225, internal/handler/hack_exportlink.go:1-80
NoneNone needed
AI appsTeam finding tools match the website
Completeai-app tools
Finding a team or listing openings should work the same from an AI app as from the website.The member tools cover listing open teams and asking to join, plus responding to requests and withdrawing one. They also cover setting looking status and inviting someone, matching the owner's decision for full parity.
Evidence
internal/mcp/hack_member_tools.go tool list (grepped), INTENT.md line 238
NoneNone needed
AI appsWatch-page prompts match live tools
Completeai-app tools
The copy-paste prompts under each film should work against the real connector and demo event.The organiser prompt chains naturally onto creating an event and setting its content. The judge and participant prompts route through demo links that track whichever event the weekly reset currently has live.
Evidence
internal/handler/static/hack-watch.html:110-162, internal/handler/hack_watch.go:21-66, live curl https://simple-hack.app/v1/hack/directory on 2026-11-01 vs 2026-11-02
NoneNone needed
EveryoneWalkthrough seen-state differs by tour
Unclearwalkthroughs
A first-time user would assume a walkthrough stays dismissed the same way for every role.The organiser and judge home tours use a server preference, so they stay dismissed on a new device. The scoring, participant, and team tours use local storage instead. They reappear on a new device or after storage clears.
Evidence
internal/handler/static/hack/tour.js:144-166, internal/handler/static/hack/tours.js:9-13, 96-97, 118, 143
The code's own comments explain this trade-off as a known, accepted choice. A participant switching devices sees a tour an organiser does not.Pick: Leave it as is, since the code already explains the trade-off and the visible cost stays small.
Options
  1. Add the missing preference fields and move every tour onto the server.
  2. Leave it as is, since the three local-only tours are low stakes and already documented.
Slow
EveryoneRole films at the watch page
Completewalkthroughs
Each 30-second film should describe steps that exist in today's product.The organiser, judge, and participant films each describe a real flow. Each one matches the current tool set and the demo's join and judge links.
Evidence
internal/handler/static/hack-watch.html:91-164
NoneNone needed
EveryoneGuided tours stay current
Completewalkthroughs
The in-app walkthroughs should point at real nav items and describe the screens as they are today.The tours match the latest redesign, covering the new next-step button and the renamed Overview and Home screens. The team tour was rewritten for the team-joining layout, with every step targeting a live, stage-gated selector.
Evidence
internal/handler/static/hack/tours.js:1-151 (in-line comments document each 2026-10-30/31 correction)
NoneNone needed
EveryoneReplay walkthrough from the Help menu
Completewalkthroughs
Replaying a walkthrough should reopen the right tour on the right screen for the person's role and state.The app picks the right section per role, always Overview for organisers. Judges get Home or Scoring depending on whether scoring is open, and a pending participant sees no Replay link.
Evidence
internal/handler/static/hack/shell.js:162-184
NoneNone needed
EveryoneAccount screen controls all work
Completeaccount
Every control on the Account page should save, confirm, and reflect the saved state on reload.Name, email, Google linking, sign-in alerts, key rotation, sign-out, and account deletion all call real endpoints. Each shows a live status message and the right disabled state while in flight.
Evidence
internal/handler/static/hack/screens/account.js (full file read, lines 13-300)
NoneNone needed
EveryoneSame stage shown to every role
Completeshell
A participant or judge should see the same stage as the organiser, in identical words.The status bar shows the same stage pill and timeline on every role's home screen. Judges get one extra pill for scoring state, dropped once the event ends.
Evidence
internal/handler/static/hack/shell.js:182-200
NoneNone needed
EveryoneNext action shown per event row
Completeaccount
Each event row should state the real next step for that role and stage.The next-action text only states what the list's own fields can support. The code's own comments record cases where an earlier version guessed wrong and was corrected to neutral copy.
Evidence
internal/handler/static/hack/screens/landing-your-events.js:23-62
NoneNone needed