Piecu Procentu Ordenis 
The annual awards platform for Latvian hip-hop — designed, built, and operated end to end for the 5% Akadēmija community.
Piecu Procentu Ordenis — “the Five Percent Order” — is the annual, community-voted award of Latvian hip-hop, run by and for the 5% Akadēmija Discord community.
For its first editions it lived in Google Forms: manual deduplication, manual tallies, no memory between years. The community needed something no off-the-shelf poll tool does — an electorate defined by live Discord membership. You sign in with Discord; you can nominate and vote only while you are a member of the server, re-verified in the background. The winners are revealed live at the annual ceremony, category by category, and every edition is preserved in a public archive.
The award came before me; the platform didn’t — I built and operate all of it: backend, frontend, admin, the design overhaul, and the box it runs on.
The next edition is assembled: categories, deadlines, rules.
Members submit entries through type-adapted forms; duplicates are caught on the way in.
Moderators curate the ballot — approve, reject with reasons, reorder.
One final ballot per member per category — single pick or a capped multi-pick.
Reveals happen live at the ceremony; each writes an immutable result snapshot.
The edition freezes at its yearly URL, joining every prior year.
A scheduler advances phases automatically when deadlines pass — a state machine with transition guards, not a checklist for an admin at 02:00.
These panels are re-created in HTML/CSS for this page, faithful to production — the Latvian strings and the 2025 results are the real thing.
Real 2025 result, 5% ALBUMS (757 votes, 21 nominations): winner — Ods, “Tavai Zināšanai Man Viss ir Labi”, 160 votes (21% share, +65 margin); then Wiesulis “500 mezgli” 95, galeniex “Ambrāža” 76, Prospekti “BIĻETE UZ VIENU GALU” 69, MAUZOLEJU MUUZIKA “DEMONU DIENAS 5” 57.
Discord is the identity provider and the membership gate. A four-branch account-matching ladder handles OAuth edge cases; a bot re-verifies stale memberships every 24h — daily batch plus lazy per-request refresh — and treats 200 / 404 / 5xx distinctly, so someone who leaves the server loses the ballot without ever seeing a login screen.
Nomination search runs through a MetadataResolver
interface with per-category resolvers — Spotify track, album,
artist; YouTube video — so forms and dedup stay provider-agnostic.
Spotify’s bearer token is cached for 59 minutes of its 60-minute
life. A YouTube search costs 100 quota units, so results are
enriched with one batched 1-unit call instead of per-video lookups.
When a provider dies or the quota burns out, the UI collapses to a
URL-paste fallback and nominations keep flowing.
Read paths are cache-aside on Redis with versioned keys: invalidation is a single counter increment fired by model observers — no key scans, no wildcard deletes, a one-hour safety TTL as the net. External API responses cache 24h for real hits, 10 minutes for empty results, and errors are never cached — a momentary Spotify outage can’t freeze “no results” for a day.
Fuzzy dedup runs in Postgres — pg_trgm trigram similarity over unaccent-normalized text (Edavārdi ≈ Edavardi) on a GIN index, one query. A soft threshold powers the live “did you mean” hint; a hard threshold blocks the submit. The public hint endpoint only ever surfaces approved entries, so anonymous probes can’t read the pending queue.
Ballot submission takes a Postgres advisory lock per user and category, re-checks everything inside it — phase, ballot size, nomination validity, already-voted — and backs it with a unique index. Votes denormalize category and cycle so tallies are one indexed aggregation; reveals snapshot results into an immutable table read by the archive.
Text nominations auto-fill page titles from pasted URLs — a classic SSRF hole, closed: private, loopback, and cloud-metadata ranges blocked, DNS rebinding checked by resolving before fetching, every redirect hop re-validated, all on a 4-second / 4-redirect / 512 KB budget.
449 Pest test cases — OAuth flows, cache invalidation, dedup behavior against a real Postgres with pg_trgm, voting guards, admin authorization — running in CI on every push. Production is six Docker services behind Caddy with Cloudflare-locked ingress, nightly rotated backups, and opcache-safe deploys.
THE PLATFORM · 6 SERVICES · 449 TESTS · ONE BOX
