Work · Archived
GNVTech
GNVTech was a platform where organizations posted their problems as briefs for student teams to take on. Teams applied and submitted solutions, and sponsors funded the work. I co-founded it through Lyceum LLC and worked on its product direction, interface and full-stack implementation.
The front end was built with React and Vite, and Supabase handled the backend: PostgreSQL with row-level security, database functions, Edge Functions and storage. Because briefs, engagements, submissions, organizations, careers and notifications were connected, a product change rarely stayed on a single page. An AI coding agent wrote much of the code: Claude authored most of the repository’s non-merge commits through pull requests on my account.
A backend alignment pass from March 9, 2026 gives a good example of what that work involved.
Old structures behind a newer interface
By then, the product’s routes were simpler. The sponsor page was down to a single inquiry form, while the application page was only for Hot Seat founder applications. The old support route redirected to the sponsor page, and an earlier sponsorship configurator and its pledge tables were no longer in use.
Removing those structures would have meant taking on a separate cleanup job. This pass was about aligning the current workflow, so it documented them as dormant and focused on two mismatches.
The first was in engagement_apply, the function behind a team’s application to a brief. It checked for active even though the current product marked available briefs as open, so the fix changed the check to open.
The second mismatch was about visibility: a brief could be open, but it wasn’t supposed to be public until a sponsor had funded it.
Putting the rule in the read policy
The migration replaced the public-read policy for briefs so that a brief is publicly readable only when its status is open, closed or archived and its funding timestamp is set. With the database enforcing that rule, pages don’t have to remember to hide unfunded briefs.
That narrower public access didn’t change what internal users could reach. The administrators’ policy stayed as it was, and sponsors and organizations still had access through separate database functions.
Alongside those fixes, the pass standardized the source value recorded for sponsor inquiries and added an administrator email for Hot Seat applications. It also documented the dormant intake structures in a migration.
What was left to do
The handoff written that day lists these changes as implemented, with the three migrations still to be applied to the live database. It also calls for confirmation that the application function works with open briefs, that unfunded briefs are excluded, and that the email sends. The handoff notes that the SQL files are historical and the live database may differ. I can describe what was implemented, but I can’t confirm whether the hosted checks were ever run.
The last commit in the repository is dated April 1, 2026. A public edition of the source can show how the briefs, roles and policies fit together using fictional organizations and briefs; it doesn’t need real applicants, sponsor contacts or production credentials to do that.
Source: github.com/gavinjudd/gnvtech-public (MIT)