Inspiration
Getting a project ready and actually submitting it are different jobs. A checked checklist can still conceal placeholder links, missing evidence or a forgotten final submission action.
What it does
Submission Desk gives independent hackathon builders a local workspace for multiple entries, deadlines with explicit time zones, requirements and official source links, evidence notes/files, repository/video links, submission copy and receipts.
Packet audit flags local completeness gaps even after every requirement is checked. Manual artifact access reviews remember the exact URL and time inspected. Editing that link makes the prior review stale. JSON backups preserve attachment bytes; Markdown exports create a portable handoff. Actual submission is recorded separately and manually. The app never sends an entry or certifies organizer acceptance.
Demonstration
The 37-second demo follows one synthetic packet whose requirements are checked but whose saved video review covers an earlier URL. Enlarged app views show the stale-review warning, a staged manual review tied to the replacement URL, and the separate organizer-confirmation record. It combines explanatory graphics with edited screenshots of actual app states and locally synthesized narration. The example does not send a contest entry or verify website access automatically.
How it was built and development chronology
Dependency-free JavaScript, HTML/CSS and a small Node.js loopback server. No paid API, runtime model, account integration or cloud storage.
The original prototype was built during the submission period before Devpost Learn Skill Pack use. The pack was subsequently read and applied to documented scope, PRD, spec, the exact-URL-review increment, regression testing and shipping preparation. The earlier prototype is preserved in Git, with source hashes. User-delegated autonomous work adapted the usual flipped-interaction interviews; docs/WORKFLOW.md discloses this rather than claiming the unmodified curriculum was completed. Required planning files are under devpost/. Organizer eligibility review remains authoritative.
Challenges and validation
Verification needs the identity of what was checked: an old note must not silently cover a changed link. Fourteen domain/server tests and fifteen browser checks passed, including stale-review detection after reload, backup restoration, literal HTML rendering, rejected imports, byte-identical attachment download and mobile overflow. Fresh-checkout tests passed. Browser checks observed no page errors or external requests.
Limits and next steps
The audit checks recorded data, not website permissions or legal eligibility. Reviews and receipts are self-reported. Exact URL matching does not detect remote content changes. Local browser storage is unencrypted, quota-limited and not synchronized across tabs. Independent user feedback and measured usefulness are next; no time savings, revenue or novelty is established.
This description and implementation were prepared with AI assistance.